-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Mon, 24 Feb 2014, Charles Marcus wrote:
Date: Mon, 24 Feb 2014 09:44:15 -0500 From: Charles Marcus CMarcus@Media-Brokers.com Reply-To: Dovecot Mailing List dovecot@dovecot.org To: dovecot@dovecot.org Subject: Re: [Dovecot] realtime backup with LDA?
On 2/24/2014 9:25 AM, Steffen Kaiser skdovecot@smail.inf.fh-brs.de wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Mon, 24 Feb 2014, Charles Marcus wrote:
On 2/24/2014 3:58 AM, Steffen Kaiser skdovecot@smail.inf.fh-brs.de wrote:
I would add a BCC recipient in the MTA. It's more save in such situation. See the thread about qmail and multiple recipients for one mail address.
The only downside to this is all of the original headers are *not* preserved in the BCC copy.
Er, I don't know what you mean with "all of the original headers". There are no headers of the delivery process to user, that's right. Everything else should be untouchted. Or in other words, the backup copy does not "backup" the delivery process.
As Stan so graciously pointed out, I was talking about the specific MTA that I use - postfix - and I based my comment on the fact that everyone on the postfix list, including Wietse, stated that using the BCC method does *not* preserve all of the original message headers (identically to the non BCC'd copy).
Are you saying Wietse was incorrect?
What changes are made by default, that are not implemented by the MTA admin? And yes, if I have two recipients of one message, I expect the headers stay untouched. If we enter the discussion "shall the MTA remove the "for XYZ" from Received headers", if one add a recipient, I back out. :-)
Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux)
iQEVAwUBUwthl3D1/YhP6VMHAQKtaAf/SFASDui9ShrUK5CQb3ohwS43lf18OOFu nUcwuVD5oFO2GQ40ukTrwXAybJZIdG5wmmN6nxhVmUcKPd3bRe75hYLLdIwURgPD KYciseZ+lKGotIuLulE0uPsrQapXFDDcrJ5Heg3kAoIG9TH6EQ0vaXNexNnKnQ/F UPQwkcBFnVBmK3lFJwZKMAzsrjql1lRc+D2v9CZ3ras2HzfSKfHQ86w9LV2jBDsA 7wsf0wTXAKGqb54Z5LiIZQLw5EVJxyKqByH1kRzT/xWSbawmkk7sgPvo2P9IOoui oi9zSYIiOfMfVY0ZmfaCkR5AlK/QWej1JY4Ezs36zgAQkzSW2Sm8iQ== =kh35 -----END PGP SIGNATURE-----