On Wed, May 20, 2009 at 02:21:42AM +0200, Karsten Bräckelmann wrote: > On Wed, 2009-05-20 at 02:42 +0300, Jari Fredriksson wrote: > > Another one. This is from Washington Post. Still with fetchmail. > > http://wwww.pastebin.ca/1427982 > > > > Marked as BOUNCE. > > > > meta __BOUNCE_RPATH_NULL 0 > > > > should be working. > > $ spamassassin --cf="meta __BOUNCE_RPATH_NULL 0" < 1427982 | grep BOUNCE > > Comes up empty. Without that custom rule, it does trigger VBounce. So, > no -- that custom rule is not working. It *is* triggered by the null > Return-Path. Did you restart the daemon, or just test it with > 'spamassassin'? > > Anyway, that's another null Return-Path. Either you are just "lucky" to > receive so much of that behavior, or something is invalidating the > Return-Path in your mail processing chain. (No, it is not fetchmail by > default. Custom setting. Or something else.)
Funnily this was just talked about in another thread.. IF for some reason people still want to see null hitting BOUNCE_MESSAGE, shouldn't that be fixed to use "EnvelopeFrom" like it should? So it gets the right header in all cases(?). Seems like a bug to me. Amavisd-new quarantine files contain Return-Path: <> and original sender in X-Envelope-From etc. I can assure you that if you have any decend amount of users, you will see legimate null traffic.
