Re: Problem with recipient address verification

2015-10-13 Thread Wietse Venema
Fredrik Sandstr?m: [ Charset ISO-8859-1 converted... ] > What's up with this? The result of the probe is "deliverable", but > postfix rejects the message with a 450 code. > > Oct 13 11:12:52 smtp5 postfix/smtpd[5261]: connect from > mail-vk0-f43.google.com[209.85.213.43] > Oct 13 11:12:52 smtp

Problem with recipient address verification

2015-10-13 Thread Fredrik Sandström
What's up with this? The result of the probe is "deliverable", but postfix rejects the message with a 450 code. Oct 13 11:12:52 smtp5 postfix/smtpd[5261]: connect from mail-vk0-f43.google.com[209.85.213.43] Oct 13 11:12:52 smtp5 postfix/cleanup[5012]: AC5E08029F: message-id=<20151013081252.

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

2014-12-28 Thread Wietse Venema
> I did not have time to fully test this patch, and guess what, some > untested code does not work. I'll send a revised version Sunday. An updated patch for Postfix 2.10 and 2.11 can be found on the source-code mirrors, for example: ftp://ftp.porcupine.org/mirrors/postfix-release/experimental/fea

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

2014-12-27 Thread Wietse Venema
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

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

2014-12-27 Thread Wietse Venema
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 serv

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

2014-12-27 Thread 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 are your tho

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

2014-12-27 Thread 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 received. > > > >

Re: problem with recipient address verification

2014-12-27 Thread Wietse Venema
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. > >

Re: problem with recipient address verification

2014-12-27 Thread Erwin Authried
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 t

Re: problem with recipient address verification

2014-12-27 Thread 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 recipient exists, > > but send DATA and disconnect after the DATA

Re: problem with recipient address verification

2014-12-27 Thread 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 received. This will cause extra noise in the logfile, t

Re: problem with recipient address verification

2014-12-26 Thread Erwin Authried
Am Freitag, den 26.12.2014, 18:35 -0500 schrieb Wietse Venema: > Wietse Venema: > > Erwin Authried: > > > I'm routing messages to a couple of servers with the transport map > > > mechanism. I'm using recipient address verification to avoid bounce > > > messages. This works fine with mail servers th

Re: problem with recipient address verification

2014-12-26 Thread Erwin Authried
Am Freitag, den 26.12.2014, 18:35 -0500 schrieb Wietse Venema: > Wietse Venema: > > Erwin Authried: > > > I'm routing messages to a couple of servers with the transport map > > > mechanism. I'm using recipient address verification to avoid bounce > > > messages. This works fine with mail servers th

Re: problem with recipient address verification

2014-12-26 Thread Wietse Venema
Wietse Venema: > Erwin Authried: > > I'm routing messages to a couple of servers with the transport map > > mechanism. I'm using recipient address verification to avoid bounce > > messages. This works fine with mail servers that send a 550 response, > > for example: > > > > RCPT TO: non-existent-u

Re: problem with recipient address verification

2014-12-26 Thread Wietse Venema
Erwin Authried: > I'm routing messages to a couple of servers with the transport map > mechanism. I'm using recipient address verification to avoid bounce > messages. This works fine with mail servers that send a 550 response, > for example: > > RCPT TO: non-existent-u...@somedomain.com > 550 5.7.

problem with recipient address verification

2014-12-26 Thread Erwin Authried
I'm routing messages to a couple of servers with the transport map mechanism. I'm using recipient address verification to avoid bounce messages. This works fine with mail servers that send a 550 response, for example: RCPT TO: non-existent-u...@somedomain.com 550 5.7.1 Unable to deliver to non-exi