You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by Nicola Piazzi <Ni...@gruppocomet.it> on 2016/09/07 08:42:58 UTC
postfix reject_unverified_recipient and Exchange 2016
I have a problem using reject_unverified_recipient to verify under Exchange 2016 that I don't have with Exchange 2010
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 rcpt to 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:ext@ext.com
250 2.1.0 Sender OK
rcpt to:doesntexist@gruppocomet.it
250 2.1.5 Recipient OK
data
354 Start mail input; end with <CRLF>.<CRLF>
some data
.
550 5.1.10 RESOLVER.ADR.RecipientNotFound; Recipient not found by SMTP address lookup
Here Exchange 2016 at port 2525 that verify unknown recipient at RCPT TO phase
telnet 10.1.1.126 2525
220 GEMMA.gruppocomet.net Microsoft ESMTP MAIL Service ready
helo me
250 GEMMA.gruppocomet.net Hello [10.2.6.4]
mail from:ext@ext.com
250 2.1.0 Sender OK
rcpt to:doesntexist@gruppocomet.it
550 5.1.10 RESOLVER.ADR.RecipientNotFound; Recipient not found by SMTP address lookup
When I connect to a Postfix configured with reject_unverified_recipient it doesn't work
I tried to transport domain to Exchange at port 2525 and at port 25 using the parameter smtp_address_verify_target = data
Postfix answer OK at RCPT TO of doesntexist@gruppocomet.it<ma...@gruppocomet.it> and need some time to answer, so I suppose that it make the call to Exchange
RCPT TO is immediate if I remove reject_unverified_recipient
Nicola Piazzi
CED - Sistemi
COMET s.p.a.
Via Michelino, 105 - 40127 Bologna - Italia
Tel. +39 051.6079.293
Cell. +39 328.21.73.470
Web: www.gruppocomet.it<http://www.gruppocomet.it/>
[Descrizione: gc]
Re: postfix reject_unverified_recipient and Exchange 2016
Posted by Noel <no...@gmail.com>.
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 dont 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: R: R: postfix reject_unverified_recipient and Exchange 2016
Posted by Antony Stone <An...@spamassassin.open.source.it>.
On Wednesday 07 September 2016 at 11:00:57, Nicola Piazzi wrote:
> I am off topici f you think that postfix is not spamassassin
Postfix is not spamassassin.
Antony.
--
The Royal Society for the Prevention of Cruelty to Animals was formed in 1824.
The National Society for the Prevention of Cruelty to Children was not formed
until 1884.
That says something about the British.
Please reply to the list;
please *don't* CC me.
Re: postfix reject_unverified_recipient and Exchange 2016
Posted by "lists@rhsoft.net" <li...@rhsoft.net>.
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\u2019t 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:ext@ext.com
250 2.1.0 Sender OK
rcpt to:doesntexist@gruppocomet.it
250 2.1.5 Recipient OK
R: R: postfix reject_unverified_recipient and Exchange 2016
Posted by Nicola Piazzi <Ni...@gruppocomet.it>.
I am off topici f 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
Nicola Piazzi
CED - Sistemi
COMET s.p.a.
Via Michelino, 105 - 40127 Bologna – Italia
Tel. +39 051.6079.293
Cell. +39 328.21.73.470
Web: www.gruppocomet.it
-----Messaggio originale-----
Da: Axb [mailto:axb.lists@gmail.com]
Inviato: mercoledì 7 settembre 2016 10:59
A: users@spamassassin.apache.org
Oggetto: Re: R: postfix reject_unverified_recipient and Exchange 2016
This is totally off topic.
You are on the wrong list for these questions.
Use the MS knowledge base.
On 09/07/2016 10:56 AM, Nicola Piazzi wrote:
> It seems NOT a Microsoft problem because with "Recipient Filter Agent"
> exchange answer "550 5.1.10 RESOLVER.ADR.RecipientNotFound; Recipient
> not found by SMTP address lookup" when a recipient is not found So I don't know why when postfix get "550 5.1.10 RESOLVER.ADR.RecipientNotFound; Recipient not found by SMTP address lookup" from Exchange 2016 it doesn't consider unexistant that recipient Someone can write me the answer of Exchange 2010 to a non existant recipient ?
>
>
>
>
>
> Nicola Piazzi
> CED - Sistemi
> COMET s.p.a.
> Via Michelino, 105 - 40127 Bologna - Italia Tel. +39 051.6079.293
> Cell. +39 328.21.73.470
> Web: www.gruppocomet.it
>
>
> -----Messaggio originale-----
> Da: lists@rhsoft.net [mailto:lists@rhsoft.net]
> Inviato: mercoledì 7 settembre 2016 10:49
> A: users@spamassassin.apache.org
> Oggetto: 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:ext@ext.com
>> 250 2.1.0 Sender OK
>> rcpt to:doesntexist@gruppocomet.it
>> 250 2.1.5 Recipient OK
>> data
>> 354 Start mail input; end with <CRLF>.<CRLF> some data
Re: R: postfix reject_unverified_recipient and Exchange 2016
Posted by Axb <ax...@gmail.com>.
This is totally off topic.
You are on the wrong list for these questions.
Use the MS knowledge base.
On 09/07/2016 10:56 AM, Nicola Piazzi wrote:
> It seems NOT a Microsoft problem because with "Recipient Filter Agent" exchange answer "550 5.1.10 RESOLVER.ADR.RecipientNotFound; Recipient not found by SMTP address lookup" when a recipient is not found
> So I don't know why when postfix get "550 5.1.10 RESOLVER.ADR.RecipientNotFound; Recipient not found by SMTP address lookup" from Exchange 2016 it doesn't consider unexistant that recipient
> Someone can write me the answer of Exchange 2010 to a non existant recipient ?
>
>
>
>
>
> Nicola Piazzi
> CED - Sistemi
> COMET s.p.a.
> Via Michelino, 105 - 40127 Bologna - Italia
> Tel. +39 051.6079.293
> Cell. +39 328.21.73.470
> Web: www.gruppocomet.it
>
>
> -----Messaggio originale-----
> Da: lists@rhsoft.net [mailto:lists@rhsoft.net]
> Inviato: mercoledì 7 settembre 2016 10:49
> A: users@spamassassin.apache.org
> Oggetto: 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:ext@ext.com
>> 250 2.1.0 Sender OK
>> rcpt to:doesntexist@gruppocomet.it
>> 250 2.1.5 Recipient OK
>> data
>> 354 Start mail input; end with <CRLF>.<CRLF> some data
R: postfix reject_unverified_recipient and Exchange 2016
Posted by Nicola Piazzi <Ni...@gruppocomet.it>.
It seems NOT a Microsoft problem because with "Recipient Filter Agent" exchange answer "550 5.1.10 RESOLVER.ADR.RecipientNotFound; Recipient not found by SMTP address lookup" when a recipient is not found
So I don't know why when postfix get "550 5.1.10 RESOLVER.ADR.RecipientNotFound; Recipient not found by SMTP address lookup" from Exchange 2016 it doesn't consider unexistant that recipient
Someone can write me the answer of Exchange 2010 to a non existant recipient ?
Nicola Piazzi
CED - Sistemi
COMET s.p.a.
Via Michelino, 105 - 40127 Bologna - Italia
Tel. +39 051.6079.293
Cell. +39 328.21.73.470
Web: www.gruppocomet.it
-----Messaggio originale-----
Da: lists@rhsoft.net [mailto:lists@rhsoft.net]
Inviato: mercoledì 7 settembre 2016 10:49
A: users@spamassassin.apache.org
Oggetto: 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:ext@ext.com
> 250 2.1.0 Sender OK
> rcpt to:doesntexist@gruppocomet.it
> 250 2.1.5 Recipient OK
> data
> 354 Start mail input; end with <CRLF>.<CRLF> some data
Re: postfix reject_unverified_recipient and Exchange 2016
Posted by "lists@rhsoft.net" <li...@rhsoft.net>.
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 dont 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 doesnt 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:ext@ext.com
> 250 2.1.0 Sender OK
> rcpt to:doesntexist@gruppocomet.it
> 250 2.1.5 Recipient OK
> data
> 354 Start mail input; end with <CRLF>.<CRLF>
> some data