On 2025-11-20 16:47, Ulf Zibis via ffmpeg-user wrote:

Am 20.11.25 um 16:08 schrieb Mark Filipak via ffmpeg-user:
On 20/11/2025 06.39, Carlos E. R. via ffmpeg-user wrote:
On 2025-11-20 12:29, Carlos E. R. via ffmpeg-user wrote:
On 2025-11-20 00:11, Mark Filipak via ffmpeg-user wrote:
In the message I just wrote to ffmpeg-user, it appears that ffmpeg- user
added a "Cc:" header.

Not only is that undesired, the "Cc:" header is wrong.
Testing.
Confirm.

The usual is

   from name via mail list
   to mail list
   reply to <sender>

Now

   from name via mail list
   to mail list
   cc to <sender>

However, I have not received a double mail. I did not get the cc copy.
You would not get a copy because what you sent did not include the "Cc:"
header. ffmpeg-user added it to what it displays as though you _had_
included it. The "Cc:" headers ffmpeg-user is adding are phony.

That creates a spam risk for senders -- us -- because a spammer could
subscribe to ffmpeg-user and harvest those phony "Cc:" headers.

On the other hand, without it would no more be possible to privately answer to a sender. Spammers already know all our emails from harvesting before June 2025 or from elsewhere.

So I more liked it as it was since June 2025:
From: <sender>
To: <ffmpeg-user>
List-ID: ffmpeg-user

No longer possible.

The antispam entries in your mail account DNS entries specify who is allowed to send email for CoSoCo.de, and it is not the mail list server. Thus mail lists are forced to change the from address to their own, and instead, put the sender somewhere else, like a reply-to or a cc.

more info:

https://en.wikipedia.org/wiki/DMARC
https://en.wikipedia.org/wiki/Sender_Policy_Framework
https://en.wikipedia.org/wiki/DomainKeys_Identified_Mail

--
Cheers / Saludos,

                Carlos E. R.
                (from 15.6 x86_64 at Telcontar)

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature

_______________________________________________
ffmpeg-user mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to