From: Ted Zlatanov <tzz@lifelogs.com>
To: jidanni@jidanni.org
Cc: ding@gnus.org
Subject: Re: don't let me send with "@@" in the address
Date: Fri, 16 May 2008 15:33:15 -0500 [thread overview]
Message-ID: <86wsluq99w.fsf@lifelogs.com> (raw)
In-Reply-To: <87bq378inu.fsf@jidanni.org> (jidanni@jidanni.org's message of "Fri, 16 May 2008 03:35:33 +0800")
On Fri, 16 May 2008 03:35:33 +0800 jidanni@jidanni.org wrote:
j> Say, maybe message-mode could have caught this before the mail system did:
MDS> 385775@@bugs.debian.org: domain missing or malformed
j> message-mode catches missing To:'s etc.
See `message-bogus-address-regexp' and `message-bogus-recipient-p' in
message.el.
message.el doesn't do full address validation according to the RFCs, and
maybe it should. It's a lot of work, though, and I don't think anyone
is interested in doing it.
Ted
prev parent reply other threads:[~2008-05-16 20:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1JwiwY-0001Yq-Gr@jidanni.org>
2008-05-15 19:35 ` jidanni
2008-05-16 20:33 ` Ted Zlatanov [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=86wsluq99w.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=ding@gnus.org \
--cc=jidanni@jidanni.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).