On Monday, March 30, 2009 2:13 PM -0600 LuKreme <krem...@kreme.com> wrote:
The changes (RFC2822) did not change enough. What is really needed is SoSMTP (Son of SMTP) defined for port 26. It would be 8bit compatible and would NOT be backward compatible with current SMTP. It would not have folding of headers lines and it would have exact standards on every header (the precise format of every date, for example). Any message that failed to be to the standards would be rejected for transfer on port 26. Of course, it would require a valid SASL chain on all servers from source to destination.
Ah, yes: SMTP is 7-bit and line-oriented, and those contributed to the faults in RFC2822. Allowing 8-bit and unlimited line length would largely eliminate the encoding and wrapping issues that the video covers.
I don't know what SASL addresses. Does it somehow eliminate anonymity of the sending server?
Putting this on a distinct port seems more a marketing thing. Why not add it as a capability in a normal SMTP server?
Messages that advertise strict compliance and pass a validator could be given a suitable negative "reward" score by SA. (Probably a batch of meta scores that null out some normal rules that invalid messages would be subject to.)
