On 5 June 1999, era eriksson <era(_at_)iki(_dot_)fi> wrote:
I imagine you are getting mixed up with the envelope recipient data
(the RCPT TO: address), which is probably lost forever by the time you
are trying to figure out who you should be delivering this message to.
My understanding is "Apparently-To:" is added by sendmail at the
final delivery stage, if it can't find any valid "To:", "Cc:", "Bcc:",
or "Apparently-To:" in the headers. I suppose you can safely assume
sendmail actually builds it from the "RCPT TO:".
From the sendmail docs:
: 2.9.2. Apparently-To:
: RFC 822 requires at least one recipient field
: (To:, Cc:, or Bcc: line) in every message. If a
: message comes in with no recipients listed in the
: message then sendmail will adjust the header based
: on the "NoRecipientAction" option. One of the pos
: sible actions is to add an "Apparently-To:" header
: line for any recipients it is aware of.
: The Apparently-To: header is non-standard and
: is deprecated.
: 5.6. O -- Set Option
: [no short name] The action to take when you
: receive a message that has no valid recipi
: ent headers (To:, Cc:, Bcc:, or Apparently-
: To: -- the last included for back compati
: bility with old sendmails). It can be None
: to pass the message on unmodified, which
: violates the protocol, Add-To to add a To:
: header with any recipients it can find in
: the envelope (which might expose Bcc: recip
: ients), Add-Apparently-To to add an Appar
: ently-To: header (this is only for back-com
: patibility and is officially deprecated),
: Add-To-Undisclosed to add a header "To:
: undisclosed-recipients:;" to make the header
: legal without disclosing anything, or Add-
: Bcc to add an empty Bcc: header.
Dr. Liviu Daia e-mail: Liviu(_dot_)Daia(_at_)imar(_dot_)ro
Institute of Mathematics web page: http://www.imar.ro/~daia
of the Romanian Academy PGP key: http://www.imar.ro/~daia/daia.asc