Re: capture information for internal generated mails

2018-12-20 Thread d tbsky
Matus UHLAR - fantomas > archiving one copy of a mail is enough. If you need information about how > the mail was sent, you need archive logs, not another copy of e-mail. yes one copy of mail is enough. other redundant mails are just for extra information and will be abandoned after extract th

Re: capture information for internal generated mails

2018-12-20 Thread d tbsky
Dominic Raferd > I never heard of such requirement before. But the QueueID can be found in the > first Received: header in each archived email and you can match this with the > relevant smtp line for the outgoing delivery in the log file. You could > extract the relevant data from this line and

Re: capture information for internal generated mails

2018-12-20 Thread Dominic Raferd
On Thu, 20 Dec 2018 at 14:23, d tbsky wrote: > Matus UHLAR - fantomas > >> On 20.12.18 21:50, d tbsky wrote: > >>I don't know if it is easier. but what I want is three information: > >>the mail content, who send the mail, the mail send to whom. > > > >the latter 2 information is not available in

Re: capture information for internal generated mails

2018-12-20 Thread Matus UHLAR - fantomas
On 20.12.18 21:50, d tbsky wrote: I don't know if it is easier. but what I want is three information: the mail content, who send the mail, the mail send to whom. the latter 2 information is not available in mail header, unless you use dirty hacks. yes I think I already use some dirty hacks.

Re: capture information for internal generated mails

2018-12-20 Thread d tbsky
Matus UHLAR - fantomas >> On 20.12.18 21:50, d tbsky wrote: >>I don't know if it is easier. but what I want is three information: >>the mail content, who send the mail, the mail send to whom. > >the latter 2 information is not available in mail header, unless you use >dirty hacks. yes I think

Re: capture information for internal generated mails

2018-12-20 Thread Matus UHLAR - fantomas
Matus UHLAR - fantomas isn;t it easier to save one copy of mail with the logs, instead of two copied of mail, without logs? Note that logs will show e.g. when mail was refused by destination server, mail won't. On 20.12.18 21:50, d tbsky wrote: I don't know if it is easier. but what I want i

Re: capture information for internal generated mails

2018-12-20 Thread d tbsky
Matus UHLAR - fantomas > isn;t it easier to save one copy of mail with the logs, instead of two > copied of mail, without logs? > Note that logs will show e.g. when mail was refused by destination server, > mail won't. I don't know if it is easier. but what I want is three information: the mail

Re: capture information for internal generated mails

2018-12-20 Thread d tbsky
Wietse Venema > ... and sender_bcc_maps add the BCC recipient when email ARRIVES > (i.e. input) not when mail is DELIVERED (i.e. output). > > Wietse thanks for the clarify. so that's my misunderstanding.

Re: capture information for internal generated mails

2018-12-20 Thread Matus UHLAR - fantomas
Wietse Venema d tbsky: > Dominic Raferd > > The incoming email is saved by always_bcc, why is it important to save it again when it is relayed (still I presume with the same 'To:' header, but different envelope recipient) to gsmtp? You can find some information about the relay transaction i

Re: capture information for internal generated mails

2018-12-20 Thread d tbsky
Wietse Venema > > d tbsky: > > Dominic Raferd > > > The incoming email is saved by always_bcc, why is it important to save it > > > again when it is relayed (still I presume with the same 'To:' header, but > > > different envelope recipient) to gsmtp? You can find some information > > > about

Re: capture information for internal generated mails

2018-12-20 Thread Wietse Venema
d tbsky: > Dominic Raferd > > The incoming email is saved by always_bcc, why is it important to save it > > again when it is relayed (still I presume with the same 'To:' header, but > > different envelope recipient) to gsmtp? You can find some information about > > the relay transaction in the

Re: capture information for internal generated mails

2018-12-20 Thread Wietse Venema
d tbsky: > hi: >I want to bcc all mails for archive purpose. one kind of mail is like > below: > >outside user (a...@gmail.com) mail to -> postfix alias with settings > to forward outside (myal...@example.com) -> forward to outside user > (b...@gmail.com) > >"always_bcc" and "recip

Re: capture information for internal generated mails

2018-12-20 Thread Bastian Blank
On Thu, Dec 20, 2018 at 08:02:12PM +0800, d tbsky wrote: > I understand the information is in the log. but I need to archive this > information for auditing in the future. so I need this information > when postfix bcc the mail. > with other kind of received mails, I can use bcc_recipient_maps and >

Re: capture information for internal generated mails

2018-12-20 Thread d tbsky
Dominic Raferd > The incoming email is saved by always_bcc, why is it important to save it > again when it is relayed (still I presume with the same 'To:' header, but > different envelope recipient) to gsmtp? You can find some information about > the relay transaction in the mail log (smtp). Ex

Re: capture information for internal generated mails

2018-12-20 Thread Dominic Raferd
On Thu, 20 Dec 2018 at 11:19, d tbsky wrote: > Dominic Raferd > > > > On Thu, 20 Dec 2018 at 09:22, d tbsky wrote: > >> > >> hi: > >>I want to bcc all mails for archive purpose. one kind of mail is > like below: > >> > >>outside user (a...@gmail.com) mail to -> postfix alias with setti

Re: capture information for internal generated mails

2018-12-20 Thread d tbsky
Dominic Raferd > > On Thu, 20 Dec 2018 at 09:22, d tbsky wrote: >> >> hi: >>I want to bcc all mails for archive purpose. one kind of mail is like >> below: >> >>outside user (a...@gmail.com) mail to -> postfix alias with settings >> to forward outside (myal...@example.com) -> forward t

Re: capture information for internal generated mails

2018-12-20 Thread Dominic Raferd
On Thu, 20 Dec 2018 at 09:22, d tbsky wrote: > hi: >I want to bcc all mails for archive purpose. one kind of mail is like > below: > >outside user (a...@gmail.com) mail to -> postfix alias with settings > to forward outside (myal...@example.com) -> forward to outside user > (b...@gmail.

capture information for internal generated mails

2018-12-20 Thread d tbsky
hi: I want to bcc all mails for archive purpose. one kind of mail is like below: outside user (a...@gmail.com) mail to -> postfix alias with settings to forward outside (myal...@example.com) -> forward to outside user (b...@gmail.com) "always_bcc" and "recipient_bcc_maps" won't capture