Take the 2-minute tour ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

I currently have Postfix running on a box that also hosts a number of websites. Although the website domains' DNS all have an A record pointing to this server, the server has no hostname of its own. The Postfix is used for outgoing SMTP only; incoming is handled by Google Apps. All outgoing mail is signed by OpenDKIM, and SPF is enabled as well.

The question is, does the server needs its own hostname, especially for Postfix? I've heard conflicting advice about whether Postfix needs to have a real FQDN set for myhostname/mydomain to prevent messages from being classified as spam.

So far, I do not seem to be experiencing any issues with a default 'server.localdomain' hostname. Is it OK to keep using this, or should I look to get a real domain just for the server?

share|improve this question

2 Answers 2

In order to deliver mail to the more critical mail systems on the Internet, having Forward-confirmed reverse DNS is of some importance.

Note that this is unrelated to, and separate from, what postfix thinks its hostname is - it is purely DNS-related.

share|improve this answer

There certainly are mail servers out there that will refuse to deliver mail that is sent from .localdomain. It is also impolite to send out mails such that you cannot easily find a domain to send abuse@ to.

This only means that the mails should be sent with a proper recipient in the SMTP dialog. If your software does not do this, it will be set by Postfix using myorigin.

share|improve this answer
    
I forgot to mention that the FROM headers are all set properly using the websites' domain names. Is this sufficient? –  Kevin Zhang Mar 5 '12 at 12:23

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.