On Tue, Feb 03, 2015 at 06:44:19AM +0100, Olivier CALVANO wrote:
> Jan 19 06:27:36 mx postfix/postscreen[3102]: NOQUEUE: reject: RCPT from
> [59.24.94.42]:22640: 550 5.7.1 Service unavailable; client [59.24.94.42]
> blocked using zen.spamhaus.org; from=<ttruedale...@indaai.com>, to=<
> myu...@mydomain.com>, proto=ESMTP, helo=<[59.24.94.42]>
>
> i want add message-id=<the msg id>
The postscreen(8) daemonn is not psychic. Since it rejects the
message envelope it never gets to see the message content.
> Jan 19 06:38:15 mx postgrey[616]: action=greylist, reason=new, client_name=
> p11144.yakapi.com, client_address=197.12.68.144, sender=nore...@obfea.com,
> recipient=myu...@mydomain.com
>
> Jan 19 06:38:15 mx postfix/smtpd[3494]: NOQUEUE: reject: RCPT from
> p11144.yakapi.com[197.12.68.144]: 450 4.2.0 <myu...@mydomain.com>:
> Recipient address rejected: Greylisting; from=<nore...@obfea.com> to=<
> myu...@mydomain.com> proto=ESMTP helo=<p11144.yakapi.com>
This is only possible if you call the policy service for the final
verdict during smtpd_end_of_data_restrictions. It would likely
also need to be called earlier to accumulate the message envelope
so it can make suitable decisions. Even in that case (with a custom
variant of postgrey someone would have to write), the policy daemon
would have the message-id, but the cleanup service will have logged
it.
--
Viktor.
