Well the symptom is that the OS X mail client just times out. It talks to port
993 on the server for a while, but just shows the user a moving icon.
Eventually it complains the mail server didn't respond. 10.3 and 10.4 work
fine, strangely enough. It times out as it's "checking connection to the mail
server."
I did upgrade from dovecot 1.0 to 1.1 without doing much of any config changes
on the dovecot side. But other clients work fine...
Actually I just realized while watching tcpdump that Mail.app is testing port
25 after 993. So it may be a Postfix SSL failure of some sort.
Chris
Peter Giessel [EMAIL PROTECTED] wrote:
> On Friday, December 05, 2008, at 10:45AM, "Chris Cappuccio" <[EMAIL
> PROTECTED]> wrote:
> >People using the new OS X mail client are unable to connect to the unsigned
> >dovecot-mkcert.sh certificate on my Dovecot installations. Turning off SSL
> >fixes the problem. Is there any way to make it work automatically, or do I
> >just have to get the certificates signed? Has anyone figured this one out
> >before?
>
> I have an unsigned SSL certificate with Dovecot and
> connect fine using OSX.5's Mail.app. What do you
> mean, "unable to connect"? Do you really mean
> "unable to connect", or do you mean, "an error
> message comes up every time they try to connect"?
>
> If its the latter complaint, please see this document:
> http://support.apple.com/kb/TA22383
>
> I know it says 10.3 Mail, but the steps to follow are
> essentially unchanged between 10.3 and 10.5.