On 2014-10-10 16:26, Wietse Venema wrote:
> Jan P. Kessler:
Or what the limitations are.
>>> Note that you can not return different results for different
>>> recipients at data or end_of_data stage. You can only pass or reject
>>> the whole mail at all.
>>>
>> p.s. the policy server example
Jan P. Kessler:
>
> >> Or what the limitations are.
> >
> > Note that you can not return different results for different
> > recipients at data or end_of_data stage. You can only pass or reject
> > the whole mail at all.
> >
>
> p.s. the policy server example included in the postfix docs would
Or what the limitations are.
Note that you can not return different results for different
recipients at data or end_of_data stage. You can only pass or reject
the whole mail at all.
p.s. the policy server example included in the postfix docs would break.
substr(0,512) is to small for a
Patrik B?t:
> I'm writing a incoming policy daemon and want to look where the mail
> ends up, if there is more then 1 recipient I'm out to just see
> rcpt_count, that will not state the destinations.
Invoke the policy service in smtpd_recipient_restrictions, so that
it will be invoked once per rec
"The "recipient" attribute is available in the "RCPT TO" stage. It is
also available in the "DATA" and "END-OF-MESSAGE" stages if Postfix
accepted only one recipient for the current message."
You can use the instance attribute to collect the list of recipients at
RCPT TO stage. That informati
Hello!
Is there ever going to be a recipient(s) attribute from postfix to
policy daemon?
"The "recipient" attribute is available in the "RCPT TO" stage. It is
also available in the "DATA" and "END-OF-MESSAGE" stages if Postfix
accepted only one recipient for the current message."
Or might I requ
