Archiveopteryx

Posted Mar 18, 2010 14:14 UTC (Thu) by nye (subscriber, #51576)
Parent article: Archiveopteryx

From the overview:

"Apart from being designed to handle large volumes of mail accumulated over a long time, Archiveopteryx keeps the future in mind by storing only the canonical form of each message in the database, correcting common syntax errors at delivery."

I'm not sure what exactly this means, but it makes me a little nervous. One person's 'canonicalisation' is another person's 'corruption'. Can anybody shed some light on the subject?

to post comments

Archiveopteryx

Posted Mar 19, 2010 23:24 UTC (Fri) by cras (guest, #7000) [Link]

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.