Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.protocols.dns.bind > #15711
| From | Brett Delmage <Brett@BrettDelmage.ca> |
|---|---|
| Newsgroups | comp.protocols.dns.bind |
| Subject | Re: DoH plugin for BIND |
| Date | 2020-05-02 12:25 -0400 |
| Message-ID | <mailman.335.1588436727.942.bind-users@lists.isc.org> (permalink) |
| References | (5 earlier) <39825fcf-bcd7-f38a-aeae-2fccc8df0be8@nixmagic.com> <002174a6-4025-fad1-afea-0e96f40d2ff0@thelounge.net> <20200502093032.09f4b5cf@ime1.iment.local> <dbcfcbfc-c092-88fe-f6ba-7cedfa45127d@nixmagic.com> <alpine.DEB.2.21.2005021216380.10756@pannier.local> |
On Sat, 2 May 2020, Michael De Roover wrote: > Even if your ISP allows it, chances are that other mail servers will > reject it Nope, not always. My residential-class static IP mail server has never had problems delivering mail. I've checked it many times over the years on many blacklist checkers and never had anything but green lights. Of course I have met all the email best practices for years: SPF, DKIM, reverse pointer, etc. Even though email is not secure, I still feel better knowing that emails end up in MY server via opportunistic TLS transport. and not in some Yahoo's or surveillance capitalist's data store. Underlying all this are my own DNSSEC-enabled BIND servers, of course.
Back to comp.protocols.dns.bind | Previous | Next — Next in thread | Find similar
Re: DoH plugin for BIND Brett Delmage <Brett@BrettDelmage.ca> - 2020-05-02 12:25 -0400 Re: DoH plugin for BIND "John Levine" <johnl@iecc.com> - 2020-05-02 12:57 -0400
csiph-web