Re: [fetchmail-users] how to have kept messages on MS Exchange Server as unread

[Matthias A. <mat...@gm...>]

Am 19.08.2010, 19:15 Uhr, schrieb Globe Trotter:


> Next I tried changing the protocol to POP3 so that I could perhaps use  
> uidl and had the following authentication error:
>
> $ fetchmail -cv
> Enter password for tr...@ex...:
> fetchmail: --check mode enabled, not fetching mail
> fetchmail: 6.3.17 querying exchange.uia.edu (protocol POP3) at Thu 19  
> Aug 2010 12:13:10 PM CDT: poll started
> Trying to connect to xxx.xxx.xx.xxx/995...connected.
> fetchmail: Server certificate:
> fetchmail: Issuer Organization: Thawte Consulting cc
> fetchmail: Issuer CommonName: Thawte Premium Server CA
> fetchmail: Subject CommonName: exchange.uia.edu
> fetchmail: exchange.uia.edu key fingerprint:  
> BF:74:A5:F0:B0:7B:BA:FA:6A:DA:FC:C7:32:02:E5:04
> fetchmail: POP3< +OK The Microsoft Exchange POP3 service is ready.
> fetchmail: POP3> CAPA
> fetchmail: POP3< +OK
> fetchmail: POP3< TOP
> fetchmail: POP3< UIDL
> fetchmail: POP3< SASL NTLM GSSAPI PLAIN
> fetchmail: POP3< USER
> fetchmail: POP3< .
> fetchmail: POP3> AUTH GSSAPI
> fetchmail: POP3< +
> fetchmail: Sending credentials
> fetchmail: Error exchanging credentials
> fetchmail: POP3< +  
> YGoGBisGAQUFAqBgMF6gMDAuBgkqhkiC9xIBAgIGCSqGSIb3EgECAgYKKoZIhvcSAQICAwYKKwYBBAGCNwICCqMqMCigJhskbm90X2RlZmluZWRfaW5fUkZDNDE3OEBwbGVhc2VfaWdub3Jl
> fetchmail: POP3> USER trotter
> fetchmail: POP3< -ERR Logon failure: unknown user name or bad password.
> fetchmail: Logon failure: unknown user name or bad password.
> fetchmail: Authorization failure on tr...@ex...
> fetchmail: POP3> QUIT
> fetchmail: POP3< +OK Microsoft Exchange Server 2007 POP3 server signing  
> off.
> fetchmail: 6.3.17 querying exchange.uia.edu (protocol POP3) at Thu 19  
> Aug 2010 12:13:10 PM CDT: poll completed
> fetchmail: normal termination, status 3
>
> Any suggestions?

*Please* try arranging for a test account for me (details please off-list)  
so that I can debug and test against Exchange 2007. This has been reported  
several times, but users always used the brutest and mindless approach of  
recompiling fetchmail without GSSAPI support.

For the nonce, try either of this:

(1) kinit trotter (this needs krb5.conf configured), then re-run fetchmail

If that does not help, try:

(2) fetchmail -cv --auth password

And report what you get.

-- 
Matthias Andree