https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7101
--- Comment #12 from Kevin A. McGrail <[email protected]> --- (In reply to Mark Martinec from comment #11) > > The entire process of parsing these headers is dealing with a number of > > non-RFC issues to try and deal with real-world, high impact scenarios. > > I wouldn't even try and deal with this from an RFC standpoint ;-) > > In my opinion the SM::Metadata::Received module is (for historical > reasons, due to its incremental growth through a decade, no blame > attached) just an ad-hoc bunch of hacks. > > In amavis I have a 100 lines of perl code to do the parsing of > trace information according to RFC 5321 syntax, with few relaxed > exceptions. Admittedly the code is mainly interested in collecting > tcp information in FROM and BY clauses (not the hello info), but > does understand the full syntax. > > There are indeed a handful of broken or misguided mailers that > deviate from the standard syntax, although I think that 90 % of > all cases could be handled by a proper standards-compliant parser, > and only what remains could be handled by hand-coded exceptions, > possibly even as a pre-parser to convert such into a standard form. 100% agreed and I would welcome something in 3.4.2+ to address this. Right now, though, I'm working more on getting 3.4.1 out the door and this was a minor change to push that kicks the can down the road a bit. -- You are receiving this mail because: You are the assignee for the bug.
