Exim4 Errors

[fartface]

I seem to be having trouble with my VestaCP Install. The web end of things works great, but the e-mail is a bit touch and go. I've got it running on a Crissic VPS (2GB RAM, Ubuntu 12.04.03 x64)

In my exim4 mainlog, I am repeatedly getting an error about the remote host is the local host: (server.domain.com).

Code: Select all

2014-01-17 02:42:27 1W444R-000311-8W <= root@server.domain.com U=root P=local S=29302
2014-01-17 02:42:27 1W444R-000311-8W remote host address is the local host: server.domain.com
2014-01-17 02:42:27 1W444R-000313-DF <= root@server.domain.com U=root P=local S=658
2014-01-17 02:42:27 1W444R-000311-8W == root@server.domain.com R=dnslookup defer (-1): remote host address is the local host
2014-01-17 02:42:27 1W444R-000311-8W Frozen

I've changed my actual FQDN in that little snippet, but the errors are all the same. I think cron, or some system process is trying to send out mails, but unfortunately I don't know enough about exim to be able to figure out what to do next. Anyone here have an idea?

I added server.domain.com as a web domain with VestaCP, but now I'm getting the error that root@server.domain.com is unrouteable. Argh!

My mail forwards to external addresses don't seem to be working either, which is strange:

Code: Select all

delivering 1W48IM-0002et-AF (queue run pid 19262)
LOG: retry_defer MAIN
  == *****@shaw.ca <info@*****.ca> R=dnslookup T=remote_smtp defer (-53): retry time not reached for any host

Does anyone have any insight into this stuff?

[jarland]

Looks like it's just failing to send to root. You could just set an external e-mail address in /etc/aliases if you want root mail to forward to an account. It's usually just filled with cron notifications.

As for forwarders, are there any other messages before that about that particular message? You may be getting rate limited by the end point. Try grep "1W48IM-0002et-AF" /var/log/exim/main.log

[fartface]

Yeah, it is failing to send to root, but how do I stop this from happening, that's the question, haha! I don't need it to forward to an account, I just need it to stop clogging up exim.

As for forwarding, here's the results of the log:

Code: Select all

root@fenrus:~# grep "1W48IM-0002et-AF" /var/log/exim4/mainlog
2014-01-17 14:23:54 1W48IM-0002et-AF unknown lookup type "fenrus.***.ca"
2014-01-17 14:24:12 1W48IM-0002et-AF == **@shaw.ca <info@*.ca> R=dnslookup T=remote_smtp defer (-53): retry time not reached for any host
2014-01-17 14:25:42 1W48IM-0002et-AF == **@shaw.ca <info@*.ca> R=dnslookup T=remote_smtp defer (-54): remote deliveries suppressed
2014-01-17 14:31:14 1W48IM-0002et-AF == **@shaw.ca <info@*.ca> R=dnslookup T=remote_smtp defer (-54): remote deliveries suppressed
2014-01-17 14:41:10 1W48IM-0002et-AF == **@shaw.ca <info@*.ca> R=dnslookup T=remote_smtp defer (-53): retry time not reached for any host
2014-01-17 14:53:11 1W48IM-0002et-AF == **@shaw.ca <info@*.ca> R=dnslookup T=remote_smtp defer (-53): retry time not reached for any host
2014-01-17 15:10:39 1W48IM-0002et-AF == *@shaw.ca <info@*.ca> R=dnslookup T=remote_smtp defer (-53): retry time not reached for any host
2014-01-17 15:40:40 1W48IM-0002et-AF == *@shaw.ca <info@*.ca> R=dnslookup T=remote_smtp defer (-53): retry time not reached for any host
2014-01-17 16:11:43 1W48IM-0002et-AF == *@shaw.ca <info@*.ca> R=dnslookup T=remote_smtp defer (-53): retry time not reached for any host
2014-01-17 16:29:50 1W48IM-0002et-AF == **@shaw.ca <info@*.ca> R=dnslookup T=remote_smtp defer (-53): retry time not reached for any host
2014-01-17 16:30:17 1W48IM-0002et-AF == **@shaw.ca <info@*.ca> R=dnslookup T=remote_smtp defer (-53): retry time not reached for any host

[jarland]

Are you sure it's clogging the queue? The reason I ask is I just checked mine, and here's some results.

Code: Select all

2014-01-13 05:34:44 1W2eqo-0001ql-KZ <= root@mxroute.com U=root P=local S=1054
2014-01-13 05:34:44 1W2eqo-0001ql-KZ ** root@mxroute.com: Unrouteable address
2014-01-13 05:34:44 1W2eqy-0001rI-B0 <= <> R=1W2eqo-0001ql-KZ U=exim P=local S=1832
2014-01-13 05:34:44 1W2eqy-0001rI-B0 ** root@mxroute.com: Unrouteable address
2014-01-13 05:34:44 1W2eqy-0001rI-B0 Frozen (delivery error message)

That's a frozen message to root obviously, but when I check the exim queue.

Code: Select all

[root@mxroute exim]# exim -bpc
0

It looks like it's clearing out frozen messages on it's own. I think because of this in exim.conf:

Code: Select all

timeout_frozen_after = 7d

On the forwards, it seems (to me) that it may not be getting a DNS return for the domain. If you run a "dig A ***.ca" or a "dig MX ***.ca" do you get values returned in the answer section? You don't happen to have ***.ca listed in /etc/hosts or in /etc/exim/domains by chance do you? I'm grasping at straws obviously, but the more I troubleshoot the more I learn too ;)

[fartface]

Sorry for the late reply!

Here's how my site is configured, and here's how I fixed this particular issue:

I have a root domain, let's call it example.com. My primary server runs at primary.example.com.

With a default installation of VestaCP, I would get the errors listed above (essentially failed to send mail to root@primary.example.com), and there was a whooooole schwack of 'em thanks to CSF/LFD.

To fix it, I just created a mail domain of primary.example.com and setup a mailing address "root".

Now the mails are being properly delivered.

[MikeP1990]

Hello,

This fixed an issue for me as I use both the server as a mail exchange and Zoho (business email). I didn't need to create the email address though, just creating the mail domain worked. I then had to add my custom static_route quote underneath the user_forward section of the exim.conf to accomplish exactly what I needed.

Thanks very much for this.

Mike

[waLplanet]

hi, I've been crazy with the same issue.. and after hours of research I've found the reason, and it's not a bug.. at least for my configuration.
in my server I added the domain example.com, which mail accounts were handled by google apps, and after that I tried to send emails to email@example.com, from another mail account in the same sever.
well, when exim tries to send the email, it looks in the local machine, because by default it's created the mail support for the domain.

and it failed giving me Unrouteable address, as expected..
so you should be careful when creating the domain, unchecking the mail support if the mail is manager out of that server.

I've deleted example.com mail account, located at vesta mail tab:

and after that tried at the ssh:
exim -bt email@example.com
and then everything was fine..

I hope I've been clear enough with the explanation and it be useful.
vestacp is simple, fast and powerful!

thanks to everyone,

Walid

[MAN5]

Y not juz do the simple way.!?

https://server.com:8083/edit/mail/?domain=server.com
Than set "Catchall Mail" > YourID@gmail.com .