Pretend I'm an idiot. (For most people who know me this won't be hard.) Could somebody please explain to me... in a way that takes into account my idiocy... what this "strict_mime_encoding_domain" option actually does, i.e. if you turn it on?
What exactly constitutes "invalid Content-Transfer-Encoding: information for the message/* or multipart/* MIME content types" ? Separate but perhaps related question: Assume that an incoming message includes the following header, either right in the initial headers, or else in the headers of some MIME subpart: Content-Transfer-Encoding: 7bit Assume further than one or more characters in the relevant MIME part actually have their high bits set. Does Postfix have any option that would cause the message in question to be either (a) rejected or else (b) flagged in some way? Regards, rfg P.S. Wietse, I've been keeping my eye open for that signal 11 crash in the local delivery agent that I reported, but it just stopped occuring for some reason. But I've set: /sbin/sysctl kern.sugid_coredump=1 on my FreeBSD system, so in case it ever does happen again, hopefully I'll be able to give you a source filename and lineno. (I really do think that what I saw was probably due to something weird/bad that _I_ must have done. I have some really hairy things being invoked from .forward files on the system in question, and _they_ were probably misbehaving.)
