On 2/6/2013 3:57 PM, Daniel L. Miller wrote: > On 2/6/2013 1:53 PM, Wietse Venema wrote: >> Daniel L. Miller: >>>> reject_unverified_recipient will stop as soon as it has a reply >>>> from the SMTP server (or from the local verify cache). >>>> >>>> If that result is "4XX Come back in a few seconds", then >>>> reject_unverified_recipient will not wait for a few seconds. >>>> >>> Thank you. Is there an adjustment that will? Or is the manual >>> client >>> step my only option? >> To sound like a broken record, reject_unverified_recipient will >> stop when it has a reply from the remote SMTP server (or from the >> local verify cache). >> >> Just don't use reject_unverified_recipient for remote destinations. > > It's quite possible I'm using this wrong - but other than the slight > hiccup I'm seeing with more servers adopting minimal greylisting I > LIKE having the recipient verification. As I said - it gives the > users immediate feedback. > > Otherwise when they send a message to "u...@domian.com", the client > hands it off - the user thinks the message actually sent when in > reality they will get a rejection message some time later. And for > my technology-challenged users... >
Sorry, using reject_unverified_recipient with outgoing mail is simply not practical because of greylisting. There is no way postfix can be configured to keep asking some remote server until it gets the answer it wants. Seems like a good way to get blacklisted... Your job is to explain to your non-techie users that email is a store-and-forward system that values reliability over instant access, and CANNOT give instant delivery confirmation. -- Noel Jones
