Clay, > But, given the example from my original email, am I thinking correctly > that the subject with it's ascii representation of the "registered sign" > not fall under RFC 2822 specifications for an unstructured header field > using US-ASCII? Shouldn't this then have been MIME encoded to meet > specifications?
Yes, it is an unstructured header field, header section must not include any characters with code above 256, and yes, the Subject should have been encoded according to RFC 2047. > I'm not sure it's safe to discard these messages. Although I am going to > look through those that are showing this type of behavior and determine > how many may be legitimate messages. It is not unusual that some older or misconfigured mail clients would put a non-encoded text into Subject or into display name or elsewhere, especially in countries using ISO Latin character sets with diacritics, or cyrillic - so despite violating the rules, in most cases it is not safe to discard such messages. It is not even a good spam sign. It's better to educate sender of such otherwise legitimate mail. Mark ------------------------------------------------------------------------------ Free Software Download: Index, Search & Analyze Logs and other IT data in Real-Time with Splunk. Collect, index and harness all the fast moving IT data generated by your applications, servers and devices whether physical, virtual or in the cloud. Deliver compliance at lower cost and gain new business insights. http://p.sf.net/sfu/splunk-dev2dev _______________________________________________ AMaViS-user mailing list AMaViS-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amavis-user Please visit http://www.ijs.si/software/amavisd/ regularly For administrativa requests please send email to rainer at openantivirus dot org
