From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: Address `questions@panoramio.com' might be bogus. Continue? (y or n)
Date: Wed, 19 Jan 2011 15:35:59 -0600 [thread overview]
Message-ID: <871v48r2yo.fsf@lifelogs.com> (raw)
In-Reply-To: <87vd1pdiu6.fsf@marauder.physik.uni-ulm.de>
On Sat, 15 Jan 2011 21:15:29 +0100 Reiner Steib <reinersteib+gmane@imap.cc> wrote:
RS> 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.
RS> The check includes several expressions that are potentially invalid or
RS> bogus addresses:
RS> ,----[ M-x customize-variable RET message-bogus-addresses RET ]
RS> | message-bogus-addresses: Hide Value Value Menu List:
RS> | Set:
RS> | [X] noreply
RS> | [X] nospam
RS> | [X] invalid
RS> | [X] duplicate @
RS> | [X] non-ascii local part
RS> | [X] whitespace
RS> | Other:
RS> | INS
RS> | State: STANDARD.
RS> |
RS> | List of regexps of potentially bogus mail addresses. Hide Rest
RS> | See `message-check-recipients' how to setup checking.
RS> |
RS> | This list should make it possible to catch typos or warn about
RS> | spam-trap addresses. It doesn't aim to verify strict RFC
RS> | conformance.
RS> `----
"Address `x' might be invalid (noreply, nospam, whitespace). Continue? (y/n/h) "
Where `h' can pop up a buffer with an explanation of each of those and a
link to Customize for `message-bogus-addresses'.
Ted
next prev parent reply other threads:[~2011-01-19 21:35 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
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 [this message]
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=871v48r2yo.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=ding@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).