Archiveopteryx
Archiveopteryx
Posted Mar 19, 2010 23:24 UTC (Fri) by cras (guest, #7000)In reply to: Archiveopteryx by nye
Parent article: Archiveopteryx
I don't know specifics, but I've read a few messages about this from Arnt. I believe this mainly
means that when the message contents are already violating RFCs, Archiveopteryx changes them to
RFC-compilant form using whatever heuristics / built-in rules that typically fix the problem. For
example many messages have 8bit characters in subject, even though this isn't permitted. So
instead of typical GIGO, it's GI-something-better-than-GO.
means that when the message contents are already violating RFCs, Archiveopteryx changes them to
RFC-compilant form using whatever heuristics / built-in rules that typically fix the problem. For
example many messages have 8bit characters in subject, even though this isn't permitted. So
instead of typical GIGO, it's GI-something-better-than-GO.