Probably if you are reading the actual RFC 2822 that is presented there. There are a couple of entries that I spotted immediately though that simplified the RFC to the point that the answer was wrong.
I was told earlier that I could use the headers to see where BCC mail was originally addressed.
I was also told that the field I need to examine is "X-Apparently-To:"
I see now (thanks to Pegasus; oh yes I'm starting to like this thing) that my headers actually have a field called "Delivered To:"
My questions are...
I have been trying for months (maybe years) to get a handle on who's giving my address(es) away, and now, I think, I hope, it looks like I'm finally going to be able to make at least a guess about the trail.
Perhaps a better question would be: Where can I learn the rules of the structure of an E-mail message ?
Or, is this the place (i.e., community.pmail.com/forums) where I learn such rules ?
I was also told that the field I need to examine is "X-Apparently-To:"
This header is added when the mail is being delivered to the users new mail directory. If nothing was changed and if it were received via SMTP then it will be the original RCPT TO: address. If it was filter and moved/forwarded/aliased/etc then this address is the address used in that process.
I see now (thanks to Pegasus; oh yes I'm starting to like this thing)
that my headers actually have a field called "Delivered To:"
This is generally the header added by the ISP when delivering SMTP mail to a POP3 mailbox. This should contain the original RCPT TO: address. All ISPs should do this, especially when providing "domain" mailboxes but mant do not. You are one of the lucky ones.
Perhaps a better question would be: Where can I learn the rules of the structure of an E-mail message ?
RFC 2822 for the body and RFC 2821 for details of the headers. There are a number of others for MIME/IMAP4/POP3/etc but these two are a good place to start.
