mail not being received for new virtual server

18 posts / 0 new
Last post
#1 Sat, 06/25/2011 - 00:57
stevebu56

mail not being received for new virtual server

Some specs: Ubuntu 10.04 Virtualmin 2 virtual servers happydaybakeshop.com & burkefreelance.com

The mail for happydaybakeshop is being received fine. I can see it coming in via the mail.log. Anything sent to the burkefreelance address I don't see in the logs or receive anything.

I use Zonedit to handle the DNS records. I have an MX record set for "mail" and it points to the ip of the server. But when I issue the 'host -t MX happydaybakeshop.com" command it says there is no MX record. I'm not sure why one of my domains works and the other doesn't. One thing that is sticking out is that the server hostname is ns1.happydaybakeshop.com.

I looked through the postfix configuration options but nothing jumped out at me as a difference between the two virtual servers.

Any thoughts on where to start to debug this issue?

Sat, 06/25/2011 - 03:05
Locutus

Actually, on my end, it seems that neither happydaybakeshop nor burkefreelance have MX records... So it's rather surprising that the former should work. :) Might just still be in some cache or local nameserver or hosts file for your test systems.

Look at this: http://www.intodns.com/happydaybakeshop.com

You might want to make sure that you actually have MX records correctly configured at "Zoneedit".

