Forum Moderators: phranque
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
The fact that it doesn't even include my e-mail address indicates to me that it's being generated by software somehow. I'm running Outlook 2002 with AVG. I'm not sure if it's related, but just now today, Outlook has begun having major stability problems.
These types of messages have been coming in periodically for a couple weeks, but didn't start until I'd been using AVG for at least a month. So far I haven't been able to track down the problem; my system configuration (Windows 2000) hasn't changed at all that I know of.
Any ideas?
Thanks,
Matthew
I also have avg, but I was getting these before avg, so I don't think they are related to that program.
Not sure if I have helped in any way, but just letting you know I do get them as well.
There are a lot of hand-shaking messages exchanged, but in a nutshell:
- The sending SMTP server connects to the receiving/routing SMTP server
- The sender tells the receiving server that it has a message for "username@domain.com"
- The receiver checks to see if it should accept the email. If it decides not to accept it, then it ends the connection. Otherwise...
- The receiver says "Ok, send the message"
- The sender sends the email message, including the TO, FROM, and other headers.
- The receiver puts the email in the inbox of the person that the sender said the message was for. It never even looks at the message headers. (exception is that it would normally add a "Received" header to the top of the header section to note where and when the message came from)
Of course, that is with standard SMTP. Anti-virus scanning and spam prevention is then retro-fitted into that flow.
As for the TO header not matching the actual recipient, keep in mind that many legitimate emails are sent to an email list. Only the name of the email list shows in the TO header. For this reason, it is next to impossible to verify the TO header against the actual recipient.
Maybe I'm not saying what I mean - either that or misunderstanding the concepts involved. There simply is no TO header at all. Viewing the message, the "To" line is blank. Entirely. Not even a single space. Looking at the message headers shows only what I quoted before. I can't tell that the message is to anyone, period. Surely spamming hasn't become that advanced - or has it?
Exactly what transpired to generate a specific blank message is anyone's guess. My guess is that most of them are the result of a spammer verifying their email list, or a spammer that doesn't know what they are doing.
When the server wants to send a message to another server, it will look at the envelope information and connect to the indicated email server. If, following the steps I listed before, the receiver agrees to receive the message, the sender sends the message. The message might be complete jibberish. Or empty. The receiving server might inspect the message to check for correct structure. Or it may not.
The point is, the envelope information is used for actually routing the message and for the handshaking that goes on. The message is what gets put into your inbox.
The spammers software is going through the handshaking motions, but it is not sending a valid message. Unless you can look at the SMTP log file, all you have to go on is what is in the message. In your case there is nothing in the message.