From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: `From: ' header oddities
Date: 05 Jul 1999 05:55:33 +0200 [thread overview]
Message-ID: <m3aetbbvii.fsf@quimbies.gnus.org> (raw)
In-Reply-To: Hrvoje Niksic's message of "04 Jul 1999 19:50:58 +0000"
Hrvoje Niksic <hniksic@srce.hr> writes:
> I've always thought that setting the `gnus-extract-address-components'
> variable to `mail-extract-address-components' should do the job, at
> the cost of making Summary generation much slower. But I've now tried
> it, and I don't get any improvement.
Well -- I think the latter function guesses right more of the time,
but even it doesn't get all the cases right.
`mail-header-parse-address' should get the correct answer 100% of the
time. Well, if the line is valid; if not, not.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
prev parent reply other threads:[~1999-07-05 3:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-04 14:18 Toni Drabik
1999-07-04 19:50 ` Hrvoje Niksic
1999-07-05 3:55 ` 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=m3aetbbvii.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).