From: merlyn@stonehenge.com (Randal L. Schwartz)
Cc: Roman Belenov <roman@nstl.nnov.ru>, ding@gnus.org
Subject: Re: Email address handling
Date: 05 Feb 2000 05:46:44 -0800 [thread overview]
Message-ID: <m1aelfiwxn.fsf@halfdome.holdit.com> (raw)
In-Reply-To: Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "04 Feb 2000 18:43:43 +0100"
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=us-ascii, Size: 1330 bytes --]
>>>>> "Kai" == Kai Großjohann <Kai.Grossjohann@CS.Uni-Dortmund.DE> writes:
Kai> I think this is because it uses a regexp to find them, and the regexp
Kai> doesn't find normal mail addresses in the body. Doubtless it should
Kai> be easy to add this. Hm. Yes, there is the variable
Kai> gnus-button-alist which might help.
I think you mistyped "h a r d" as "easy" there. The regex to match an
RFC822 email address is about 7000 characters long, and would take far
too long to scan each incoming message. (I've got some friends
working on a similar Perl module, and are being likewise frustrated.)
For example: fred!barney@stonehenge.com is a legitimate email address.
And so is that with included whitespace, as fred! barney@stonehenge.com,
but how do you distinguish that from "hey, fred! barney@stonehenge.com"
where only the "barney..." part is the email?
Nope. The problem is a DWIM problem... there's not enough encoding
in the email message to correctly identify the sequence of characters
that *may* be an email address.
--
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn@stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
Perl/Unix/security consulting, Technical writing, Comedy, etc. etc.
See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!
next prev parent reply other threads:[~2000-02-05 13:46 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-04 15:59 Roman Belenov
2000-02-04 16:10 ` Colin Marquardt
2000-02-04 17:10 ` Kai Großjohann
2000-02-04 17:13 ` Roman Belenov
2000-02-04 17:43 ` Kai Großjohann
2000-02-04 17:48 ` Roman Belenov
2000-02-04 17:58 ` Jason Rumney
2000-02-04 18:18 ` Kai Großjohann
2000-02-05 13:46 ` Randal L. Schwartz [this message]
2000-02-07 14:59 ` Colin Rafferty
2000-02-07 15:14 ` Kai Großjohann
2000-02-07 15:26 ` Colin Rafferty
2000-02-07 17:56 ` Steinar Bang
2000-02-07 12:34 ` Toby Speight
2000-02-07 19:00 ` Per Abrahamsen
2000-04-20 23:43 ` Lars Magne Ingebrigtsen
2000-02-05 12:48 ` Mike Fabian
2000-02-06 15:55 ` Kai Großjohann
2000-02-08 6:55 ` Mike Fabian
2000-02-08 12:15 ` Kai Großjohann
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=m1aelfiwxn.fsf@halfdome.holdit.com \
--to=merlyn@stonehenge.com \
--cc=ding@gnus.org \
--cc=roman@nstl.nnov.ru \
/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).