After upgrading to the version 2.4.0 of amavisd-new I suddendly recieved wrong DSN's for clean messages with receipients all recipients of some earlier processed mails together. According to this message [1] of the amavis-user mailing list, this is a little bug in this release. After applying the proposed patch, the problem was fixed. To save other users time, probably it's best to include the patch into the ebilds until this bug is fixed upstream. [1] http://marc.theaimsgroup.com/?l=amavis-user&m=114530996117532&w=2
Created attachment 85528 [details, diff] Patch to amavisd that resolves the bug
Created attachment 85529 [details] amavisd-new-2.4.0-r1 ebuild which includes the patch
Sorry for neglecting this, but I'm not using courier myself. The thread you link to mentions that this should be fixed in 2.4.1 (which I just committed into portage). Can you confirm this? I can't find piece of code from the patch in amavisd executable.
(In reply to comment #3) > The thread you link to mentions that this should be fixed in 2.4.1 (which I > just committed into portage). Can you confirm this? I can't find piece of code > from the patch in amavisd executable. I've upgraded and tested this issue. In 2.4.1 this bug is fixed. The new ebuild doesn't need the patch anymore.
Ok, I'm closing this as FIXED, since 2.4.0 is not stable on any arch, and 2.4.1 supersedes it on unstable. I'm also removing 2.4.0, since it's probably not worth of getting marked stable - it has couple of nasty bugs, which were fixed in 2.4.1. Thanks for reporting, Markus!
