MBOX-Line: From guenther+imap at sendmail.com  Thu Aug 31 23:31:03 2006
To: imap-protocol@u.washington.edu
From: Philip Guenther <guenther+imap@sendmail.com>
Date: Fri Jun  8 12:34:37 2018
Subject: [Imap-protocol] changed capabilities after login
In-Reply-To: <Pine.WNT.4.65.0608311723400.2392@Tomobiki-Cho.CAC.Washington.EDU>
References: <20060901002118.GB16606@ventoux.cs.ubc.ca>
	<Pine.WNT.4.65.0608311723400.2392@Tomobiki-Cho.CAC.Washington.EDU>
Message-ID: <Pine.BSO.4.64.0609010022420.28193@vanye.mho.net>

On Thu, 31 Aug 2006, Mark Crispin wrote:
...
> The untagged CAPABILITY response to a CAPABILITY command always announces all 
> capabilities in UW imapd.  Mirapoint, on the other hand, seems to suppress 
> inappropriate capabilities.

The word "PROXY" in the Mirapoint banner makes me guess (haha) that while 
the first CAPABILITY response is generated by Mirapoint's software, once 
you log in it just goes into a 'pass through' mode talking to some other 
IMAP server.  Thus the different capabilities before and after 
authentication.

You should consult the Mirapoint documentation: there may be a way to 
configure the (pre-authentication) capabilities that it announces. 
Removing ACL from that set would be a more friendly behavior by the 
server.


> The Mirapoint server has one strange behavior; it only announces 
> LOGIN-REFERRALS after authentication.  Since that's only useful prior to 
> authentication, it seems a bit strange.

Not if it's the server 'behind' Mirapoint's proxy that supports 
LOGIN-REFERRALS...


Philip Guenther

