From: Eric Wong via lttng-dev <lttng-dev@lists.lttng.org>
To: lttng-dev <lttng-dev@lists.lttng.org>
Subject: [lttng-dev] efficios MX problems? (was: urcu 7ca7fe9c03 + _LGPL_SOURCE regression?)
Date: Sat, 20 Aug 2022 19:13:48 +0000 [thread overview]
Message-ID: <20220820191348.GC5248@dcvr> (raw)
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; normalperson@yhbt.net
> Arrival-Date: Sat, 20 Aug 2022 18:51:43 +0000 (UTC)
>
> Final-Recipient: rfc822; mathieu.desnoyers@efficios.com
> Original-Recipient: rfc822;mathieu.desnoyers@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.marchi@efficios.com
> Original-Recipient: rfc822;simon.marchi@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
next reply other threads:[~2022-08-20 19:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-20 19:13 Eric Wong via lttng-dev [this message]
2022-08-22 14:35 ` [lttng-dev] efficios MX problems? (was: urcu 7ca7fe9c03 + _LGPL_SOURCE regression?) Michael Jeanson via lttng-dev
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220820191348.GC5248@dcvr \
--to=lttng-dev@lists.lttng.org \
--cc=normalperson@yhbt.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.