Results 1 to 7 of 7

Thread: Relay access denied when sending mail out to the Internet

Hybrid View

  1. #1
    Join Date
    Mar 2010
    Posts
    6
    Rep Power
    5

    Default Relay access denied when sending mail out to the Internet

    Hi,

    I'm new to Zimbra CS and also new to email servers, dns etc. in general. Kind of learning as I go.

    I get the message "Message not sent; one or more addresses were not accepted.
    Rejected addresses: someone@yahoo.com" etc. when sending mails from the Zimbra Web Client to external addresses. Sending to other internal addresses works fine. It also says: Invalid Addresses; chained exception is: com.sun.mail.smtp.SMTPAddressFailedException: 554 5.7.1 : Relay access denied etc.

    However, it is working fine to both internal and external addresses when sending over IMAP in another client, like Windows Mail or Zimbra Desktop.

    I've installed Zimbra Collaboration Suite 6.05 and during the installation I created a domain: mail.exampledomain.com (exampledomain.com is not the real name of the domain). The host machine is named: mail.exampledomain.com.

    All services is running in the Zimbra installation, except stats.

    The DNS setup at my domain provider is:
    - exampledomain.com MX 10 mail.exampledomain.com
    - mail.exampledomain.com A
    - exampledomain.com A

    I also tried to change the domain name from mail.exampledomain.com to only exampledomain.com, and changed back again, but it is not working. It is possible that it worked from the Web Client before I changed the domain the first time. Not sure.

    Hope someone can help me with this

  2. #2
    Join Date
    Nov 2006
    Location
    UK
    Posts
    8,017
    Rep Power
    24

    Default

    Welcome to the forums

    Please post the following information so we may help you
    Code:
    cat /etc/hosts
    cat /etc/resolv.conf
    dig yourdomain mx
    dig yourdomain any
    host `hostname` <- note backticks and not single quotes

  3. #3
    Join Date
    Mar 2010
    Posts
    6
    Rep Power
    5

    Default

    Ok, here's the information.

    Code:
    #
    # hosts         This file describes a number of hostname-to-address
    #               mappings for the TCP/IP subsystem.  It is mostly
    #               used at boot time, when no name servers are running.
    #               On small systems, this file can be used instead of a
    #               "named" name server.
    # Syntax:
    #
    # IP-Address  Full-Qualified-Hostname  Short-Hostname
    #
    
    127.0.0.1       localhost
    
    
    # special IPv6 addresses
    ::1             localhost ipv6-localhost ipv6-loopback
    
    fe00::0         ipv6-localnet
    
    ff00::0         ipv6-mcastprefix
    ff02::1         ipv6-allnodes
    ff02::2         ipv6-allrouters
    ff02::3         ipv6-allhosts
    192.168.161.x   dns1.xxxx.xxxx
    192.168.169.x   mail.agitel.no mail
    192.168.169.x   mail.agitel.no
    Code:
    nameserver 192.168.161.x
    search xxxx.xxxx
    Code:
    ; <<>> DiG 9.3.4 <<>> agitel.no mx
    ;; global options:  printcmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 32258
    ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
    
    ;; QUESTION SECTION:
    ;agitel.no.                     IN      MX
    
    ;; ANSWER SECTION:
    agitel.no.              3600    IN      MX      10 mail.
    
    ;; Query time: 19 msec
    ;; SERVER: 192.168.161.x#53(192.168.161.x)
    ;; WHEN: Mon Mar  8 09:11:34 2010
    ;; MSG SIZE  rcvd: 47
    Code:
    ; <<>> DiG 9.3.4 <<>> agitel.no any
    ;; global options:  printcmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 20583
    ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 6, AUTHORITY: 0, ADDITIONAL: 1
    
    ;; QUESTION SECTION:
    ;agitel.no.                     IN      ANY
    
    ;; ANSWER SECTION:
    agitel.no.              3600    IN      NS     dns1.xxxx.xxxx.
    agitel.no.              3600    IN      NS      dns1.itpays.net.
    agitel.no.              3600    IN      NS      dns2.itpays.net.
    agitel.no.              3600    IN      NS      dns3.itpays.net.
    agitel.no.              3600    IN      SOA     dns1.xxxx.xxxx. admin.xxxx.xxxx. 16 900 600 86400 3600
    agitel.no.              3600    IN      MX      10 mail.
    
    ;; ADDITIONAL SECTION:
    dns1.xxxx.xxxx. 3600    IN      A       192.168.161.x
    
    ;; Query time: 2 msec
    ;; SERVER: 192.168.161.x#53(192.168.161.x)
    ;; WHEN: Mon Mar  8 09:12:21 2010
    ;; MSG SIZE  rcvd: 208
    Code:
    mail.xxxx.xxxx has address 192.168.169.x
    Btw. I forgot to mention that I also tried to configure a host and MX record in our internal DNS server, but I'm not sure if I got it correct.
    Last edited by morgab; 03-11-2010 at 11:37 AM.

  4. #4
    Join Date
    Nov 2006
    Location
    UK
    Posts
    8,017
    Rep Power
    24

    Default

    Your hosts file is incorrect as it should look like
    Code:
    127.0.0.1       localhost.localdomain  localhost
    
    
    # special IPv6 addresses
    ::1             localhost ipv6-localhost ipv6-loopback
    
    fe00::0         ipv6-localnet
    
    ff00::0         ipv6-mcastprefix
    ff02::1         ipv6-allnodes
    ff02::2         ipv6-allrouters
    ff02::3         ipv6-allhosts
    192.168.169.5   mail.agitel.no mail
    Make sure in your internal DNS you have a A record for mail.agitel.no and a MX record for the domain agitel.no that is pointed to mail.agitel.no.

    Once you have made the changes run those commands again and post if you are still having issues.

  5. #5
    Join Date
    Mar 2010
    Posts
    6
    Rep Power
    5

    Default

    Thanks for the suggestions. It seemed it was the DNS.

    I tidied up the etc/hosts file as you suggested, however the problem remained.
    Then I tried a complete reinstall (uninstalled prior installation), and making sure all preinstall requirements were met according to the QuickStart-guide. Zimbra could not resolve the A host in the internal DNS server, so I kept making changes in that one until it worked. I had to make a new zone in the DNS named mail.agitel.no (different from what I previously had made), and make a A host in that one. Then Zimbra didn't complain and continued the installation without error.

    After the server was started it worked without problems.
    Case resolved.

  6. #6
    Join Date
    Nov 2006
    Location
    UK
    Posts
    8,017
    Rep Power
    24

    Default

    What you have defined as a zones is in-fact the FQDN of the server. If you are happy then that is fine; but from what you have said both the server and DNS have not been defined correctly.

  7. #7
    Join Date
    Mar 2010
    Posts
    6
    Rep Power
    5

    Default

    Ok, well as long as it doesn't have any security implications or other things I'm ok. Has it? But the best would have been to get it correct. Previously I had a zone called just agitel.no with both MX and A host. I still have it, but seemed that it only worked when I made the zone mail.agitel.no with both MX and A. Which zone do you suggest I use/create?

Similar Threads

  1. Mail deferred with Connection timed out
    By Miklos Kalman in forum Administrators
    Replies: 7
    Last Post: 11-17-2012, 05:11 AM
  2. Replies: 7
    Last Post: 02-03-2011, 06:01 AM
  3. No email in or out
    By ValueVPS in forum Installation
    Replies: 37
    Last Post: 01-13-2010, 11:56 AM
  4. Help!!! Moving ZCS does not work!
    By ASebestian in forum Migration
    Replies: 7
    Last Post: 02-12-2009, 05:06 PM
  5. server dropped connection
    By ferra in forum Installation
    Replies: 20
    Last Post: 10-06-2008, 04:32 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •