
Signature
Michael Bednarek http://mbednarek.com/ "POST NO BILLS"
>>Normally when you send out a Newsletter, or email to a sensitive list like
>>suppliers or customers, you want the To: field of each recipient's email
[quoted text clipped - 25 lines]
> into the BCC: field. Note that some servers regard excessively long
> distribution lists as a SPAM indicator.
You are confusing the customization of content inside the *body* of the
email with customization of the To: field, which is part of the RFC822
header.
Customization of an RFC822 header is not a traditional mailmerge and is not
in the scope of what Microsoft Word can or should do. You are probably
right that the most straightforward implementation of that customization
would be in the mailer/client. It's just that with the level of
sophistication in Exchange now, you can imagine a server based
implementation, but I think it would require additional software that is
specially tailored to the application.
And, as you correctly point out, putting the list in the BCC field is not a
good solution because it guarantees that half of your recipients will file
away the email as spam.

Signature
Will
Michael Bednarek - 26 Apr 2007 05:13 GMT
>>>Normally when you send out a Newsletter, or email to a sensitive list like
>>>suppliers or customers, you want the To: field of each recipient's email to
>>>be customized with their name appearing as the only name. That requires
>>>special support at your mail server, and I would like to know if Exchange
>>>implements such a concept maybe as a special type of distribution list, or
>>>if there are third party applications to support this.
[snip]
>> Mailmerge is a function of the client, not of the Exchange server.
>>
>> AFAIK Mailmerge in Outlook requires Microsoft Word, or VBA code. Other
>> SMTP clients, including command line mailers, do it self contained.
[snip]
>You are confusing the customization of content inside the *body* of the
>email with customization of the To: field, which is part of the RFC822
>header.
>
>Customization of an RFC822 header is not a traditional mailmerge and is not
>in the scope of what Microsoft Word can or should do.
[snip]
I'm pretty sure that Microsoft Word/Outlook can send a single
uncustomized message/attachment, iow a newsletter, to many recipients by
generating a message for each. I'm similarly sure that this approach is
not the most effective or even convenient way of doing this. I would use
a command line mailer.

Signature
Michael Bednarek http://mbednarek.com/ "POST NO BILLS"