R
Roland
It is a big problem that OL 2003 generates NO Message-ID !!
So my Solution is that Microsoft, change this in the next Service-Pack
as Usersettings to:
[X] Generate Message-ID by Outlook (default on)
Reasons:
The most Soft- and Hardware for Anti-Spam marks ALL Messages without
Message-ID as Spam, because most of the Spam does have a Message-ID
of some flavour, wrong,empty Message-ID or other.
So the Test of the Spam-Programms are:
# Message-ID Spam tests mark as Spam
Message-ID: {\<\>} [empty Message-ID]
@Message-ID: {[a-z0-9]{1,}} [NOT RFC]
Message-ID: {.*@.*} [Message-ID without @]
It is NOT the Job of the Server to generate this ID, it is
the job of the eMail-Client !!
Mozilla, Netscape and ALL other Mail-Clients use RFC to generate an
ID:
Example:
<3F31B8A2.4070901@my_domain.de>
my_domain.de = Outgoing SMTP-Server in Mail-Setup !
There are NO security reason don´t do that.
Quote to this Topic from statement Jeff Stephenson (Microsoft) some
weeks agao:
This is wrong !
There is *no* requirement that "the name of the machine" be the
right hand side of the msg-id - read RFC !!
And the proposed Message-ID generated by Server would contain the
domain
name as define in RFC - so whats the difference?
I don't know how he came to that conclusion.
RFC 2822 "Internet Message Format" contains neither 'server' nor
'client' not 'MUA' nor 'MTA'.
Outllok is the first Email-Client in all OS, which don´t generate a
Message-ID,
so the most Email-Server don´t support this feature !
-Roland-
So my Solution is that Microsoft, change this in the next Service-Pack
as Usersettings to:
[X] Generate Message-ID by Outlook (default on)
Reasons:
The most Soft- and Hardware for Anti-Spam marks ALL Messages without
Message-ID as Spam, because most of the Spam does have a Message-ID
of some flavour, wrong,empty Message-ID or other.
So the Test of the Spam-Programms are:
# Message-ID Spam tests mark as Spam
Message-ID: {\<\>} [empty Message-ID]
@Message-ID: {[a-z0-9]{1,}} [NOT RFC]
Message-ID: {.*@.*} [Message-ID without @]
It is NOT the Job of the Server to generate this ID, it is
the job of the eMail-Client !!
Mozilla, Netscape and ALL other Mail-Clients use RFC to generate an
ID:
Example:
<3F31B8A2.4070901@my_domain.de>
my_domain.de = Outgoing SMTP-Server in Mail-Setup !
There are NO security reason don´t do that.
Quote to this Topic from statement Jeff Stephenson (Microsoft) some
weeks agao:
We made this change because we've had a number of complaints about
revealing internal machine names in the Message-IDs we generated.
As you know, a message id has an ID portion preceeding the '@' sign,
followed by the name of the machine that generated that ID.
This is wrong !
There is *no* requirement that "the name of the machine" be the
right hand side of the msg-id - read RFC !!
A number of people have objected to this for two major reasons:
2) They don't want to reveal their employer when sending mail via
their ISP from work, and a message id generated by Outlook would
contain the domain name of their employer.
And the proposed Message-ID generated by Server would contain the
domain
name as define in RFC - so whats the difference?
... As has been pointed out, RFC 2822 applies to server-server
interactions, not client-server interactions, so it's necessary for
servers to ensure the validity of the messages they send.
I don't know how he came to that conclusion.
RFC 2822 "Internet Message Format" contains neither 'server' nor
'client' not 'MUA' nor 'MTA'.
Outllok is the first Email-Client in all OS, which don´t generate a
Message-ID,
so the most Email-Server don´t support this feature !
-Roland-