From: Lars-Johan Liman <liman@netnod.se>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: ding@gnus.org
Subject: Re: Remove message-valid-fqdn-regexp?
Date: Sat, 06 Feb 2016 15:21:00 +0100 [thread overview]
Message-ID: <228u2x538z.fsf@hiptop.autonomica.net> (raw)
In-Reply-To: <877fiis9cm.fsf@gnus.org> (Lars Ingebrigtsen's message of "Sat, 06 Feb 2016 16:20:41 +1100")
larsi@gnus.org:
>> https://publicsuffix.org/list/public_suffix_list.dat
larsi@gnus.org:
> Hm... that doesn't really have all the domains, perhaps? Only those
> that have special cookie rules?
> Then I guess the best solution is to just remove
> message-valid-fqdn-regexp. Anybody have opinions here?
Thanks. That would be appreciated.
Cheers,
/Liman
next prev parent reply other threads:[~2016-02-06 14:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <22wptj39o0.fsf@netnod.se>
2016-02-06 5:09 ` Lars Ingebrigtsen
2016-02-06 5:20 ` Lars Ingebrigtsen
2016-02-06 14:21 ` Lars-Johan Liman [this message]
2016-02-07 3:20 ` Lars Ingebrigtsen
2016-02-08 14:14 ` Lars-Johan Liman
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=228u2x538z.fsf@hiptop.autonomica.net \
--to=liman@netnod.se \
--cc=ding@gnus.org \
--cc=larsi@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).