From: "Bjørn Mork" <bjorn@mork.no>
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: ding@gnus.org
Subject: Re: New DNS tld “might be bogus”.
Date: Tue, 09 Oct 2018 12:59:19 +0200 [thread overview]
Message-ID: <87d0sjfks8.fsf@miraculix.mork.no> (raw)
In-Reply-To: <87ftxg1bes.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Mon, 08 Oct 2018 12:33:15 -0700")
Eric Abrahamsen <eric@ericabrahamsen.net> writes:
> "Garreau, Alexandre" <galex-713@galex-713.eu> writes:
>
>> No need to go until source or even debugging, my documentation’s last
>> paragraph says “An address might be bogus if the domain part is not
>> fully qualified, see ‘message-valid-fqdn-regexp’, or if there’s a
>> matching entry in ‘message-bogus-addresses’”, and in fact
>> `message-valid-fqdn-regexp' (content afterwards [0]) doesn’t contain
>> “space” as a TLD in my version.
>>
>> So maybe the object of this discussion
>
> I can short-circuit this and tell you that, in the interim, someone's
> already had the discussion, and `message-valid-fqdn-regexp' doesn't even
> exist anymore in Emacs 27. I think the conclusion was that times have
> changed and it's harder to predict what the internet will do, and we
> shouldn't be pedantically restrictive when it's not even clear what's
> "right" anymore. So there's that!
>
> Emacs 27 isn't released yet, but I'd recommend switching to 26 if
> possible. It looks like this option was removed in Feb 2016, so Emacs 26
> probably has that change.
Or simply set it to something like
(setq message-valid-fqdn-regexp "[a-z0-9][-.a-z0-9]+\\.[a-z0-9][-.a-z0-9]+")
until you can upgrade emacs. Works For Me (tm).
Bjørn
prev parent reply other threads:[~2018-10-09 10:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-08 15:53 Garreau, Alexandre
2018-10-08 17:12 ` Eric Abrahamsen
2018-10-08 17:26 ` Garreau, Alexandre
2018-10-08 18:21 ` Eric Abrahamsen
2018-10-08 18:56 ` Garreau, Alexandre
2018-10-08 19:33 ` Eric Abrahamsen
2018-10-08 19:43 ` Adam Sjøgren
2018-10-09 10:59 ` Bjørn Mork [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=87d0sjfks8.fsf@miraculix.mork.no \
--to=bjorn@mork.no \
--cc=ding@gnus.org \
--cc=eric@ericabrahamsen.net \
/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).