Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Step by step guide to configure 10.8 mail server

Looking for a decent guide to walk me through configuring the mail server, testing the configuration, etc. plus the obvious DNS and other configuration necessary to make it work and access it from the outside world.


Any suggestions?

OS X Server, 10.8 Mail Server

Posted on Sep 13, 2012 12:37 PM

Reply
45 replies

Sep 16, 2012 1:30 PM in response to Mike Edwards

It may very well be that your ISP blocked port 25 to prevent spam from being sent from misconfigured mail servers as users running Windows normally have a hard time setting up mail (they do not have the simple On-Off switch and a way more likely to be infected with spam sending malware).


If this applies to your ISP you could use an SMTP service that lets you send and receive on another port than port 25 (TCP) and use an airport extreme to translate the 'wrongly' set outside port to port 25 on your internal network.


Or you could just switch to a business package with your ISP, although the first option seems easier and cheaper 🙂

Sep 18, 2012 8:06 PM in response to Mike Edwards

Hi Mike,


There are two things to verify. The first, is that the mailserver is up and running. Run the following command in Terminal.app of the server...


sudo serveradmin fullstatus mail


If that says mail is not running, let us know and we'll go from there. If it says the mailserver is running, try this from the Terminal.app of a client machine you wish to send mail from...


telnet your.server.tld 25


This command tests whether a connection can be made from the client to the server.

Sep 19, 2012 9:46 AM in response to Mike Edwards

Are these machines on the same IP network? What happens if you try the following in the command line...


host mail.xyz.com ip.of.dns.server


What the "host" command is doing is querying the specificed DNS server (last argument) for the mail domain (first argument)


Did you end up configuring your DNS by hand, or did you use the Server.app GUI? If you used the GUI, did you select the pulldown for answering all client queries?

Sep 19, 2012 9:51 AM in response to JaimeMagiera

Both machines are on the same local network although running the command line on the server or one of the other machines gives the same results, i.e.


host mail.xyz.com www.xyz.com

Using domain server:

Name: www.xyz.com

Address: 192.168.1.12#53

Aliases:


Host mail.xyz.com not found: 2(SERVFAIL)


The DNS was set up using the Server.app GUI and the option is set for answering all client queries.

Sep 19, 2012 9:59 AM in response to Mike Edwards

OK, that's not good. Something is akew with your DNS configuration. Did you create an A record for mail.xyz.com? In Server.app, that would be done by either checking the "Create MX record for this hostname" checkbox on the mail.xyz.com entry, or manually configuring an A record and adding an MX record to any host that wants to use it as a mailserver.

Sep 19, 2012 10:57 AM in response to Mike Edwards

You should only setup the DNS at your registrar to have mail delivered at your server, together with Reverse DNS with your hosting provider (some mail servers reject mail with a non working Reverse DNS),.


To set up your mail server for internal use you need to have a DNS server running on your network, but it doesn't have to be your OS X Server.


In OS X Server the record Jaime is referring to is called a Machine Record, but if you haven't selected the option to Show All Records in the menu (gear) of the Server app's DNS section you will not see any options listed when you click the plus ➕ symbol, but instead will be presented the New Host Name window. An Machine Record actually is an A record.


Try checking just:

host mail.xyz.com


And it will tell you the ip set at your registrar...

Sep 19, 2012 12:55 PM in response to Mark23

Dear Mark23,


You didn't read what I wrote. He needs to find what nameservers are connected to the actual domain, not what IP is connected to the host - hence "whois". We need to do this because it's unclear if the actual domain itself is even mapped to the DNS servers he hopes to use. If you read back on this, he clearly doesn't grock the details of local vs. actual registered DNS. You've overloaded him with a bunch of stuff that detracts from the actual understanding of DNS overall. You said "You should only setup the DNS at your registrar" - which will mean nothing to him with without context.


My cut and paste error was clearly meant to be "xyz.com".


Sorry...

Step by step guide to configure 10.8 mail server

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.