On 10/9/07, Stut <stuttle@xxxxxxxxx> wrote: > Philip Thompson wrote: > > On 10/7/07, Stut <stuttle@xxxxxxxxx> wrote: > >> I would recommend avoiding the use of BCC from PHP. > > > > Why avoid Bcc from PHP? > > Note that this applies to all automated sending, not just from PHP. > > It depends on how it's sending the mail. I've come across configurations > where the first mail server it hits refuses to send it because there are > so many BCC recipients. > > You are also more likely to fall foul of antispam systems because the To > address is not the same as the address the recipient. > > IMHO the only legitimate use for BCC in an automated system is to have a > copy sent to you for debugging/monitoring purposes. > > Of course this is just my experience-based opinion. > > -Stut > > -- > http://stut.net/ > > -- > PHP General Mailing List (http://www.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php > > Also keep in mind that some buggy or misconfigured mail systems have been known to forward the BCC data as an "X-Apparently-To" or "Delivered-To" tag, even if the message is not 'apparently to' you. In fact, I even used it years back in a honeypot server. So if it's important to keep those addresses private or transparent (though I understand that it's not the issue in your case here), then that's another reason to agree with Stut's point about shying away from BCC. -- Daniel P. Brown [office] (570-) 587-7080 Ext. 272 [mobile] (570-) 766-8107 Give a man a fish, he'll eat for a day. Then you'll find out he was allergic and is hospitalized. See? No good deed goes unpunished.... -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
