Re: [courier-users] Problems with Apple Mail.app 2.0/2.0.1 (Tiger) and Courier servers?

I thought that others on the list might like to know that upgrading
to courier 0.50 fixed the problems that I was seeing.

On May 17, 2005, at 10:29 AM, Matthew Wilson wrote:

> I'm seeing a problem where a flaky internet connection combined
> with Mail 2.0's aggressive queries causes imapd processes to get
> disconnected from the client and run themselves out. At one point
> my normally quiet mail server had a load average of about 100
> because there were so many imapds reading from disk and sending the
> results into the ether.
>
> Once I've got a good connection to the mail server (no flaky DSL
> line involved) then everything works fine.
>
> I've currently got a script running that looks for abandoned imapd
> processes and kills them off. I had been meaning to write to the
> list about this but hadn't gotten around to it.
>
> (fyi: I'm running courier 0.46 on redhat 7.3)
>
> Matthew
>
> On May 17, 2005, at 10:00 AM, Bill Taroli wrote:
>
>
>
>> Oh, I struggled with Mail.app hoping it would work (and I do run
>> 10.4 on all my Macs now).. but then I tried a variety of IMAP
>> clients to gauge them. And after all this, I still come up with
>> the same simple answer:
>>
>> Thunderbird
>>
>> Bill
>>
>>
>> Greg Earle wrote:
>>
>>
>>
>>
>>> Starting with 10.3.9, the Apple Mail.app client has not played
>>> nice in the sandbox with Courier. The 10.4 client (Mail.app 2.0;
>>> now 2.0.1 in 10.4.1) fares no better. This is what I posted to
>>> MacInTouch a week ago regarding the symptoms I'm seeing:
>>>
>>> "Mail.app 2.0 has been a disaster for me. Performance with my main
>>> e-mail (IMAP) server at work has been extremely sluggish - I can go
>>> to a folder with only 1 new e-mail in it and instead of it being
>>> shown
>>> immediately, the "1" indicator turns into a clock and it takes
>>> minutes
>>> to update the counter and display the message.
>>>
>>> But that's only the start of it. I have a secondary backup/testbed
>>> e-mail server (also Courier IMAP) that uses, for expediency's sake,
>>> the same SSL Certificate as the main server. Since the hostnames
>>> don't match, the Certificate is technically invalid. But 10.3.8's
>>> Mail.app worked just fine with it - it would ask you on first
>>> connection if you wanted to Continue, and you could just click on it
>>> and things worked fine. (I also have a home e-mail server, using
>>> the
>>> same software, but with a self-signed certificate. It's also
>>> "invalid".)
>>>
>>> With this Certificate issue, I cannot use the testbed e-mail server
>>> when Secure IMAP (on port 993) is in use. I have to fall back to
>>> unsecure (port 143) IMAP where passwords are sent in the clear -
>>> which
>>> is clearly not a long-term solution. But because I'm not willing to
>>> send cleartext passwords over the Internet, I cannot use my home
>>> e-mail
>>> server at all - Mail.app 2.0 connects, but it never shows any new
>>> e-mail.
>>>
>>> I thought it was a problem with Mail.app 2.0's Import function, so I
>>> deleted the account and recreated it manually. I then did a
>>> Synchronize so that all of the home e-mail messages were sucked up
>>> and cached. While that worked, once everything was pulled in, it
>>> went
>>> right back to its previous behavior of not pulling in new e-
>>> mail! VERY
>>> frustrating ...
>>>
>>> In short, Mail.app 2.0 has been an unmitigated disaster in my
>>> environment.
>>> Something is clearly wrong with Mail.app 2.0 vs. invalid/expired SSL
>>> Certificates, at a minimum. I even tried pulling all of the
>>> Certificates onto my Mac (using Keychain Access' new "Certificate
>>> Assistant" sidecar app) and changing the policy on all of them to
>>> "Always Trust" (in Keychain Access), and it *still* doesn't work.
>>> I sure hope Apple fixes this soon ... "
>>>
>>> Other people have been mentioning Mail.app problems, and Courier
>>> IMAP
>>> comes up a lot in these posts.
>>>
>>> Now, mind you, I don't think Courier is doing anything wrong here -
>>> the fact that the Mail.app in 10.3.8 works just fine is proof of
>>> that
>>> (and, to be more specific, Entourage and Thunderbird work just fine
>>> with it in 10.4.1, too). I'm just posting to the list to see if
>>> there's anyone else out there who uses Apple's Mail.app 2.0(.1) with
>>> a Courier server, and I'd be especially keen to know if anyone uses
>>> multiple IMAP servers where one (or more) is Courier and there's
>>> at least one other one they're using that isn't - and whether or
>>> not they're having problems talking to the Courier server but not
>>> the others. I'm hoping there's some common thread, and that perhaps
>>> there's a way to change something in Courier's setup that can work
>>> around this new Apple brain-damage in the Mail.app client.
>>>
>>> Thanks,
>>>
>>> - Greg
>>>
>>>
>>>
>>> -------------------------------------------------------
>>> This SF.Net email is sponsored by Oracle Space Sweepstakes
>>> Want to be the first software developer in space?
>>> Enter now for the Oracle Space Sweepstakes!
>>> http://ads.osdn.com/?ad_id=7412&alloc_id=16344&op=click
>>> _______________________________________________
>>> courier-users mailing list
>>> courier-users@lists.sourceforge.net
>>> Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-
>>> users
>>>
>>>
>>>
>>
>>
>>
>> -------------------------------------------------------
>> This SF.Net email is sponsored by Oracle Space Sweepstakes
>> Want to be the first software developer in space?
>> Enter now for the Oracle Space Sweepstakes!
>> http://ads.osdn.com/?ad_id=7412&alloc_id=16344&op=click
>> _______________________________________________
>> courier-users mailing list
>> courier-users@lists.sourceforge.net
>> Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-
>> users
>>
>>
>>
>
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by Oracle Space Sweepstakes
> Want to be the first software developer in space?
> Enter now for the Oracle Space Sweepstakes!
> http://ads.osdn.com/?ad_id=7412&alloc_id=16344&op=click
> _______________________________________________
> courier-users mailing list
> courier-users@lists.sourceforge.net
> Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-
> users
>



-------------------------------------------------------
This SF.Net email is sponsored by Yahoo.
Introducing Yahoo! Search Developer Network - Create apps using Yahoo!
Search APIs Find out how you can build Yahoo! directly into your own
Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005
_______________________________________________
courier-users mailing list
courier-users@lists.sourceforge.net
Unsubscribe: https://lists.sourceforge.net/lists/.../courier-users