From: Julien Danjou <julien@danjou.info>
To: Albert Krewinkel <albert+gnus@zeitkraut.de>
Cc: ding@gnus.org
Subject: Re: [PATCH] Accept new TLDs when validating FQDNs
Date: Mon, 17 Nov 2014 09:36:36 +0100 [thread overview]
Message-ID: <m2oas6p6jv.fsf@danjou.info> (raw)
In-Reply-To: <1416048795-30803-1-git-send-email-albert+gnus@zeitkraut.de> (Albert Krewinkel's message of "Sat, 15 Nov 2014 11:53:15 +0100")
[-- Attachment #1: Type: text/plain, Size: 425 bytes --]
On Sat, Nov 15 2014, Albert Krewinkel wrote:
> The fully qualified domain name validation regex in message didn't
> accept new top-level domain names, causing additional confirmation
> steps or failures when sending mail. This adds the
> non-internationalized new TLDs listed here:
> https://en.wikipedia.org/wiki/GTLD
Good idea, pushed.
--
Julien Danjou
# Free Software hacker
# http://julien.danjou.info
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]
next prev parent reply other threads:[~2014-11-17 8:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-15 10:53 Albert Krewinkel
2014-11-17 8:36 ` Julien Danjou [this message]
2015-01-26 4:16 ` 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=m2oas6p6jv.fsf@danjou.info \
--to=julien@danjou.info \
--cc=albert+gnus@zeitkraut.de \
--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).