[imp] Horde accessing Exchange 2007 via POP3 or IMAP

[Liam Hoekenga]

The version of c-client your PHP installation is probably linked against 
kerberos.   If your exchange server is advertising the ability to do 
kerberos authentication, c-client will try to use it.  I believe that 
c-client will want to use the best authentication method available, and 
kerberos is far better than plaintext, cram/md5, etc.

Things to try..
- prevent the IMAP/POP server from advertising the ability to accept 
kerberos authentication
- try rebuilding c-client w/o kerberos  (you'll also need to rebuild the 
php imap extension, depending on how things are linked)

Liam

Games, Dax wrote:
> Tried it.  I get exactly the same message.  Why is Imp trying to use
> Kerberos?  The Exchange server is set to accept clear text login.
>  
> Dax
>
> ________________________________
>
> From: Andrew Morgan [mailto:morgan at orst.edu]
> Sent: Thu 8/16/2007 12:51 PM
> To: Games, Dax
> Cc: imp at lists.horde.org
> Subject: Re: [imp] Horde accessing Exchange 2007 via POP3 or IMAP
>
>
>
> Have you read the comments at the top of imp/config/servers.php?  You
> probably want to specify 'pop3/tls/novalidate-cert'.
>
>         Andy
>
>
> On Thu, 16 Aug 2007, Games, Dax wrote:
>
>   
>> I found this on Microsoft's site:
>> http://technet.microsoft.com/en-us/library/aa997290.aspx and now I get
>> this when running the Horde tests.
>>
>> server="host" user="user1" mailbox="{host:110/pop3}INBOX"
>>
>> array(2) {
>>  [0]=>
>>  string(58) "No credentials cache found (try running kinit) for host"
>>  [1]=>
>>  string(91) "Can not authenticate to POP3 server: The AUTH protocol
>> exchange was canceled by the client."
>> }
>>
>>
>> Dax
>>
>> ________________________________
>>
>> From: imp-bounces at lists.horde.org on behalf of Games, Dax
>> Sent: Thu 8/16/2007 12:25 PM
>> To: imp at lists.horde.org
>> Subject: Re: [imp] Horde accessing Exchange 2007 via POP3 or IMAP
>>
>>
>>
>> After further investigation I think the certificate error is due to
>>     
> the
>   
>> Horde box requesting a TLS connection to the POP3 server.  Can I
>>     
> disable
>   
>> this?  If so how?
>>
>> Or better yet how can I make it work with TLS?
>>
>> Thanks,
>>
>> Dax
>>
>> ________________________________
>>
>> From: imp-bounces at lists.horde.org on behalf of Games, Dax
>> Sent: Wed 8/15/2007 11:51 AM
>> To: imp at lists.horde.org
>> Subject: [imp] Horde accessing Exchange 2007 via POP3 or IMAP
>>
>>
>>
>> I am trying to setup Horde/IMP to login via POP3 or IMAP to an
>>     
> Exchange
>   
>> 2007 server.  Please don't ask WHY!
>>
>> Let's just say it is a requirement of the client.
>>
>> All host names and user ids below have been changed for security
>> reasons.
>>
>> POP 3 and IMAP both work via a third party email client with no
>>     
> special
>   
>> settings. My server config from servers.php is below:
>>
>> $servers['mail'] = array(
>>    'name' => 'Mail',
>>    'server' => 'mail.host.com',
>>    'protocol' => 'pop3',
>>    'port' => 110,
>>    'folders' => '',
>>    'namespace' => '',
>>    'maildomain' => 'host.com',
>>    'realm' => 'host.com',
>>    'preferred' => ''
>> );
>>
>> When I test authentication via
>>     
> http://horde.host.com/horde/imp/test.php
>   
>> I get:
>>
>> server="mail.host.com" user="user1"
>> mailbox="{mail.host.com:110/pop3}INBOX"
>>
>> array(1) { [0]=> string(99) "Certificate failure for host.com: unable
>>     
> to
>   
>> get local issuer certificate: /CN=mail" }
>>
>> Any ideas?
>>
>> Thanks,
>>
>> Dax
>>
>>
>> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
>>     
> _
>   
>> _ _
>>
>> The information contained in this transmission is confidential. It is
>> intended solely for the use of the individual(s) or organization(s)
>> to whom it is addressed. Any disclosure, copying or further
>>     
> distribution
>   
>> is not permitted unless such privilege is explicitly granted in
>> writing by SARCOM, Inc. Furthermore, SARCOM, Inc. is not responsible
>>     
> for
>   
>> the proper and complete transmission of the substance
>> of this communication, nor for any delay in its receipt.
>>
>> --
>> IMP mailing list - Join the hunt: http://horde.org/bounties/#imp
>> Frequently Asked Questions: http://horde.org/faq/
>> To unsubscribe, mail: imp-unsubscribe at lists.horde.org
>>
>>
>>
>>
>> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
>>     
> _
>   
>> _ _
>>
>> The information contained in this transmission is confidential. It is
>> intended solely for the use of the individual(s) or organization(s)
>> to whom it is addressed. Any disclosure, copying or further
>>     
> distribution
>   
>> is not permitted unless such privilege is explicitly granted in
>> writing by SARCOM, Inc. Furthermore, SARCOM, Inc. is not responsible
>>     
> for
>   
>> the proper and complete transmission of the substance
>> of this communication, nor for any delay in its receipt.
>>
>> --
>> IMP mailing list - Join the hunt: http://horde.org/bounties/#imp
>> Frequently Asked Questions: http://horde.org/faq/
>> To unsubscribe, mail: imp-unsubscribe at lists.horde.org
>>
>>
>>
>>
>> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
>>     
> _ _ _
>   
>> The information contained in this transmission is confidential. It is
>>     
> intended solely for the use of the individual(s) or organization(s)
>   
>> to whom it is addressed. Any disclosure, copying or further
>>     
> distribution is not permitted unless such privilege is explicitly
> granted in
>   
>> writing by SARCOM, Inc. Furthermore, SARCOM, Inc. is not responsible
>>     
> for the proper and complete transmission of the substance
>   
>> of this communication, nor for any delay in its receipt.
>>
>> --
>> IMP mailing list - Join the hunt: http://horde.org/bounties/#imp
>> Frequently Asked Questions: http://horde.org/faq/
>> To unsubscribe, mail: imp-unsubscribe at lists.horde.org
>>
>>
>>     
>
>
>
>
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
>
> The information contained in this transmission is confidential. It is intended solely for the use of the individual(s) or organization(s) 
> to whom it is addressed. Any disclosure, copying or further distribution is not permitted unless such privilege is explicitly granted in 
> writing by SARCOM, Inc. Furthermore, SARCOM, Inc. is not responsible for the proper and complete transmission of the substance 
> of this communication, nor for any delay in its receipt. 
>
>