The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: lyndon@orthanc.ca (Lyndon Nerenberg)
Subject: [TUHS] Excessive bouncing ... argh!
Date: Sat, 23 Sep 2017 11:17:42 -0700	[thread overview]
Message-ID: <C00A2CED-0626-41DB-B259-C84CA6DE6BB4@orthanc.ca> (raw)
In-Reply-To: <20170923140725.sqxxg7bb7cxkkwmi@thunk.org>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1280 bytes --]


> On Sep 23, 2017, at 7:07 AM, Theodore Ts'o <tytso at mit.edu> wrote:
> 
> This is actually the whole *point* of DMARC.  They want to make sure
> that if you see a from field of paypal.com, it means "paypal.com", and
> did not come from SCAMMER at MAKE.MONEY.FAST.NG.  So this is why DMARC
> apologists who argue that this could be fixed by having MUA's hacked
> so they display the X-List-From: field in the threaded mail summary
> are wrong.  If you do this, then Nigerian spammers will be able to use
> X-List-From: field to fool stupid e-mail users, and then Yahoo and
> Paypal will end up pushing DMARCv2 (outside the IETF standards
> structures, just as DMARC is pushed outside of the standards bodies,
> but by big companies imposing their will on the rest of the Internet)
> to censor the X-List-From: field just as DMARC is trying to force
> mailing list reflectors to munge the From field.

Amen.

I hope this whole topic doesn't go off the rails – we've had enough of those on the list the past couple of weeks.

But I will note that, if the sites that enforce the fully-anal interpretation of DMARC start destroying the list, it's completely within the spirit of TUHS to migrate to a UUCP-only distribution.  (Note the deliberate absence of a smiley.)

--lyndon



  reply	other threads:[~2017-09-23 18:17 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 [this message]
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
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=C00A2CED-0626-41DB-B259-C84CA6DE6BB4@orthanc.ca \
    --to=lyndon@orthanc.ca \
    /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).