On Sat, Aug 9, 2008 at 2:05 AM, Amedee Van Gasse
On Sat, August 9, 2008 03:18, John Andersen wrote:
It does. At the SMTP level. I'm looking at the protocol level, you are looking at the data level.
Yup. I'm looking at what is available in real data. You are looking at theory.
I think I don't like where this is going.
But I know this: because you are using gmail, you are probably not running your own mailserver, at least not for receiving mail from this list. That means you don't have access to server logs. I am running my own postfix installation and I have access to the logs. That means you have only the client-side information of the email story, while I have both client-side and server-side.
But the Gmail SMTP servers that receive the mail from the list has access to both the envelope as well as the headers. That server could know if the mail from the list originated from recipient, (as it purports to do). Especially given the amount of stuff google stuffs into domain keys, spf, etc. It could alert the recipient to the forgery, especially the forgery of his own from header, allowing him to warn others. Look, its not like this is a totally new idea, you know. Forged "From" header detection (especially when one's own domain is the one being forged) has been bandied about for some time. Its available in Kolab, and probably other smtp servers as well. See: http://www.mikerubel.org/computers/rmx_records/ Its usefulness might not be that great, and it does hold a potential for false alarms for mail from people who insist on sending from one domain and receiving from another (falsifying their own headers in effect). But realistically, how many people do that? -- ----------JSA--------- There are 10 kinds of people in this world, those that can read binary and those that can't. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org