Re: [mailop] IP RBLs and large cidr blocks

[Matthew Stith via mailop]

Michael,

Feel free to hit me up off list.

Also one statement for the group, Spamhaus only lists IPv6 space in /64s 
with the XBL and CSS lists. There may be larger ones in the SBL DROP or 
EDROP lists but those are indicative of hijacked space and wouldn't 
belong to a legit hosting company.


On 3/9/2023 7:50 AM, Michael Grant via mailop wrote:

Is there some way an ISP can tell an RBL how it's split up it's
internal IP address space?  For example, our Linode's ipv6 address is
on the Spamhaus XBL, but it's the entire /28.  (Thanks Tobias for
prompting me to check this!)

Anyway, it got me wondering, is there some way an ISP such as Linode
can communicate to Spamhaus how it carves up it's large swatches of
addresses?  Or does this somehow happen automatically over time as I
as a customer delist my single /128 address in their database?

In the case of Spamhaus, I tried to delist my address and the delist
page says I need to make sure the problem in 2600:3c02::/32 has been
resolved.

When I do a whois lookup on my ipv6 addr, Linode is responsible for
the entire /28 yet Spamhaus seems already to have split that up down
to the /32 level, yet really it probably should be split down to the
/64 and in some cases /56 level.

I was curious, does this happen and how?  Is there some internet
database that keeps track of how smaller swatches of the address space
are actually carved up?  Smaller than what whois reports.

To be clear, I'm talking about how the address space is split up, NOT
the actual customer like whois reports.

Barring that, is there some way to tell Spamhaus how the address space
is carved up so I can communicate that to Linode?  I looked but didn't
see anything obvious.

Michael Grant

___
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] Cyren

[Matthew Stith via mailop]

All,

Spamhaus is offering our data query service for free for 90 days for 
users impacted by Cyren's sudden liquidation. No strings attached just 
an effort to get those that are impacted by the news this week protected 
as quickly as possible. Our hopes is that this gives users protection 
against abuse while they figure out their next steps.
https://www.spamhaus.com/free-trial/sign-up-for-a-free-data-query-service-account/ 



And any Cyren employees that may be on this list. Know that you have the 
support of the community behind you.


Thanks,
Matt Stith
Spamhaus

___
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop

Re: [mailop] Anyone from Spamhaus?

[Matthew Stith via mailop]

Replying offlist

On 1/27/2023 3:23 AM, Support 3Hound via mailop wrote:

Hi All,
we are also having false positive with CSS on any sending IP in our 
212.115.97.0/24 since we re-start mailing after we stopped Christmas 
Holidays.

I opened a CSS ticket having replies (and re-listing) every 3-4 days.
The "issue" identified every time differs:
-"message characteristics identical to previously identified spam 
messages" => switched to another message template
-"There are a number of factors involved [...] I am unable to tell you 
exactly what it is that is setting off
the detectors" => re check every technical staff and verified no any 
user added since more than 1 year, only lists hygiene
-"IPs all lighting up at the same time is the most likely cause" => 
reduced the number of the IP to a correct value of 48 (for 8 different 
database/senders)
-"At this precise moment in time, 49 IPs are listed with no reason or 
rhyme that I can identify" => asked for a whitelisting
-"lighting up 48 IPs on 20thwill set off the robots that are trained 
to look for spikes" => lowered the amount of sending IPs to 16
-"Some of these IPs are now such regular guests that they are in 
extended purgatory to prevent gaming the system."


It seem that stop mailing for Christmas holidays and trying to follows 
suggestions from the ticket bring us to purgatory.

If this mood continue, I think it's going to bring us to hell..

I figured out (not sure of that) the person that is replying me to the 
ticket cannot act any cleaning/correction on CSS even if I'm confident 
he understood there are no real issues in our mailing practice but 
only some pattern that CSS misunderstood.
So I'm writing here hoping anyone from Spamhaus may have a different 
"grants" to solve this on ther side.


Many thanks,
Luca






Il 20/01/2023 05:20, Mark Fletcher via mailop ha scritto:

Hi All,

