Re: problem with recipient address verification

wietse: If it is DATA, then address verification is possible but it requires source code changes to Postfix: - After successful RCPT TO, do not assume that the recipient exists, but send DATA and disconnect after the DATA response is received. This will cause extra noise in the logfile,

Re: problem with recipient address verification

Erwin Authried: Is this the reply to DATA or end-of-data? If it is DATA, then address verification is possible but it requires source code changes to Postfix: - After successful RCPT TO, do not assume that the recipient exists, but send DATA and disconnect after the DATA response

questions about adress verify

Hi am i right that with the settings below refresh_time is implicit disabled without side-effects? i don't want pro-active sender-verification refresh while i can live with the once per 24h pseudo greylisting in case of rcpt-verification address_verify_positive_expire_time = 24h

Re: questions about adress verify

li...@rhsoft.net: Hi am i right that with the settings below refresh_time is implicit disabled without side-effects? i don't want pro-active sender-verification refresh while i can live with the once per 24h pseudo greylisting in case of rcpt-verification Don't do that. The proactive

Re: problem with recipient address verification

Am Samstag, den 27.12.2014, 08:23 -0500 schrieb Wietse Venema: Erwin Authried: Is this the reply to DATA or end-of-data? If it is DATA, then address verification is possible but it requires source code changes to Postfix: - After successful RCPT TO, do not assume that the

Re: questions about adress verify

Am 27.12.2014 um 14:37 schrieb Wietse Venema: li...@rhsoft.net: am i right that with the settings below refresh_time is implicit disabled without side-effects? i don't want pro-active sender-verification refresh while i can live with the once per 24h pseudo greylisting in case of

Re: problem with recipient address verification

Erwin Authried: Shouldn't postfix reject a message in general if there is a 5xx response to the DATA command, instead of creating a bounce message? Postfix address verification (via SMTP) never sends DATA. It sends RSET/QUIT instead. Thus, the question makes no sense. I wasn't

Re: questions about adress verify

li...@rhsoft.net: for negative in case of sender-verification and flooded forged addresses not so because it means asking the not involved server (gmail and so on) again even if no future attempt with that sender happens You don't understand how Postfix works. The refresh is made ONLY when

Re: questions about adress verify

Am 27.12.2014 um 16:33 schrieb Wietse Venema: li...@rhsoft.net: for negative in case of sender-verification and flooded forged addresses not so because it means asking the not involved server (gmail and so on) again even if no future attempt with that sender happens You don't understand how

PATCH: verify after DATA (problem with recipient address verification)

is documentation and user interface stuff. Wietse 20141227 Feature: smtp_address_verify_target (default: rcpt) that determines what protocol stage decides if a recipient is valid. Specify data for servers that reject recipients after the DATA command. mantools

Re: PATCH: verify after DATA (problem with recipient address verification)

On 12/27/2014 10:07 AM, Wietse Venema wrote: Patch follows. Most if not all *should* also work with Postfix 2.11 and possibly earlier versions. This introduces a new parameter smtp_address_verify_target (default: rcpt) that can be set to data for qmail-like servers. What are your thoughts

Re: [Fwd: Multiple PTR and reject_unknown_helo_hostname]

On 23 Dec 2014, at 8:32, James B. Byrne wrote: We have an smtpd_helo_restriction of reject_unknown_helo_hostname that regularly fails for one of our (very) large correspondents. As it turns out the reason is quite legitimate, the helo identity fqdn issued from several of their email gateways

Re: PATCH: verify after DATA (problem with recipient address verification)

Noel Jones: On 12/27/2014 10:07 AM, Wietse Venema wrote: Patch follows. Most if not all *should* also work with Postfix 2.11 and possibly earlier versions. This introduces a new parameter smtp_address_verify_target (default: rcpt) that can be set to data for qmail-like servers. What

Re: Yet another relay access denied problem

Hi Wietse and Istvan, thanks for pointing me to my error with the version. Was too busy digging for information and overlooked the obvious. I realized that my real problem is that SASL auth is not working. Would like to get it from dovecot, but as long as it works I'm fine with cyrus, too.

Re: Yet another relay access denied problem

Doubt if this is the cause but I just noticed this and was curious if it would cause problems. You have inet_protocols as ipv4 and have ipv6 notation under mynetworks. Again not sure about this, but do these exist and why can't you do better? smtpd_tls_cert_file =

Re: Yet another relay access denied problem

Jonathan Hermann: Hi Wietse and Istvan, thanks for pointing me to my error with the version. Was too busy digging for information and overlooked the obvious. I realized that my real problem is that SASL auth is not working. Would like to get it from dovecot, but as long as it works I'm

Re: PATCH: verify after DATA (problem with recipient address verification)

Wietse Venema: A. Schulze: wietse: If it is DATA, then address verification is possible but it requires source code changes to Postfix: - After successful RCPT TO, do not assume that the recipient exists, but send DATA and disconnect after the DATA response is