From: Reiner Steib <reinersteib+gmane@imap.cc>
To: Tommy Kelly <tommy.kelly@verilab.com>
Cc: jidanni@jidanni.org, ding@gnus.org
Subject: Re: Address `questions@panoramio.com' might be bogus. Continue? (y or n)
Date: Sat, 15 Jan 2011 21:15:29 +0100 [thread overview]
Message-ID: <87vd1pdiu6.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <m2zkr3w4cr.fsf@verilab.com> (Tommy Kelly's message of "Fri, 14 Jan 2011 15:41:08 -0600")
On Fri, Jan 14 2011, Tommy Kelly wrote:
> jidanni@jidanni.org writes:
>
>> Address `questions@panoramio.com' might be bogus. Continue? (y or n) y
>>
>> Better have the message say why: Silly user name? Invisible character in
>> the address? Etc.
The check includes several expressions that are potentially invalid or
bogus addresses:
,----[ M-x customize-variable RET message-bogus-addresses RET ]
| message-bogus-addresses: Hide Value Value Menu List:
| Set:
| [X] noreply
| [X] nospam
| [X] invalid
| [X] duplicate @
| [X] non-ascii local part
| [X] whitespace
| Other:
| INS
| State: STANDARD.
|
| List of regexps of potentially bogus mail addresses. Hide Rest
| See `message-check-recipients' how to setup checking.
|
| This list should make it possible to catch typos or warn about
| spam-trap addresses. It doesn't aim to verify strict RFC
| conformance.
`----
> I agree. I just (for the first time) saw the same message and had no
> idea what it was telling me.
Feel free to suggest a better wording.
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
next prev parent reply other threads:[~2011-01-15 20:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-13 1:48 jidanni
2011-01-13 2:18 ` jidanni
2011-01-14 21:41 ` Tommy Kelly
2011-01-15 20:15 ` Reiner Steib [this message]
2011-01-15 20:25 ` Tommy Kelly
2011-01-15 22:40 ` Rupert Swarbrick
2011-01-16 5:04 ` jidanni
2011-01-19 21:35 ` Ted Zlatanov
2011-01-22 19:12 ` Lars Ingebrigtsen
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=87vd1pdiu6.fsf@marauder.physik.uni-ulm.de \
--to=reinersteib+gmane@imap.cc \
--cc=Reiner.Steib@gmx.de \
--cc=ding@gnus.org \
--cc=jidanni@jidanni.org \
--cc=tommy.kelly@verilab.com \
/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).