Yes it is referring to an A record in DNS. which is weird cause ping finds it no problems. Might be a partially busted zone file, without...
the IP you get back is different than the one you specified in your hosts file. although that still doesn't solve the issue here. Can you post...
hrm...that's weird...if you ping mail.mydomain.com do you get the right IP?
problem solved. duplicate entry overriding a previous one. damn these long config files.. :)
Shouldn't but won't hurt to try, Postfix may store it's own cache of the domain. Try putting all the names on the same line: 212.193.49.223...
Then your DNS is busted too. So update your hosts file for now to test the mail server. Once you get that working then focus on cleaning up the...
That zone looks ok. From your server can you resolve mail.mydomain.com: dig +short @localhost mail.mydomain.com If you get an IP back from...
Yup...although it may not be an mx record. Your host just can't find an IP for mail.mydomain.com. Can add that to /etc/hosts for testing or get...
And your logs show that the message was received by your server and delivered to a mailbox? tail -f /var/log/mail.log
http://www.howtoforge.com/virtual-users-domains-postfix-courier-mysql-squirrelmail-ubuntu8.10-p4 that howto has it but the CentOS version...
I might be wrong but I think this has to do with your transports. Not familiar enough with it to provide more detail though...
hrm...interesting. Looks like postfix isn't creating the domain/user directories. Did you send a test message TO an account in your domain?...
And the contents of the vmail directory. Does it have the same perms/ownership?
Well that creates the user and group on the system. So that's a good start. What are the permissions on the /home/vmail directory? Who owns it?...
Are you sure you have given permissions to the /home/vmail directory as per the howto? As for an e-mail addy that can send but not receive you...
Separate names with a comma.
