From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: New DNS tld “might be bogus”.
Date: Mon, 08 Oct 2018 10:12:09 -0700 [thread overview]
Message-ID: <87y3b81hxy.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <8736tg5tal.fsf@portable.galex-713.eu>
"Garreau, Alexandre" <galex-713@galex-713.eu> writes:
> It seems Gnus is getting issues with new fancy ICANN tlds, like (from my
> *Messages*):
>
> ”Address ‘van@scratch.space’ might be bogus. Continue? (y or n) y”
>
> PS: please take care of putting me in copy as since some times I appear
> unable to re-subscribe to this ding mailing-list (or maybe I should use
> help-gnu-emacs instead as I’m subscribed and they got archives and such?
> it’s still unclear to me where is it more appropriated to ask)…
What's your value of `message-bogus-addresses'? My setup doesn't
complain about that message:
(message-bogus-recipient-p "van@scratch.space") => nil
Eric
next prev parent reply other threads:[~2018-10-08 17:12 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 [this message]
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
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=87y3b81hxy.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--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).