Results 1 to 8 of 8

Thread: Cannot send mail after upgrade from 7.2.1. to 8 (ose)

Threaded View

  1. #1
    Join Date
    Mar 2012
    Posts
    6
    Rep Power
    3

    Wink [SOLVED ?] Cannot send mail after upgrade from 7.2.1. to 8 (ose)

    Hi All,

    =====
    I kind of solved the problem below by:

    - unchecking the milter server in the MTA settings pages in the admin console.
    - removing the milter server name (was pointing to my own mailserver name.
    - restarting. I can send mail again.

    Then I experimented a bit:

    - rechecking the milter server and restarting zimbra: I can still send mail.
    - setting the milter server name to "localhost" and restarting: Still able to send mail.
    - setting the milter server name to my email server fqdn hostname: Not able to send mail.
    - setting the milter server name back to localhost: Can send mail again!

    So it seems that using my fqdn server name is the source of the problem. I am still not shure of why this can be.

    =====

    A few days ago I upgraded my Zimbra 7.2.1. Open Source Edition to Zimbra 8 (O.S.E.). Zimbra is running on Ubuntu 10.04 LTS.
    I had no problems whatsoever with running 7.2.1.

    I'm not running split DNS, but I do use a relay host for all outbound emails using smtp authentication. I did a renewed setup of that after the upgrade to zimbra 8.

    Since the upgrade I cannot send email. Receiving works ok. After some searching in the mail.log file I found the following error:

    Sep 18 20:23:14 email postfix/smtpd[13609]: connect from email.xxxxxxxx.xx[999.999.999.999]
    Sep 18 20:23:14 email postfix/smtpd[13609]: warning: connect to Milter service inet:localhost:8465: Connection refused
    Sep 18 20:23:14 email postfix/smtpd[13609]: NOQUEUE: milter-reject: CONNECT from email.xxxxxxxx.xx[999.999.999.999]: 451 4.7.1 Service unavailable - try again later; proto=SMTP
    Sep 18 20:23:14 email postfix/smtpd[13609]: NOQUEUE: milter-reject: EHLO from email.xxxxxxxx.xx[999.999.999.999]: 451 4.7.1 Service unavailable - try again later; proto=SMTP helo=<email.xxxxxxxx.xx>
    Sep 18 20:23:14 email postfix/smtpd[13609]: NOQUEUE: milter-reject: MAIL from email.xxxxxxxx.xx[999.999.999.999]: 451 4.7.1 Service unavailable - try again later; from=<henry@vorsterp.nl> proto=ESMTP helo=<email.xxxxxxxx.xx>
    Sep 18 20:23:14 email postfix/smtpd[13609]: disconnect from email.xxxxxxxx.xx[999.999.999.999]


    What struck me was that the milter service seems to be listening on port 8465. In my mta-settings on the admin console the bind port is 7026. The milter server checkbox is checked. Furthermore I found out that an opendkim process is listening to 8465. To be honest, I had no idea what that opendkim does or why I need it. But it seems to be conflicting with the milter settings in the admin console.

    I have tried the following:

    - unchecking the milter server checkbox and restarting zimbra. No effect.
    - Changing the milter server bind address to 8465, with the milter server checkbox on and off. No effect.

    The milter service is running (checked with zmmilterctl status).

    So now I am at a loss. Are there any setting that I have missed? Are there any changes I should make? Help is most welcome!

    Kind regards,

    Henry
    Last edited by henryvandevorst; 09-19-2012 at 05:34 AM.

Similar Threads

  1. Replies: 2
    Last Post: 06-05-2011, 11:56 PM
  2. [SOLVED] Upgrade to 6.0.9 - can't send mail
    By mingus8686 in forum Installation
    Replies: 0
    Last Post: 12-20-2010, 09:50 AM
  3. [SOLVED] Can't send mail after upgrade
    By bluenix in forum Installation
    Replies: 1
    Last Post: 10-06-2008, 06:52 AM
  4. Replies: 9
    Last Post: 01-26-2007, 05:31 AM
  5. Mail send problem after upgrade
    By cutigersfan in forum Administrators
    Replies: 2
    Last Post: 05-13-2006, 06:28 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
  •