Exim problem with external e-mailservers

Dennis

Dennis

Verified User
Joined
Nov 13, 2004
Messages
103
Location
The Netherlands
Hello,

Recently I got some problems with Exim in combination with external e-mail servers like office 365, Google and other IP related mail servers.

Problem:
Our domain has office 365 and the configuration on our server is:

- DNS with only one MX record to office 365
- Internal mail server option is off

Almost all mail is being handled like it should and redirected to office 365, but some e-mail still is being send to Exim. In the Exim log I only see for example:

Code: 
2016-04-01 21:23:05 H=fep14.mx.upcmail.net [62.179.121.34] F=<[email protected]> rejected RCPT <[email protected]>: authentication required

But this is not possible (in theory).....well it is still happening. This also happens with mail servers which have an A record (mail) and MX records pointing away from my server. But still there are some e-mails entering Exim…..

Searched the forum, have done online checks for MX, SPF records, A records and other. I have no clue and I do not know how to get it fixed.

Any ideas?

Thanks in advance!

Using Exim version 4.86.2
Using SpamBlockerTechnology* powered exim.conf, Version 4.3.4
Using ClamAV 0.99.1
Using SpamAssassin Server version 3.3.2
 
Hi Richard,

Thanks for the response.

Yes, I have unchecked the local mail server.

The problem is that it 9 of the 10 times I get mail it is delivered through office 365. Only a few are redirected to Exim and get this message.....
 
I've just tried every record, seems you got all OK, I only can't find any sip entry's, did you make them too?
The _sip._tls entry and the other one, examples can be found here (click) and als here they are with DA examples.

If you have those too, I'm also wondering why it goes wrong sometimes and will follow this topic with interest. Very strange issue.
 
Ok, found the problem I think with some help from John (thanks again)

I changed one nameserver in our resolv.conf to one which is updated frequently and used worldwide. Now the problem is solved, still strange how this could happen, but it had to do something with redirecting from our server to other mailservers though the DNS. The nameserver I used always worked before and is still used by our datacenter....maybe they know more.

Hope this helps people with the same issues.
 
Hmmz that's odd indeed. Thank you for reporting this. Glad you've found it. I'm curious about the answer of the datacenter.
 
You must log in or register to reply here.
Back
Top