Anne Wainwright writes:
> The first is reflected in the users FAQ 3.10 "How to enforce a
> text-plain policy". The answer being "with difficulty" because this
> option probably (as I read it) ensures that any message with
> non-plain-text content is completely, utterly, and totally, rejected,
Dear Lindsay,
perhaps I can make an input to this thread since I was about to
post something similar. If my comments are incorrect, please advise
since I have no desire to mislead any one.
We, too, have a load of old dinosaurs on one list who always manage to
post to wrong addresses and whose pos
Lindsay Haisley wrote:
[...]
>>
>> Message: 25
>> Date: Fri, 7 Oct 2011 08:42:29 -0700
>> From: "foo bar" <...>
>> To: cyberpluck...@autoharp.org
>> Subject: Re: [CP] Intro
>> Message-ID:
>> Content-Type: text/plain; charset="us-ascii"
>>
>> An HTML attachment was scrubbed...
>> URL:
>> http
Lindsay Haisley writes:
> One of two things needs to happen. Either the list server should refuse
> and bounce posts with no MIME text/plain part,
Refuse, maybe, but bouncing is a problem (spam-by-backscatter). But
refusing such mail is only going to confuse the kind of subscriber who
is as "
On Oct 21, 2011, at 11:21 PM, Lindsay Haisley wrote:
> The list is configured with mime_is_default_digest set to MIME, which I
> assume sends digests with each post as a separate attachment (I've never
> subscribed to the digest for this list, so I don't really know). I had
> assumed that this mi
I host a list for about 700 autoharp musical enthusiasts on Mailman
2.1.12. The subscribers are by and large somewhat elderly and non
techie, and to most of them an explanation of the difference between
HTML-enhanced email and plain text email would be unintelligible
geek-speak. I recently receiv
