Bernhard Schmidt:
> This gets even worse when the mail has two recipients ... doesnotexist@
> does not exist, t1@ does...
>
> mail from: <t...@test.de>
> 250 2.1.0 Sender OK
> rcpt to: <doesnotex...@test.customer.de>
> 250 2.1.5 Recipient OK
> rcpt to: <t...@test.customer.de>
> 250 2.1.5 Recipient OK
> data
> 354 Start mail input; end with <CRLF>.<CRLF>
> test
> .
> 550 5.1.1 User unknown
>
> mail from: <t...@test.de>
> 250 2.1.0 Sender OK
> rcpt to: <t...@test.customer.de>
> 250 2.1.5 Recipient OK
> data
> 354 Start mail input; end with <CRLF>.<CRLF>
> test
> .
> 250 2.6.0 <MSGID> [InternalId=2740189134859] Queued mail for delivery
>
> This is not only unusable for Recipient validation, but will reject
> legitimate mail since you cannot reject individual recipients in DATA
> with SMTP.
That is really awful. Your gateway will need to use smtp_recipient_limit=1
for all inbound mail (whether a RAV probe message or not). As for
people who have to expose their Exchange 2013 server to the Internet
there is no such workaround.
Wietse
