From: tytso@mit.edu (Theodore Ts'o)
Subject: [TUHS] Excessive bouncing ... argh!
Date: Sat, 23 Sep 2017 10:12:32 -0400 [thread overview]
Message-ID: <20170923141232.aotf4m5eol6gr3v6@thunk.org> (raw)
In-Reply-To: <1bfefa2f-4433-0d13-5972-ffb92bae3fa1@tnetconsulting.net>
On Sat, Sep 23, 2017 at 03:05:47AM -0600, Grant Taylor wrote:
>
> I have leading industry standard email security enabled on my email. Things
> like DKIM and DMARC which are specifically designed to tell receiving email
> servers where email from my domain should come from and what to do with
> email that does not come from my servers.
DMARC is only useful if you are worried about people trying to use
your domain for phishing purposes. This is more of an issue for
Paypal.com and bankofamerica.com. In general it's not really an issue
for thunk.org and tnetconsulting.net.
DKIM and SPF are useful if you need to interoperate with big, free
e-mail systems such as Yahoo, AOL, and Google which are *using* DMARC.
Using DKIM and SPF are useful in trying avoid your site from falsely
being accused as being a spammer.
DMARC has no real value, and in fact has negative value, as it means
that when you send e-mail from a DMARC site that causes other people
to be ejected off of mailing lists, the mailing list administrator may
decide that you are actively causing harm to the community, and simply
prevent you from sending mail to the mailing list all.
Other proposed solutions is to have the mailing list software detect
that you are using DMARC, and only having *your* postings munged so
the from field says thus at minnie.tugs.org, instead of
gtaylor at tnetconsulting.net. That way only people who are using mail
systems with DMARC get their From field munged, instead of punishing
everyone using the mailing list.
- Ted
next prev parent reply other threads:[~2017-09-23 14:12 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-21 22:34 Warren Toomey
2017-09-22 11:46 ` Steffen Nurpmeso
2017-09-22 19:51 ` Grant Taylor
2017-09-23 14:07 ` Theodore Ts'o
2017-09-23 18:17 ` Lyndon Nerenberg
2017-09-23 18:35 ` Tom Ivar Helbekkmo
2017-09-22 20:09 ` Gregg Levine
2017-09-23 7:50 ` Tom Ivar Helbekkmo
2017-09-23 9:05 ` Grant Taylor
2017-09-23 14:12 ` Theodore Ts'o [this message]
2017-09-23 14:57 ` Tom Ivar Helbekkmo
2017-09-23 16:27 ` Ian Zimmerman
2017-09-23 15:41 ` Ian Zimmerman
2017-09-23 20:24 ` Grant Taylor
2017-09-24 0:03 ` Random832
2017-09-24 6:52 ` Tom Ivar Helbekkmo
2017-09-23 22:27 ` Dave Horsfall
2017-09-24 22:32 ` Derek Fawcus
2017-09-24 23:43 ` Dave Horsfall
2017-09-25 16:50 ` Ian Zimmerman
2017-09-26 4:19 ` Dave Horsfall
2017-09-26 5:30 ` Tom Ivar Helbekkmo
2017-09-26 14:32 ` Gregg Levine
2017-09-26 16:00 ` Ralph Corderoy
2017-09-23 15:54 Norman Wilson
2017-09-23 16:18 ` Tom Ivar Helbekkmo
2017-09-23 20:02 ` Grant Taylor
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=20170923141232.aotf4m5eol6gr3v6@thunk.org \
--to=tytso@mit.edu \
/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).