[SOLVED] imapproxy conflict since 4.5.10 > 5.0.0 upgrade

[centrex]

Hi,

Since upgrading from 4.5.10GA to 5.0.0GA, users can no longer download messages via IMAP. Clients are using the Thunderbird client, connecting to IMAP over SSL on port 993 and can usually see mail headers, but when they try to open a message it comes up with blank content. Viewing the same message from within the web interface works just fine.

Sometimes Thunderbird displays an error "Mail Server mail.domain.com is not an IMAP4 mail server." At this point, I can restart zimbra and this message won't occur for a while, reverting back to the issue with the mail bodies being empty.

Prior to the upgrade from 4.5.10 this never happened.

Server status shows all services, including imapproxy are running just fine.

If I telnet to port 143, I get this:

* OK IMAP4 ready
BAD invalid command


The "capability" command returns:

* CAPABILITY IMAP4rev1 STARTTLS BINARY CHILDREN ID LITERAL+ LOGIN-REFERRALS NAME SPACE QUOTA SASL-IR UIDPLUS UNSELECT STARTTLS

[phoenix]

Is this a single server install? If it is, why are you using the proxy? If it's not, what is the exact configuration of your system?

[centrex]

Is this a single server install? If it is, why are you using the proxy? If it's not, what is the exact configuration of your system?

Hi,

Yes, it's a single server install. When I originally upgraded from 4.5.10 to 5.0.0 without imapproxy, I would get "connection refused" on imap and imaps, so I installed imapproxy thinking this is some sort of 5.0.0. quirk.

I will try without imapproxy and see how I go.

[phoenix]

You shouldn't need the proxy enabled, if this is a straight zimbra install on one box then the proxy is unnecessary. Let us know what happens when you disable it.

[centrex]

Just did a yum remove zimbra-proxy and reinstalled 5.0.0, this time keeping the default answer "no" when prompted if I want zimbra-proxy.

Same as when I originally upgraded 4.5.10 to 5.0.0, there were no errors during the process, but now connections are refused on 110, 143 and their SSL counterparts.

FWIW SMTP is responding.

When I log into the admin interface, imapproxy is stil listed, but it's showing as stopped / failed with a red X next to it.

[phoenix]

Did you get any errors in the installation logs? What does this command show:

zmproxyctl status

[centrex]

I was watching the installation live in the console and could not see any errors. Going over the log file now I cannot see anything that indicates trouble.

But should imapproxy show in the admin console when it's not even installed ?

Should I need it in the first place when the MTA and the IMAP are all on the same host ? I never needed it before. Only tried it today because originally after upgrading to 5.0.0, connections to imap and imaps were being refused.

[zimbra@mail ~]$ zmproxyctl status
nginx is not running
memcached is running

[zimbra@mail ~]$ rpm -qa | grep zimbra
zimbra-core-5.0.0_GA_1869.RHEL4_64-20071218185942
zimbra-snmp-5.0.0_GA_1869.RHEL4_64-20071218185942
zimbra-ldap-5.0.0_GA_1869.RHEL4_64-20071218185942
zimbra-mta-5.0.0_GA_1869.RHEL4_64-20071218185942
zimbra-store-5.0.0_GA_1869.RHEL4_64-20071218185942
zimbra-spell-5.0.0_GA_1869.RHEL4_64-20071218185942
zimbra-logger-5.0.0_GA_1869.RHEL4_64-20071218185942
zimbra-apache-5.0.0_GA_1869.RHEL4_64-20071218185942

[centrex]

One interesting thing I found is that during the 5.0.0 install, the script pauses at one point, asking for a password and won't continue without interaction.

Pressing ENTER at that point resumes the script.

It happens just after you get the option to notify Zimbra of your install:

Notify Zimbra of your installation? [Yes] no
Notification skipped
Starting servers...Password:
done.

[centrex]

Phoenix,

Your questions lead me down a productive track..

It seems my installation is confused about whether imapproxy is in use or not.

I need to find a way to make it clear to zimbra that imapproxy shouldn't be installed, used or relied upon. I just nmapped the machine, and I can see that IMAP, IMAPs and POP3 / POP3s are running, but on ports 7110, 7143, 7993, etc.

[phoenix]

You shouldn't have memcached running either, try running

zmproxyctl stop

then run the status command again and see if it's gone away. The answer to your questions is, no you don't need the proxy on a single server install.

[edit] ...... and it shouldn't show in the admin ui either if it's disabled.