Leopard Server Mail on the fritz!?!
Something happened recently and I'm having trouble narrowing it down. It's either DNS related or perhaps a Mail config got bent out of whack?
problem may also arise out of fact that hostname of mail server is xserve.primarydomain.com but it handles mail for secondarydomain.com as well.. the setup for this was fine but something has thrown it out of whack and now inbound messages to secondarydomain.com don't get delivered.
so many things look odd. anyone point out the obvious?
Jul 12 11:40:21 xserve postfix/postmap[67479]: warning: /etc/postfix/sasl/passwd: logical line must not start with whitespace: "??:"
Jul 12 11:40:23 xserve postfix/postfix-script[67484]: refreshing the Postfix mail system
Jul 12 11:40:23 xserve postfix/master[55222]: reload configuration /etc/postfix
Jul 12 11:40:54 xserve postfix/smtpd[67504]: connect from 173-164-237-110-SFBA.hfc.comcastbusiness.net[173.164.237.110]
Jul 12 11:40:54 xserve postfix/smtpd[67504]: warning: unknown smtpd restriction: "zen.spamhaus.org"
Jul 12 11:40:54 xserve postfix/smtpd[67504]: NOQUEUE: reject: RCPT from 173-164-237-110-SFBA.hfc.comcastbusiness.net[173.164.237.110]: 451 4.3.5 Server configuration error; from=<bob@externaldomain.com> to=<meltemi@secondarydomain.com> proto=ESMTP helo=<mail.externaldomain.com>
Jul 12 11:40:54 xserve postfix/cleanup[67508]: 8D9CCA028C6: message-id=<20110712184054.8D9CCA028C6@xserve.primarydomain.com>
Jul 12 11:40:54 xserve postfix/qmgr[67489]: 8D9CCA028C6: from=<double-bounce@xserve.primarydomain.com>, size=1090, nrcpt=1 (queue active)
Jul 12 11:40:54 xserve postfix/smtpd[67504]: disconnect from 173-164-237-110-SFBA.hfc.comcastbusiness.net[173.164.237.110]
Jul 12 11:40:54 xserve postfix/local[67509]: 8D9CCA028C6: to=<root@xserve.primarydomain.com>, orig_to=<postmaster>, relay=local, delay=0.23, delays=0.19/0.02/0/0.02, dsn=2.0.0, status=sent (delivered to file: /dev/null)
Jul 12 11:40:54 xserve postfix/qmgr[67489]: 8D9CCA028C6: removed
starting with the first line. the contents of which are " :"
Can that be fixed with Server Admin? We've never touched this file before?!?