Over the past couple of days, the two servers that send email for 
groups.io , 66.175.222.12 and 66.175.222.108, have 
been listed on the Spamhaus CSS blacklist a couple times each. We're 
an email groups hosting service, like Google Groups. Nothing has 
changed on our end for quite a long time with those machines, and I 
don't believe they're compromised. Meanwhile, the email is backing up.


I've gone through the delisting process for the IPs. (I assume at 
some point that'll stop working). I've sent an inquiry to Spamhaus' 
contact form.


I'm scratching my head and feeling a bit dumb. Is there anyone here 
from Spamhaus that could give me some more information as to what's 
going on and how I can fix it?


Thanks,
Mark

___
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] USPS mailing

[Matthew Stith via mailop]

Hey there Mailop folks,

On Monday March 7th and going on for a few days Microsoft and Amazon 
will be sending out messages on behalf of USPS in relation to Covid 
Home-test-kits. They ask that these message be allowed. We were provided 
with the following information regarding the mailing:*USPS March 7th 
mailing*

U.S. Postal Service
Sending Domain email-special.usps.com 
Sending Address 
nore...@email-special.usps.com
*Main URL*https://special.usps.com/testkits 
The messages are going to be coming 
from Amazon space. I have added the list of IPs that they will be 
sending from.
54.240.10.6
54.240.10.14
54.240.10.15
54.240.10.23
54.240.10.31
54.240.10.32
54.240.10.34
54.240.10.35
54.240.10.36
54.240.10.37
54.240.10.38
54.240.10.39
54.240.10.40
54.240.10.41
54.240.10.42
54.240.10.43
54.240.10.46
54.240.10.47
54.240.10.48
54.240.10.49
54.240.10.50
54.240.10.52
54.240.10.53
54.240.10.54
54.240.10.55
54.240.10.56
54.240.10.57
54.240.10.58
54.240.10.59
54.240.10.61
54.240.10.62
54.240.10.63
54.240.10.64
54.240.10.68
54.240.10.69
54.240.10.73
54.240.10.74
54.240.10.75
54.240.10.76
54.240.10.77
54.240.10.78
54.240.10.79
54.240.10.81
54.240.10.82
54.240.10.85
54.240.10.86
54.240.10.89
54.240.10.97
54.240.10.98
54.240.10.99
54.240.10.100
54.240.10.110
54.240.10.112
54.240.10.113
54.240.10.115
54.240.10.116
54.240.10.120
54.240.10.133
54.240.10.137
54.240.10.140
54.240.10.150
54.240.10.170
54.240.10.184
54.240.10.200
54.240.10.201
54.240.10.202
54.240.10.203
54.240.10.206
54.240.10.207
54.240.10.208
54.240.10.209
54.240.10.210
54.240.10.211
54.240.10.212
54.240.10.213
54.240.10.214
54.240.10.215
54.240.10.216
54.240.10.217
54.240.10.218
54.240.10.219
54.240.10.220
54.240.10.221
54.240.10.222
54.240.10.223
54.240.10.224
54.240.10.225
54.240.10.226
54.240.10.227
54.240.10.228
54.240.10.229
54.240.10.230
54.240.10.231
54.240.10.232
54.240.10.233
54.240.10.234
54.240.10.235
54.240.10.236
54.240.10.237
54.240.10.238
54.240.10.239
54.240.10.240
54.240.10.241

54.240.11.13
54.240.11.14

54.240.14.143

54.240.30.6
54.240.30.7
54.240.30.8
54.240.30.9
54.240.30.10
54.240.30.41
54.240.30.42
54.240.30.55
54.240.30.72
54.240.30.73
54.240.30.74
54.240.30.78
54.240.30.79
54.240.30.126
54.240.30.134
54.240.30.183
54.240.30.190
54.240.30.208
54.240.30.209
54.240.30.210
54.240.30.211
54.240.30.214
54.240.30.215
54.240.30.236

54.240.31.31
54.240.31.37
54.240.31.38
54.240.31.39
54.240.31.45
54.240.31.46
54.240.31.55
54.240.31.59
54.240.31.60
54.240.31.61
54.240.31.70
54.240.31.71
54.240.31.151
54.240.31.176
54.240.31.177
54.240.31.178
54.240.31.179
54.240.31.180
54.240.31.181
54.240.31.182
54.240.31.183
54.240.31.196
54.240.31.197
54.240.31.220
54.240.31.241
54.240.31.242
54.240.31.243
54.240.31.244
54.240.31.247

