procmail
[Top] [All Lists]

Re: /var/spool/mail, MailDir and quota

2001-04-17 07:28:00
Martin Lorensen asked,

| In /etc/procmailrc I have:
| 
|  DEFAULT = $HOME/Maildir/
| 
| This works almost as expected - users normaly get mail in
| $HOME/Maildir/new/.
| 
| But there is a few problems:
| 
| 1) Even though mail is put into $HOME/Maildir/new, an empty file (or with
|    50K users, 50K empty files) is created as /var/spool/mail/$LOGNAME

You need to recompile procmail with $HOME/Maildir/ as the value of $ORGMAIL. 
Unless you invoke procmail with the -m option, the first thing it does is
test the accessibility and writability of the compiled-in value of $ORGMAIL.
Reassigning ORGMAIL=somewhere_else in /etc/procmailrc or in ~/.procmailrc
won't change that.

| 2) When inode disk quota exceeds, mails are delivered in
|    /var/spool/mail/$LOGNAME with something like this in procmails log:

When it can't write to $DEFAULT, procmail tries to write to $ORGMAIL, which
was compiled in as /var/spool/mail/$LOGNAME and hasn't been changed.  Reas-
signing the value of $ORGMAIL in /etc/procmailrc or in ~/.procmailrc will
fix that (though it won't fix #1).

| 3) When block disk quota exceeds, mails are bounced with error:
| 
|     (reason: can't create (user) output file)
|     550 5.0.0 <test>... Can't create output
| 
|    This is ofcause correct - But how will I be able to give a better error
|    message?

You'll need to tweak your MTA to change that.

_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail

<Prev in Thread] Current Thread [Next in Thread>