Well, you were right, and it did create a new cert (or at the very least changed the date on the cert file) but when I restarted sasl, I get the message below in the zimbra.log file:
Code:
Oct 31 14:19:47 mail postfix/smtpd[20576]: initializing the server-side TLS engine
Oct 31 14:19:47 mail postfix/smtpd[20576]: warning: cannot get private key from file /opt/zimbra/conf/smtpd.key
Oct 31 14:19:47 mail postfix/smtpd[20576]: warning: TLS library problem: 20576:error:0B080074:x509 certificate routines:X509_check_private_key:key values mismatch:x509_cmp.c:411:
Oct 31 14:19:47 mail postfix/smtpd[20576]: cannot load RSA certificate and key data
However, when I grep for sasl, it show that it is "running":
Code:
[root@mail ~]# ps aux | grep sasl
zimbra 22671 0.0 0.1 5812 1280 ? Ss 14:24 0:00 /opt/zimbra/cyrus-sasl-2.1.21.ZIMBRA/sbin/saslauthd -r -a zimbra
zimbra 22672 0.0 0.1 5812 1280 ? S 14:24 0:00 /opt/zimbra/cyrus-sasl-2.1.21.ZIMBRA/sbin/saslauthd -r -a zimbra
zimbra 22673 0.0 0.1 5812 1280 ? S 14:24 0:00 /opt/zimbra/cyrus-sasl-2.1.21.ZIMBRA/sbin/saslauthd -r -a zimbra
zimbra 22674 0.0 0.1 5812 1280 ? S 14:24 0:00 /opt/zimbra/cyrus-sasl-2.1.21.ZIMBRA/sbin/saslauthd -r -a zimbra
zimbra 22675 0.0 0.1 5812 1280 ? S 14:24 0:00 /opt/zimbra/cyrus-sasl-2.1.21.ZIMBRA/sbin/saslauthd -r -a zimbra
root 600 0.0 0.0 3764 676 pts/2 R+ 14:48 0:00 grep sasl
[root@mail ~]#
Additionally, I am having the same conditions as shown in the thread below, where I can send messages to outside mail servers when DNS lookups are enabled, but I can't receive. And then if I disable DNS lookups, I can receive but not send:
Zimbra Send OR recieve, not both
The only thing that I haven't tried in this post is to open up port 7025... which I don't quite understand why that would be necessary.
I feel like I am getting SO CLOSE to getting it to work correctly! As soon as I get it figured out, I'm going to write up my exact install specs, so I can attach it to a post and say "RTFM, n00b!" when anyone asks questions like mine.
