Re: [fetchmail-users] Fetchmail fails with BAD Command received in invalid state after upgrade to 6.3.24

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

Am 06.01.2013 22:39, schrieb Peter van Nes:

> poll mail.the-future-group.com proto imap port 143:
>         auth password user 'username' with password 'password' sslproto TLS1 smtpname my...@pe...
> 
> When running fetchmail in debug ;
> fetchmail superuser$ /usr/local/bin/fetchmail -vvvv --nodetach -f /private/var/fetchmail/.fetchmailrc --nosyslog
> 
> i get the following output ;
> 
> Old UID list from mail.the-future-group.com: <empty>
> Scratch list of UIDs: <empty>
> fetchmail: starting fetchmail 6.3.24 daemon
> fetchmail: 6.3.24 querying mail.the-future-group.com (protocol IMAP) at Sun, 06 Jan 2013 22:14:55 +0100 (CET): poll started
> Trying to connect to 46.244.15.13/143...connected.
> fetchmail: IMAP< * OK The Microsoft Exchange IMAP4 service is ready.
> fetchmail: IMAP> A0001 CAPABILITY
> fetchmail: IMAP< * CAPABILITY IMAP4 IMAP4rev1 LOGINDISABLED STARTTLS UIDPLUS CHILDREN IDLE NAMESPACE LITERAL+
> fetchmail: IMAP< A0001 OK CAPABILITY completed.
> fetchmail: Protocol identified as IMAP4 rev 1
> fetchmail: IMAP> A0002 LOGIN "p.vannes" *

Peter,

it seems you have found a bug, and also may have misconfigured fetchmail
when compiling it.

Exchange has advertised LOGINDISABLED, so fetchmail must not be trying
LOGIN.

Exchange has also advertised STARTTLS, but fetchmail is not using it -
have you run ./configure with the --with-ssl option? I suppose not;
fetchmail -V|head -n1 will show it, there should be +SSL somewhere.

If fetchmail were to use and succeed with STARTTLS, Exchange would
likely offer LOGIN through the secure channel so you would no longer get
BAD.

Hope that helps.

Best regards,
Matthias