54.240.32.56
54.240.32.57
54.240.32.58
54.240.32.62
54.240.32.68
54.240.32.80
54.240.32.85
54.240.32.86
54.240.32.113
54.240.32.114
54.240.32.131
54.240.32.132
54.240.32.135
54.240.32.137
54.240.32.148
54.240.32.149
54.240.32.150
54.240.32.151
54.240.32.160
54.240.32.161
54.240.32.162

54.240.33.96
54.240.33.97
54.240.33.98
54.240.33.120
54.240.33.121
54.240.33.122
54.240.33.128
54.240.33.129
54.240.33.130
54.240.33.136
54.240.33.137
54.240.33.138
54.240.33.192
54.240.33.193
54.240.33.194
54.240.33.200
54.240.33.201
54.240.33.202
54.240.33.208
54.240.33.209
54.240.33.210

54.240.34.1
54.240.34.2
54.240.34.3
54.240.34.160
54.240.34.161
54.240.34.162
54.240.34.168
54.240.34.169
54.240.34.170
54.240.34.208
54.240.34.209
54.240.34.210
54.240.34.232
54.240.34.233
54.240.34.234
54.240.34.248
54.240.34.249
54.240.34.250

54.240.35.8
54.240.35.9
54.240.35.10
54.240.35.224
54.240.35.225
54.240.35.226

54.240.36.137
54.240.36.138
54.240.36.139
54.240.36.141
54.240.36.142
54.240.36.143
54.240.36.144
54.240.36.145
54.240.36.146
54.240.36.147
54.240.36.152
54.240.36.153
54.240.36.154
54.240.36.192
54.240.36.193
54.240.36.194

54.240.37.8
54.240.37.9
54.240.37.10
54.240.37.32
54.240.37.33
54.240.37.45
54.240.37.56
54.240.37.59
54.240.37.128
54.240.37.129
54.240.37.144
54.240.37.145
54.240.37.152
54.240.37.153
54.240.37.232
54.240.37.233
54.240.37.248
54.240.37.249

54.240.38.216
54.240.38.72

54.240.39.1
54.240.39.2
54.240.39.97
54.240.39.120
54.240.39.121
54.240.39.122
54.240.39.136
54.240.39.168
54.240.39.169


___
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop

[mailop] Beta domain block list testing

[Matthew Stith via mailop]

Hey there Mailop folks,

Spamhaus would like to invite the MailOP community to test our beta 
domain blocklists with hostnames.


We’ve developed this version of the DBL to provide increased accuracy 
when using the abused-legit component of the DBL (listings of 
compromised websites). 
 https://www.spamhaus.com/resource-center/hostnames-for-spamhaus-domain-blocklist/


The beta blocklist is available via our public mirrors 
“dbl-beta.spamhaus.org”. It will be available until Jan 31st, 2022. 
After this time, it will be moved to production and will only be 
available via our Data Query Service or rsync.


If you are a non-commercial user of the Spamhaus Project’s blocklists 
(via its Public Mirrors), we recommend moving to a free DQS account with 
access to additional blocklists. 
https://www.spamhaus.com/free-trial/sign-up-for-a-free-data-query-service-account/


For anyone using one of Spamhaus’ specially developed plug-ins, we have 
configuration updates available so you can easily use this newly 
released beta 
DBL. SpamAssassin https://github.com/spamhaus/spamassassin-dqs/blob/master/HOWTO_DBL_with_hostnames.md and Rspamd https://github.com/spamhaus/rspamd-dqs/blob/master/HOWTO_DBL_with_hostnames.md.


We’d love to get your feedback on the beta DBL with hostnames. You can 
reach us either in this forum, via our contact form 
https://www.spamhaus.com/#contact-form, or on Twitter 
https://twitter.com/SpamhausTech.


Thanks for your support and feedback.

___
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop

Re: [mailop] I disabled Spamhaus checking due to false-positives

