Mail delivery problem - spamassassin, disk quota

Hi Andreychek,

Thank you for the quick reply.

I can see the mail in the procmail log like this:

Time:1367297196 From:illetekigazolas@allamkincstar.gov.hu To:USERNAME@DOMAIN User:USERNAME.DOMAIN Size:50418 Dest:/etc/webmin/virtual-server/clam-wrapper.pl /usr/bin/clamdscan Mode:None procmail: Quota exceeded while writing "/home/DOMAIN/homes/USERNAME/Maildir/tmp/1367297615.453_0.vm.rewaresoft.hu" procmail: Quota exceeded while writing "/home/DOMAIN/homes/USERNAME/Maildir/tmp/1367297615.453_1.vm.rewaresoft.hu" From illetekigazolas@allamkincstar.gov.hu Tue Apr 30 06:53:20 2013 Subject: =?ISO-8859-2?Q?Illet=E9kbefizet=E9si_igazol=E1s?= Folder: Bounced 50224

What is the Bounced folder in procmail terms? Is that means that procmail bounced it and then postfix delivered the standard bounce message to the sender?

Thanks, Andrew

No sign of any outgoing mails to those addresses where the messages in question came from. I've checked the procmail.log and the maillog also and I've checked multiple mails where I saw the "Disk quota exceeded" warning.

I might be on a completely wrong track (I'm not a seasoned procmail user), but there is this in the procmail config:

and 73 means: Can't create (user) output file, according to sysexits.h

From my point of view this means that procmail(-wrapper) will return with zero exit code (to postfix) in case it can't create the user output file so postfix thinks everything is fine although it isn't.

I've found a mini-faq about procmail () and it says: (The mechanism when you use this from Procmail is that Procmail quits with the specified error code, and the calling program is expected to catch that and act accordingly, i.e. generate a bounce message in most situations. If you are calling Procmail from a program which doesn't do this, there will obviously be no bounce. So if you test Procmail from your shell prompt and you see Bounced or Requeued in the log, it only really means Procmail quit with a non-zero exit code.)

Could it be the reason why the bounce message hasn't been sent?

Thanks, but I couldn't find the messages in the mail queue.

Where can I find the settings for this behavior? (what should happen with the mails when quota is full)

Hi,

It's been more than 7 months since I wrote and I was very careful with quotas but it happened again when /home ran out of disk space for a few hours during the night (yeah I know, silly me for letting it but that's another story)

The flow is the same: - mail comes in - postfix hands it to spamassassin - SA can't write the bayes file but returns with "not spam" - postfix hands the mail to procmail-wrapper - procmail can't deliver (no space left) instead puts it in Bounced, but the bounce mail never sent to the sender and the mail is lost forever with no sign of trouble (except the user who knows that someone sent him a letter but it never arrived)

Is there any way configure procmail to send the bounce mail in case of "no space left"?

Thanks, Andrew

Sorry I wasn't specific enough.

/home ran out of space but / had plenty so I thought that the mails were sitting in the mail queue until the mailbox delivery is possible or it will send back a bounce message.

I understand that if / ran out of space then postfix can't write the spool files but in case the user ran out of space (either because of quota or /home is full) I expect postfix/procmail to handle this glitch.

As you can see at the beginning of the thread I had an issue with the quota but now I had the /home problem, the result is the same: mails lost without a trace.

Maillog:

The procmail log has been rotated since, so I don't have them, but I remember that it had a line: Folder: * * Bounced * *

And that's the last sign of that message. No outgoing mail which suggest that it's a bounce message (and the sender never got an error message).

Sorry that I can't be more helpful with the procmail log, but look back in the thread it's almost the same except it's not the quota that exceeded but the /home ran out of space.