![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
Entry tags:
oh, the irony
I just sent mail to the administrator of the Reform movement's mailing lists asking him to stick to the standard. :-)
Dear [name],
Thank you for your reply.
> There is no text only version currently available for [list].
> We may pursue this in the near future.
I would like to encourage you to provide this for all of your mailing lists. While of course any service provider is free to support or reject any formats he chooses, the internet community as a whole works better when standards are followed. So far as I know nothing has superseded RFC 822, which calls for email to be sent in plain text. This specifies a minimum, and many modern mail programs also support HTML. However, older mail programs do *not* support HTML well, and even when the mailer itself does, text archives are rendered unreadable if they are not in plain text.
The result of this for me is that while I can mostly read the messages, I cannot usefully save them or pass them on to other interested members of my congregation. Perhaps this is your intent -- that the mailing lists be ephemereal and that people have to subscribe directly. That wouldn't have been my guess, however.
Thank you for your time in considering this matter.
Dear [name],
Thank you for your reply.
> There is no text only version currently available for [list].
> We may pursue this in the near future.
I would like to encourage you to provide this for all of your mailing lists. While of course any service provider is free to support or reject any formats he chooses, the internet community as a whole works better when standards are followed. So far as I know nothing has superseded RFC 822, which calls for email to be sent in plain text. This specifies a minimum, and many modern mail programs also support HTML. However, older mail programs do *not* support HTML well, and even when the mailer itself does, text archives are rendered unreadable if they are not in plain text.
The result of this for me is that while I can mostly read the messages, I cannot usefully save them or pass them on to other interested members of my congregation. Perhaps this is your intent -- that the mailing lists be ephemereal and that people have to subscribe directly. That wouldn't have been my guess, however.
Thank you for your time in considering this matter.
mmm, pedantry
Re: mmm, pedantry
I thought that even if you tacked on the other junk (HTML, other MIME, random Microsoft lossage), the plain text was still required. I guess I'm wrong about that. How sad.
As you might have guessed, this is a mailing list that is sending only as text/HTML. Even though pine does mostly render it ok (there are glitches), it still annoys me because I can't easily just pop into emacs to find something in my mail archives when people do crap like that. And pine doesn't offer anything nearly as fast or featureful as regular-expression search in emacs.
Re: mmm, pedantry
RFC 2822 - Internet Message Format
And while it does indeed restrict itself to plain text, as RFC822 did, it specifically refers to the MIME RFCs [RFC2045, RFC2046, RFC2049] for transmission of non-text data.
(And, pedantic self-correction: RFC822/STD11 is still the official standard; RFC2822 is still pending. Not to mention that I butchered "supersedes" yet again. :/)
Re: mmm, pedantry
no subject
no subject
procmail rocks
no subject
no subject
no subject