Failure to send e-mail( retry timeout exceeded) in exim/mainlog

alemmsm

alemmsm

Verified User
Joined
Nov 9, 2017
Messages
43
Hi,

I can't send to any email, but I receive any email

By executing the following command, I realized that:

/var/log/exim/mainlog

2023-08-13 12:01:09 1qV6VB-0008Mn-33 User 0 set for local_delivery transport is on the never_users list
2023-08-13 12:01:09 1qV6VB-0008Mn-33 == root@server-***-151-135-196.da.direct R=localuser T=local_delivery defer (-29): User 0 set for local_deliv$
2023-08-13 12:01:09 1qV6VB-0008Mn-33 ** root@server-***-151-135-196.da.direct: retry timeout exceeded
2023-08-13 12:01:09 1qV6VB-0008Mn-33 root@server-***-151-135-196.da.direct: error ignored
2023-08-13 12:01:09 1qV6VB-0008Mn-33 Completed
2023-08-13 12:09:52 login authenticator failed for (User) [93.123.118.118]: 535 Incorrect authentication data (set_id=[email protected])
2023-08-13 12:38:13 login authenticator failed for (User) [93.123.118.118]: 535 Incorrect authentication data (set_id=[email protected])
Click to expand...


image from cloudflare.com
sd.jpg

I receive but can't send email...
 
2023-08-13 12:09:52 login authenticator failed for (User) [93.123.118.118]: 535 Incorrect authentication data (set_id=[email protected])
2023-08-13 12:38:13 login authenticator failed for (User) [93.123.118.118]: 535 Incorrect authentication data (set_id=[email protected])
Click to expand...

I am sure you are not the owner of da.direct domain :)
Check you domain and DNS settings + hostname
 
alemmsm said:
I don't know why it shows da.direct
Click to expand...
Nowadays this is the default hostname setup server-xxx.xxx.xxx-da.direct where xxx.xx.xxx is your server's ip address.

This is so you can visit the server via https when it's installed.
I'm not happy with this procedure because it will cause these kinds of mistakes. However, it was DA's choice to do it this way. I would strongly suggest to create your own hostname. However that is your choice.

Result is that if mail is send via php, then it will be send from server.xxx.xxx.xxx.da.direct and not via server.yourdomain.com like should be.

However, what you see in the log, you should not be worried about. Because 93.123.118.118 is not your ip address and they are just trying to bruteforce [email protected] and [email protected] which domain isn't on your server anyway, so just ignore that.

Now to your other problem. What you see there is:
User 0 set for local_delivery transport is on the never_users list
Click to expand...
which is normal. Mail for root is not send directly.

Fix this by either editting the /etc/aliases file and on the bottom add:
root: [email protected]
ofcourse fill in the mail address where you want to receive root mail to.
After that, restart exim.

If you are on Debian/Ubuntu this might not work, in that case, create a file called .forward (mind the dot in front) in the /root directory and put your e-mail address in there.
 
alemmsm said:
The problem is that my emails are not sent to anyone
Click to expand...
Since you did not show any proof of that in a logfile, it's hard to be able to help you. The only thing I've seen until now, is that root could not send mail, which is normal. And my answer should have fixed that part.

If you can't send any mail, in most cases that is caused by the provider or the datacenter having port 25 TCP outgoing closed.
You could try that by issuing this command via SSH:
telnet directadmin.com 25
be sure port 25 tcp incoming and outgoing is opened in your own firewall too!!

You should get an answer like:
Code: 
Connected to directadmin.com.
Escape character is '^]'.
220 do.directadmin.com ESMTP Exim 4.96-58-g4e9ed49f8 Tue, 15 Aug 2023 16:18:18 -0600
you can just type quit to exit the mailer.

If you encounter a timeout, then somewhere port 25 outgoing is closed either in your firewall or your provider/datacenter has it closed and then you have to contact them.

There could be other causes, but this is the most likely one.
 
You must log in or register to reply here.
Back
Top