[SOLVED] No mail after Zimbra 5.0.1 and a new SSL Cert

[fizi]

I updated Zimbra 5.0 (which was working just fine) to Zimbra 5.0.1 and then generated a new self-assigned certificate changing my Common Name from 'mydomain.ca' to 'webmail.mydomain.ca' as to remove an annoying SSL popup and because I couldn't get -subjectAltNames flag to work.

Zimbra was loading fine but it was not receiving any e-mail it appears.

In the /opt/zimbra/log/mailbox.log I found a whole lot of this:

2008-01-12 00:36:28,685 INFO  [btpool0-7] [ip=127.0.0.1;] SoapEngine - handler exception
com.zimbra.cs.account.AccountServiceException: no such domain: webmail.mydomain.ca
Code:account.NO_SUCH_DOMAIN

Today I tried to send out going e-mail and I was greeted with a "The server appears to be slow to respond, and may be unavailable." dialog box. After a long enough time I got:

msg: system failure: MessagingException
code: service.FAILURE
method: ZmCsfeCommand.prototype.invoke
detail: soap:Receiver

Today I regenerated the default self-assigned SSL certificate for mydomain.ca and am now able to send/receive e-mail.

Now every time I start and stop Zimbra using 'zmcontrol' I get a large display of errors for the antispam.

Starting antispam...0    INFO  [main] log - Logging to org.slf4j.impl.Log4jLoggerAdapter(org.mortbay.log) via org.mortbay.log.Slf4jLog
0    INFO  [main] log - Logging to org.slf4j.impl.Log4jLoggerAdapter(org.mortbay.log) via org.mortbay.log.Slf4jLog
Zimbra server reserving server socket port=995 bindaddr=null ssl=true
Zimbra server reserving server socket port=995 bindaddr=null ssl=true
Zimbra server reserving server socket port=143 bindaddr=null ssl=false
Zimbra server reserving server socket port=993 bindaddr=null ssl=true
Zimbra server reserving server socket port=7025 bindaddr=null ssl=false
817  INFO  [main] log - Setting umask=02
818  INFO  [main] log - Setting GID=501
818  INFO  [main] log - Setting UID=501
818  INFO  [main] log - jetty-6.1.5
935  INFO  [main] log - No Transaction manager found - if your webapp requires one, please configure one.
Zimbra server reserving server socket port=143 bindaddr=null ssl=false
Zimbra server reserving server socket port=993 bindaddr=null ssl=true
Zimbra server reserving server socket port=7025 bindaddr=null ssl=false
817  INFO  [main] log - Setting umask=02
818  INFO  [main] log - Setting GID=501
818  INFO  [main] log - Setting UID=501
818  INFO  [main] log - jetty-6.1.5
935  INFO  [main] log - No Transaction manager found - if your webapp requires one, please configure one.
Zimbra server process is running as uid=501 euid=501 gid=501 egid=501
Zimbra server process is running as uid=501 euid=501 gid=501 egid=501
Done.

I've attached as much of the shutdown error as I can but it goes off my terminals scroll limit and when I try to pipe the output of zmcontrol into a file it doesn't actually put the errors in the file just the "mailbox......Done" part of things.

Seems Zimbra randomly decides to forget it has a SSL Certificate to and I have to regenerate it after a shutdown/startup.

[fizi]

All of the above listed errors and problems have gone away since following these instructions: [SOLVED] Expired Cert in 5.0GA can cause mail Delivery failure