EXIM fail to transport mail.

Aug 30, 2014 3 Replies
B

The other day I had some problems to send mail at root@raspberrypi.



Example of correct log:



2014-08-26 10:02:38 Start queue run: pid=31708
2014-08-26 10:02:38 End queue run: pid=31708
2014-08-26 10:12:09 1XMDjV-0008Gl-9W pi R=local_user T=mail_spool
2014-08-26 10:12:10 1XMDjV-0008Gl-9W Completed
2014-08-26 10:32:06 1XME2n-0008J7-Ig pi R=local_user T=mail_spool
2014-08-26 10:32:06 1XME2n-0008J7-Ig Completed
2014-08-26 10:32:38 Start queue run: pid=31941
2014-08-26 10:32:39 End queue run: pid=31941


Failed log:



2014-08-28 20:02:39 Start queue run: pid=664
2014-08-28 20:02:39 End queue run: pid=664
2014-08-28 20:32:39 Start queue run: pid=3730
2014-08-28 20:32:39 End queue run: pid=3730
2014-08-28 20:50:40 1XN6eV-0001Vu-1N
Vote
Twitter Facebook LinkedIn
G

Am 30.08.2014 21:58, schrieb BIG (Umberto):

A provider mistake is very unlikely (at least here [de]).

Regards,

Gregor

Vote
Twitter Facebook LinkedIn
B

Gregor Szaktilla in data 10:53, domenica 31 agosto 2014, nel gruppo comp.sys.raspberry-pi ha scritto:

Thank, any idea for this comportament?

Vote
Twitter Facebook LinkedIn
T

behaviour? (comportament?)

First thing to do is check the rejectlog /var/log/exim4/rejectlog..

next try 'mail -v ' to see if that shows errors.

It may be that you are sending via a smart host by IP address that is no longer a relay, or via an old relay that has been decommissioned.

also try a mailq to see if mail is stuck

Be root for all of these things...

Everything you read in newspapers is absolutely true, except for the rare story of which you happen to have first-hand knowledge. ? Erwin Knoll
Vote
Twitter Facebook LinkedIn

Join the Discussion

Have something to add? Share your thoughts — no account required.

Didn't find your answer?

Ask the community — no account required