[ih] Email reliability

[Jack Haverty]

True.   But ISOC doesn't seem to follow this requirement (from the 
Amazon blog announcement):

"Bulk senders are expected to include a mechanism to unsubscribe by 
adding an easy to find link within the message. The February 2024 
mailbox provider rules will require senders to additionally add 
one-click unsubscribe headers as defined by RFC 2369 
<https://datatracker.ietf.org/doc/html/rfc2369> and RFC 8058 
<https://datatracker.ietf.org/doc/html/rfc8058>."

At least I don't see any "unsubscribe" header...perhaps that rule won't 
be enforced at first.  We'll see...

Jack


On 1/14/24 10:43, Andrew G. Malis wrote:
> Jack,
>
> Note that this list (Internet History) already properly rewrites the 
> headers to be conformant with the anti-spam rules. I believe that's 
> true for all ISOC-based lists.
>
> Cheers,
> Andy
>
>
> On Sun, Jan 14, 2024 at 1:33 PM Jack Haverty via Internet-history 
> <internet-history at elists.isoc.org> wrote:
>
>     It will likely reduce spam, but also disrupt real email - in
>     particular
>     any email that travels using any mailing list (like this one).   The
>     effect comes not from the new rules for "bulk senders", but rather
>     from
>     the mail servers changes to their filters for handling incoming mail,
>     especially the rules that classify mail travelling through mailing
>     lists
>     as inherently suspicious.
>
>      From Amazon's blog announcement:
>
>     "For example, /gmail.com/ <http://gmail.com/> will be publishing a
>     quarantine DMARC policy,
>     which means that unauthorized messages claiming to be from Gmail
>     will be
>     sent to Junk folders."  It's likely that yahoo and others are taking
>     similar steps, effective sometime in the next month or so.
>     Depending on
>     exactly how they set it up, the effect might be that all email
>     from any
>     mailing list will be automatically classed as spam, or even just
>     silently deleted.
>
>     I suspect lots of "mailing lists" will sustain such "collateral
>     damage".   Anyone who sends or receives their email using a gmail or
>     yahoo address will likely discover that they are effectively cut off
>     from using this list (and probably others).
>
>     I'm on several mailing lists (isoc, groups.io <http://groups.io>,
>     googlegroups, ...) and
>     haven't seen announcements from any of them about imminent
>     changes.  Nor
>     have the "email providers" (yahoo, gmail, etc.) said anything about
>     their plans' effects on mailing lists or groups. Perhaps they're just
>     not aware of what's happening?...
>
>     Jack Haverty
>
>
>
>     On 1/14/24 02:56, Olivier MJ Crépin-Leblond via Internet-history
>     wrote:
>     >
>     >
>     > On 11/01/2024 20:10, Dave Crocker via Internet-history wrote:
>     >> Large email service providers have been on a long march towards
>     >> increasingly restrictive rules, for the mail they will accept. The
>     >> onslaught of email abuse obviously creates a clear and present
>     >> danger.  The challenge in formulating acceptance changes is the
>     >> potential for collateral damage to legitimate users.
>     >
>     > This week, AWS customers received an email detailing changes with
>     > Google + Yahoo and others.
>     > See forwarded in full. As an evolution of email, is this likely to
>     > make it more reliable again or will it lead to further
>     deterioration
>     > of the service?
>     > Best,
>     >
>     > Olivier
>     >
>     > -------- Forwarded Message --------
>     > Subject:     [Action may be required] Mailbox providers announce
>     new
>     > requirements for bulk email senders [AWS Account: xxx ]
>     > Date:     Sun, 14 Jan 2024 10:26:30 +0000
>     > From:     Amazon Web Services, Inc. <no-reply-aws at amazon.com>
>     > To:
>     >
>     >
>     >
>     > Hello,
>     >
>     > In a move to safeguard user inboxes, Gmail [1] and Yahoo Mail [2]
>     > announced a new set of requirements for senders. Effective February
>     > 2024, the new requirements affect email senders who distribute over
>     > 5,000 bulk messages per day or have >0.3% of messages reported as
>     > spam. Failure to comply with the new requirements may result in
>     Gmail
>     > and Yahoo rejecting message delivery to their customers.
>     >
>     > For more information on the new mailbox provider requirements
>     and how
>     > to comply, please visit the AWS blog [3]. If you have any
>     questions or
>     > concerns, please reach out to AWS Support [4].
>     >
>     > [1]
>     >
>     https://blog.google/products/gmail/gmail-security-authentication-spam-protection/
>     > [2]
>     >
>     https://blog.postmaster.yahooinc.com/post/730172167494483968/more-secure-less-spam
>     > [3]
>     >
>     https://aws.amazon.com/blogs/messaging-and-targeting/an-overview-of-bulk-sender-changes-at-yahoo-gmail/
>     > [4] https://aws.amazon.com/support
>     >
>     > Sincerely,
>     > Amazon Web Services
>     >
>     > Amazon Web Services, Inc. is a subsidiary of Amazon.com, Inc.
>     > Amazon.com is a registered trademark of Amazon.com, Inc. This
>     message
>     > was produced and distributed by Amazon Web Services Inc., 410 Terry
>     > Ave. North, Seattle, WA 98109-5210
>
>     -- 
>     Internet-history mailing list
>     Internet-history at elists.isoc.org
>     https://elists.isoc.org/mailman/listinfo/internet-history
>

-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature.asc
Type: application/pgp-signature
Size: 665 bytes
Desc: OpenPGP digital signature
URL: <http://elists.isoc.org/pipermail/internet-history/attachments/20240114/0484a9a4/attachment.asc>