RE: Additional discussion: null sender -> MAILER-DAEMON

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Instead of having Postfix fill in the gaps when it comes to RFC's and =
the FROM: header, would it be wise to reject the mail after the DATA =
conversation completes if there's no valid FROM: header? Could I use =
header_checks(5) (or are header_checks even done before Postfix adds a =
missing FROM: header)?

-=3D| Ben=20

- -----Original Message-----
From: owner-postfix-users@postfix.org =
[mailto:owner-postfix-users@postfix.org] On Behalf Of Wietse Venema
Sent: Tuesday, May 31, 2005 2:24 PM
To: Postfix users
Subject: Re: Additional discussion: null sender -> MAILER-DAEMON

Postfix 2.2 and later has an option to disable message header=20
address rewriting.

http://www.postfix.org/postconf.5.ht...ewrite_clients
http://www.postfix.org/ADDRESS_REWRI...E.html#william

The FROM: header is required by RFC 822 and RFC 2822; there currently
is no feature to prevent Postfix from adding one that's missing,
nor is the format of the added header configurable at this time.
Postfix 2.2 and later has a header_checks action that can REPLACE
one message header by another one, but that is just one workaround
instead of a solution.

Wietse

-----BEGIN PGP SIGNATURE-----
Version: PGP Desktop 9.0.1 (Build 2179)

iQA/AwUBQp3pJ1QK10CpvqFVEQIBCACgpF2hB+9i2WK/ByIInYb+685mV7sAoP8R
UMVEFxdh0MKaU1f5NYuZELu2
=3DnGI7
-----END PGP SIGNATURE-----