dovecot - Feb 2014 - realtime backup with LDA?

On 2/24/2014 10:13 AM, Steffen Kaiser <skdovecot at smail.inf.fh-brs.de>
wrote:
>
> What changes are made by default, that are not implemented by the MTA 
> admin?
Sorry, I don't understand the question (language thing I'm sure).

I'm talking about the 'always_bcc' feature in postfix, which
obviously
must be enabled by the MTA sysadmin.
> 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. :-)
I don't recall the specifics of the differences, but after the 
differences were discussed on list, they were enough that some people 
said it was not satisfactory for the legal requirements for mail archiving.

-- 

Best regards,

Charles

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

On Mon, 24 Feb 2014, Charles Marcus wrote:
> On 2/24/2014 10:13 AM, Steffen Kaiser <skdovecot at
smail.inf.fh-brs.de> wrote:
>> 
>> What changes are made by default, that are not implemented by the MTA 
>> admin?
>
> Sorry, I don't understand the question (language thing I'm sure).
Doesn't matter with always_bcc :-)
> I'm talking about the 'always_bcc' feature in postfix, which
obviously must
> be enabled by the MTA sysadmin.
Ah, OK. But this is not what I meant, because it would sent all messages 
to one and a single mail address, for all users, right? I mean to add a 
BCC per user to "user"_backup, like a per user alias or forward.

A message to user A is "split" into a message to user A and A_backup, 
where the new message to user A is not split again.

- -- 
Steffen Kaiser
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iQEVAwUBUwtv2XD1/YhP6VMHAQJ2ogf+NPnVnFTeY95938ZreunCK6iQW4LEpS+m
pBoG2YsxlQMsPWtIsi702R3WqFgBdGVYLKRI91ikrfpjqNFL3YIqmfsmJ63Skm8W
RxuYU2UPWJExWot3v0WJXntB5hy22qDG7lelfqI+5DdeWtls1vW1y9XiHkSldOQL
29ZtCxqkiYC1XHAbEIdO70v3DVd9GVzzkfQ3bY2zPH85+5ntsBkppM/G3jhu+kuh
hIXAFYcfVN7MuqTPE2FkoUZCB/2HlkG2wzDGJiqReYfCy2Sp5ejScPtRdUupKD5P
lyROk+d9+tBcfaMMtoe9IWNwb2HLw6JnSvzqhp36/H1D9dXkRYhXqg==y9GX
-----END PGP SIGNATURE-----