Linode blocks port 25 by default and requires manual intervention and a
"discussion" with support before they unblock it.
Unlike other providers like OVH and hetzner...
On 25 Nov 2021 23:18:51 -0500 John Levine via mailop wrote:
> It appears that Jarland Donnell via mailop said:
> >In all
Blacklists tend to target a whole /64 at once for IPv6 and this is
standard behavior. I just looked at my two Linode VMs and both have one
IPv6 from the same /64. It's possible that Linode is assigning a /64 per
customer and that no one else is in the same /64 as you. This is a
reasonable
On Thu, Nov 25, 2021 at 12:33:54PM +0200, Mary via mailop wrote:
> Hello everyone,
>
> I noticed today that spamhaus.org is blocking large net blocks of IPv6
> (2a01:7e01) owned by Linode. Pretty much all my clients hosted at Linode are
> being blocked en mass (for IPv6 only).
Hello everyone,
I noticed today that spamhaus.org is blocking large net blocks of IPv6
(2a01:7e01) owned by Linode. Pretty much all my clients hosted at Linode are
being blocked en mass (for IPv6 only).
Is there a way to inform spamhaus about this rather aggressive blocking and get
things
I first noticed that all outgoing emails that are using IPv6 addresses, are
being rejected by anyone using zen.spamhaus.org
I then tried a bunch of my addresses and they all tested as listed in
https://check.spamhaus.org/
Please see attached screenshot.
On Thu, 25 Nov 2021 12:52:18 +0200
On 25 Nov 2021, at 10:33, Mary via mailop wrote:
> I noticed today that spamhaus.org is blocking large net blocks of IPv6
> (2a01:7e01) owned by Linode. Pretty much all my clients hosted at Linode are
> being blocked en mass (for IPv6 only).
>
> Is there a way to inform spamhaus about this
I think Linode does not follow the /64 rule and assigns thousands of customers
within the 2a01:7e01::/64 block. They user a bunch of blocks, depending on
their data centre.
I think by default each client is assigned a single /128 IPv6 address per
server.
:(
On Thu, 25 Nov 2021 05:57:03
Hi Mary,
please see:
https://www.linode.com/community/questions/266/ipv6-64-blocks-on-linode
Linode can assign you a /64 that will probably solve your problems.
On 25/11/21 11:33, Mary via mailop wrote:
Hello everyone,
I noticed today that spamhaus.org is blocking large net blocks of IPv6
But that is not a real solution is it?
Maybe linode and spamhaus can come up with a better solution between them?
On Thu, 25 Nov 2021 13:48:27 + Riccardo Alfieri via mailop
wrote:
> Hi Mary,
>
> please see:
> https://www.linode.com/community/questions/266/ipv6-64-blocks-on-linode
>
Well, RIPE itself (https://www.ripe.net/publications/docs/ripe-690)
states that it's a best practice to assign to an end user no less than a /64
On 25/11/21 15:22, Mary via mailop wrote:
But that is not a real solution is it?
Maybe linode and spamhaus can come up with a better solution
On Thu, Nov 25, 2021 at 04:22:05PM +0200, Mary via mailop wrote:
>
> But that is not a real solution is it?
It is because it's the right thing to do in the first place.
> Maybe linode and spamhaus can come up with a better solution between them?
I would not expect any changes on the policy of
> Sure. Linode could decide to stop operating a public nuisance and
> police their sewer more effectively. Historically, Spamhaus has a
> long record of delisting network operators who reform their
> abuse-handling.
This isn't even about that. This is only about Linode cramming more
than one
Hi,
I think Linode does not follow the /64 rule and assigns thousands of customers
within the 2a01:7e01::/64 block. They user a bunch of blocks, depending on
their data centre.
I think by default each client is assigned a single /128 IPv6 address per
server.
See
On 2021-11-25 at 09:22:05 UTC-0500 (Thu, 25 Nov 2021 16:22:05 +0200)
Mary via mailop
is rumored to have said:
But that is not a real solution is it?
Maybe linode and spamhaus can come up with a better solution between
them?
Sure. Linode could decide to stop operating a public nuisance and
On Thu, Nov 25, 2021 at 03:07:02PM +0200, Mary via mailop wrote:
>
> I think Linode does not follow the /64 rule and assigns thousands of
> customers within the 2a01:7e01::/64 block. They user a bunch of blocks,
> depending on their data centre.
>
> I think by default each client is assigned a
On 25/11/2021 14:22, Mary via mailop wrote:
But that is not a real solution is it?
Maybe linode and spamhaus can come up with a better solution between them?
Why is it not a real solution?
It's a bigger problem than Linode and Spamhaus. (I refer to Linode
in my writings, but I don't
On Thu, Nov 25, 2021 at 03:07:02PM +0200, Mary via mailop wrote:>> I
think Linode does not follow the /64 rule and assigns thousands of
customers within the 2a01:7e01::/64 block. They user a bunch of blocks,
depending on their data centre.>> I think by default each client is
assigned a single
On 11/25/21 06:22, Mary via mailop wrote:
But that is not a real solution is it?
Maybe linode and spamhaus can come up with a better solution between them?
It's not a Spamhaus problem. Linode is beyond stupid. Linode has over
four billion /64s. The rest of the Internet treats a /64 as a
On 11/25/21 12:18 PM, Jay Hennigan via mailop wrote:
It's not a Spamhaus problem. Linode is beyond stupid. Linode has over
four billion /64s. The rest of the Internet treats a /64 as a single
user or subnet. Linode should be allocating each customer subnet a /64
as a minimum.
If you're a
In all fairness, some of these systems may have been deployed before we
were all really certain that a /64 per customer was going to be an
accepted standard. You know how RFCs go, they're the law of the land
except when they're not, which is actually pretty often. By now most
should have
One thing that I think we can do to "help" in this instance is actually
list which addresses traffic has been seen from, rather than just
reporting the /64 being listed.
For this range - I'm only seeing 3 IPv6 addresses hitting traps
2a01:7e01::f03c:92ff:fed4:25b5 "YourBud " -
abuseable web
Fair enough too, the amount of crap coming from linode in recent weeks
exceeds the levels from gmail and outlook combined, both ipv4 and 6
usually they send about the same as the others, not more than both of
them together.
On 25/11/2021 21:15, Mary via mailop wrote:
I first noticed that
It appears that Jarland Donnell via mailop said:
>In all fairness, some of these systems may have been deployed before we
>were all really certain that a /64 per customer was going to be an
>accepted standard.
A /64 per customer has always been the plan. There is no good reason
to assign
23 matches
Mail list logo
