Trying to sign up individual IPs or ranges in the SNDS can be tricky. In
addition to the two errors you ran into, you can also get:
- Range too big for sufficient accuracy in detection of hostname similarity
We have found that the easiest way to sign up IPs is via an ASN.
If you don't have you
We have similar issues with Trend Micro.
None of our IPs are dynamic, but from time to time we get reports from
our clients that their IPs are listed on Trend Micro's DUL.
The lookup form, and linked removal form, work well for us:
https://servicecentral.trendmicro.com/en-us/ers/ip-lookup/
I'
For what it's worth, I requested an authorization email on Wednesday,
and it just arrived now (more than 50 hours later).
Regards
Bastiaan
Am 07.06.2024 um 04:46 schrieb Scott Mutter via mailop:
Yea, the authorization emails aren't coming through. I don't know if they
aren't being sent or if
Hear, hear!
SORBS is (was?) one of the best DNS-based blacklists, because they
provided reports with information on the listings.
Thank you Michelle, and all the best for your future endeavors.
Regards
Bastiaan
Am 05.06.2024 um 03:22 schrieb Michael Wise via mailop:
What He Said.
The data
Am 12.12.2023 um 07:37 schrieb Kirill Miazine via mailop:
But we're getting off-topic, my initial post triggered by discovery of
the "new" dnsbl.spam.fail list, which I never had experienced earlier,
and that question has been answered.
For the record, I reached out to Domeneshop yesterday.
O
I am referring to the fact that the wording of the autoreply suggests
that Hetzner is simply passing complaints verbatim to the spammers
themselves and not dealing with it yourselves.
If we were passing them on verbatim we wouldn’t have to manually process
them. The whole point is not to simply
> 20 days (!) later I received a reply [AbuseID:BEA948:23]:
That’s too long of a delay, I agree.
We’re currently in the middle of a restructuring in our abuse
department, where a number of processes are also being updated.
For example, we’re no longer immediately referring to our abuse form
wh
That error message means your IP has a poor email reputation on Cisco Talos:
https://talosintelligence.com/reputation_center/
Regards
Bastiaan
Am 28.06.2022 um 12:09 schrieb Sidsel Jensen via mailop:
Hi
I'm trying to locate a contact to mx1.hc1932.iphmx.com - does anybody know who to reach o
Am 11.01.2022 um 20:04 schrieb Mark G Thomas via mailop:
I'm not generally involved in our support issues, but a coworker at
my work (Linode) reached out to me about what looks to be a new problem
involving hosting customers being blocked by by Microsoft.
It's nice to see another representative o
Am 06.12.2021 um 22:03 schrieb Jarland Donnell via mailop:
A worthwhile note is that, at least in my experience, the messaging
there can be a bit misleading. I've removed my old blog where I proved
it with logs, but what it basically amounted to was this: I have many
times received that exact e
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
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
Thank you Francisco, I'm seeing data for the past few days again.
Regards
Bastiaan
Am 27.07.2021 um 01:48 schrieb Francisco Gomez via mailop:
> Issue acknowledged. Working on rebuilding the data.
>
>
> Francisco Gomez
> Principal Program Manager
>
__
Same here.
Happens several times a year (often with an accompanying thread here on
mailop), and it's usually (automatically?) resolved within a few days.
As for the SNDS, Microsoft only shows data for IPs that sent at least
100 emails on the date you are looking at. Is it possible the IPs you
are
side. If you have any diagnostic
>> info you can share, e.g. session info on browser, OS, etc...
>>
>> E.g. One report indicates fails in Firefox, works in Chrome...
>>
>> Feel free to ping me direct: tom . bartel @ validity dot com
>>
>> On Wed, May 5
> Hi Bastiaan,
>
> working fine on my side, I can access universal fbl without any trouble.
>
> I hate to say that, but maybe clear cookies ? There's maybe corrupted
> ones, or having legacy infos ?
>
> On Tue, May 4, 2021 at 5:38 PM Hetzner Blacklist via mailop
> wrote
I want to add some new ranges to our FBL account, but the page at
fbl.validity.com has been down for over a week now with the message:
"This service is currently unavailable. Please refresh the page or try
again later."
There was a post on here two weeks ago regarding senderscore, and that
was li
UCEPROTECT just recently changed their listing criteria for level 3
listings (blacklisting an entire ASN).
Direct source: http://www.uceprotect.net/en/index.php?m=12&s=0
What they don't make clear (for whatever reason) is the actual change.
Previously if 0.2% of a provider's IPs were blacklisted,
They switched over to 0spam.org a few years ago, but kept
0spam.fusionzero.com as a mirror.
Interestingly those mirrors are still online, but 0spam.org has been
offline since September 30th, and is still offline.
Maybe they're switching back to fusionzero.com?
It's just surprising the website is
Just a quick heads-up: the 0spam blacklist is down.
The website (0spam.org) can't be reached, and the domain appears to be
for sale.
Queries to bl.0spam.org are currently failing. At least that's better
than listing the world, but that might still happen in the future, as
with other blacklists th
As far as I know this isn't a bug, it's a feature.
For the past few years, T-Online have been moving to a system where they
block all unknown IPs. How exactly they define that is not 100% clear,
but it seems to be any IPs that haven't recently sent them email.
So if an IP hasn't sent them email i
Just a quick heads-up: Webiron appears to be having issues. Their
website is down, and their blacklists (combined in all.rbl.webiron.net)
are listing the world.
Their live feed bot stopped tweeting around 3 weeks ago:
https://twitter.com/WebironBots
This has happened with other blacklists, and mi
It's working (again) for me.
I login to the SNDS every day, and these "hiccups" are an almost weekly
occurrence. Usually they get fixed within a few hours though.
By the way, if you have an IP that Microsoft is rejecting emails from,
you'll need to fill out their form to get it delisted/mitigated
I haven't quite figured out how Barracuda decides which IPs are ok for
delisting and which aren't. Sometimes you will get an immediate email
response saying the IP will be delisted, other times there is no email.
Even if there is no email though, sometimes the IP will actually get
delisted, but mos
Bad sign-ups, there's been an uptick of that in the past ~2 weeks.
We usually find and kick them out within a few hours, but if you see
anything showing up in your logs for more than 24 hours, you're very
welcome to contact me.
Am 22.10.2019 um 13:00 schrieb Michael Peddemors :
> Are these compr
My job involves (trying to) monitor the reputation of our ASN, so I have
some experience here.
I think it's important to start by noting that reputation isn't
something you can easily quantify. There is also no single authority
deciding (or showing) what the repuation of a provider is.
The real i
The official email address is investigat...@review.symantec.com, though
I just saw a forum post where a Symantec employee said
customerc...@symantec.com might work.
https://www.symantec.com/connect/ideas/investigationreviewsymanteccom-554-512-recipient-address-rejected-user-unknown
Hope that help
Am 01.08.2019 um 20:52 schrieb "Bill Cole"
:
> I'm trying to set up FBLs for a /21 allocated by RIPE to my employer...
The easiest way to add IPs to the SNDS is using the AS number. This
might add some ranges you don't want, but it's much easier to simply
remove them after you have access, then i
Hi Al,
I just tried adding a /16 that we bought a while ago but aren't using
yet. There were no issues adding it to the SNDS.
Having said that, I've often had issues in the past adding ranges. Most
of the time simply waiting and trying again a few hours or days later
worked.
Make sure the WHOIS
Thank you for your responses everyone.
When I checked the SNDS this morning I was very surprised to discover
that Microsoft has delisted almost all IPs from 5.9.0.0/16. So 7 days
after the entire range was blacklisted, it has just as suddenly been
delisted.
I have no idea what caused this. If som
it is rhetoric from
> politicians around the globe, or those involved in the infosec
> community, I expect to see a lot more cases where the idea's of openness
> on the internet, becomes more about putting up 'walls' first..
>
> -- Michael --
>
> PS.. hehehe..
Hello Mailop,
For the past two years things have been going really well for us in
regards to the Microsoft blacklist. We've had very few issues, probably
because we aggressively check the SNDS and block/terminate IPs/clients
that send spam to Microsoft. Now, all of a sudden and without warning,
Mi
32 matches
Mail list logo
