|
From: Rob M. <rob...@gm...> - 2013-01-06 22:55:48
|
On Sun, Jan 6, 2013 at 9:39 PM, Peter van Nes <ma...@pe...> wrote: > > Hi, > > > After the upgrade up Mac OS X 10.7 to 10.8 fetchmail disappeared. After installing fetchmail 6.3.24 i try to use fetchmail using the same .fetctmailrc file as before, but now get authorization errors. > Specifically, it fails on the following poll from an account on an exchange 2010 server; > > defaults keep smtphost 127.0.0.1 > set syslog > set daemon 60 > set no bouncemail > set no spambounce > > 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" * > fetchmail: IMAP< A0002 BAD Command received in Invalid state. A Google search suggests the problem is that you either need to use SSL or TLS - the Exchange administrator should be able to confirm that. I suspect your previous configuration had that enabled by default (possibly on the command line). -- Please keep list traffic on the list. Rob MacGregor Whoever fights monsters should see to it that in the process he doesn't become a monster. Friedrich Nietzsche |