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
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 tha
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 confus
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 L
4 matches
Mail list logo
