MBOX-Line: From miguel at mtelleria.com  Fri Jan 20 02:18:41 2006
To: imap-protocol@u.washington.edu
From: Miguel Telleria de Esteban <miguel@mtelleria.com>
Date: Fri Jun  8 12:34:36 2018
Subject: [Imap-protocol] Telnet IMAP on Exchange 5.5
In-Reply-To: <E367CF6341304D4ABC5BF22A1BD34DAB3102DE@donald.chronotech.nl>
References: <E367CF6341304D4ABC5BF22A1BD34DAB3102DE@donald.chronotech.nl>
Message-ID: <1137752321.7151.8.camel@ines>

Hello Daan,

El vie, 20-01-2006 a las 10:28 +0100, Daan Rijnders escribi?: 
> Hello, 
>  
> I might be on the complete wrong list, but I still hope their might be
> someone who can send me into the right direction. 
>  
> I'm trying to connect to my exchange server using Telnet on port 143
> (IMAP). 

[Note:  I have never used Exchange and I am not familiar with its
particularities].

> I'm getting the mail servers welcome message, but then I need to enter
> my login credentials. 

This proves that as far as telnet is concerned the connection is
correctly established.

> I enter: "? Login domain/username password" (without the quotes) 

I don't know if maybe the character '?' would create a problem.  Use a
normal text label by typing something like:

	a001 login <user> <password>

> this results in an error: one of the requested permissions is not
> assigned to the client.

Can you send us the exact error message?  (this might help seeing the
problem).

Maybe for some reason the server does not succeed to create/read the
possibly needed mail storage area...

> I checked this on the Exchange server to see if my user is IMAP
> enabled and did the same thing in Active Directory. Both state that my
> user is able to use IMAP. 

I have never used Exchange but I have heard that indeed the user's IMAP
access needs to be explicitly enabled.  Apparently this is the case.

> Question: is this case sensitive? Should I use all CAPS? forward
> slashes?

AFAIK IMAP protocol is case insesitive to the commands.   Of course
login and password values are system dependent.

>  
> Is there any kind of guide on IMAP using telnet?

As I said above, I think that the problem is not related to telnet.
Exchange or any other server does not have the capacity to know whether
the connection comes from Outlook, Mozilla thunderbird or a telnet
process.

If you want to know the exact commands to send and the possible expected
responses I don't know of an available out-of-the-box guide (maybe
somebody here knows).

I would suggest the following approaches:

A)  Grab the IMAP standard (RFC3501) and give it a global overview.

B)  If you have access to a working IMAP server with an IMAP client,
    capture a session with Ethereal and try to reproduce it in the
    telnet connection.

> Microsoft has 1 KB article but I already noticed that they misspelled
> the login line, and they expect that the login works.
>  

Microsoft is well known for not following standards in their products.  

And besides, having their own exchange protocol I don't think they are
interested in promoting IMAP support beyond some basic needs (like
importing emails from an existing IMAP account).

So I wouldn't expect any help from them in this matter.

> Can anyone shine a light on this one?
>  
> Cheers,
> Daan
> 
>  
> _______________________________________________
> Imap-protocol mailing list
> Imap-protocol@u.washington.edu
> https://mailman1.u.washington.edu/mailman/listinfo/imap-protocol
-- 

      (O-O)
---oOO-(_)-OOo-----------------------------------------------------
 Miguel TELLERIA DE ESTEBAN               Personal Homepage:
 Email: Miguel at mtelleria.com           http://www.mtelleria.com

 Miembro de http://www.linuca.org         Tel home: +32 2 280 1614
 Membre de  http://www.bxlug.be           GSM:      +32 497 038804
-------------------------------------------------------------------
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 196 bytes
Desc: This is a digitally signed message part
URL: <http://mailman13.u.washington.edu/pipermail/imap-protocol/attachments/20060120/28254a98/attachment.sig>
