From: Lars Ingebrigtsen <larsi@gnus.org>
To: Julien Danjou <julien@danjou.info>
Cc: Albert Krewinkel <albert+gnus@zeitkraut.de>, ding@gnus.org
Subject: Re: [PATCH] Accept new TLDs when validating FQDNs
Date: Mon, 26 Jan 2015 15:16:13 +1100 [thread overview]
Message-ID: <877fwajhwy.fsf@building.gnus.org> (raw)
In-Reply-To: <m2oas6p6jv.fsf@danjou.info> (Julien Danjou's message of "Mon, 17 Nov 2014 09:36:36 +0100")
Julien Danjou <julien@danjou.info> writes:
> 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.
I wonder whether we could reuse the domains from the Emacs
etc/publicsuffix.txt file instead of adding all these domains once
again...
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog http://lars.ingebrigtsen.no/
prev parent reply other threads:[~2015-01-26 4:16 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
2015-01-26 4:16 ` 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=877fwajhwy.fsf@building.gnus.org \
--to=larsi@gnus.org \
--cc=albert+gnus@zeitkraut.de \
--cc=ding@gnus.org \
--cc=julien@danjou.info \
/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).