The following bug has been ACKNOWLEDGED.
======================================================================
http://dbmail.org/mantis/bug_view_advanced_page.php?bug_id=0000086
======================================================================
Reported By: jnorell
Assigned To:
======================================================================
Project: DBMail
Bug ID: 86
Category: PIPE delivery (dbmail-smtp)
Reproducibility: always
Severity: major
Priority: normal
Status: acknowledged
======================================================================
Date Submitted: 09-Sep-04 21:26 CEST
Last Modified: 14-Sep-04 14:24 CEST
======================================================================
Summary: quota exceeded causes forwards to fail
Description:
When an alias lookup resolves to multiple deliver_to's with at least one
local INBOX delivery and one or more external forwards, if the local
mailbox is over quota the external forwards are sent an empty message
rather than the real email.
======================================================================
----------------------------------------------------------------------
aaron - 09-Sep-04 21:44 CEST
----------------------------------------------------------------------
I think you're exactly right about moving the quota checks to follow the
forwards. Try that out and see if that patches it right up. The new
delivery chain in 2.0 should not be affected, but it would be prudent to
double check it against related bugs... like what happens if the *delivery
user* has a quota applied, for whatever odd reason, or with combinations
of within quota, above quota and non-quota accounts and forwards.
----------------------------------------------------------------------
jnorell - 11-Sep-04 01:08 CEST
----------------------------------------------------------------------
After surmounting the delivery-chain learning curve, a fix is quite simple,
and that's just it (move forwards to happen before quota checks). Patch
is attached, tested only in pgsql, but is working fine on our production
machines so far.
----------------------------------------------------------------------
ilja - 14-Sep-04 14:14 CEST
----------------------------------------------------------------------
I can't apply the patch. It bails out when trying to patch
pgsql/dbpgsql.c.
Also, the patch looks a bit big. Does it change more than only the
forwarding code?
Jesse, can you please make a patch that applies cleanly to dbmail 1.2 CVS
(not 1.2.10)
Bug History
Date Modified Username Field Change
======================================================================
09-Sep-04 21:26jnorell New Bug
09-Sep-04 21:26jnorell File Added: problem.log
09-Sep-04 21:44aaron Bugnote Added: 0000233
11-Sep-04 01:08jnorell Bugnote Added: 0000234
11-Sep-04 01:08jnorell File Added: dbmail_1_2-20040910_nullforward.patch
14-Sep-04 14:14ilja Bugnote Added: 0000236
14-Sep-04 14:24ilja Status new => acknowledged
======================================================================
