Re: sender verification on lowest MX?

19 msg	postmap can't always find keys
3 msg	deliver mail to different servers but in same d...
4 msg	corrupted queue

sender verification on lowest MX?
\ martin f krafft (26 Nov 2007)
. \ Noel Jones (26 Nov 2007)
. . \ martin f krafft (26 Nov 2007)
. . . \ Noel Jones (26 Nov 2007)
. . . . \ martin f krafft (26 Nov 2007)
. . . . . \ Noel Jones (26 Nov 2007)

4 msg	Disable reject_unknown_sender_domain for certai...
2 msg	Supress ErrorMail from piped Script
7 msg	Mail archive solution
4 msg	4xx code is returned when next hop gives 5xx
2 msg	domain alias and recipient check
2 msg	postfix delivering to a cyrus-mupdate setup
3 msg	Outbound support for confirmations
2 msg	Basic distribution list query?
9 msg	rejecting 'unknown client', but manual lookup w...
10 msg	dict_get
3 msg	virtual hosts and outgoing email question
4 msg	unable to execute postdrop?
4 msg	Literal IP helo
2 msg	Header fields inserted by a milter glued with t...
7 msg	Policy daemon - return multiples recipients
2 msg	restrict mass mail

Subject:	Re: sender verification on lowest MX?
Group:	Postfix-users
From:	Noel Jones
Date:	26 Nov 2007

martin f krafft wrote:
> also sprach Noel Jones <njones> [2007.11.26.1844 +0100]:
>> I wasn't clear enough. If the *connection* fails to the 1st MX so that
>> postfix doesn't get an answer, or of the 1st MX says 450 try later, postfix
>> will immediately try the next MX. This is correct behavior.
>
> Right, I agree, and I am aware. The first MX greylisted me, so
> return 4xx. What I wonder about is that postfix never tried it
> again. From that first try, it only ever tried to talk to the second
> MX, which is unreachable.
>

Postfix will try the primary MX on the next scheduled delivery
attempt.

In the case of reject_unverified_sender, the answer from a
previous probe will be cached for address_verify_{positive,
negative}_expire_time, and no new probes will be sent for at
least address_verify_{positive, negative}_refresh_time.

--
Noel Jones