On Mar 7, 2009, at 9:55 PM, Greg Stein wrote:
> For efficiency reasons, the system has converted the large body of
> this message into an attachment.
> Months ago, when the mailing list software was "upgraded" into this
> broken state, you said there were people working on it with the
> highest priority and non-stop. What is the status of that work? When
> are we going to get a mailing list that doesn't turn large emails into
> attachments? (you know, like *every other* piece of mailing list
> software on the planet)
> The commit below has been made unreviewable by the software on
> I have chosen Gmail as my mail client. For very large emails, it clips
> the message and then offers a link if you'd like to see the full
> message. However, since the email below is a *short* email, but with a
> very large inline attachment, I *do not* get that choice. Instead, it
> is simply clipped.
> How am I supposed to do my work here? Why should we continue to stick
> with mailing list software that seems to break us every few weeks?
> (witness the loss of mail headers last weekend, after an unannounced
> downtime and "upgrade"; or the half-day "scheduled maintenance" a
> month ago?)
> "Choose another mail client" is not a very good answer, I'd think,
> since no other piece of mailing list software has ever made me do
> that. Nor do I see it as a good option for our project to dictate my
> choices of a mail client. There are other options for our mailing list
> that do not cause this kind of pain, this amount of downtime, or this
> lack of reliability.
Just one more bit of brokenness just discovered in Discussion
Services: it munges the Content-Type headers of messages in transit.
That's a Bad Thing.
(In this specific instance, my mailer sends the following header:
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
but what comes through the mailing list is:
Content-Type: text/plain; charset=us-ascii
That's bad form on the part of the mailing list software.)
Received on 2009-03-10 19:17:34 CET