Basically, i am wondering if anyone has had any success in decoding or reverse engineering the values attached to email fields
X-imail-threadid
X-uidl
Message-id
Thread-index
Appreciate any help.
Thanks
my apologies if this is old stuff, i looked around and could not find much information on FF.
Greetings,
Message-IDs are very well documented. RFC 822 is a good starting point
This field contains a unique identifier (the local-part
address unit) which refers to THIS version of THIS message.
The uniqueness of the message identifier is guaranteed by the
host which generates it. This identifier is intended to be
machine readable and not necessarily meaningful to humans. A
message identifier pertains to exactly one instantiation of a
particular message; subsequent revisions to the message should
each receive new message identifiers.
In other words, it is unique to the host and, depending on the host, may not have any meaning if "reverse engineered".
You can check the other headers in the RFCs.
-David
Greetings,
Message-IDs are very well documented. RFC 822 is a good starting point
This field contains a unique identifier (the local-part
address unit) which refers to THIS version of THIS message.
The uniqueness of the message identifier is guaranteed by the
host which generates it. This identifier is intended to be
machine readable and not necessarily meaningful to humans. A
message identifier pertains to exactly one instantiation of a
particular message; subsequent revisions to the message should
each receive new message identifiers.In other words, it is unique to the host and, depending on the host, may not have any meaning if "reverse engineered".
You can check the other headers in the RFCs.
-David
Thanks, yeah i did look at that, and RFC 193 for UIDL, but i have also seen some variants of the Message-ID on the local side that are partially or wholly decryptable. I will post this info on this thread and if anyone has some input, it might make a decent resource.
Thanks again