Results 1 to 2 of 2

Thread: Header problems from AWS MX server

  1. #1
    Join Date
    Aug 2009
    Posts
    25
    Rep Power
    6

    Default Header problems from AWS MX server

    I've recently moved our Zimbra server and our sendmail-based MX server to Amazon's EC2 service. Everything is working fine except for one minor glitch that really doesn't hurt anything, but is simply an annoyance (at least for now it is only an annoyance).

    If mail is generated on the MX server (say, for instance, via cron), it gets sent to the Zimbra server with headers as follows:

    From: somebody@mx.example.com
    To: me@mx.example.com

    which is fine - that's the way I want the headers to look. However, when it arrives in my Zimbra mailbox, the headers have been rewritten as follows:

    From: somebody@ec2-##-##-##-##.compute-1.amazonaws.com
    To: me@ec2-##-##-##-##.compute-1.amazonaws.com

    which is not what I want. I've tracked this down as something that is occurring on the Zimbra server - if I telnet in to port 25 and send the headers I want, they still end up being rewritten somewhere in the Zimbra system.

    ec2-##-##-##-##.compute-1.amazonaws.com is the "real" name for our MX server, with mx.example.com being a CNAME that points to that name. Reverse DNS returns mx.example.com

    Any ideas about how to prevent Zimbra from rewriting these headers?

    TIA

    PS. The header says I'm using release 5.0.18 - we're actually using zcs-6.0.14_GA_2928.RHEL5_64.20110802123437 (not sure how to change the header)
    Last edited by WolfyPDX; 08-30-2011 at 08:41 PM. Reason: updating info

  2. #2
    phoenix is offline Zimbra Consultant & Moderator
    Join Date
    Sep 2005
    Location
    Vannes, France
    Posts
    23,587
    Rep Power
    58

    Default

    Quote Originally Posted by WolfyPDX View Post
    ec2-##-##-##-##.compute-1.amazonaws.com is the "real" name for our MX server, with mx.example.com being a CNAME that points to that name. Reverse DNS returns mx.example.com

    Any ideas about how to prevent Zimbra from rewriting these headers?
    A CNAME should never be used to point to a mail server, it can cause problems (including lost mail). In these circumstances, however, it would appear the system is working correctly - Zimbra (Postfix) does an MX lookup for your other server and does not use the CNAME.

    Quote Originally Posted by WolfyPDX View Post
    PS. The header says I'm using release 5.0.18 - we're actually using zcs-6.0.14_GA_2928.RHEL5_64.20110802123437 (not sure how to change the header)
    It went walkabout during a recent software upgrade, you can modify it here: www.zimbra.com/forums/profile.php?do=editprofile
    Regards


    Bill


    Acompli: A new adventure for Co-Founder KevinH.

Similar Threads

  1. centos 5 zcs 7: Server Status Problems - again
    By alex_rhys-hurn in forum Administrators
    Replies: 0
    Last Post: 03-09-2011, 04:03 AM
  2. Please help
    By scott_summers in forum Administrators
    Replies: 0
    Last Post: 09-27-2007, 12:11 AM
  3. Zimbra Installation Problems (RHEL AS v4)
    By stillwell in forum Installation
    Replies: 15
    Last Post: 06-28-2007, 08:58 PM

Tags for this Thread

Posting Permissions

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