>
> It's a catchall forwarded domain "@olddomain -> @newdomain", so
> Postfix accepted it before checking the final recipient.
>
> Now that you said it, I'm going to suggest to the user to just
> alias individual addresses instead of the catchall.
>
> I still think Microsoft should not
> Date: Tuesday, September 05, 2023 18:00:17 -0500
> From: Ken Johnson via mailop
>
> Writing from $dayjob:
>
> Is there a contact for the debian.org mailing lists listening?
>
>
You'll find list maintainer contact information in the "list
maintenance" section of:
We have been seeing this also for about the last week. Our Verizon reps are
telling us we need to pay for their EMAG (Enterprise Messaging) service to not
get blocked.
Richard Osborne
Information Systems
West Tennessee Healthcare
NOTICE: (1) The foregoing is not intended to be a legally
> Date: Monday, December 05, 2022 10:50:48 -0800
> From: William Kern
>
> I was contacted by a website customer over the weekend, who is
> affected by the RackSpace Exchange "security issue".
>
> At this point, they are transitioning to O365 so they should be
> fine going forward, but aside
> Date: Tuesday, August 18, 2020 14:27:09 -0700
> From: Ken Simpson
>
> Is anyone else seeing this when they try to connect to the listserv?
>
> $ curl https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
> *curl: (7) Failed to connect to chilli.nosignal.org
>
