Hi:
sorry for stupid me. I have read the document
http://postfix.cs.utah.edu/RESTRICTION_CLASS_README.html
and I understand " you can't specify a lookup table on the
right-hand side of a Postfix access table. This is because Postfix
needs to open lookup tables ahead of time"
now I want to
Wietse Venema
> Use a per-recipient table:
>
> /etc/postfix/main.cf
> check_recipient_access hash:/etc/postfix/recipient_access.pcre
>
> /etc/postfix/recipient_access.pcre
> /^me@/ FILTER blah:blah-
> /./ reject_unknown_sender_domain
>
> Wietse
thanks a lot for
Hi:
I want to filter all the mails send to filter...@example.com. so I
create configuration at main.cf like below:
smtpd_recipient_restrictions =
check_recipient_access hash:/etc/postfix/filter_access,
reject_unknown_sender_domain,
permit
and create filter_access like below
filter_m
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
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
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
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
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.
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
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
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
>> t
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
Wietse Venema
> If you deliver to file this way, the file needs to be writable by
> the $mail_owner user (default: postfix). The file will grow until
> the mailbox_size_limit is reached, then further delivery will fail.
> It may be possible to trigger one-file-per-message (maildir style)
> delive
hi:
I want to save every email copy to a Maildir format directory.
just like "always_bcc", but put the mails in some directory outside
normal mail storage area.
I wonder if this can be done with configuration, or I need to write
some transport script.
I tried to use "always_bcc=archive@loc
14 matches
Mail list logo
