Mail delivery broken. No solution in sight. Please help.

O

Orbserver

Verified User
Joined
May 2, 2005
Messages
20
Mail sends but isn't delivered and is held in spool. What should I look for next?

- Exim logs indicate messages are completed or rejected (logs look normal)
- spamd and clamd are processing mail
- exim.conf file is fine.
- No other exim.conf variation works, exim4.conf or custom
- Dovecot is fine, dovecot.conf is fine
- Squirrelmail's config is fine
- popb4smtp, iptables, named...anything that affects mail delivery is running.
- Stopping iptables is no help; ports 143, 25 and 110 are open.
- All daemons and services stop and start without errors
- I see nothing out of the ordinary in /var/mail or /var/spool directories
- Spooled mail is intact and ready to go out
- PHP uploads are enabled (Squirrelmail)


Andybody with similar problems or some familarity?

To answer the obvious first question: Yes, I messed with it. I ran several updates: Custom Apache/PHP/Zend, Squirrelmail, plus outdated ClamAV and SpamAssassin.
 
Give this a shot

Well, I am having the same issue and I have not yet tested this solution but I figured I would post here to help before I forgot. I read somewhere that some ISP's block port 25 and port 26 to prevent spam(usually large ISP's but some smaller ones do as well). There is not much at all you can do about this except change the port that exim works off of to basically any open port that isn't 25 or 26, and be sure that your firewall settings allow the new port to have access. Well, can't gaurentee it will work but its worth a shot. Good luck!

-Mike
 
help

If anyone knows how to change the port that exim works off of I would appreciate it if you could let me know how to go about doing that. Thank you in advance.

-Mike
 
Your DA exim config should already be using both ports 25 and 587.

Try using 587, it is working fine for me and my users, haven't seen a block there yet.

If you are interested you can find the line in /etc/exim.conf:

daemon_smtp_ports = 25 : 587

And edit to taste (and then restart exim).

BUT

This should only affect email being delivered TO your server for delivery. If email isn't leaving your server this is NOT the reason unless you're hosting your DA server from your local residential ISP; all commercial data centers allow outgoing traffic on port 25.

(Except GoDaddy, but that's another (sad) story.)

You should probably check to make sure that the dig command works on your server. Try:

dig earthlink.net

and if you don't get an A record as a response your dns rsolution is broken.

Jeff
 
Ok

Ok, I ran the dig command and it seems to be fine, it displayed the A records. I went on dnsreport.com and ran a report and the only test that seemed to fail is the response of my secondary nameserver. Here is the error:

ERROR: Some of your nameservers listed at the parent nameservers did not respond. The ones that did not respond are:

69.13.212.131


Note: If you are running a Watchguard Firebox with DNS Proxy enabled, there may be a bug causing port numbers get mixed up -- if this is the case, you can contact Watchguard to see if they have a fix.
Click to expand...

I would appreciate it if anyone knew how I could properly setup that secondary nameserver via DA/host config on my server. I am probably missing something stupid but I can't seem to put my finger on it.

Here is my /etc/hosts file:

69.13.212.130 server1.xeroweb.net
69.13.212.131 server1.xeroweb.net
Click to expand...

And my DNS config for xeroweb.net in DA:

Name Type Value Select
ftp A 69.13.212.130
localhost A 127.0.0.1
mail A 69.13.212.130
ns1.xeroweb.net. A 69.13.212.130
ns2.xeroweb.net. A 69.13.212.131
pop A 69.13.212.130
www A 69.13.212.130
xeroweb.net. A 69.13.212.130
xeroweb.net. A 69.13.212.131
xeroweb.net. NS ns1.xeroweb.net.
xeroweb.net. NS ns2.xeroweb.net.
mail MX 10
xeroweb.net. TXT "v=spf1 a mx ip4:69.13.212.130 ~all"
Click to expand...

Thanks in advance for your response.

-Mike
 
You must log in or register to reply here.
Back
Top