On 27 April 2014 16:52, Christian Rößner <c...@sys4.de> wrote: > The milter is using callbacks, which are called from Postfix in each of its > smtpd_*_restrictions. So if you have something like reject_unauth_destination > inside smtpd_recipient_restrictions, I would guess that Postfix will stop at > the RCPT TO stage. And even if you have smtpd_delay_reject=yes (default), the > error response is not part of the message and the milter won't see it.
This, and what Wietse said, makes sense to me - I understand why the message that was an attempted relay email would not be seen by the milter. Sorry, I didn't explain myself well, the thing I don't understand is why the notification email, sent to the postmaster, is not processed by the milter. A sample notification is below. -tom Return-Path: <double-bou...@mail.ritter.vg> X-Original-To: postmaster Delivered-To: postmas...@mail.ritter.vg Received: by mail.ritter.vg (Mail) id 8D8C725404E; Mon, 28 Apr 2014 06:34:01 -0400 (EDT) Date: Mon, 28 Apr 2014 06:34:01 -0400 (EDT) From: Mail Delivery System <mailer-dae...@mail.ritter.vg> To: Postmaster <postmas...@mail.ritter.vg> Subject: Mail SMTP server: errors from 114-43-1-25.dynamic.hinet.net[114.43.1.25] Message-Id: <20140428103401.8d8c7254...@mail.ritter.vg> Transcript of session follows. Out: 220 mail.ritter.vg ESMTP Mail In: HELO 66.175.214.151 Out: 250 mail.ritter.vg In: MAIL FROM: <1...@163.com> Out: 250 2.1.0 Ok In: RCPT TO: <sanjinn...@yahoo.com.tw> Out: 454 4.7.1 <sanjinn...@yahoo.com.tw>: Relay access denied Session aborted, reason: lost connection For other details, see the local mail logfile
