james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Paul Hammant <Paul_Hamm...@yahoo.com>
Subject Re: SPAM handling.
Date Tue, 05 Mar 2002 15:27:04 GMT

You are perhaps exposing that I am out of my depth here :-)  My SMTP 
knowledge is limited to poking it at college with Telnet.

I am trying to push the fact that some change of mail forwarding design 
is needed to make the system more accountable and less spoofable.  And 
that five of you knowledgeble enough could sit down, publish an RFC and 
gaim mindshare for the eventual migration from SMTP as is at the moment.

- Paul

>While I like the idea of XML headers, that seems to imply changing or
>dropping the MIME spec.  Or were you referring to the handful of protocol
>commands (I don't really see that as headers)?
>Serge Knystautas
>Loki Technologies - Unstoppable Websites
>----- Original Message -----
>From: "Paul Hammant" <Paul_Hammant@yahoo.com>
>To: "James Developers List" <james-dev@jakarta.apache.org>
>Sent: Tuesday, March 05, 2002 4:34 AM
>Subject: Re: SPAM handling.
>>I appreciate there are blocks that can be put up using the current
>>protocols, but my contention is that blocks are the wrong solution.  See
>>What we need is some solution (that possibly changes the SMTP protocol)
>>that does not upset whole countries and closes the spoofing loopholes.
>> We will still be spammed, but the originators will be easier to find.
>>I still think that we should migrate to a new, say, SMTP2 solution that
>>closes all the loopholes (upgrades to XML headers at the same time).  At
>>some point in the future mail administrators choose to turn off support
>>to old SMTP and any mail servers trying to forward mail for them find
>>they just cannot connect.  I.e. we are shooting the messanger in this
>>case (with bullet that takes two years to percolate through the system).
>>My point is there smart enough brains in this list who can design
>>son-of-SMTP and propose it to the IETF.
>>- Paul
>To unsubscribe, e-mail:   <mailto:james-dev-unsubscribe@jakarta.apache.org>
>For additional commands, e-mail: <mailto:james-dev-help@jakarta.apache.org>

To unsubscribe, e-mail:   <mailto:james-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:james-dev-help@jakarta.apache.org>

View raw message