[quote user="Thomas R. Stephenson"]> Now the IMAP4 protocol has many problems of it's own so in this case I'm not too sure anyone, even the original UW developers, ever get this right.

[/quote]

Sorry Thomas, did not quote the sentence that I was referring to.

IMAP4 is a busy protocol is true, having problems is what I would challenge or disagree with. Looking at the Exchange 2000 thru 2010 protocol makes IMAP seem very simple and robust. Having to admin Exchange 2k-210 for anywhere from 300 to 45k endusers I am glad to be away from it.

As with pop3/smtp you very well know and see how different clients play fast and loose with RFC's.

Mark Crispin is one of the original developers of the protocol and major sections of Pine which was used to develop other clients.

Sorry this is getting OT.

I like and use Pegasus, it has some quarks, but it gets the job done. Pegasus follows e-mail standards, sometimes having to bend them in order to communicate with broken servers/clients. It is a very tough job for David H and the beta group which I do appreciate, not member of the 1000 but do make donations when possible (next scheduled for march).

As a long term user of Pegasus mail, I have been fighting a rear-guard action to continue using the mailer in the face of my local University trying to force everyone onto Microsoft exchange. I have been able to continue to use pegasus mail using the pop3 protocol.

My question concerns access to shared mailboxes. In outlook 07 this is done  through access to the Microsoft exchange server so I tried to do this using imap but have not been successful. Is this possible with pegasus mail or is this a feature of microsoft exchange that is proprietary? 

I am using pegasus mail v 4.52 with Windows XP.

If the Mail Admins did not enable IMAP (which is broken anyway - MS and real standards do not mix) on the Exchange server then you will most likely be out of luck. Exchange by default does Microsoft own protocol and not pop3/imap unless the 'transport' is enabled.

> If the Mail Admins did not enable IMAP (which is broken anyway - MS and real standards do not mix) on the Exchange server then you will
> most likely be out of luck. Exchange by default does Microsoft own protocol and not pop3/imap unless the 'transport' is enabled.

Actually I've found that MS Exchange does quite well with IMAP4.  Our group was a Mercury/Pegasus Mail setup in a Exchange/Lookout environment  and the IMAP4 connection and LDAP worked quite well.  

Now the IMAP4 protocol has many problems of it's own so in this case I'm not too sure anyone, even the original UW developers, ever get this right.
 

[quote user="aderoy"]If the Mail Admins did not enable IMAP (which is broken anyway - MS and real standards do not mix) on the Exchange server then you will most likely be out of luck. Exchange by default does Microsoft own protocol and not pop3/imap unless the 'transport' is enabled.[/quote]

I have been working at the Inet sphere for some years and couple times saw similar issues. To my mind one of the best solution may become the next software which I had found a soft portal. It has many good resources and proved that is able to manage any kind of problem - software rebuild database exchange. 

Would have to challenge that:

Mulberry, Alpine/Pine, Sylpheed are all clients (multiplatform to boot) that handle IMAP with ease. These plus Pegasus, Opera M2 and Thunderbird (not great) are the better than most to use with Fastmail and Dovecot under IMAP.

Would have to challenge that:

Mulberry, Alpine/Pine, Sylpheed

are all clients (multiplatform to boot) that handle IMAP with ease.

These plus Pegasus, Opera M2 and Thunderbird (not great) are the better

than most to use with Fastmail and Dovecot under IMAP.

Challenge what?  IMAP4 is a very busy protocol that is not implemented consistently across servers as is POP3 and SMTP.  The IMAP4 developers can't even agree most of the time exactly what each of the requirements of the RFC mean. Since I always keep the major mail clients installed, Outlook 2002, OE, T-bird, Eudora plus Sylpheed and SquirrelMail and test against various IMAP4 servers it becomes apparent that not all IMAP4 servers work all that well.  That said my Fastmail/GMail IMAP4 accounts work pretty well but I do not use them very extensively not do I stress them with huge mailboxes, I do not have a Dovecot server to test against. I do test all of these clients against huge mailboxes on Mercury with mixed results.