Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

You can avoid this mess altogether by using the quoted-printable content encoding when generating emails.


How so? Quoted printable doesn't require the dot to be encoded.

Maybe you're thinking of base64 encoding?


Doesn't require, but comfortably allows you to do.


Agreed.

But this is SMTP, I have no doubt there are gateways out there that will reencode the mail and put the dot back in the wrong place, eg in the name of wrapping all URLs behind a phishing-warning-page


I think the point here is that any subsequent implementation handling the message may well not be susceptible to the problem thus avoiding the erroneous behavior.


It can handle it fine in that sense, but still unquote it before sending it over to the next node. Which might have the bug.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: