BD said:
Send email to yourself, bcc everyone that needs to get it.
-bd
Actually you should NOT have to send it to yourself (by entering a
non-blank entry in the To field which is yourself). RFC 2822, section
3.6 (
http://www.cis.ohio-state.edu/cgi-bin/rfc/rfc2822.html#sec-3.6),
makes it quite clear that the To, Cc, Bcc, Reply-To, and Subject headers
are completely optional; they may appear 0 (zero) or 1 (one) times. The
RCPT command to the SMTP server is what dictates to where the e-mail
will go (which can be different than the To field which is part of the
user's DATA and can whatever they want to specify, if anything).
If an SMTP server required the To field be populated, it violates RFC
2822. Of the SMPT commands, MAIL seems to be where the sender is
identified (the HELO or EHLO are supposed to identify the sending mail
server). Perhaps some SMTP server put the sender's e-mail address from
there into a To header that they insert into the headers of the e-mail,
but then they are modifying the headers in manner inconsistent with the
RFCs. If you must make the To field non-blank, that's because your ISP
configured their SMTP server to require it.
Outlook takes the safe approach and will put the e-mail address of the
account you are using to send the e-mail into the To field if you left
it blank. It doesn't tell you that it did this; it sends the e-mail and
only the recipient (which could be you if you were in the BCC field) see
that the To field got populated. In fact, if you look at your copy in
the Sent Items folder, it will show that you left the To field blank.
So here's another example of Microsoft protecting you too much.
