MessageID of Outlook 2003 Mail

[Pete Havenhand]

When an e-mail is sent to multiple people using Outlook XP , each copy of
the message has the same ID or just 1 message is sent out...

When the same is done in Outlook 2003 , each recipients message has a
different messageid.
Does this mean seperate copies of mail are sent out.

When you send to different people on the same domain , whose e-mails are
being collected from a pop mailbox by a mail server, all the seperate
messages are processed seperatley and they end up with multiple copies of
the mail , which is relative to how many people were sent the message in the
1st place?

Is there a workaround for this , and if not , does anyone know why this was
changed in 2003?

It has took me ages to work this out , seems the only way to resolve the
multiple copies is to roll back to outlook XP

Regards

Pete

 

[neo [mvp outlook]]

Outlook 2003 does not generate a message-id. It leaves it up to the SMTP
server to attach the message-id per the rfcs. So in the case you describe,
the following is happening.

1) Outlook 2003 sends a single copy of the item to the SMTP server
2) SMTP server accepts the message
3) SMTP server categorizes the message (what domains does it have to go to
and probably attaches a message id at this point or see next step)
4) SMTP server delivers it (during the smtp session, the server could be
attaching a message-id at this point. <- this is the one that you are
probably seeing)

Outlook 2003 doesn't generate a message id because Microsoft received
complaints from many that it exposes to much internal information. This
coupled with that fact that mail servers tend to be hardened (secured)
better than desktops and the rfcs permitted the removal of the message id,
it seemed the right thing to do. (There are old threads in
microsoft.public.outlook and microsoft.public.outlook.general that cover
this topic.)

There is no option in Outlook 2003 to get back the old behaviour back of
having it generate the message-id. Depending on who/what the SMTP server
is, you might try checking with the vendor to see if the message-id can be
attached earlier in the logic processes.