From: Ted Zlatanov <tzz@lifelogs.com>
Cc: <bbdb-info@lists.sourceforge.net>, Ding Mailing List <ding@gnus.org>
Subject: Re: problems with splitting and imap
Date: Mon, 20 Jul 2009 13:59:24 -0500 [thread overview]
Message-ID: <87ocrfi3jn.fsf@lifelogs.com> (raw)
In-Reply-To: <871vobjn07.fsf@lifelogs.com> (Ted Zlatanov's message of "Mon, 20 Jul 2009 12:13:44 -0500")
The following message is a courtesy copy of an article
that has been posted to gnu.emacs.gnus as well.
On Mon, 20 Jul 2009 12:13:44 -0500 Ted Zlatanov <tzz@lifelogs.com> wrote:
TZ> On Sun, 19 Jul 2009 15:31:09 +0200 Richard Riley <rileyrgdev@gmail.com> wrote:
RR> A couple of days ago I had to remove all my splitting code because of
RR> this error:
RR> ,----
RR> | Debugger entered--Lisp error: (wrong-type-argument listp "(Unparsable address -- Strange character \\> found: \">_^_\")")
RR> | bbdb/gnus-split-method()
RR> | nnimap-split-to-groups(bbdb/gnus-split-method)
RR> | nnimap-split-articles(nil "mymail")
RR> | nnimap-request-scan(nil "mymail")
RR> | gnus-request-scan(nil (nnimap "mymail" (nnimap-stream ssl) (nnimap-address "imap.richardriley.net") (nnimap-authinfo-file "~/.authinfo") (nnir-search-engine imap)))
RR> | gnus-read-active-file-1((nnimap "mymail" (nnimap-stream ssl) (nnimap-address "imap.richardriley.net") (nnimap-authinfo-file "~/.authinfo") (nnir-search-engine imap)) nil)
RR> | gnus-read-active-file()
RR> | gnus-group-get-new-news(nil)
RR> | gnus-1(nil nil nil)
RR> | gnus(nil)
RR> | call-interactively(gnus nil nil)
RR> `----
RR> Could someone please suggest how to fix this/locate the offending message?
RR> I'm talking to a dovecot IMAP server btw.
TZ> Looks like a bug in bbdb/gnus-split-method. It should return nil if
TZ> this error happens (or maybe do something smarter, I don't know the code
TZ> too well so I didn't write a patch). The error is coming from
TZ> `rfc822-addresses' which is part of Emacs.
TZ> I am cc-ing the BBDB group for help.
Sorry, the first CC didn't work. Retrying. This may get hairy because
gnu.emacs.gnus is a newsgroup. I also cc-ed the Ding mailing list for
Gnus, so replies from BBDB developers make it back to Gnus developers.
Ted
next parent reply other threads:[~2009-07-20 18:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <h3v7is$if4$1@rileyrgdev.eternal-september.org>
[not found] ` <871vobjn07.fsf@lifelogs.com>
2009-07-20 18:59 ` Ted Zlatanov [this message]
[not found] ` <h42q22$ded$1@rileyrgdev.eternal-september.org>
2009-07-21 16:00 ` Ted Zlatanov
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=87ocrfi3jn.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=bbdb-info@lists.sourceforge.net \
--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).