Re: [mailop] spamhaus blocking Linode IPv6 (2a01: 7e01)
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 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 less. It's not like there is any risk of running out of addresses. > > A reasonable transition plan would be for linode (or any other hosting > provlder) > to block port 25 by default. If a customer asks to unblock it, put them > in their own /64. > > ___ > mailop mailing list > mailop@mailop.org > https://list.mailop.org/listinfo/mailop ___ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
Re: [mailop] spamhaus blocking Linode IPv6 (2a01: 7e01)
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 less. It's not like there is any risk of running out of addresses. A reasonable transition plan would be for linode (or any other hosting provlder) to block port 25 by default. If a customer asks to unblock it, put them in their own /64. ___ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
Re: [mailop] spamhaus blocking Linode IPv6 (2a01:7e01)
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 all outgoing emails that are using IPv6 addresses, are being rejected by anyone using zen.spamhaus.org -- Regards, Noel Butler This Email, including attachments, may contain legally privileged information, therefore at all times remains confidential and subject to copyright protected under international law. You may not disseminate this message without the authors express written authority to do so. If you are not the intended recipient, please notify the sender then delete all copies of this message including attachments immediately. Confidentiality, copyright, and legal privilege are not waived or lost by reason of the mistaken delivery of this message.___ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
Re: [mailop] spamhaus blocking Linode IPv6 (2a01:7e01)
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 form 2a01:7e01::f03c:92ff:fee3:7758 - infected/compromised host 2a01:7e01::f03c:91ff:fece:24e8 - ""Sparkasse" " - compromised account Hope that helps. Kind regards, Steve. -- Steve Freegard Senior Product Owner Abusix Intelligence On 25/11/2021 11:15, Mary via mailop wrote: 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 inhttps://check.spamhaus.org/ Please see attached screenshot. On Thu, 25 Nov 2021 12:52:18 +0200 Atro Tossavainen via mailop wrote: 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). https://www.spamhaus.org/sbl/listings/linode.com contains nothing on IPv6. What exactly are you seeing? Is there a way to inform spamhaus about this rather aggressive blocking and get things sorted? Thank you. ___ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop -- Atro Tossavainen, Chairman of the Board Infinite Mho Oy, Helsinki, Finland tel. +358-44-5000 600,http://www.infinitemho.fi/ ___ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop ___ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop ___ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
Re: [mailop] spamhaus blocking Linode IPv6 (2a01:7e01)
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 figured out that they need to conform to this one, but I don't really blame early adopters for second guessing what common implementations would look like a few years down the road. On 2021-11-25 12:04, Jay Hennigan via mailop wrote: 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 /128 IPv6 address per server. That is rather stupid behavior on Linode's part then. The rest of the Internet uses a /64 per subnet and typically a /56 per customer minimum. What are they thinking? Are they really worried about running out of IPv6 addresses? Vote with your feet. ___ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
Re: [mailop] spamhaus blocking Linode IPv6 (2a01:7e01)
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 Linode customer, demand a /64. Point them here: https://datatracker.ietf.org/doc/html/rfc7421 There's some questionable info on this thread. Linode uses SLAAC to assign a single IPv6 to each linode, but gives out /64 blocks on request https://www.linode.com/docs/guides/linux-static-ip-configuration/ They recommended to me to use a /64 address and not the SLAAC address for my servers, including the mail server. No charge. You don't have to demand, just submit a support ticket as the docs say. I ran into this problem a couple of years ago, switching to the /64 block resolved it. It wasn't a huge deal. John ___ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
Re: [mailop] spamhaus blocking Linode IPv6 (2a01:7e01)
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 single user or subnet. Linode should be allocating each customer subnet a /64 as a minimum. If you're a Linode customer, demand a /64. Point them here: https://datatracker.ietf.org/doc/html/rfc7421 -- Jay Hennigan - j...@west.net Network Engineering - CCIE #7880 503 897-8550 - WB6RDV ___ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
Re: [mailop] spamhaus blocking Linode IPv6 (2a01:7e01)
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 /128 IPv6 address per server. That is rather stupid behavior on Linode's part then. The rest of the Internet uses a /64 per subnet and typically a /56 per customer minimum. What are they thinking? Are they really worried about running out of IPv6 addresses? Vote with your feet. -- Jay Hennigan - j...@west.net Network Engineering - CCIE #7880 503 897-8550 - WB6RDV ___ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
Re: [mailop] spamhaus blocking Linode IPv6 (2a01:7e01)
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 mean to single them out. It could refer to any VM or hosting provider) And in a way it is because the address space numbers (and maths) for IPv6 are so completely bonkers, it takes a big of getting used to. There have been various ideas floated over the years to declare the allocation size in a way that improves on what is in the whois data or RIPE database. I don't think any have really worked. The theory being a spam blocker could look up an IP address and see what size netblocks are allocated to customers. So how wide to block to stop the customer just swapping to one of the other 18446744073709551616 IP addresses a typically IPv6 user with a /64 has. 2001:db8:1::/48 - > in here, customers are each given a /64 So 2001:db8::1 and 2001:db8::2 will be the same customer/VM just with 2 IP's on the machine. If one is spamming, maybe don't trust the other. 2001:db8:2::/48 -> in here, customers are each given a /128 so 2001:db8:2::1 and 2001:db8:2::2 are 2 absolutely completely unrelated customers and so if ::1 is spamming, this is no indication about what ::2 might be doing (except that maybe if it keeps going a long time, the provider is not proactive in kicking off spammy customers) But I don't think any of these schemes really got off the ground. Is it realistic to do some kind of lookup everytime you want to drop in a firewall rule or some kind of blocklist (or be less trusting list)? I don't think the whois system could scale that well to the numbre of lookups. Ok, my home /48 is in RIPE saying I have a /48 allocation, but my ISP happens to be good at keeping the RIPE DB up to date and they like the detail in RIPE. Other ISPs have way less complete data. In reality IPv6 addresses are abundant and even consumer services like SKY are allocating a /56 (256 lots of /64) to every single home customer. So probably just easier for VM providers to dish out /64 per paying customer or VM. Or at least make it really easy for a customer who needs it just request a /64. And let everybody block on /64. Linode's /32 allocation allows for 4,294,967,296 customers to have their own /64 network. (ok, less than this, some grouping to make their internal routing table easier, network segmentation, different datacentres) And if you think that isn't enough, linode have at least 13 x /32 allocations. See https://bgp.he.net/AS63949#_prefixes6 They aren't exactly short of address space. :) I'm sure linode could to go RIPE and ask for more space too. (if Linode go past 52 billion customers, give me a call) -- Tim Bray Huddersfield, GB t...@kooky.org ___ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
Re: [mailop] spamhaus blocking Linode IPv6 (2a01:7e01)
> 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 customer into a /64 against best current practice, pure and simple. -- Atro Tossavainen, Chairman of the Board Infinite Mho Oy, Helsinki, Finland tel. +358-44-5000 600, http://www.infinitemho.fi/ ___ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
Re: [mailop] spamhaus blocking Linode IPv6 (2a01:7e01)
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 police their sewer more effectively. Historically, Spamhaus has a long record of delisting network operators who reform their abuse-handling. -- Bill Cole b...@scconsult.com or billc...@apache.org (AKA @grumpybozo and many *@billmail.scconsult.com addresses) Not Currently Available For Hire ___ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
Re: [mailop] spamhaus blocking Linode IPv6 (2a01:7e01)
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 https://www.spamhaus.org/organization/statement/012/spamhaus-ipv6-blocklists-strategy-statement :( Indeed. That would seem like a very counterproductive approach from Linode. As talvi.dovecot.org is also on the list, which provides Dovecot mailinglists - does Upcload also assign only a /128 from a /64 shared with other customers? Regards Bjoern ___ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
Re: [mailop] spamhaus blocking Linode IPv6 (2a01:7e01)
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 the latter. > > > > 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 > > > > Linode can assign you a /64 that will probably solve your problems. > ___ > mailop mailing list > mailop@mailop.org > https://list.mailop.org/listinfo/mailop -- Atro Tossavainen, Chairman of the Board Infinite Mho Oy, Helsinki, Finland tel. +358-44-5000 600, http://www.infinitemho.fi/ ___ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
Re: [mailop] spamhaus blocking Linode IPv6 (2a01:7e01)
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 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 Linode can assign you a /64 that will probably solve your problems. ___ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop -- Best regards, Riccardo Alfieri Spamhaus Technology https://www.spamhaustech.com/ ___ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
Re: [mailop] spamhaus blocking Linode IPv6 (2a01:7e01)
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 > > Linode can assign you a /64 that will probably solve your problems. ___ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
Re: [mailop] spamhaus blocking Linode IPv6 (2a01:7e01)
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 (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 sorted? Thank you. ___ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop -- Best regards, Riccardo Alfieri Spamhaus Technology https://www.spamhaustech.com/ ___ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
Re: [mailop] spamhaus blocking Linode IPv6 (2a01:7e01)
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 /128 IPv6 address per > server. See https://www.spamhaus.org/organization/statement/012/spamhaus-ipv6-blocklists-strategy-statement > :( Indeed. That would seem like a very counterproductive approach from Linode. > > > On Thu, 25 Nov 2021 05:57:03 -0600 Jarland Donnell via mailop > wrote: > > > 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 expectation, and while arguing over v6 implementation will > > probably continue for the rest of my lifetime, this is an expected > > standard. Here's a little fun thing people like to use as a quick > > reference on that note: https://slash64.net/ > > > > This would suggest that Spamhaus is not blocking all of Linode's IPv6, > > but instead just you, a single customer with a single /64. This would be > > for the reasons that they note, and would need to be resolved prior to > > requesting delisting. If you're certain that the listing has nothing to > > do with you, then you'll want to ask Linode support if there could be > > anyone else on that /64. If they say yes, stop sending mail over IPv6 > > from Linode right away, because blacklists will target a /64 at once and > > Linode's implementation will be proven at that moment to be bad. I don't > > think that'll be the case though. > > > > On 2021-11-25 05:15, Mary via mailop wrote: > > > 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 Atro Tossavainen via mailop > > > wrote: > > > > > >> 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). > > >> > > >> https://www.spamhaus.org/sbl/listings/linode.com contains nothing on > > >> IPv6. What exactly are you seeing? > > >> > > >> > Is there a way to inform spamhaus about this rather aggressive > > >> > blocking and get things sorted? > > >> > > > >> > Thank you. > > >> > > > >> > > > >> > > > >> > > > >> > ___ > > >> > mailop mailing list > > >> > mailop@mailop.org > > >> > https://list.mailop.org/listinfo/mailop > > >> > > >> -- > > >> Atro Tossavainen, Chairman of the Board > > >> Infinite Mho Oy, Helsinki, Finland > > >> tel. +358-44-5000 600, http://www.infinitemho.fi/ > > >> ___ > > >> mailop mailing list > > >> mailop@mailop.org > > >> https://list.mailop.org/listinfo/mailop > > > > > > ___ > > > mailop mailing list > > > mailop@mailop.org > > > https://list.mailop.org/listinfo/mailop > > ___ > > mailop mailing list > > mailop@mailop.org > > https://list.mailop.org/listinfo/mailop > ___ > mailop mailing list > mailop@mailop.org > https://list.mailop.org/listinfo/mailop -- Atro Tossavainen, Chairman of the Board Infinite Mho Oy, Helsinki, Finland tel. +358-44-5000 600, http://www.infinitemho.fi/ ___ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
Re: [mailop] spamhaus blocking Linode IPv6 (2a01:7e01)
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 -0600 Jarland Donnell via mailop wrote: > 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 expectation, and while arguing over v6 implementation will > probably continue for the rest of my lifetime, this is an expected > standard. Here's a little fun thing people like to use as a quick > reference on that note: https://slash64.net/ > > This would suggest that Spamhaus is not blocking all of Linode's IPv6, > but instead just you, a single customer with a single /64. This would be > for the reasons that they note, and would need to be resolved prior to > requesting delisting. If you're certain that the listing has nothing to > do with you, then you'll want to ask Linode support if there could be > anyone else on that /64. If they say yes, stop sending mail over IPv6 > from Linode right away, because blacklists will target a /64 at once and > Linode's implementation will be proven at that moment to be bad. I don't > think that'll be the case though. > > On 2021-11-25 05:15, Mary via mailop wrote: > > 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 Atro Tossavainen via mailop > > wrote: > > > >> 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). > >> > >> https://www.spamhaus.org/sbl/listings/linode.com contains nothing on > >> IPv6. What exactly are you seeing? > >> > >> > Is there a way to inform spamhaus about this rather aggressive blocking > >> > and get things sorted? > >> > > >> > Thank you. > >> > > >> > > >> > > >> > > >> > ___ > >> > mailop mailing list > >> > mailop@mailop.org > >> > https://list.mailop.org/listinfo/mailop > >> > >> -- > >> Atro Tossavainen, Chairman of the Board > >> Infinite Mho Oy, Helsinki, Finland > >> tel. +358-44-5000 600, http://www.infinitemho.fi/ > >> ___ > >> mailop mailing list > >> mailop@mailop.org > >> https://list.mailop.org/listinfo/mailop > > > > ___ > > mailop mailing list > > mailop@mailop.org > > https://list.mailop.org/listinfo/mailop > ___ > mailop mailing list > mailop@mailop.org > https://list.mailop.org/listinfo/mailop ___ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
Re: [mailop] spamhaus blocking Linode IPv6 (2a01:7e01)
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 expectation, and while arguing over v6 implementation will probably continue for the rest of my lifetime, this is an expected standard. Here's a little fun thing people like to use as a quick reference on that note: https://slash64.net/ This would suggest that Spamhaus is not blocking all of Linode's IPv6, but instead just you, a single customer with a single /64. This would be for the reasons that they note, and would need to be resolved prior to requesting delisting. If you're certain that the listing has nothing to do with you, then you'll want to ask Linode support if there could be anyone else on that /64. If they say yes, stop sending mail over IPv6 from Linode right away, because blacklists will target a /64 at once and Linode's implementation will be proven at that moment to be bad. I don't think that'll be the case though. On 2021-11-25 05:15, Mary via mailop wrote: 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 Atro Tossavainen via mailop wrote: 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). https://www.spamhaus.org/sbl/listings/linode.com contains nothing on IPv6. What exactly are you seeing? > Is there a way to inform spamhaus about this rather aggressive blocking and get things sorted? > > Thank you. > > > > > ___ > mailop mailing list > mailop@mailop.org > https://list.mailop.org/listinfo/mailop -- Atro Tossavainen, Chairman of the Board Infinite Mho Oy, Helsinki, Finland tel. +358-44-5000 600, http://www.infinitemho.fi/ ___ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop ___ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop ___ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
Re: [mailop] spamhaus blocking Linode IPv6 (2a01:7e01)
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 Atro Tossavainen via mailop wrote: > 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). > > https://www.spamhaus.org/sbl/listings/linode.com contains nothing on > IPv6. What exactly are you seeing? > > > Is there a way to inform spamhaus about this rather aggressive blocking and > > get things sorted? > > > > Thank you. > > > > > > > > > > ___ > > mailop mailing list > > mailop@mailop.org > > https://list.mailop.org/listinfo/mailop > > -- > Atro Tossavainen, Chairman of the Board > Infinite Mho Oy, Helsinki, Finland > tel. +358-44-5000 600, http://www.infinitemho.fi/ > ___ > mailop mailing list > mailop@mailop.org > https://list.mailop.org/listinfo/mailop ___ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
Re: [mailop] spamhaus blocking Linode IPv6 (2a01:7e01)
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 rather aggressive blocking and > get things sorted? It’s on the XBL rather than the SBL: https://check.spamhaus.org/listed/?searchterm=2a01:7e01:: "A device using 2a01:7e01::/64 is infected with malware and is emitting spam.” Coincidentally there’s also a CSS (so SBL) listing for 2a01:7e00::/32, also Linode. Graeme signature.asc Description: Message signed with OpenPGP ___ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
Re: [mailop] spamhaus blocking Linode IPv6 (2a01:7e01)
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). https://www.spamhaus.org/sbl/listings/linode.com contains nothing on IPv6. What exactly are you seeing? > Is there a way to inform spamhaus about this rather aggressive blocking and > get things sorted? > > Thank you. > > > > > ___ > mailop mailing list > mailop@mailop.org > https://list.mailop.org/listinfo/mailop -- Atro Tossavainen, Chairman of the Board Infinite Mho Oy, Helsinki, Finland tel. +358-44-5000 600, http://www.infinitemho.fi/ ___ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
[mailop] spamhaus blocking Linode IPv6 (2a01:7e01)
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 sorted? Thank you. ___ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
