On Wed, Apr 18, 2007 at 11:56:25AM -0230, Devin Rubia wrote:
On Wed, Apr 18, 2007 at 10:35:35AM +0200, Peter Mann wrote:
On Tue, Apr 17, 2007 at 10:45:54AM -0400, Gordon Thagard wrote:
--- courier-0.53.3/maildrop/deliver.C 2006-05-28 17:29:52.000000000 +0200
+++ courier-0.53.3_NEW/maildrop/deliver.C 2006-12-25 13:15:00.000000000
+0100
@@ -160,7 +160,7 @@
maildrop.msgptr->MessageSize()) < 0)
{
#if HAVE_COURIER
- throw 75;
+ throw 77;
#else
throw 77;
#endif
That's just wrong on so many levels. The main one, though is that the
code in the "if HAVE_COURIER" block is meant to be compiled is you are
using maildrop with the Courier MTA, not Postfix. If maildrop is
properly compiled as standalone, the OP will already be getting 77 on
over-quota.
ok, you are maybe right, but it's working fine with Postfix
Also, is
there a way to give an informational message back to the sender to let
them know this user is over their quota?
/etc/postfix/master.cf: ... argv=/usr/bin/maildrop -w 80 -d ${recipient}
/etc/courier/quotawarnmsg
Also wrong. This drops a warning message in the _recipient's_ mailbox,
not back to the sender. IF the MTA doesn't support it then judicious
use of exception, if, and mailbot would be able to do this. Me, I'll
stick to the standard bounce messages.
yes, my mistake - it's ok for recipient - warning about mailbox quota ...
anyway - sender gets message:
<some...@tuke.sk> permission denied. Command output: maildrop: maildir over
quota.
it's because of "throw 77" ...
if there is "throw 75", message wait in postfix queue ...
5 messages in net.sourceforge.lists.courier-maildropRe: [maildropl] Changing temporary er...
