Skip to main content
8 events
when toggle format what by license comment
May 16, 2011 at 0:47 comment added nemmy I'll start looking through headers and let you know.
May 15, 2011 at 5:27 comment added Charles @nemmy, I'd also love to know what email clients your users were having trouble with.
May 14, 2011 at 22:42 comment added nemmy Email wrapping is most certainly a problem. I have a set of standard answers to questions that my customers ask me that include links to my blog. Typically these links are long (I know I could tinyURL them) and about 10% of them complain of links being broken due to line wrapping in their email clients.
May 14, 2011 at 4:07 comment added Charles I'd love to know what client you had problems with so I can ensure bad things will happen to the author...
May 14, 2011 at 4:05 comment added John Conde I only mentioned it because I recently had issues with it myself. The problem with emails is you never know how the user's email client will display it. Even if it is HTML since they can view them as plain text anyway if their client is set to do so. You pretty much need to make sure the entire URL is short enough to fit on one line in plain text to be reasonably sure everyone will see it intact.
May 14, 2011 at 4:03 comment added Charles I'm not sure that line wrapping is a major problem in the modern era. Everything supports quoted-printable now, which permits longer lines to be split in the message body without impacting the formatting. We'd then just need to worry about wrapping post-decoding, and most users, especially users that we'd worry about usability for, are going to be running a client that probably won't obsessively break lines into 76/78 character chunks. Even then, HTML email avoids the wrapping problem entirely.
May 14, 2011 at 3:46 comment added John Conde Make sure the URL with the token isn't very long or it will wrap in the body of their email and break the token causing it to fail.
May 14, 2011 at 0:06 history answered Charles CC BY-SA 3.0