From: Sam Steingold <sds@gnu.org>
Subject: Re: follow-up & CC
Date: Tue, 18 Nov 2003 13:50:30 -0500 [thread overview]
Message-ID: <ur805jytl.fsf@gnu.org> (raw)
In-Reply-To: <v9ad6t8xwp.fsf@marauder.physik.uni-ulm.de>
> * Reiner Steib <4.hpr.03.e.f@aheshrefcnz.qr> [2003-11-18 17:05:42 +0100]:
>
>> + when (and old-header (string-match new-header old-header))
>
> Hm, another problem here. Say, I have "To: bar@foo.invalid.my.domain"
> in the current message. Then, the following examples wont work as
> expected:
>
> - (message-carefully-insert-headers '((To . "bar@foo.invalid")))
>
> - (message-carefully-insert-headers '((To . "ar@foo.invalid.my.domain")))
>
> - (setq case-fold-search nil)
> (message-carefully-insert-headers '((To . "bar@FOO.INVALID.my.domain")))
>
> Maybe it would be better to use something like (gnus-string-equal (nth
> 1 (mail-extract-address-components ...))).
it depends on what you want.
I wouldn't want to see _both_ "bar@foo.invalid" and
"bar@foo.invalid.my.domain", I would prefer to either pick the shortest
or the "correct" one or...
--
Sam Steingold (http://www.podval.org/~sds) running w2k
<http://www.camera.org> <http://www.iris.org.il> <http://www.memri.org/>
<http://www.mideasttruth.com/> <http://www.honestreporting.com>
Just because you're paranoid doesn't mean they AREN'T after you.
next prev parent reply other threads:[~2003-11-18 18:50 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-10 1:18 Sam Steingold
2003-11-10 12:30 ` Reiner Steib
2003-11-10 14:47 ` Sam Steingold
2003-11-10 17:44 ` Reiner Steib
2003-11-10 18:04 ` Sam Steingold
2003-11-10 18:54 ` Reiner Steib
2003-11-10 19:12 ` Sam Steingold
2003-11-10 19:26 ` Sam Steingold
2003-11-10 20:26 ` Reiner Steib
2003-11-12 16:05 ` Sam Steingold
2003-11-12 16:54 ` Reiner Steib
2003-11-12 18:36 ` Sam Steingold
2003-11-12 20:00 ` Reiner Steib
2003-11-12 21:13 ` Sam Steingold
2003-11-18 16:05 ` Reiner Steib
2003-11-18 18:50 ` Sam Steingold [this message]
2003-11-18 19:57 ` Reiner Steib
2003-11-18 20:47 ` Sam Steingold
2004-01-03 14:07 ` Reiner Steib
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=ur805jytl.fsf@gnu.org \
--to=sds@gnu.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).