Martin Schröder:
> > I did. And they have pulled the article.
>
> And it wasn't printed (new issue just dropped).
That's the March one. The article was scheduled for the April issue.
It's still listed here in their preview:
https://www.heise.de/select/ix/2025/3/2500316133559550686
--
Christian "naddy" Weisgerber naddy@mips.inka.de
OpenBSD Mail Box
BTC:1BsNfN6m7xtT4PqDb9jJHnDDFBb38zS9Yi
Thursday, February 20, 2025
Re: blacklisted for spam
On Thu, 20 Feb 2025 10:13:31 +0100, "Piotr K. Isajew" wrote:
> This blacklisting looks like a nonsense to me as the IP address
> in question is just a mail exchanger I use for my personal
> domain, no third parties are using this machine to send any
> emails and checking this address using publicly available
> blacklist checkers reports "no issues" for me. The address is
> leased from a bare metal server provider popular in Europe so it
> might be that it has been hit as part of a class containing other
> offensive IPs, but other than that I control this address for a
> few years now, so I don't get how come it get blacklisted. When I
> dispatch my mails to misc by a different MX for the same domain,
> they went through.
This may have been due to an overly broad blacklist on an OVH IP
range, though that is not something that has changed recently. I've
removed that IP range from the blacklist which may fix the issue
for you.
- todd
> This blacklisting looks like a nonsense to me as the IP address
> in question is just a mail exchanger I use for my personal
> domain, no third parties are using this machine to send any
> emails and checking this address using publicly available
> blacklist checkers reports "no issues" for me. The address is
> leased from a bare metal server provider popular in Europe so it
> might be that it has been hit as part of a class containing other
> offensive IPs, but other than that I control this address for a
> few years now, so I don't get how come it get blacklisted. When I
> dispatch my mails to misc by a different MX for the same domain,
> they went through.
This may have been due to an overly broad blacklist on an OVH IP
range, though that is not something that has changed recently. I've
removed that IP range from the blacklist which may fix the issue
for you.
- todd
Subscribe to:
Posts (Atom)