From: Florian Weimer <fw@deneb.enyo.de>
Subject: Re: [patch] gnus-art.el handling for t-online addresses
Date: Sun, 04 May 2003 18:37:49 +0200 [thread overview]
Message-ID: <874r4abrc2.fsf@deneb.enyo.de> (raw)
In-Reply-To: <v9issqj47k.fsf@marauder.physik.uni-ulm.de> (Reiner Steib's message of "Sun, 04 May 2003 14:17:51 +0200")
Reiner Steib <4.uce.03.r.s@nurfuerspam.de> writes:
> As it's name says, `gnus-button-mid-or-mail-heuristic' is a heuristic
> function. It's not intended to cover every special case. BTW: In
> your example the function returns 'ask, which isn't really wrong. :-)
In fact, I did this on purpose. Quite a few news clients allocate
Message-IDs in the t-online.de domain, and I couldn't tell these
Message-IDs from T-Online email addresses.
> But maybe, we don't have to be that careful and use
> "^[A-Za-z]+[A-Za-z._-][A-Za-z._-][A-Za-z._-][A-Za-z._-]+@t-online\\.de$"
> instead?
I think this regexp is too broad, it will catch a few Message-IDs
too. 8-(
prev parent reply other threads:[~2003-05-04 16:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-04 9:36 Jhair Tocancipa Triana
2003-05-04 12:17 ` Reiner Steib
2003-05-04 12:50 ` Jhair Tocancipa Triana
2003-05-04 16:37 ` Florian Weimer [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=874r4abrc2.fsf@deneb.enyo.de \
--to=fw@deneb.enyo.de \
/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).