Meta Stack Exchange is where users like you discuss bugs, features, and support issues that affect the software powering all 158 Stack Exchange communities.

What is meta?
Here's how it works:
  1. Any Stack Exchange user can ask a question
  2. The community provides support, votes on ideas, and reports bugs
  3. Your voice helps shape the way Stack Exchange operates

The verification email for CSO contains dodgy line endings, and looks like this in Mutt:

Thanks for registering with Stack Overflow Careers^M
To ensure that potential employers can reach you via email, we need to confirm your email address. All it takes is a single click.^M

The whole message shows a ^M at the end of each line. The encoded form of the text/plain message looks like:

Content-Transfer-Encoding: quoted-printable

Thanks for registering with Stack Overflow Careers=0D =0A=0D=0ATo ensure=
 that potential employers can reach you via email, we need to confirm your=
 email address. All it takes is a single click.=0D =0A=0D=0AClick here to=

I'm pretty sure there isn't supposed to be that extra =0D in there (especially not with that extra space), and taking it out allows the message to render correctly in Mutt.

share|improve this question
up vote 2 down vote accepted

Try to view the HTML version; the quoted-printable text/plain text stuff is only there as a weak fallback. (On Trilogy sites, the entirety of the text/plain is "view the html, please")

The QP bug is in the .NET framework mail classes.

Option for plain text mail notifications? (and spamassassin scoring due to HTML-only-ness)

Update: we have switched to a third party email component recommended by our pals at Doctype.

X-Mailer: MailBee.NET
From: "Stack Overflow" 

I can confirm that it "fixes" the quoted-printable encoding bug in the .NET framework.

share|improve this answer
Yes, the HTML one looks fine because whitespace is pretty much ignored by HTML renderers. I realise I'm in the minority here in using a text-only client, but SO may be one of the places with the highest proportion of users with non-HTML email clients. It seems pretty typical for Microsoft to get line endings wrong in email (they got it wrong everywhere else, after all). – Greg Hewgill Oct 8 '09 at 18:02
believe me I am not happy about this, but writing our own mail classes from scratch (or adopting some third party code) is really painful. – Jeff Atwood Oct 8 '09 at 18:32

The notifications are all about sharing the love.

^M = Kissing you with sharp lips. Because it hurts when you lick a live CPU.

=0D = They're happy to help you, smile! (Their in ur newlinez fixin your ln breks)

share|improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .