On 31-Mar-2009, at 04:07, Matus UHLAR - fantomas wrote:
On 30-Mar-2009, at 11:52, Rik wrote:
The MAIL RFC's were conceives a long time ago and have had some
changes.
On 30.03.09 14:13, LuKreme wrote:
The changes (RFC2822) did not change enough. What is really needed
is
SoSMTP (Son of SMTP) defined for port 26.
You Might Be An Anti-Spam Kook If...
http://www.rhyolite.com/anti-spam/you-might-be.html#programmer-11
Heh. Yeah, I know. I am well familiar with that list and even have
one of the items in my random signature list<1>. The point is not just
that the servers have certs, but that the servers are also properly
configured, have proper DNS, etc. And like I said, this would not
eliminate spam, but it would certainly reduce it.
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.
http://www.rhyolite.com/anti-spam/you-might-be.html#senior-IETF-member-5
Now now, that is not what I said at all. I said it would take 15-20
years.
Maybe some RFC's have flaws, however I'm afraid replacing SMTP
wouldn't
replace them all...
It doesn’t have to replace them all. It just has to be enough of a
job to make the burden of spamming a little higher. A little higher
means a *lot* less spam. Heck, secure server chains would completely
eliminate the primary source of most the spam attempts I see, zombied
PCs.
<1> Despite having invented the FUSSP, you not only don't know the
difference between the SMTP envelope and SMTP headers. You doubt there
is such a thing as the SMTP envelope because email doesn't involve
paper.
--
Incredible! One of the worst performances of my career and they
never doubted it for a second.