Sat, 06/25/2011 - 11:20 (Reply to #2)
stevebu56

Ok, now I put the following 2 records in zoneedit. These are the entries in their gui. Do these look right?

Subdomain : Type : TTL : Preference : Host (These are the boxes in zoneedit to enter a record)

mail : MX : 300 : 10 : 67.9.168.60

@ : MX : 300 : 10 : mail

And when I look at intodns.com it says the MX records are showing up. Is that all I should have to do? And now I just have to wait for caches to clear on other mail servers before they actually get this record? In this case it shouldn't matter what my hostname of the 67.9.168.60 machine is correct?

Sat, 06/25/2011 - 11:40
andreychek

Howdy,

Yup, that should be good.

And no, the hostname of your server doesn't matter. So long as the IP address in the MX record is pointing to your server, it should be able to deliver email.

-Eric

Sat, 06/25/2011 - 13:20 (Reply to #4)
stevebu56

How long will it take for this to propagate?

Sat, 06/25/2011 - 18:18
Locutus

happydaybakeshop looks okay now. burkefreelance.com though reports an error:

Looks like your nameservers do not agree on the SOA serial. Ths SOA records as reported by your nameservers: 75.125.10.187 -> 2011252423 209.126.137.108 -> 2011252548 This can cause some serious problems that is why you should fix this asap.

You should report this to your zone hoster ("zoneedit") if it does not clear up in the next hours. Looks like they have a misconfiguration there.

Also, just for completeness: MX records have to point to host names, not IP addresses. The report from Zoneedit looks okay, but the line you posted: mail : MX : 300 : 10 : 67.9.168.60 is, for your information, incorrect.

Propagation times for zone changes depend on the configured TTL values. After the TTL have elapsed the change should at the latest have propagated. Though nameservers can, even if they should not, ignore the TTL values in the zone data and employ their own.

Sat, 06/25/2011 - 21:24 (Reply to #6)
stevebu56

Ok I'll let zoneedit know and see what they say.

Also as for the records I posted I made a typo and the record for "mail" should be an A record. Does that still look ok?

mail : A : 300 : 10 : 67.9.168.60

Sun, 06/26/2011 - 04:41 (Reply to #7)
Locutus

Yep, that looks good.

Sat, 06/25/2011 - 21:40
stevebu56

So my hostname for this server is ns1.happydaybakeshop.com. Initially I was going to use it as a dns server hence the ns1 naming but opted to use zoneedit for the dns records. I'm wondering how the mail.burkefreelance.com domain fits into the mix with the MX record. Since I'll have multiple virtual servers with other domains with other MX records for those domains. They will all just point to the correct IP address and that's it? Does my hostname of the server need to resolve. Like should I be able to do host ns1.happydaybakeshop.com and get something back because right now I can't.

I read on some posts how postfix needs the server to have a FQDN and resolve. Is this just a red herring for me or is this causing some of my issues?

Sat, 06/25/2011 - 22:06
andreychek

The name your MX record uses doesn't matter -- all that matters is that the domain name resolves to an IP hosted on your server.

The hostname of your server should resolve... if it doesn't, odd things could happen :-)

You'd at least want to make sure an entry for your hostname existed in your /etc/hosts file.

Does anything out of the ordinary show up if you go into System Settings, and click Re-Check Config?

-Eric

Sun, 06/26/2011 - 09:36 (Reply to #10)
stevebu56

This is what I'm getting now.

Your Postfix configuration is missing the system's mail hostname happydaybakeshop.com from the mydestination line, which will cause mail to bounce.

Sun, 06/26/2011 - 09:46 (Reply to #11)
stevebu56

I fixed this configuration issue. When messing around with settings I deleted a comma in the mydestination line. Now the check is fine.

Sun, 06/26/2011 - 10:01
stevebu56

Mail still isn't hitting the server from outside. I'm testing it with Wormly putting in the following

SMTP Server: 67.9.168.60
Sender Email: steve@burkefreelance.com
Recipient Email: steve@burkefreelance.com

I get the following error.

Connecting...
SMTP -> ERROR: Failed to connect to server: Connection timed out (110)
Message sending failed.

I am behind a NAT and have port 25 being forwarded. Postfix is running. What else am I missing here?

Sun, 06/26/2011 - 10:59
andreychek

Howdy,

Hmm, well, I attempted to connect to a few ports on the IP 67.9.168.60... port 25 (SMTP), 80 (http), 110 (POP), and 10000 (Webmin/Virtualmin) -- none of those worked, I received a Connection Refused error for each of those.

Are you certain that the port forwarding is setup correctly?

Also, some ISP's block certain ports -- it's possible that your ISP is blocking those ports.

-Eric

Sun, 06/26/2011 - 12:38
Locutus

I can confirm that. Telnet connects fail, ping fails, a traceroute from my server stops here:

traceroute to 67.9.168.60 (67.9.168.60), 30 hops max, 60 byte packets 1 pandora.tianet.de (188.40.20.81) 0.256 ms 0.214 ms 0.232 ms 2 static.1.142.40.188.clients.your-server.de (188.40.142.1) 1.601 ms 1.574 ms 1.547 ms 3 hos-tr2.juniper1.rz10.hetzner.de (213.239.227.161) 0.750 ms 0.730 ms hos-tr3.juniper2.rz10.hetzner.de (213.239.227.193) 0.708 ms 4 hos-bb2.juniper3.s06.hetzner.de (213.239.240.139) 3.078 ms 3.035 ms 3.005 ms 5 lambdanet-gw.hetzner.de (213.239.242.213) 3.504 ms 3.483 ms 3.720 ms 6 FRA-3-eth110.de.lambdanet.net (217.71.96.161) 6.732 ms 6.609 ms 6.591 ms 7 ix-0-2-0-0.tcore1.FR0-Frankfurt.as6453.net (195.219.180.69) 6.865 ms 6.834 ms 6.818 ms 8 if-4-2.tcore1.PVU-Paris.as6453.net (80.231.153.10) 100.919 ms 100.902 ms 100.888 ms 9 if-12-871.tcore2.AEQ-Ashburn.as6453.net (216.6.87.73) 101.365 ms 101.327 ms 101.311 ms 10 if-2-2.tcore1.AEQ-Ashburn.as6453.net (216.6.87.2) 99.096 ms 99.082 ms 101.278 ms 11 66.198.154.14 (66.198.154.14) 102.686 ms 206.82.139.54 (206.82.139.54) 102.997 ms 66.198.154.14 (66.198.154.14) 104.911 ms 12 107.14.19.132 (107.14.19.132) 102.463 ms ae-2-0.cr0.dca10.tbone.rr.com (66.109.6.168) 104.941 ms 102.964 ms 13 ae-5-0.cr0.hou30.tbone.rr.com (66.109.10.11) 137.937 ms 136.042 ms 137.838 ms 14 66.109.6.55 (66.109.6.55) 143.560 ms 142.882 ms 149.036 ms 15 gig0-0-0-2.austtxrdcsc-cr02.austin.rr.com (72.179.205.59) 147.025 ms 144.635 ms 144.601 ms 16 agg20.austtxrdcsc-rtr1.austin.rr.com (66.68.2.239) 145.090 ms 142.153 ms 144.821 ms 17 gig3-17.austtxm-er03.texas.rr.com (24.27.13.29) 143.241 ms 145.869 ms 143.682 ms 18 te1-0-0.austtxm-10k2.austin.rr.com (66.68.1.134) 145.673 ms 143.197 ms 143.388 ms 19 * * *

My assumption is the same as Eric's. Incorrect port forwarding, some firewall or ISP blocking ports before your PC. Or maybe your Internet connection is not permanently up?

Sun, 06/26/2011 - 13:24 (Reply to #15)
stevebu56

First of all thanks for the help. I do appreciate it immensely. Sorry for the wild goose chase but I did learn some in the process. It turned out my router just decided to stop working and nothing was being forwarded through. I reset the router & everything started working again. Initially I thought things were working since I was testing within my local net, which always trips me up. I have a Netgear WNDR3700. Have any of you guys heard of issues like this with Netgear routers?

Again thanks.

Sun, 06/26/2011 - 13:57
andreychek

Howdy,

Glad to hear you got it working!

That's actually the same router I use here at home. I haven't had that sort of problem before, though I don't do much port forwarding with it :-)

Have a good one!

-Eric

Sun, 06/26/2011 - 14:32
Locutus

Good luck with your further hosting endeavors! :)

I'm myself using a FritzBox as home router (I like the tight integration of DSL modem, router, access point, VPN host, DECT phone base, ISDN VoIP gateway, fax reception, answering machine, ...) Port forwarding works okay with it, am using it for some stuff like [cough]filesharing[cough].

I'm not (currently / anymore) using it for hosting purposes at home though, got my VMWare root server for that. :)