Cannot send email out

[clarky2k3]

Hello, I have a little problem it just started happening yesterday before I put the 5.0.12 upgrade on the server. When any of my users send email out to lets say username@googlemail.com it shows a 'critical error. Message not sent; one or more addresses not accepted. Rejected addresses : username@googlemail.com. I am new to zimbra and only have been using this for a few weeks. We can send mail to members of the GAL and recieve mail in from username@googlemail.com. Help?

[uxbod]

Are you the Administrator ? If so I would recommend checking your logfiles especially /var/log/zimbra.log and /opt/zimbra/log/mailbox.log for any error messages. Also ensure that your DNS is still fully functional.

[clarky2k3]

Yes I am the administrator. The DNS seems to be ok.

[clarky2k3]

I am looking through the logs but as a noob I not sure what I am looking for. Should I post the logs.

[uxbod]

Is it happening on all external domains ? Do you send directly out to the internet or are you using a smarthost to relay ?

[clarky2k3]

Yes it is happening on all external domains. We send out through our endian firewall using a rule to allow port 25 on all TCP.

[uxbod]

Send a email and monitor /var/log/zimbra.log. You could also try from the command line telneting to port 25 to one of the domains and manually sending a email through to see if the firewall is not restricting anything.

[clarky2k3]

This is what I have found in /var/log/zimbra.log

Jan 29 09:23:34 mail postfix/smtpd[25202]: connect from mail.coqueths.org[217.23.230.158]
Jan 29 09:23:34 mail postfix/smtpd[25202]: NOQUEUE: reject: RCPT from mail.coqueths.org[217.23.230.158]: 554 5.7.1 <USER@googlemail.com>: Relay access denied; from=<adminkc@coqueths.org> to=<USER@googlemail.com> proto=ESMTP helo=<mail.coqueths.internal>
Jan 29 09:23:34 mail postfix/smtpd[25202]: disconnect from mail.coqueths.org[217.23.230.158]

I have taken out the username from the googlemail address.

[uxbod]

Your RDNS for your mail server also has a A record for www. You probably should make the www a CNAME instead as when a reverse lookup is performed they could be blocking on that.

[clarky2k3]

Our remote DNS is managed by our local county council