I'm not sure why b.barracudacentral.org doesn't like my MTA. I got something similar in my initial message to Simon but brushed it off thinking it was a fluke, but I just got this again with Mathieu in the recipient list, as well.
dcvr.yhbt.net was recently forced to get a new IP address, but DKIM + SPF are set up and it manages to deliver fine to at least one major email provider: > Reporting-MTA: dns; dcvr.yhbt.net > X-Postfix-Queue-ID: 343331F54E > X-Postfix-Sender: rfc822; normalper...@yhbt.net > Arrival-Date: Sat, 20 Aug 2022 18:51:43 +0000 (UTC) > > Final-Recipient: rfc822; mathieu.desnoy...@efficios.com > Original-Recipient: rfc822;mathieu.desnoy...@efficios.com > Action: failed > Status: 5.7.1 > Remote-MTA: dns; mail.efficios.com > Diagnostic-Code: smtp; 550 5.7.1 Service unavailable; client [173.255.242.215] > blocked using b.barracudacentral.org > > Final-Recipient: rfc822; simon.mar...@efficios.com > Original-Recipient: rfc822;simon.mar...@efficios.com > Action: failed > Status: 5.7.1 > Remote-MTA: dns; mail.efficios.com > Diagnostic-Code: smtp; 550 5.7.1 Service unavailable; client [173.255.242.215] > blocked using b.barracudacentral.org I wonder if any other self-hosters are hitting this problem... _______________________________________________ lttng-dev mailing list lttng-dev@lists.lttng.org https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
