Re: postfix reject_unverified_recipient and Exchange 2016
On 9/7/2016 3:42 AM, Nicola Piazzi wrote: > > > > I have a problem using reject_unverified_recipient to verify under > Exchange 2016 that I don’t have with Exchange 2010 > This is the wrong list for this question. Please ask this on the postfix-users list for a solution. http://www.postfix.org/documentation.html http://www.postfix.org/ADDRESS_VERIFICATION_README.html http://www.postfix.org/postconf.5.html#smtp_address_verify_target
Re: postfix reject_unverified_recipient and Exchange 2016
Am 07.09.2016 um 11:00 schrieb Nicola Piazzi: I am off topic if you think that postfix is not spamassassin I think that this is not a Microsoft problem because exchange answer correctly to unknown recipients I suppose that there is something in the return string that postix doesn’t like postfix don't parse strings, postfix is just interested in the 3-digit response code where 2xx means "OK", 4xx "temporary problem" and 5xx "permanent problem don't come back" "250 2.1.5 Recipient OK" is a corret answer to unknown recipients? since when? Here Exchange 2016 at port 25 that verify unknown recipient at DATA phase telnet 10.1.1.126 25 220 GEMMA.gruppocomet.net Microsoft ESMTP MAIL Service ready helo me 250 GEMMA.gruppocomet.net Hello [10.2.6.4] mail from:e...@ext.com 250 2.1.0 Sender OK rcpt to:doesntex...@gruppocomet.it 250 2.1.5 Recipient OK
Re: postfix reject_unverified_recipient and Exchange 2016
Am 07.09.2016 um 10:42 schrieb Nicola Piazzi: I have a problem using reject_unverified_recipient to verify under Exchange 2016 that I don’t have with Exchange 2010 how is that a spamassassin or even postfix related problem? call the microsoft support why their stuff is playing backscatter in recent versions (as you can see by all that exchange bounces flying around in the web) there is nothing the delivery software can do when exchange has no clue about it's valid rcpt's until it received and acknolwedged the full message instead just reject the rcpt workaround: list your vaild RCPT's diretly on your inboud MX and maintain it parallel to exchange Postfix is used to send and receive mail and is between the internet and the internal Exchange Server Now, when an internet user send an email to our domain postfix verify it making an rcptto to our exchange using reject_unverified_recipient instruction This worked well with Exchange 2010 but now with Exchange 2016 doesn’t work. Exchange 2016 needs the installation of Recipient Filter Agent and obviously I installed it. Now we have Frontend Transport that answer at port 25 and verify recipient at DATA phase and the Hub Transport that answer at port 2525 and verify recipient at RCPT TO Here Exchange 2016 at port 25 that verify unknown recipient at DATA phase telnet 10.1.1.126 25 220 GEMMA.gruppocomet.net Microsoft ESMTP MAIL Service ready helo me 250 GEMMA.gruppocomet.net Hello [10.2.6.4] mail from:e...@ext.com 250 2.1.0 Sender OK rcpt to:doesntex...@gruppocomet.it 250 2.1.5 Recipient OK data 354 Start mail input; end with . some data
