This is what I think is feasible/infeasible from experiments here:
a. when you use the out-of-the-box merge to e-mail, you have to be logged
in to the account you want to send from. If there's some way to be logged in
as a Public Folder, I guess you could do it that way (but I don't know of
such a way)
b. if you use an approach such as the one Doug Robbins describes at
http://word.mvps.org/FAQs/MailMerge/MergeWithAttachments.htm
then I think you can specify the "Send As" mailbox by specifying
objMailItem.SentOnBehalfOfName = "the mailbox name you want to use"
What happens then depends on what permissions the Exchange Admin. has give
to the currently logged in User. If they have permission to Send on Behalf
As, the mail is sent out with a "Sent on behalf of" address. If they have
permission to Send As, it goes out as if it was from the specified user.
c. Although a mail-enabled Public Folder has an SMTP and Exchange (X.400)
E-mail address, I don't think it's actually also an Exchange Mailbox. And I
suspect that therefore, if you set the SentOnBehalfOfName to be the name of
a public folder (or, for example, its SMTP address), you may just get errors
back from exchange.
d. If (c) is correct, then all I can suggest is that you probably need to
set up a Mailbox whose incoming mail is redirected to a Public Folder.
However, my experience of Exchange is now from the early days of the product
(around 10 years ago) and I cant advise how to do that, or whether in fact
there is a way to do (c).
Finally, since a public folder does have an SMTP address, there may be some
other way of generating e-mails that completely bypasses Outlook (perhaps
using Windows "NT" CDO directly but which will work with Exchange. But
again, if so, I can't advise what that might involve.
Peter Jamieson
