[c-nsp] Error

Jason Gurtz jasongurtz at npumail.com
Tue Jul 1 16:39:30 EDT 2008


> 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

-- 


More information about the cisco-nsp mailing list