-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Thu, 30 Jul 2009, Stephan Bosch wrote:
How do you look at adding one more header, for example X-Sieve-Forward-From:
Now, when redirect action is in use - mail forwards using sendmail command line interface. The problem that there is no suitable way to know which user's script has generate redirect. Received: header may contain envelope receiver but this is valid if only 1 "rcpt to:" command was specified on SMTP session. This invokes problem when forwarding mail to non-local domains, breaking such things like SPF. I'd like to setup SRS for fixing this, but I don't know sender("sieve local user") mail. Adding one header with valid local user e-mail address will fix this. Google add 2 headers for this - X-Forwarded-To: and X-Forwarded-For: .
What do you think about this ? I have no objection, but then again my experience on this subject is pretty bleak. Does anyone else have comments?
Basically I like the idea.
I've seen
X-Resent-By: Forwarder <email@hoster.example.com> X-Resent-For: steffen@example.com X-Resent-To: kaiser@example.net
inserted by one of my hosters.
Pine adds RFC 2822 sec 3.6.6 style headers (RFC 4021 sec 2.1.14 ff.)
ReSent-Date: Thu, 30 Jul 2009 14:36:18 +0200 (CEST) ReSent-From: re-sender ReSent-To: new recipients ReSent-Subject: new Subject ReSent-Message-ID: New msgid ReSent-User-Agent: New MUA id string
However, the section starts with: "Resent fields SHOULD be added to any message that is reintroduced by a user into the transport system." Dunno, if "by a user" applies to Sieve, too.
IMHO, it should be customizable.
Bye,
Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux)
iQEVAwUBSnGWi3WSIuGy1ktrAQLUYggAw/BXIWXFEPw4pKpKpTbvufnsXLpP4Qew GGo/9URurlk1TXPHywvLpgvRIQsfpe8elfqWmpiwMi56uIdXcDTY0rQ1TQ5HvlP2 3hqTGmKPF9y33HikCTTR9ZxVf9aebHDAkLKWeFyKNR6it4KCc1L9y2b2ebxhmrWj u8vSX2tzeghr5XMHoowz8JMo3VdGnti6SBjeIOVHFeyVZSuNlXitZwLdPmTG7WEz sqkqEvPJv3tXppDOahyayTu4SG9PkfKIv/Oe0Rsl7eQg3Lg5UK+uRmiJlA1KZnt1 SqGoTnqnDs4vBS8x6w70YxL+7rHwtMW9rZv9RBVt8pC8Lr6RkRanEw== =AN8H -----END PGP SIGNATURE-----