From: Lars Ingebrigtsen <larsi@gnus.org>
To: ding@gnus.org
Subject: Re: Address `questions@panoramio.com' might be bogus. Continue? (y or n)
Date: Sat, 22 Jan 2011 20:12:22 +0100 [thread overview]
Message-ID: <874o90sqg9.fsf@gnus.org> (raw)
In-Reply-To: <871v48r2yo.fsf@lifelogs.com>
Ted Zlatanov <tzz@lifelogs.com> writes:
> "Address `x' might be invalid (noreply, nospam, whitespace). Continue? (y/n/h) "
Well, I think the only really interesting case here is the invisible
characters. I'll amend the message to be what jidanni suggested.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
prev parent reply other threads:[~2011-01-22 19:12 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
2011-01-22 19:12 ` Lars Ingebrigtsen [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=874o90sqg9.fsf@gnus.org \
--to=larsi@gnus.org \
--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).