Ah, indeed. I imagine that it is part of a move, since roughly March,
where many mail sources like yahoo and google are blocking addresses from
places where the hostname cannot be identified as they define that
concept.
I can no longer post to freelist.org for example, because the guy who owns
shellworld has not updated the ptr record..will be interesting if this
post gets through.
Karen
On Wed, 31 Jul 2024, Carlos E. R. via Alpine-info wrote:
On 2024-07-20 23:09, Bret Busby via Alpine-info wrote:
On 21/7/24 04:41, Bret Busby via Alpine-info wrote:
> On 21/7/24 04:15, James Miller via Alpine-info wrote:
Why has the mailing list administration been changed to conceal the email
address of posters?
Is that to prohibit subscribers from directly contacting a poster of a
message, in response to content of a post, and, to prohibit subscribers
from blocking email from a particular poster, if a poster shows delinquent
behaviour?
This change to the mailing list administration is ominous.
This is because mail having the poster email, but being actually sent by a
list server break security features such as DKIM-Signature, dmarc, or others
(I don't remember which one, exactly), but make the receiving mail server
reject the mail as if forged or manipulated in transit.
Thus the list mail server has to change the "From" line and add a new
Reply-To:
From: Bret Busby via Alpine-info <alpine-info@u.washington.edu>
Reply-To: Bret Busby <...>
Ie, if doing it the traditional way the receiving servers see that the post
is coming from u.washington.edu but have a from address someone.com, which
they consider invalid and reject the email. That's hundreds of rejects and
mail users angry because their mail is not received by subscribers. It is a
consequence of the fight on spam.
This is happening on several mail lists. Some do it only for some domains,
some do it for everybody.
This can not be avoided.
I had this explained by an admin on another mail list, but I can not locate
his post with the correct explanation. What I wrote is from memory.
Oh, found it (the short version):
??It is called "DMARC mitigation". We do that for sending domains with
DMARC policies.??
Well, u.washington.edu seems to be doing it for everybody.
--
Cheers / Saludos,
Carlos E. R.
(from 15.5 x86_64 at Telcontar)
_______________________________________________
Alpine-info mailing list
Alpine-info@u.washington.edu
http://mailman12.u.washington.edu/mailman/listinfo/alpine-info
