On Mon, Oct 31, 2022 at 04:42:14PM -0700, Kevin Fenzi wrote:
On Tue, Nov 01, 2022 at 12:18:43AM +0100, Wolfgang Pfeiffer wrote:
> Kevin,
> Thanks for your quick response!
> [ ... ]
I have already tried this, so I guess let me know when/if you get the
bounce. ;) (ie, I have unsubscribed the user who I think is forwarding
to
outlook.com).
Good. Thanks! - After my last message to this list ("Nov 01, 2022 at
12:18:43AM +0100") I got no "Undeliverable" messages coming in to my
Inbox again. So far .. ;) .. I'll write back to you (not to the list)
if problems reappear ..
> > 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).
>
> Again: Please see my tl;dr from above: is this what your suggesting in
> this last part? If yes: as I said above: I'm fine with the address
> replacement for this list and for my roto(a)gmx.net address ...
I can't force the list to do this. Your domain would need to enable
DMARC and set reject or quarantine for the list software to decide to
set this for you. ;(
As Stephen already wrote a few hours ago:
gmx.net - I say: sadly -
isn't mine .. ;) .. it's a - I think German - email and I don't know
what else provider offering free and, I think, paid email services.
This needs a DNS entry added to your domain. See
https://dmarc.org/overview/
Thanks for this link - seems interesting: nice side-effect of this
"Undeliverable" messages problem is now that I might set up my own
email domain: I'm getting curious about this whole thing ... :) but on
the other hand: as long as
gmx.net works here: why care .. :)
Thanks for your efforts, Kevin - goes out also to everyone else in
this thread.
Regards,
Wolfgang
kevin