Re: fetchmail 4.3.6 vs. m$ exchange
Joost Kooij [EMAIL PROTECTED]:
Looking at the changelog, I suspect that:
* IMAP code can now deal with untagged responses during CAPABILITY
(at least one server issues the motd in a bunch of * OK {ALERT] lines
in response to the first command after connecting.)
is related to the changed behaviour.
This seems plausible. Could somebody please send me the entire
fetchmail -v log of a failed session?
I bet the Exchange server is doing something weird that's messing up
fetchmail. It wouldn't be the first time, as at least Arjan knows well...
--
a href=http://www.ccil.org/~esr;Eric S. Raymond/a
No kingdom can be secured otherwise than by arming the people. The possession
of arms is the distinction between a freeman and a slave.
-- Political Disquisitions, a British republican tract of 1774-1775
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
[EMAIL PROTECTED] .
Trouble? e-mail to [EMAIL PROTECTED] .
Re: fetchmail 4.3.6 vs. m$ exchange
On Tue, Feb 03, 1998 at 01:59:16PM -0600, D. W. Wieboldt wrote: I am trying to run fetchmail in imap mode with a m$ exchange server. Does anybody know if this a bug, or am I doing something wrong, like failing to bow toward Redmond? I'm not sure about your problem, but I can tell you that fetchmail was segfaulting on me until I built it without -O flags. Has anyone else had this problem? Scott -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: fetchmail 4.3.6 vs. m$ exchange
Hi,
The behaviour that you quote below is the same as what I got since
upgrading to fetchmail 4.3.6.
The quick solution, suggested by Arjan de Vet, is to add proto pop3 to
your .fetchmailrc (or as command line switches.) Apparently, probing
for IMAP capabilities in ms-exchange makes it confuse fetchmail. Perhaps
this gotcha could be added to the ms-exchange section of the fetchmail
FAQ.
Looking at the changelog, I suspect that:
* IMAP code can now deal with untagged responses during CAPABILITY
(at least one server issues the motd in a bunch of * OK {ALERT] lines
in response to the first command after connecting.)
is related to the changed behaviour.
Cheers,
Joost
On Tue, 3 Feb 1998, D. W. Wieboldt wrote:
I am trying to run fetchmail in imap mode with a m$ exchange server.
With fetchmail 4.3.6-1, I get:
fetchmail: IMAP a0006 OK FETCH completed.
fetchmail: IMAP a0007 FETCH 1 RFC822.TEXT.PEEK
fetchmail: IMAP a0007 BAD Protocol Error: Invalid FETCH_ITEM in FETCH
command
fetchmail: IMAP a0008 LOGOUT
fetchmail: IMAP * BYE Microsoft Exchange IMAP4rev1 server version
5.5.1960.6 signing off
fetchmail: IMAP a0008 OK LOGOUT completed.
fetchmail: client/server synchronization error while fetching from nt_xchg
fetchmail: SMTP QUIT
At this point, fetchmail 4.3.6 hangs and has to be killed; it does not
retrieve the mail.
Downgrading back to fetchmail 4.3.5-1, it works just fine:
fetchmail: IMAP a0006 OK FETCH completed.
fetchmail: IMAP a0007 FETCH 1 BODY.PEEK[TEXT]
fetchmail: IMAP * 1 FETCH (BODY[TEXT] {321}
(321 body bytes)
fetchmail: IMAP )
fetchmail: IMAP a0007 OK FETCH completed.
fetchmail: message 1 was not the expected length (1112 != 560)
fetchmail: SMTP. (EOM)
fetchmail: SMTP 250 Mail accepted
flushed
fetchmail: IMAP a0008 STORE 1 +FLAGS (\Deleted)
fetchmail: IMAP * 1 FETCH (FLAGS (\Deleted))
fetchmail: IMAP a0008 OK STORE completed.
fetchmail: IMAP a0009 EXPUNGE
fetchmail: IMAP * 1 EXPUNGE
fetchmail: IMAP * 0 EXISTS
fetchmail: IMAP a0009 OK EXPUNGE completed.
fetchmail: selecting or re-polling default folder
fetchmail: IMAP a0010 NOOP
fetchmail: IMAP a0010 OK NOOP completed.
fetchmail: IMAP a0011 LOGOUT
fetchmail: IMAP * BYE Microsoft Exchange IMAP4rev1 server version
5.5.1960.6 signing off
fetchmail: IMAP a0011 OK LOGOUT completed.
fetchmail: SMTP QUIT
fetchmail: SMTP 221 shiloh closing connection
fetchmail: normal termination, status 0
Does anybody know if this a bug, or am I doing something wrong, like
failing to bow toward Redmond?
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
[EMAIL PROTECTED] .
Trouble? e-mail to [EMAIL PROTECTED] .
fetchmail 4.3.6 vs. m$ exchange
I am trying to run fetchmail in imap mode with a m$ exchange server.
With fetchmail 4.3.6-1, I get:
fetchmail: IMAP a0006 OK FETCH completed.
fetchmail: IMAP a0007 FETCH 1 RFC822.TEXT.PEEK
fetchmail: IMAP a0007 BAD Protocol Error: Invalid FETCH_ITEM in FETCH
command
fetchmail: IMAP a0008 LOGOUT
fetchmail: IMAP * BYE Microsoft Exchange IMAP4rev1 server version
5.5.1960.6 signing off
fetchmail: IMAP a0008 OK LOGOUT completed.
fetchmail: client/server synchronization error while fetching from nt_xchg
fetchmail: SMTP QUIT
At this point, fetchmail 4.3.6 hangs and has to be killed; it does not
retrieve the mail.
Downgrading back to fetchmail 4.3.5-1, it works just fine:
fetchmail: IMAP a0006 OK FETCH completed.
fetchmail: IMAP a0007 FETCH 1 BODY.PEEK[TEXT]
fetchmail: IMAP * 1 FETCH (BODY[TEXT] {321}
(321 body bytes)
fetchmail: IMAP )
fetchmail: IMAP a0007 OK FETCH completed.
fetchmail: message 1 was not the expected length (1112 != 560)
fetchmail: SMTP. (EOM)
fetchmail: SMTP 250 Mail accepted
flushed
fetchmail: IMAP a0008 STORE 1 +FLAGS (\Deleted)
fetchmail: IMAP * 1 FETCH (FLAGS (\Deleted))
fetchmail: IMAP a0008 OK STORE completed.
fetchmail: IMAP a0009 EXPUNGE
fetchmail: IMAP * 1 EXPUNGE
fetchmail: IMAP * 0 EXISTS
fetchmail: IMAP a0009 OK EXPUNGE completed.
fetchmail: selecting or re-polling default folder
fetchmail: IMAP a0010 NOOP
fetchmail: IMAP a0010 OK NOOP completed.
fetchmail: IMAP a0011 LOGOUT
fetchmail: IMAP * BYE Microsoft Exchange IMAP4rev1 server version
5.5.1960.6 signing off
fetchmail: IMAP a0011 OK LOGOUT completed.
fetchmail: SMTP QUIT
fetchmail: SMTP 221 shiloh closing connection
fetchmail: normal termination, status 0
Does anybody know if this a bug, or am I doing something wrong, like
failing to bow toward Redmond?
Thanks!
--
[EMAIL PROTECTED] . . . . . . . My other computer runs Linux!
The sooner all the animals are extinct, the sooner we'll find their money.
- Ed Bluestone
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
[EMAIL PROTECTED] .
Trouble? e-mail to [EMAIL PROTECTED] .
