https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6403
--- Comment #20 from Karsten Bräckelmann <[email protected]> 2010-05-27 11:33:33 EDT --- (In reply to comment #19) > I think I found what it is going on. > > As specified in the bug description, we are running SpamAssassin through > Postfix + spamass-milter. Spamass-milter adds a custom Received header to the > message: Ah, see, that's why UNPARSEABLE_RELAY and spamass-milter in the same context did sound familiar. Good catch, Giovanni, thanks! Peter, I assume you are also using spamass-milter? Can you confirm this fixes it for you, too? > BTW: the fix to match ESMTPA vs ESMPT for google header still appears a > correct > fix to me, though not the main bug here. This would only be relevant, if google servers happen to be in ones *_network settings. And maybe if one pulls directly from google using e.g. fetchmail, which can lead to the same behavior. Also, it feels more like a workaround for broken google headers than a fix... I'm inclined to change the Summary to properly reflect the main issue, so it can be found easier. But thanks to the proposed patch there are now two bugs handled in one report. ;) -- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
