Submitted by izoox on Fri, 02/17/2012 - 11:09
I am having some domains with email not being delivered. The maillog says it was sent to procmail and the procmail log reports:
Dest:/etc/webmin/virtual-server/clam-wrapper.pl /usr/bin/clamdscan Mode:None
But the message never gets there.
Status:
Closed (fixed)
Comments
Submitted by JamieCameron on Fri, 02/17/2012 - 15:00 Comment #1
Does turning off virus scanning for this domain fix the problem?
Submitted by izoox on Fri, 02/17/2012 - 15:46 Comment #2
No, when I disable virtus scanning for that domain nothing is delivered and the procmail log reports:
Dest: Mode:None
Submitted by izoox on Fri, 02/17/2012 - 15:54 Comment #3
It's actually only one domain and it was definitely working up until 4 days ago.
Submitted by JamieCameron on Sat, 02/18/2012 - 00:39 Comment #4
It could be some error in the domain's procmail config file. You can force this to be re-generated by disabling spam and virus filtering for the domain (on the Edit Virtual Server page), then re-enabling them again.
Submitted by izoox on Sat, 02/18/2012 - 00:58 Comment #5
I tried that already. Doesn't change things.
Submitted by JamieCameron on Sat, 02/18/2012 - 12:09 Comment #6
Could you find the domain's unique ID with the command
virtualmin list-domains --domain example.com --id-only, and then post the file under/etc/webmin/virtual-server/procmailwith that name?Submitted by izoox on Sat, 02/18/2012 - 12:15 Comment #7
DROPPRIVS=yes:0cw
| /etc/webmin/virtual-server/clam-wrapper.pl /usr/bin/clamdscan
VIRUSMODE=1
:0e
/dev/null
VIRUSMODE=0
:0fw
| /usr/bin/spamc
SPAMMODE=1
:0
* ^X-Spam-Status: Yes
$HOME/Maildir/.spam/
SPAMMODE=0
Submitted by JamieCameron on Sat, 02/18/2012 - 21:04 Comment #8
That all looks fine ..
Could you post all the lines that get logged to
/var/log/procmail.logwhen email is sent to this domain?Submitted by izoox on Mon, 02/20/2012 - 10:37 Comment #9
I figured it out. Sorry to be a bother.
Submitted by JamieCameron on Mon, 02/20/2012 - 14:05 Comment #10
What was the cause?
Submitted by izoox on Mon, 02/20/2012 - 15:36 Comment #11
It actually ended up being a quota issue. WHMCS assigned the wrong plan... I didn't check that first because of how the customer explained the issue happening. And then I saw the weird entries in the logs... so, definitely sorry for wasting your time.
Submitted by JamieCameron on Mon, 02/20/2012 - 16:16 Comment #12
Ok, that would explain it ..
Submitted by Issues on Mon, 03/05/2012 - 16:18 Comment #13
Automatically closed -- issue fixed for 2 weeks with no activity.