When I said,
T> Good. Bigfoot manages to send a bounce that says which Bigfoot username
T> pointed to the undeliverable downstream address by including a "for" phrase
T> in the Received: headers even when the item was blind-carboned to more than
T> one Bigfoot address (at least in my tests). Surely iName can do something
T> similar.
Nick Simicich replied,
S> This is a really bad idea, unless this is produced as part of a bigfoot
S> internal expansion after they are internally directing the mail to only one
S> recipient. Is that more or less what you are saying?
The "unless" clause is exactly what I'm saying, because it's what I believe.
Here is what I did: I set my Bigfoot address to spread to two valid addreses
of mine plus an invalid one. I sent mail from yet another address of mine
to yet ANOTHER address of mine, blind-carboned to my Bigfoot address and
also blind-carboned to a friend's Bigfoot address. It was delivered to the
To: address, to the two valid forwarding points of my Bigfoot account, and
to my friend; it was also bounced back to me. While the invalid address was
given as the one with the delivery problems, the returned Received: headers
below it had a "for" phrase that named only my Bigfoot address, not my
friend's and not the final false address (nor either of the other two
addresses to which my Bigfoot address was forwarding).
S> Can one bigfoot customer see that another bigfoot customer was BCC'd?
It appears not.
