On Sun, Oct 30, 2022 at 08:57:28PM +0100, Wolfgang Pfeiffer wrote: ...snip... > > By now the list management - provided there is one - should know about > the problem. If they can't fix it I will by sending those DSNs to > /dev/null - or I just unsubscribe. > > Thanks a lot for your time - goes out equally to everyone having > contributed to this thread. Just FYI, I looked into this and: So, from what I can see, I think this is whats happening: 1. You send an email to the users list. 2. It goes to the lists.fedoraproject.org list server, is processed and sends out to subscribers. 3. Some subscriber on the list (not 100% clear who) forwards their email to yurelw@xxxxxxxxxxx 4. yurelw@xxxxxxxxxxx email is in turn forwarded to antoniowatson@xxxxxxxxx 5. gmail checks the SPF record of the email sender (you, thus gmx.net): gmx.net descriptive text "v=spf1 ip4:213.165.64.0/23 ip4:74.208.5.64/26 ip4:212.227.126.128/25 ip4:212.227.15.0/25 ip4:212.227.17.0/27 ip4:74.208.4.192/26 ip4:82.165.159.0/24 ip4:217.72.207.0/27 ip4:82.165.229.31 ip4:82.165.230.21 -all" Since outlook.com (which is sending the email) isn't in any of those IP addresses, gmail.com rejects it. I can try unsubscribing the email I _think_ is being forwarded to the outlook.com user. The list has mitigation for a similar case (DMARC). It applies this to messages From: a domain publishing a DMARC policy of reject or quarantine So, if you could add such a policy/support to gmx.com it could use this workaround (basically it replaces your sender address with the list address). kevin
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
