[c-nsp] Error

[Ziv Leyes]

I'm not the one that is capable to do it and I don't wanna sound demagogic but I think the whole SMTP protocol should be re-written from scratch. We're talking about a protocol that is over 40 years old! And nowadays we need much more than a "simple mail transfer protocol"
Well, this goes also for TCP...
Ziv


-----Original Message-----
From: cisco-nsp-bounces at puck.nether.net [mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Jason Gurtz
Sent: Tuesday, July 01, 2008 11:40 PM
To: cisco-nsp at puck.nether.net
Subject: Re: [c-nsp] Error


> Then write an updated RFC that changes the standards to reflect this
> behavior, and get it published and accepted.

Looks like 5821 will have to do (3821/4821 already taken) and be great
when everyone's compliant by the year 2030.  In the meantime, BATV (draft
is: draft-levine-smtp-batv-01) can be of help.  Helpfully, it even breaks
most C/R systems as well :)

~JasonG

--
_______________________________________________
cisco-nsp mailing list  cisco-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/





************************************************************************************
This footnote confirms that this email message has been scanned by
PineApp Mail-SeCure for the presence of malicious code, vandals & computer viruses.
************************************************************************************






 
 
************************************************************************************
This footnote confirms that this email message has been scanned by
PineApp Mail-SeCure for the presence of malicious code, vandals & computer viruses.
************************************************************************************