> I wasn't aware that I could use multiple RCPT TO:<> commands to > accomplish Bcc. Hence me adding Bcc after the DATA.
It's the other way around, actually. Multiple RCPT TO:'s is how Bcc: is done. One has to have a clear understanding of the difference between RFC 822 (the message), and RFC 821 (the mechanism by which the message is delivered). ok, ok, ok, 2822 and 2821. oh wai, 5322 and 5321... /pause and wait... When people talk about full headers, they're talking about the message. When people talk about the envelope, they're talking about a record of the transaction to move the message from one server to another until it finally arrives at its destination. Some aspects of the envelope can be encoded in the headers, typically as a final step of delivery (ie Return-Path:, Delivered-To:), but the fact they are in the headers at final delivery should not be confused with their presence in the data as it moves from MUA to server to server. And such it is with Bcc:. It's a "virtual" header seen only in the sending MUA, typically. Any other sightings of it In The Wild are just figments of the diseased and fevered imagination of all concerned, or seriously b0rked software. :) Main take-away: 822 vs 821, they are not the same thing at all. Aloha mai Nai`a. -- " So this is how Liberty dies ... " To Thunderous Applause.