[Matthew Stith via mailop]

Mark,

Replying off list to see if we can figure out what is going on.

On 7/15/2021 7:29 AM, Mark Milhollan via mailop wrote:
> Spamhaus has been working fine for me and has been a wonderful
> resource for many years, but I recently decided I had to disable using
> them on my personal, low volume mail server because of a few recent
> surprises (that's right, I don't look at Spamhaus rejects, timestamps
> are UTC):
>
>   Jul 10 22:20:34 mm-new smtpd[28996]: NOQUEUE: reject: RCPT from
> s0.eburgsquare.com[104.223.145.19]: 554 5.7.1 Service unavailable;
> Unverified Client host [s0.eburgsquare.com] blocked using
> dbl.spamhaus.org;
> https://www.spamhaus.org/query/domain/eburgsquare.com;
> from= to=<[elided]@milhollan.com>
> proto=ESMTP helo=
>   Jul 13 21:59:33 mm-new smtpd[20435]: NOQUEUE: reject: RCPT from
> liaoningosaurus.mktdns.com[192.28.148.54]: 554 5.7.1 Service
> unavailable; Client host [192.28.148.54] blocked using
> sbl-xbl.spamhaus.org;
> from=<733-ksk-625.0.175526.0.0.16914.9.10824...@email1.digium.com>
> to=<[elided]@milhollan.com> proto=ESMTP helo=
>   Jul 14 00:13:04 mm-new smtpd[22318]: NOQUEUE: reject: RCPT from
> mail-ej1-f68.google.com[209.85.218.68]: 554 5.7.1 Service unavailable;
> Client host [209.85.218.68] blocked using sbl-xbl.spamhaus.org;
> from=
> to=<[elided]@milhollan.com> proto=ESMTP helo=
>   Jul 14 15:25:30 mm-new smtpd[3627]: NOQUEUE: reject: RCPT from
> gk-w94-email.usps.gov[56.0.84.94]: 554 5.7.1 Service unavailable;
> Client host [56.0.84.94] blocked using sbl-xbl.spamhaus.org;
> from=
> to=<[elided]@milhollan.com> proto=ESMTP helo=
>   Jul 14 22:37:33 mm-new smtpd[10015]: NOQUEUE: reject: RCPT from
> my-mail.splashtop.com[34.208.80.28]: 554 5.7.1 Service unavailable;
> Client host [34.208.80.28] blocked using sbl-xbl.spamhaus.org;
> from= to=<[elided]@milhollan.com>
> proto=ESMTP helo=
>   Jul 15 06:17:18 mm-new smtpd[14530]: NOQUEUE: reject: RCPT from
> mta0.tedlarbagsale.com[134.73.145.18]: 554 5.7.1 Service unavailable;
> Unverified Client host [mta0.tedlarbagsale.com] blocked using
> dbl.spamhaus.org;
> https://www.spamhaus.org/query/domain/tedlarbagsale.com;
> from= to=<[elided]@milhollan.com>
> proto=ESMTP helo=
>   Jul 15 10:00:11 mm-new smtpd[3294]: NOQUEUE: reject: RCPT from
> mx.mailop.org[91.132.147.157]: 554 5.7.1 Service unavailable; Client
> host [91.132.147.157] blocked using sbl-xbl.spamhaus.org;
> from= to=<[elided]@milhollan.com>
> proto=ESMTP helo=
>
> Both DBL rejections look to be spam.  But all but 1 of these SBL-XBL
> rejections were non-spam (I know those senders and want their
> messages) so for me are false-positives -- the Gmail rejection looks
> like spam (I don't know that sender).  16 rejections (9 good
> rejections not shown) between Jul 10 00:00Z and Jul 15 10:20Z, 4 of
> which were not appropriate makes for a not good ratio.
>
> Manually checking the SBL-XBL rejections on the mail server shortly
> after the last rejection yielded null/NXDOMAIN responses via DNS using
> getent/dig and showed "no issues" via the Spamhaus web site reputation
> center.  I use my own local resolver (unbound 1.13.1) with no
> forwarders configured.
>
>
> /mark
> ___
> 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 PBL question

[Matthew Stith via mailop]

