From: Tassilo Horn <tassilo@member.fsf.org>
To: James Cloos <cloos@jhcloos.com>
Cc: ding@gnus.org
Subject: Re: imap-parse-fetch: End of file during parsing
Date: Wed, 26 Mar 2008 23:35:13 +0100 [thread overview]
Message-ID: <87ej9xdsgu.fsf@member.fsf.org> (raw)
In-Reply-To: <m3wsnpo2it.fsf@lugabout.jhcloos.org> (James Cloos's message of "Wed, 26 Mar 2008 12:47:31 -0400")
James Cloos <cloos@jhcloos.com> writes:
> I see that some of the Received headers have continuation lines which
> start with a space rather than a tab.
>
> I wonder whether that is confusing dovecot?
Normally I use an local dovecot imap server which is synched with my
providers imap server via offlineimap. Now I've tried to access the
provider's imap directly with Gnus and got the same error. The provider
runs courier imap. So it seems it's not dovecot's fault.
Bye,
Tassilo
prev parent reply other threads:[~2008-03-26 22:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-26 9:17 Tassilo Horn
[not found] ` <m3wsnpo2it.fsf@lugabout.jhcloos.org>
2008-03-26 18:05 ` Tassilo Horn
2008-03-26 19:27 ` James Cloos
2008-03-27 9:04 ` Tassilo Horn
2008-03-27 9:37 ` Katsumi Yamaoka
2008-03-27 22:16 ` Tassilo Horn
2008-03-27 23:47 ` Katsumi Yamaoka
2008-03-26 22:35 ` Tassilo Horn [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ej9xdsgu.fsf@member.fsf.org \
--to=tassilo@member.fsf.org \
--cc=cloos@jhcloos.com \
--cc=ding@gnus.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).