>
> On 19.10.17 17:01, A. Schulze wrote:
>
>> it's simpler.
>> you do not need a separate transport to enforce
>> destination_recipient_limit=1
>>
>> pcrefile:
>> /(.+)@(.+)/ someuser+${1}_at_${2}@archive
>> /(.*)/ someuser+${1}@archive
>>
>> main.cf:
>> recipient_bcc_maps = pcre:/path/to/p
A. Schulze:
(braindump, I'll post an update tomorrow if I'm wrong...)
pcrefile:
/^(.+)\@(.+)$/ someuser+$1_at_$2@archive
transport_maps:
archivesmtp_to_archive:
main.cf:
recipient_bcc_maps = pcre:/path/to/pcrefile
transport_maps = hash:/path/to/transport_maps
smtp_to_archive_destina
A. Schulze:
(braindump, I'll post an update tomorrow if I'm wrong...)
pcrefile:
/^(.+)\@(.+)$/ someuser+$1_at_$2@archive
transport_maps:
archive smtp_to_archive:
main.cf:
recipient_bcc_maps = pcre:/path/to/pcrefile
transport_maps = hash:/path/to/transport_maps
smtp_to_archive_de
Am 18.10.2017 um 14:54 schrieb Tavolodo Bela:
> Hello,
>
> I have a mail server running postfix, and another server running an email
> archive software
> which can talk smtp.
>
> Postfix is configured to pass a copy of each emails to the archive, using
> always_bcc = someuser@archive
>
> When
On 18.10.17 14:54, Tavolodo Bela wrote:
So my question is that is it possible that when customer1 sends an email to
customer2
then to send a bcc email to customer1@archive address, and another to
customer3@achive
address?
Have you tried sender_bcc_maps and recipient_bcc_maps with different bcc
Hello,
I have a mail server running postfix, and another server running an email
archive software
which can talk smtp.
Postfix is configured to pass a copy of each emails to the archive, using
always_bcc = someuser@archive
When an email is received it's copied to the archive properly, so far, so