Replied off list.

On 4/22/2021 1:41 PM, Liam Fisher via mailop wrote:
> I'm setting up some outbound relays in a new DC on new (to me) IP space.
>
> The subnet I am using is on the Spamhaus PBL, which is causing problems.
>
> I'm trying to get these delisted but Spamhaus isn't replying to the forms.
>
> Anyone have any current contacts or if anyone here can help and reply 
> privately?
>
>
> ___
> 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] Spamhaus Public Mirror Error Return Code Update

[Matthew Stith via mailop]

MailOP Folks,

Wanted to get this out to you all for awareness for anyone who is using
the Spamhaus public mirrors to query our DNSBLs. Beginning in March
Spamhaus will start enforcing the follow error return codes for these
news codes announced in 2019:

127.255.255.252 - Typing error in DNSBL Name
127.255.255.254 - Query via public/open resolver/generic unattributable rDNS
127.255.255.255 - Excessive Number of Queries

The main thing to take away from this announcement is that these codes
are meant to be treated as errors and not an indicator of negative
reputation. The plugins that we have developed for Spamassassin and
Rspamd already properly parse out these errors. You can read more about
the change here:

https://www.spamhaus.org/news/article/807/using-our-public-mirrors-check-your-return-codes-now

Thanks,
Stith

___
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop

[mailop] Spamhaus phishing campaign

[Matthew Stith via mailop]

All,

A SBL notification phishing campaign has been reported to us. Just
wanted to FYI the list so they could keep an eye on mail flows to make
sure no one gets owned by a bogus phishing message. Obvious phishing
rules apply here with the message and they aren't even trying to spoof
spamhaus.org. Looks like it is a download to a .zip which has VBS file
in it. Here is an example:

From:
Date : 31 January 2020 00:12
To:
Objet : URGENT ATTENTION - SBL #FUGTQ52ON
 
SBL Information: Email: Your Email address found in Spamhaus Blacklist (SBL)

SBL#84445 - The Spamhaus Project - SBL International Anti-Spam Systems

Good afternoon,
It is an automatic letter sourced from Spamhaus Block List (SBL)
instance to inform you that this Email just below has actually been
included in sbl.spamhaus.org:
Issue: phishing spam supplier
SBL Ref: SBL97962
Our servers have discovered emailing of a variety of spam letters off of
your own email address. Consequently, we have been forced to suspend
your e-mail.
It's very important to fix the issue within 48 hours. You should do a
couple of actions to do it. We're going to attach the guide:
GET THE INSTRUCTION: https:XXX//drive.google.com/[Redacted]
PASSWORD: S9823
In case you pay no attention to this letter, we'll suppose that this
email doesn't belong to you and it's programmed to perform junk
mailings. This simply means, that we'll be forced to add your e-mail
address to our stop list.
This means that recipients will not be able to accept emails from this
address ; your email tend to be blocked forever.
SBL System Robot
The Spamhaus Project
https://www.spamhaus.org

Thanks,
Matt Stith



___
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop

Re: [mailop] No response on DNS queries to NS for zen.spamhaus.org

[Matthew Stith via mailop]

Kevin,

Thanks for the response and concerns here.

We've opened up a Bugzilla ticket here
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7757 regarding the
return codes and it looks like it has been accepted.

The DQS plugin is distributed as an external commercial plugin for
SpamAssassin
https://cwiki.apache.org/confluence/display/spamassassin/CustomPlugins
but we do offer this also in free access method for those users impacted
by ranges that we have been forced to block from the public mirrors due
to abuse.

Also to reiterate the information from Simon's post, ranges that have
been blocked by the public mirrors will receive an NXDOMAIN return
rather than the return codes to prevent any issues with out of
date/improperly developed software.

Please hit me up off-list if you'd like any additional clarification or
have other concerns and we can work together on it.

Regards,

Stith

