On 3/4/21 7:05 PM, Stephen J. Turnbull wrote: > Mark Sapiro writes: > > Does Scrubber really do that? Per RFC, the two Content-Type fields > have exactly the same semantics: "it is plain text, encoded as ASCII."
Yes, scrubber really does this. This dates back to Tokio and various Japanese language emails which presumably weren't all ascii. Perhaps we should revisit this, but you know much more about Japanese language emails than I do. Apparently, Tokio thought it was better to scrub such a part than to treat it as ascii when it wasn't. Perhaps a compromise is to give scrubbed text/plain attachments a .txt. extension rather than taking the first item returned by mime_types.guess_all_extensions. Note that this is a Mailman 2.1 issue only. In MM 3 scrubber is only invoked for plain text digests and just removes with notice all non-text/plain elemental parts and for text/plain treats missing or unknown charsets as ascii. -- Mark Sapiro <m...@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan ------------------------------------------------------ Mailman-Users mailing list -- mailman-users@python.org To unsubscribe send an email to mailman-users-le...@python.org https://mail.python.org/mailman3/lists/mailman-users.python.org/ Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/ https://mail.python.org/archives/list/mailman-users@python.org/
