Question related to reject_unverified_recipient

Hi Group,

I have set up Postfix to forward mail from and to our Domino Server. To
avoid queueing mails that cannot be delivered to Domino I have
configured Postfix to ask Domino if a user exists while receiving a mail
and eventually rejecting the mail right away. No problem. When the
Domino server rejects a user, Postfix rejects the mail with code 550.

But if the Domino server is down for some reason, Postfix also rejects
the mail, but with code 450.

So far everything works correctly as it's written in the docs:
http://www.postfix.org/postconf.5.ht...fied_recipient

But now I want to configure that Postfix queues all mails as long as the
Domino server is down and not rejecting them with code 450. How can I
achieve that?

Related options in main.cf

smtpd_recipient_restrictions = permit_mynetworks,
reject_unauth_destination, reject_unknown_recipient_domain,
reject_unverified_recipient

unverified_recipient_reject_code = 550

Thanks in advance

Peter

Peter Fahsel wrote:
> Hi Group,
>
> I have set up Postfix to forward mail from and to our Domino Server. To
> avoid queueing mails that cannot be delivered to Domino I have
> configured Postfix to ask Domino if a user exists while receiving a mail
> and eventually rejecting the mail right away. No problem. When the
> Domino server rejects a user, Postfix rejects the mail with code 550.
>
> But if the Domino server is down for some reason, Postfix also rejects
> the mail, but with code 450.
>
> So far everything works correctly as it's written in the docs:
> http://www.postfix.org/postconf.5.ht...fied_recipient
>
> But now I want to configure that Postfix queues all mails as long as the
> Domino server is down and not rejecting them with code 450. How can I
> achieve that?
>
> Related options in main.cf
>
> smtpd_recipient_restrictions = permit_mynetworks,
> reject_unauth_destination, reject_unknown_recipient_domain,
> reject_unverified_recipient
>
> unverified_recipient_reject_code = 550
>
> Thanks in advance
>
> Peter


What might work for you is to increase the expiry values of
the cached database, especially the negative probes which are set
to a low value. These are the latest default values:

address_verify_positive_expire_time (31d)
The time after which a successful probe expires from the
address verification cache.

address_verify_positive_refresh_time (7d)
The time after which a successful address verification probe
needs to be refreshed.

address_verify_negative_cache (yes)
Enable caching of failed address verification probe results.

address_verify_negative_expire_time (3d)
The time after which a failed probe expires from the address
verification cache.

address_verify_negative_refresh_time (3h)
The time after which a failed address verification probe needs
to be refreshed.


--
Greg