sendmail question...

[Thomas Mondoshawan Tate]

--5vNYLRcllDrimb99
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Good thing I was playing with sendmail all this morning... =3Dop
Coincidentially, I was looking for exactly that functionality. The option
that sounds like what you're looking for is NoRecipientAction
("O NoRecipientAction=3D<value>" in the sendmail.cf file).

It seems that if a mail client sends sendmail an e-mail
without a To: field, you have three options (really four, but you shouldn't
really consider the fourth option -- it's deprecated):
       - "None"   (passes the message accross unmodified
                   -- breaks the protocol, yet it seems to be the default
		   behaviour on RedHat 6.2 systems. Dunno about later versions)
       - "Add-To" (add a To: header with any recipients it can find in the
                   mail -- can expose Bcc: recipients)
       - "Add-To-Undisclosed" (adds the header "To: undisclosed-recipients:=
;")
       - "Add-Apparently-To"  (deprecated -- only for back-compatibility)
      =20
Which you use is dependant on what purpose you're using the mailer for, and
how private you wish the Bcc: headers to be. Personally, I use the "Add-To"
value.

OTOH, there is a header that lists the mail path and who the mail was
originally for -- it's called the "Recieved:" header, but I'm not sure if
that'd be reliable across MTAs.

-- Mondoshawan

On Mon, Jul 30, 2001 at 08:41:44PM -0700, Nick Estes wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>=20
> Anyone know how to get a Delivered-To header (or similar) in sendmail?
> When a message comes in at foo@bar.com, it might go through several
> translations in the virtusertable before popping out in my mailbox, but
> there seems to be no indication that it was originally for foo@bar.com in
> the message headers (that is unless the sender was kind enough to place it
> in the To: field, but that generally doesn't work with spam).
>=20
> 	--Nick
>=20
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.0.6 (GNU/Linux)
> Comment: pgpenvelope 2.10.2 - http://pgpenvelope.sourceforge.net/
>=20
> iD8DBQE7Zij/v+hjYTGg7s4RAhp4AJ9BuFSDjXPxYs6n8b2M94dca4rlbwCfWIvo
> 9ilhPv/j8hBHgBDUA+vWptQ=3D
> =3D7lCi
> -----END PGP SIGNATURE-----
>=20
> ________________________________________________
> See http://PLUG.phoenix.az.us/navigator-mail.shtml if your mail doesn't p=
ost to the list quickly and you use Netscape to write mail.
>=20
> PLUG-discuss mailing list  -  PLUG-discuss@lists.PLUG.phoenix.az.us
> http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss

--5vNYLRcllDrimb99
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE7ZjL7Yp5mUsPGjjwRAidyAJ9LIEU1Fpi14bS4Z4OQMmKerkdq0ACdFSpI
JgXlHsYI8tnEa5bWZkyGtgA=
=lozj
-----END PGP SIGNATURE-----

--5vNYLRcllDrimb99--