Re: Question about adding a special header to emails

7 msg	Invalid Sender Address syntax
2 msg	high availability
2 msg	BFD (Brute Force Detection) & Postfix
5 msg	relay domain and forwarding
2 msg	dk-milter - emal size issues
5 msg	Mail sent from local machine shows undisclosed-...
16 msg	Sorting incoming mails according to rules
5 msg	Correct use of smtpd_tls_security_level
1 msg	graph queue sizes
6 msg	large deferred queue ('too many connections')
3 msg	To see IP's
5 msg	How Can I Block certain IP's Within Range of my...

Question about adding a special header to emails
\ Richard Bates (15 Jun 2007)
. \ Duane Hill (15 Jun 2007)
. . \ Richard Bates (15 Jun 2007)
. . . \ Dhawal Doshy (15 Jun 2007)
. . . . \ Duane Hill (15 Jun 2007)
. \ Duane Hill (15 Jun 2007)
. . \ mouss (15 Jun 2007)
. . \ Noel Jones (15 Jun 2007)

3 msg	rcpt count mismatch and corrupt queue file ?
2 msg	too many connections
11 msg	Whitelist broken email servers?
4 msg	Write failed in network_biopair_interop with er...
2 msg	Pattern-matching in HELO
3 msg	header_checks du jour
3 msg	Good Resource for additional Spam Blocking

Subject:	Re: Question about adding a special header to emails
Group:	Postfix-users
From:	Noel Jones
Date:	15 Jun 2007

>On Fri, 15 Jun 2007, Richard Bates wrote:
>
>>using postfix FreeBSD Package
>> postfix-2.0.19
>>
>>I was planning to upgrade this summer, but until then,
>>is there a solution I can use?

You can have your mobile/home users submit mail to the "submission"
port 587 and then mangle the headers of mail arriving on that
port. Some people also like to enable the deprecated "smtps" port
465 to work with older clients.
Using alternate ports has the added benefit of sidesteping issues
where ISPs may block access to port 25.

# main.cf
submission inet n - n - - smtpd
-o smtpd_enforce_tls=yes
-o smtpd_sasl_auth_enable=yes
-o smtpd_client_restrictions=
-o smtpd_helo_restrictions=
-o smtpd_sender_restrictions=
-o smtpd_recipient_restrictions=permit_sasl_authenticated,reject
-o cleanup_service_name=cleanup-sasl
smtps inet n - n - - smtpd
-o smtpd_tls_wrappermode=yes
-o smtpd_sasl_auth_enable=yes
-o smtpd_client_restrictions=
-o smtpd_helo_restrictions=
-o smtpd_sender_restrictions=
-o smtpd_recipient_restrictions=permit_sasl_authenticated,reject
-o cleanup_service_name=cleanup-sasl
cleanup-sasl unix n - n - 0 cleanup
-o header_checks=header_checks_sasl_cleanup

Now in the header_checks_sasl_cleanup file we mangle the Received
header so SpamAssassin won't trip over it.

In postfix versions above 2.2, use REPLACE to alter the header and
preserve this valuable debugging and tracking information. In
earlier versions of postfix, our only choice is to remove the header
with IGNORE.

# header_checks_sasl_cleanup
# uncomment next line for postfix 2.2 and newer
# /^Received: (.*)/ REPLACE X-Auth-Received: $1
#
# must use next line for older postfixen.
/^Received: / IGNORE

--
Noel Jones