-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Mon, 1 Feb 2010, Timo Sirainen wrote:
It's beginning to sound like I should add "lmtp_headers" setting where
you could do all kinds of "interesting" things like:
lmtp_headers = \
Return-Path: %f\n \
Envelope-To: %t\n \
X-Envelope-To: %t\n \
X-Original-To: %t\n \
Delivered-To: %t\n
Charles wrote:
"Dunno if it is different, but I like having the X-Original-To header -
it lets me see that the message was originally was to an alias (when it
was)."
In LMTPd it is to late to insert that information, therefore I would
change the syntax a bit, e.g.
@X-Original-To: %t\n
+X-Original-To: %t\n
X-Original-To: %t\n
"@" forces to overwrite existing headers, "+" adds another header, none
adds the header if none is present.
In Charles's case, the no-prefix variant would be ideal, because usually
the MTA has to insert that information, but the user can rely on the
existance of the header - as a fallback added by lmtpd.
For local headers the value should overwrite any existing header passed
from the outside.
===
Oh, the syntax should probably allow spaces in the value :-)
Regards,
- --
Steffen Kaiser
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iQEVAwUBS2fng7+Vh58GPL/cAQJtwQgAkCmhBz+IwrWHR28bcJiZYbMx1Ci1Lhv/
clsI7hkEf7nwrJVdyYL0SVo2M1Y1h+dzvFz2CEw8XRVSOj0+V3EAmjEBb/Ws9Atj
TkE5myFswBeu3TBNRH2BXHmOD9gqeSEger2fQ+x5dvVTqt3vKxkne9uQa05C30r4
nKImvNavjRifot067/sndF6Jaj+6N8ZjpY0oWYabQ9cNQV4mnNOqpzhSMhcH03Cu
QWGYJZxonvqcaaaQnZLVAh9hmI4anG+hM8gUaxZNO8+mnoDhMNzeL94ortCUc/ES
wuo7MaZ26/yyF+JaBRqVIg1NT8wCqP6XnNj+dZ+bxiLF4qarfWbt+w==
=x3p/
-----END PGP SIGNATURE-----
