4 messages in net.sourceforge.lists.courier-maildropRe: [maildropl] Filesystem quotas / T...
FromSent OnAttachments
Henk van LingenDec 9, 2004 5:29 am 
Andre FortinDec 9, 2004 5:39 am 
Henk van LingenDec 9, 2004 8:21 am 
Tony EarnshawDec 9, 2004 10:05 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: [maildropl] Filesystem quotas / TEMPFAILActions...
From:Tony Earnshaw (ton@billy.demon.nl)
Date:Dec 9, 2004 10:05:52 am
List:net.sourceforge.lists.courier-maildrop

tor, 09.12.2004 kl. 14.29 skrev Henk van Lingen:

I'm buiding a Postfix, spamassassin, courier-imap, ClamAV, ClamSMTP, Maildrop, Squirrelmail mailserver which uses filesystem quotas. I have maildrop as default MDA (mailbox_command = /usr/bin/maildrop (postfix)) because that way I can use spamassassin (spamc) at local delivery time by the way of /etc/maildroprc so I can have spamassassin user preferences.

Now the problem is that when a user is over quotum, maildrop gives a tempfail and mail stays in the queue. That's not what I want, I want a bounce with an overquota message. Using postfixs building MDA one gets this message:

maildir delivery failed: error writing message: Disk quota exceeded

Using procmail as MDA, also a bounce with (less informative):

can't create user output file

With maildrop however I can't find a solution to send a quota error back.

If you were willing to "superimpose" Maildrop's own quota mechanism on top of your filesystem quota (only valid foe users with no shell access to their Maildir/) you could have what you want, plus quota warning messages in advance to the users, too. It's just a design question - where to put the Maildirs in your structure and which owner:group owns them.

--Tonni

They love us, don't they, They feed us, won't they ...