From: Manuel Werlberger <noSpam@TUGraz.at>
Subject: Re: Assert in imap-parse-body, dovecot and rfc822 multipart messages
Date: 11 Sep 2006 18:41:58 +0200 [thread overview]
Message-ID: <87odtmjqy1.fsf@athena.werlberger.org> (raw)
In-Reply-To: <87irjvqv80.fsf@thosu.err.no>
Tollef Fog Heen <tfheen@err.no> writes:
> I'm running No Gnus v0.6 accessing my mails over IMAP to a dovecot
> server. I keep hitting the (assert (eq (char-after) ?\)) nil "In
> imap-parse-body 2"). After enabling the IMAP log I found a line which
> imap-parse-body seems to fail on:
I also tried to access my imap repository with gnus but no success. I'm
also running dovecot. If there's really a problem with dovecot a fix
would be perfekt. I really want to "kill" all those external tools...
rgds,
manuel
next prev parent reply other threads:[~2006-09-11 16:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-10 21:15 Tollef Fog Heen
2006-09-11 16:41 ` Manuel Werlberger [this message]
2006-09-11 18:58 ` Assert in imap-parse-body, dovecot and rfc822 multipart Jouni K Seppanen
2006-09-12 13:32 ` Assert in imap-parse-body, dovecot and rfc822 multipart messages Simon Josefsson
2006-09-17 17:59 ` Tollef Fog Heen
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=87odtmjqy1.fsf@athena.werlberger.org \
--to=nospam@tugraz.at \
--cc=web@werlberger.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).