On 10/30/2019 10:58 AM, Kevin A. McGrail via mailop wrote:
>
> Definitely confusing so ignore any previous responses I sent :-)
>
> Speaking for the Apache SpamAssassin project, I want to make sure this
> is compliant with our free for some RBL inclusion policy [1] at
> SpamAssassin but I think the 3 follow-up emails clarified it DOES work
> out of the box for low volume without a key.
>
> I would also suggest you look at the URIBL_BLOCKED rule and returning
> a quad that allows an administrator to know why they are blocked.  We
> can add a rule for that.  Can you make a suggested rule and email to
> the SA Dev list or put in a bugzilla request, Please?
>
> [1] See
> https://cwiki.apache.org/confluence/display/spamassassin/DnsBlocklistsInclusionPolicy
>
> Regards,
>
> KAM
>
> On 10/30/2019 10:20 AM, Simon via mailop wrote:
>>
>>> On 30 Oct 2019, at 12:01, Heiko Schlittermann via mailop
>>> mailto:mailop@mailop.org>> wrote:
>>>
>>> Still it is not clear, if Spamhaus doesn't answer, or of there is some
>>> device in between.
>>
>> Worth a separate post as we see the potential for confusion here.
>>
>> On 30th September, in a Spamhaus posted blog:
>>
>> "A new range containing return codes (127.255.255.0/24) has been
>> added to return possible errors related to the DNSBL queries
>> themselves, which should NOT be interpreted as any sort of reputation
>> related to the data being queried. While it will be quite uncommon
>> for most Spamhaus users to encounter these codes, it is vitally
>> important that software developers implement all return codes
>> correctly, and NOT treat these error codes as any sort of reputation
>> or "listed" values. The first two new error codes, and links to pages
>> further explaining their meaning, are:
>>
>>
>> Return CodeZoneDescription
>> 127.255.255.254AnyQuery via public/open resolver
>> 127.255.255.255AnyExcessive number of queries"
>>
>> Full article at
>> .
>>
>> However, it is unlikely that these return codes will be used in anger
>> for quite some time as the internet moves very slly at times.
>> Especially when updating software and baked in practices are concerned.
>>
>> Simon
>>
>> ___
>> mailop mailing list
>> mailop@mailop.org
>> https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
>
> ___
> mailop mailing list
> mailop@mailop.org
> https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
___
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop

Re: [mailop] No response on DNS queries to NS for zen.spamhaus.org

[Matthew Stith via mailop]

All and Heiko,

There are some cases where Spamhaus is forced to block queries from
certain ranges due to abuse or commercial usage on our public servers.
We realize that this can cause some collateral damage to individuals who
may be attempting to access the public mirrors from those ranges. To
remediate this problem we offer our data query service (DQS) for free to
non-commercial and low volume usage. This service is accessed via a
unique key so access isn't tied to an IP address. The access to DQS is
gated behind a signup located at https://www.spamhaustech.com/dqs/.

Here is installation documentation for SpamAssassin
(https://github.com/spamhaus/spamassassin-dqs) and Rspamd
(https://github.com/spamhaus/rspamd-dqs)

Also please reference
https://www.spamhaus.org/news/article/788/spamhaus-dnsbl-return-codes-technical-update
about the changes recently made to our public mirrors regarding usage.

@Heiko I believe that you have been contacted directly by Spamhaus
Technology about your inquiry.

Regards,

~Stith

On 10/30/2019 8:42 AM, Heiko Schlittermann via mailop wrote:
> Bjoern Franke via mailop  (Mi 30 Okt 2019 13:20:15 CET):
>> As a.gns.spamhaus.org has some IPv6 addresses, is resolving via IPv6
>> blocked from the whole 64-prefix of the vserver, too?
> No, it isn't (I thought, that mentioned it already, the the issue
> is isolated to IPv4.)
>
> Though, I didn't test the whole ::/64 they assigned to my vServer as
> source addresses.
>
> Best regards from Dresden/Germany
> Viele Grüße aus Dresden
> Heiko Schlittermann
> --
>  SCHLITTERMANN.de  internet & unix support -
>  Heiko Schlittermann, Dipl.-Ing. (TU) - {fon,fax}: +49.351.802998{1,3} -
>  gnupg encrypted messages are welcome --- key ID: F69376CE -
>  ! key id 7CBF764A and 972EAC9F are revoked since 2015-01  -
>
> ___
> mailop mailing list
> mailop@mailop.org
> https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
___
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop