No mail!!!

tino

Verified User
Joined
Jan 8, 2004
Messages
92
Hi,

None of the domains of my DirectAdmin box is recieving mail.

DNS resolves fine, The MTA on the box gets the mail and sais it's okay (tested it with TELNET).

But the mail does not end up in a mailbox...

What to do?!

This is a REAL problem by now!!!!

TIno
 
Is this happening with the main user accounts or with the virtual accounts (or both?).

What does /etc/resolv.conf say? Have you set the hostname different from your primary domain (domain.com --> server.domain.com)?
 
Found it.

I searched for the wrong terms, but by browsing the forum I found the problem.

The domain of the hostname of the machine was also declared in an account. That caused the problems.

But that's kinda crap. I want to name my server host.domain.com and be able to host the domain domain.com on it! Dzjeez...

Tino
 
You can, you just can't name the hostname the same as a domain running on it. Running server.domain.com as the hostname and running www.domain.com wouldn't be a problem

If you're planning on hosting server.domain.com for some reason then change the hostname to whatever you like. thisisavalidhostname.domain.com. Your choice ;)
 
Well.. it IS a problem.
And I found out the hard way.

The server name was: server1.mydomain.com and I hosted mydomain.com. No mail whatsoever to any domain on the box. Renamed the server to server1.somedomain.com and, like magic, everything started working the same second!

Tino
 
Hi,

Well, no domain was recieving e-mail. (Even tried to send mail from one account on that server to another account on that server by using webmail on the server and TELNET.)

I Changed the server name... Voila! Everyting started to work. :-)

TIno
 
Well this is the first time I've heard about using a same domain in any form giving problems.

If the hostname is similar to an account on the server that creates problems because all mail to primary accounts is sent towards the catch all of that domain.

From what I've learned and saw on the forum having:

servername.domain.com which is *not* hosted on the server shouldn't give any problems. Did you perhaps have wildcard DNS running for that domain?
 
Hi,

I created the domain as any other domain and did not actively change the DNS settings. If DirectAdmin creates a wildcard DNS record by default, that most probably caused the error.

Well, it's solved now. Queued mail for the domain is hitting the server and everything is well.

Too bad I had to without mail for 4 days. :-(

Tino
 
Back
Top