From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: bug in ietf-drums-parse-address
Date: Sun, 30 Dec 2001 22:23:56 +0100 [thread overview]
Message-ID: <m3ofkgjtar.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <2nitaok332.fsf@zsh.cs.rochester.edu>
ShengHuo ZHU <zsh@cs.rochester.edu> writes:
> I installed a patch when you posted the message, so that Gnus won't
> barf on the address, (not extract the address either). But I wonder
> whether mail-header-parse-addresses should only parse the encoded
> addresses instead of decoded addresses.
Yes, that's true -- it isn't meant to be able to handle decoded
addresses, really. Perhaps the picon code should switch to
`mail-extract-address-components' or the like.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
prev parent reply other threads:[~2001-12-30 21:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-30 17:33 Владимир Волович
2001-12-30 17:52 ` ShengHuo ZHU
2001-12-30 21:23 ` Lars Magne Ingebrigtsen [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=m3ofkgjtar.fsf@quimbies.gnus.org \
--to=larsi@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).