Zimbra Forums

su - zimbra
Then run the command.
Step by step.
Have never had it ask for password.

Do a search in the wiki. It will probably be the first return. Follow it step by step.

You may need to use the zmsetservername utility. Not sure how this would affect the domain setup as the default. I would probably setup a test server to see if the above worked and any residual effects if any.

Every install I've done always tries to use the FQDN instead of just the domain suffix during the install. So when it prompts you with the MX error during install you must change the domain from the FQDN to the domain suffix. It should resolve at this point.

was what I ended up doing. Including MTA and the web interface. Not sure which SSL was actually causing the problem so I made sure all was disabled. I also made sure all clear text authentication was enabled and did the IMAP migration in clear text. I made sure all clear text firewall ports were ope...

Figured the problem out myself.

Is using a commercial cert the only answer to this problem? I'm having the exact same problem. SSL for IMAP is turned off so I'm not sure why the two servers are doing an SSL handshake.
I know this is an old post but wondering if anyone having this problem has made it work.

Server settings. "MTA", "IMAP", and "POP"

plain text authentication. So if the SSL connection is not made, the auth appears as plain text and is not accepted. This is how the SSL connection is enforced. Plus the port is not the issue. An SSL connection can be made using port 25 as long as the server and client support it. It is the hand sha...

My take on this is the client and server make an SSL connection at which point all communication is encrypted, including the authentication. However, if the authentication takes place before an SSL connection is made then the login would be unencrypted. I believe the former is the case and and that ...