On 12/1/06, Chris Lear <[EMAIL PROTECTED]> wrote:
In fact, every full stop in the html is represented as . for some reason.
In SMTP, a dot all by itself on a line is interpreted as the end of the message. The SMTP client is supposed to double any such dot that is truly present in the message body, and the SMTP server then removes the extra dot for final delivery. My guess would be that (a) they have a crappy SMTP cllient, probably something written in Java by a junior programmer who doesn't know a protocol from a parsnip, to send mail directly from a web server platform; and (b) they once had a message truncated because there was a dot in the wrong place; so (c) because they don't know how to fix the crappy SMTP client, they encode all the dots instead.
Still wondering though... how do you solve a problem like EasyJet?
By doing what you don't want to do: whitelisting.
