From: Michael Jeanson via lttng-dev <lttng-dev@lists.lttng.org>
To: Eric Wong <normalperson@yhbt.net>, lttng-dev <lttng-dev@lists.lttng.org>
Subject: Re: [lttng-dev] efficios MX problems? (was: urcu 7ca7fe9c03 + _LGPL_SOURCE regression?)
Date: Mon, 22 Aug 2022 10:35:42 -0400 [thread overview]
Message-ID: <12ef14f0-c09e-5fb6-1114-e814521a79ab@efficios.com> (raw)
In-Reply-To: <20220820191348.GC5248@dcvr>
On 2022-08-20 15:13, Eric Wong via lttng-dev wrote:
> 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...
Hi Eric,
The ip address of your mx server (173.255.242.215) is blacklisted at Barracuda
and SORBS, since you mention the address was recently changed this is probably
because of the previous owners. Both of those blacklists should provide ways
to get delisted, this is something I had to handle previously with other
blacklists when setting up a new mx.
A good tool to check the reputation of your mx ip is mxtoolbox.com [1].
I will manually whitelist the address of you mx on our server since I know
it's legitimate but you should have the people managing it look into this
since you'll probably have issues with other servers.
Hope this helps, cheers,
Michael
[1] https://mxtoolbox.com/SuperTool.aspx?action=blacklist%3ayhbt.net&run=toolpage
_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
prev parent reply other threads:[~2022-08-22 14:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-20 19:13 Eric Wong via lttng-dev
2022-08-22 14:35 ` Michael Jeanson via lttng-dev [this message]
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=12ef14f0-c09e-5fb6-1114-e814521a79ab@efficios.com \
--to=lttng-dev@lists.lttng.org \
--cc=mjeanson@efficios.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox