It appears that Michael Peddemors via mailop said:
>See item one.
>
>> - Submits a JSON report to XYZ provider (https://blocklist.api.provider.com)
See RFC 5965, published 11 years ago.
Spamhaus has extensive facilities for ISPs that want to know what their users
are up to.
If you're not an IS
Aye. We use Debouncer for our notifications. HetrixTools has also proven
quite useful. Monitoring blacklists for a large number of IPs can scale
into a bit heavier of a task than some might assume up front.
But on that note, I worked for a very large cloud provider for a few
years. Really quit
Hi Mary,
On Fri, Nov 26, 2021 at 11:25:06AM +0200, Mary via mailop wrote:
> Would it be possible for the two sides (blocklists and a
> cloud/hosting providers) to come together and have some kind of
> automated notification?
As a tiny hosting provider we already receive notifications from
SpamCop
Cloudways most likely has their SMTP block disabled by default.
Cloudways deploys managed Wordpress VPS on various cloud providers,
Linode being one. Of course, their managed isn't like a fully shared
managed platform where everything is tightly controlled, so Wordpress
compromises are just as
Is "hey bad ISP please come here and defend yourself against my accusation"
really on topic for this mailing list?
Isn't there some other list like SPAM-L or something that might be more
suited to that type of conversation?
On Fri, Nov 26, 2021 at 1:05 PM Michael Peddemors via mailop <
mailop@mail
I didn't call Linode 'Bad'... please don't assume.. Actually I don't
consider them bad at all.. it was others on the list that were complaining..
Continuing on an earlier thread on this topic, where it was reported
that Linode blocks port 25 by default for all new accounts.
I am just seeing i
Maybe someone from Linode can comment on this..
Here is a typical spam outbreak from Linode..
Usually these are trapped/tagged because the default PTR is still in
place, so doesn't cause enough problems to report, but they do happen
occasionally in spurts.
Since several times it has been men
On 2021-11-26 11:25:06, Mary via mailop wrote:
>
> Thinking out loud...
>
> Would it be possible for the two sides (blocklists and a
> cloud/hosting providers) to come together and have some kind of
> automated notification?
The blocklists already provide a convenient API to the providers: if
yo
On 2021-11-26 1:25 a.m., Mary via mailop wrote:
Thinking out loud...
Yes Mary.. in a perfect world.. but..
Would it be possible for the two sides (blocklists and a cloud/hosting
providers) to come together and have some kind of automated notification?
Sample automated conversation via JSO
On 2021-11-26 2:24 a.m., Hetzner Blacklist via mailop wrote:
I manually check those lists every other day, and then use our abuse
system to send notifications to the respective clients. Hosters who have
implemented the API can do so automatically.
The obvious question, given that you manually
Am 26.11.2021 um 10:25 schrieb Mary via mailop:
Thinking out loud...
Would it be possible for the two sides (blocklists and a cloud/hosting
providers) to come together and have some kind of automated notification?
It is possible and it already works that way for a handful of blacklists.
Sinc
Dnia 26.11.2021 o godz. 09:23:08 Hans-Martin Mosner via mailop pisze:
> "Unlike" refers to "blocks port 25 by default" in the line above,
> not to assigning /64s to customers. And yes, blocking outgoing port
> 25 would make a bit of a difference.
From a customer point of view (contrary to hosting
Hi,
Raymond Dijkxhoorn wrote on 26.11.21 at 10:57:
I saw that. I resolved it locally and posted just here to give both
Microsoft and Manitu/NixSpam a heads up.
The list might not be used insain widely, i dont know, but decided to
post so they can resolve it. I am not going to request seperat
Hi Florian,
Raymond Dijkxhoorn via mailop wrote on 26.11.21 at 09:53:
(Also sended to them directly but hopeing someone can ping them)
rejected because 40.107.8.138 is listed at ix.dnsbl.manitu.net
never tried myself, but on https://www.nixspam.net there's a form to ask for
unblocking. Not
> Would it be possible for the two sides (blocklists and a cloud/hosting
> providers) to come together and have some kind of automated notification?
Objection, requires an interest in collaboration from hosting providers.
--
Atro Tossavainen, Chairman of the Board
Infinite Mho Oy, Helsinki, Fin
Hello,
Raymond Dijkxhoorn via mailop wrote on 26.11.21 at 09:53:
(Also sended to them directly but hopeing someone can ping them)
rejected because 40.107.8.138 is listed at ix.dnsbl.manitu.net
never tried myself, but on https://www.nixspam.net there's a form to ask
for unblocking. Not sure
Am 26.11.21 um 10:25 schrieb Mary via mailop:
Thinking out loud...
Would it be possible for the two sides (blocklists and a cloud/hosting
providers) to come together and have some kind of automated notification?
Possible - yes of course.
Doable as in both sides cooperating - when OVH, Digita
Thinking out loud...
Would it be possible for the two sides (blocklists and a cloud/hosting
providers) to come together and have some kind of automated notification?
Sample automated conversation via JSON API:
- The blocklist adds a block for X net block
- Resolves the owner of the net block (
Am Freitag, dem 26.11.2021 um 09:23 +0100 schrieb Hans-Martin Mosner
via mailop:
> Am 26.11.21 um 09:04 schrieb Bastian Blank via mailop:
> > On Fri, Nov 26, 2021 at 09:34:44AM +0200, Mary via mailop wrote:
> > > Unlike other providers like OVH and hetzner...
> > Hetzner does not assign less then a
Hi!
(Also sended to them directly but hopeing someone can ping them)
rejected because 40.107.8.138 is listed at ix.dnsbl.manitu.net
138.8.107.40.in-addr.arpa domain name pointer
mail-eopbgr80138.outbound.protection.outlook.com.
Not sure if this is intended but this 'might' give much colleter
Correct, we automatically assign a /64 per server, and we've done that
since the beginning of our IPv6 support (2011 if memory serves me
correctly). A /56 is possible via a support request.
We also block port 25 by default for new cloud clients, though we've
only been doing that since April of
Am 26.11.2021 um 08:34 schrieb Mary via mailop:
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...
Hetzner Cloud has Port 25 blocked by default, you need to send a request
to
Am 26.11.21 um 09:04 schrieb Bastian Blank via mailop:
On Fri, Nov 26, 2021 at 09:34:44AM +0200, Mary via mailop wrote:
Unlike other providers like OVH and hetzner...
Hetzner does not assign less then a /64 in all their current products.
Bastian
"Unlike" refers to "blocks port 25 by default"
On Fri, Nov 26, 2021 at 09:34:44AM +0200, Mary via mailop wrote:
> Unlike other providers like OVH and hetzner...
Hetzner does not assign less then a /64 in all their current products.
Bastian
--
There is an order of things in this universe.
-- Apollo, "Who Mourns for Adonais?"
24 matches
Mail list logo
