Koozali.org: home of the SME Server
Legacy Forums => General Discussion (Legacy) => Topic started by: hejole on January 20, 2004, 04:59:38 PM
-
For some strange reason I am not able to recieve mail on my SME box...
It used to work, but it stopped working approximately 1 month ago.
I have checked and double checked my DNS and MX records, and the IP is resolved correctly according to the DNS...
Using dnsreport.com i get the following:
mydomain.tld. - xx.xxx.xx.xxx [Could not connect: Could not connect to mail server: error #10054.]
Sending and receiving within local domains works fine (since the data never leaves the local network).
I have tried restarting qmail, rebooting the SME box, installing darrel mays port opener contrib and opened port 110 and 25, all with no result.
Any help is highly apprecieated.
Cheers
Ole
-
What happens when you telnet to your external IP address using port 25?
i.e.
telnet xx.xxx.xxx.xx 25
you should get a line of info back, if not have you made sure the mail retrieval is set to 'standard'?
PeterG.
-
This is what I get when I telnet my external IP:
----------
[root@www root]# telnet xx.xxx.xx.xxx 25
Trying xx.xxx.xx.xxx...
Connected to xx.xxx.xx.xxx.
Escape character is '^]'.
220 www.mydomain.tld mailfront ESMTP
----------
Checked that mail retrieval is set to standard and it is.
- still no go when checking at dns-report.com -
-
Hmmmm. If your MX records are also configured ok.....
I don't suppose you have performed an upgrade recently have you?
PeterG.
-
no update performed recently.
I'm running SME 5.6.
Just checked with my ISP and port 25 is NOT blocked (in fact none are :-) )
Any other ideas as to why it just won't work? Is there anywhere in specific I should check to find out why it's not working?
Cheers
Ole
-
ok, it sounds similar to this, but this was after an upgrade from 5.1 to 6.0. But it might be worth a look, read the whole thread for the background.
http://wiki.contribs.org/posting.php?mode=quote&p=76261
PeterG.
-
On second thoughts skip that, try this instead.
host -t mx yourdomain.com yourispdnsserveripaddress
PeterG.
-
It resolves fine...
Here's a screendump:
# host -t mx coffeespot.dk 80.63.205.140
Using domain server:
Name: 80.63.205.140
Address: 80.63.205.140#53
Aliases:
coffeespot.dk mail is handled by 10 coffeespot.dk.
# host -t mx coffeespot.dk 212.10.10.4
Using domain server:
Name: 212.10.10.4
Address: 212.10.10.4#53
Aliases:
coffeespot.dk mail is handled by 10 coffeespot.dk.
# host -t mx coffeespot.dk 212.10.10.5
Using domain server:
Name: 212.10.10.5
Address: 212.10.10.5#53
Aliases:
coffeespot.dk mail is handled by 10 coffeespot.dk.
-
hmm.
If that is the true domain name(?) then there is something definately refusing port 25 somewhere on the way to your server.
I presume that when you did the telnet to port 25 previously you were on your own server or network?
When I try to to trace route to your server it starts being blocked it gets here -
16 gw-aarh-4.access.stofa.net (212.10.10.7) 53.517 ms 53.127 ms 53.649 ms
well that is where it stops reporting back at least.
So either its an isp issue OR maybe it's the firewall in SME playing silly buggers, unfortunately I can't help much with that bit
PeterG.
-
Doh!
Contacted my ISP again and insisted on the problem being caused by them. And so it turned out that I have to use their MX-backup server :-)
Just beautiful... well, changed the DNS record and now I'll just be waiting and anticipating the result.
Thanks for all your help.
Cheers
Ole
-
Is it working now?
PeterG.