This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Recipient verification failing

We've had several problems receiving mails from different domains lately (all delivered to our UTM (primary MX-record) and all to be routed to another host (mostly Office365)).

Today I went for a more thorough search and found out that whenever I have Recipient verification (with callout) selected, which has always been selected in the past, it fails with a lot of addresses (all valid) hence the mail is simply rejected.

Here's what is shown in the logfile (masked real mailaddresses):

2018:07:12-23:18:48 utm-2 exim-in[26983]: 2018-07-12 23:18:48 [209.85.161.171] F=<***@gmail.com> R=<***@p***.**> Verifying recipient address with callout

2018:07:12-23:18:48 utm-2 exim-in[26983]: 2018-07-12 23:18:48 TLS error on connection from mail-yw0-f171.google.com [209.85.161.171]:34565 (renegotiation not allowed): error:00000000:lib(0):func(0):reason(0)

When I set to No verification, mails are allowed and routed to the external mailbox correctly.

The fail is also seen when using https://www.checktls.com/TestReceiver for sending to a mailaddress. Once no verificiation is setup this site also gets a "OK".

Is there some reason verification is failing?

This thread was automatically locked due to age.

Parents

0 Thorsten Langer over 5 years ago

Noticed this today too, was wondering about lack of incoming emails. I use SMTP callout on a Exchange 2016 on premise. Worked. Until I installed 9.510 obviously. If callout is active I also got the message logged: (renegotiation not allowed): error:00000000:lib(0):func(0):reason(0). Disabling smtp callout recipient verification it works again.
Cancel
Vote Up 0 Vote Down

Cancel
0 DouglasFoster over 5 years ago in reply to Thorsten Langer

So the problem applies to more than just Office365, and is specific to 9.510?
Cancel
Vote Up 0 Vote Down

Cancel
0 Thorsten Langer over 5 years ago in reply to DouglasFoster

I am not sure about this. I have to admit I didn't look regularly in the smtp proxy log the last two or three updates. But this error message is new for me in 9.510 and I have no O365 stuff. I also didn't look any further but I think there is a problem with TLS and SMTP communication from my UTM to my Ex2016 on premise.
Cancel
Vote Up 0 Vote Down

Cancel

Reply

0 Thorsten Langer over 5 years ago in reply to DouglasFoster

I am not sure about this. I have to admit I didn't look regularly in the smtp proxy log the last two or three updates. But this error message is new for me in 9.510 and I have no O365 stuff. I also didn't look any further but I think there is a problem with TLS and SMTP communication from my UTM to my Ex2016 on premise.
Cancel
Vote Up 0 Vote Down

Cancel

Children

No Data