Results 1 to 3 of 3

Thread: Zimbra-cluster and Mailman issue

  1. #1
    Join Date
    Apr 2007
    Location
    WV
    Posts
    49
    Rep Power
    8

    Default Zimbra-cluster and Mailman issue

    I followed the instructions per the <a href=http://www.zimbra.com/forums/administrators/1380-zimbra-mailman-howto.html>Zimbra+Mailman Howto</a> with a few minor exceptions. Mainly, since I am running a single node cluster, I created the mailman directory under /opt/zimbra-cluster/mountpoints/clustername/mailman and sym-linked it back to /usr/local/mailman. The pages work just fine and become available during failover.

    The main issue is that the emails to any given list keep bouncing back. These servers are still being built/tested, so the domain mx record does not point to them. But, I didn't think that mattered since it is being delivered to localhost.

    Also, I've noticed that any changes I make to the postfix main.cf are being over written somehow. I save the changes, check the file and it's ok - go back a few minutes later and it's back like it was originally. Ideas?

    Here's an example of a bounced message:

    #######################################
    Received: by mx.domain.com (Postfix)
    id 31FA21DB8046; Fri, 27 Jul 2007 09:42:52 -0400 (EDT)
    Date: Fri, 27 Jul 2007 09:42:52 -0400 (EDT)
    From: MAILER-DAEMON@mx.domain.com (Mail Delivery System)
    Subject: Undelivered Mail Returned to Sender
    To: briasrapier@domain.com
    MIME-Version: 1.0
    Content-Type: multipart/report; report-type=delivery-status;
    boundary="1E6391DB8045.1185543772/mx.domain.com"
    Content-Transfer-Encoding: 8bit
    Message-Id: <20070727134252.31FA21DB8046@mx.domain.com>

    This is a MIME-encapsulated message.

    --1E6391DB8045.1185543772/mx.domain.com
    Content-Description: Notification
    Content-Type: text/plain

    This is the Postfix program at host mx.domain.com.

    I'm sorry to have to inform you that your message could not
    be delivered to one or more recipients. It's attached below.

    For further assistance, please send mail to <postmaster>

    If you do so, please include this problem report. You can
    delete your own text from the attached returned message.

    The Postfix program

    <tlcsysadmins@tlcdelivers.com>: domain.com

    --1E6391DB8045.1185543772/mx.domain.com
    Content-Description: Delivery report
    Content-Type: message/delivery-status

    Reporting-MTA: dns; mx.domain.com
    X-Postfix-Queue-ID: 1E6391DB8045
    X-Postfix-Sender: rfc822; briansrapier@domain.com
    Arrival-Date: Fri, 27 Jul 2007 09:42:52 -0400 (EDT)

    Final-Recipient: rfc822; tlcsysadmins@domain.com
    Action: failed
    Status: 5.0.0
    Diagnostic-Code: X-Postfix; domain.com

    --1E6391DB8045.1185543772/mx.domain.com
    Content-Description: Undelivered Message
    Content-Type: message/rfc822
    Content-Transfer-Encoding: 8bit

    Received: from localhost (localhost.localdomain [127.0.0.1])
    by mx.domain.com (Postfix) with ESMTP id 1E6391DB8045
    for <tlcsysadmins@domain.com>; Fri, 27 Jul 2007 09:42:52 -0400 (EDT)
    X-Virus-Scanned: amavisd-new at
    X-Spam-Score: -4.399
    X-Spam-Level:
    X-Spam-Status: No, score=-4.399 tagged_above=-10 required=6.6
    tests=[ALL_TRUSTED=-1.8, BAYES_00=-2.599]
    Received: from mx.domain.com ([127.0.0.1])
    by localhost (mx.domain.com [127.0.0.1]) (amavisd-new, port 10024)
    with ESMTP id qzQsr-plHqok for <tlcsysadmins@domain.com>;
    Fri, 27 Jul 2007 09:42:46 -0400 (EDT)
    Received: from mx.domain.com (mx.domain.com [10.10.22.10])
    by mx.domain.com (Postfix) with ESMTP id E87711DB8044
    for <tlcsysadmins@domain.com>; Fri, 27 Jul 2007 09:42:46 -0400 (EDT)
    Date: Fri, 27 Jul 2007 09:42:46 -0400 (EDT)
    From: B A <briansrapier@domain.com>
    To: tlcsysadmins <tlcsysadmins@domain.com>
    Message-ID: <15643654.101185543766858.JavaMail.root@wsl-mx1.domain.com>
    Subject: Test
    MIME-Version: 1.0
    Content-Type: text/plain; charset=utf-8
    Content-Transfer-Encoding: 7bit
    X-Originating-IP: [10.10.57.107]

    --1E6391DB8045.1185543772/mx.tlcdelivers.com--

    #######################################

  2. #2
    Join Date
    Oct 2005
    Location
    Thatcher, AZ
    Posts
    5,606
    Rep Power
    21

    Default

    Hi Brian-
    Have you tried contacting amitbapat?

    He may be able to help more.

    john

  3. #3
    Join Date
    Apr 2007
    Location
    WV
    Posts
    49
    Rep Power
    8

    Default

    Sort of. I posted the same information to the end of his howto thread. However, also being a Zimbra customer, I have been in contact with their sales engineers as well.

    So far, no resolution for mailman on the same server, but I did a nice work around. I had an older server that was no longer being used and I pressed it back into service as my list server. In order to make it work the way I'd
    like, I have created distribution lists for each of the mailing lists to
    redirect the incoming email to the list server. Example:

    list@domain.com -> list@listserv.domain.com

    On the list server, I have modified sendmail to only accept connections
    from the mx server. Once the message is processed by Mailman, I have a
    rule to rewrite the RHS address:

    list@listserv.domain.com -> list@domain.com

    Then the server is allowed to send out without passing back through the
    mx server, thereby reducing load and negating the need to scan the same
    message twice.

    I suppose this is a bit convoluted, but it works very well so far -
    blazing fast... at least compared to our existing mail server which is a
    piece of garbage.

Posting Permissions

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