Weave Code
Collector Rbl Laravel Package
abuseio/collector-rbl
An AbuseIO collector that checks IPs against RBL/DNSBL blocklists and imports listings as abuse events, feeding them into the AbuseIO pipeline for ticketing and notification.
AbuseIO Collector for RBL lists
Frequently asked questions about Collector Rbl
- What does the abuseio/collector-rbl package do?
- It is an AbuseIO collector that queries RBL and DNSBL blocklists for the IP addresses you manage in AbuseIO and imports any listings it finds as abuse events. Those events then flow into the AbuseIO pipeline for ticketing, correlation and notification. In short, it turns DNS blocklist hits into actionable abuse records without manual lookups.
- How do I install abuseio/collector-rbl with Composer?
- Install it with composer require abuseio/collector-rbl from your AbuseIO application root. After that, register the collector in your AbuseIO configuration and publish or adjust its config file so it knows which blocklists to query. Because collector registration can vary between AbuseIO releases, follow the install steps in the repository README for your version.
- How do I configure which RBL/DNSBL lists the collector checks?
- Blocklists are defined in the collector's configuration file, usually as a list of DNS zones such as zen.spamhaus.org or bl.spamcop.net. Add or remove zones there, and the collector will query each one for the IPs it processes. Check each list's usage policy first, since some providers restrict queries from public or high-volume resolvers.
- Which Laravel versions does abuseio/collector-rbl support?
- Support follows the AbuseIO release you run, since AbuseIO is a Laravel application and the collector must match its framework and dependency versions. Check the require section of the package's composer.json and the AbuseIO version matrix before upgrading Laravel. If you are on an older AbuseIO branch, pin the collector version that matches it.
- How does the RBL collector create abuse events inside AbuseIO?
- For each IP it checks, the collector performs DNS lookups against the configured blocklists and, when a listing is returned, builds an abuse event with the source IP, the listing zone and related metadata. AbuseIO then applies its normal matching, ticketing and notification rules. This keeps RBL findings consistent with events from your other collectors.
- How can I test the RBL collector without querying live blocklists?
- Point the collector at a test DNS zone you control, or stub the DNS resolution layer in your test suite so lookups return deterministic answers. That lets you assert both the listed and not-listed paths without rate limits or policy violations. Run integration tests against live RBLs only sparingly.
- What DNS and production concerns should I watch for with RBL lookups?
- RBL lookups are DNS queries, so resolver reliability, timeouts and caching matter at scale. Use a local caching resolver, keep concurrency moderate, and make sure your resolver IPs are not blocked by the blocklist providers you query. Many lists also enforce query limits, so schedule checks sensibly and log failures rather than retrying aggressively.
- How do I schedule the RBL collector to run automatically?
- Register the collector's command or job in your AbuseIO scheduling configuration, typically via Laravel's scheduler or the AbuseIO cron setup, and run it as often as your blocklists allow. Stagger it against other collectors so DNS traffic stays reasonable. Run it manually the first time so you can inspect the events it produces.
- Can I use abuseio/collector-rbl outside of AbuseIO?
- It is built as an AbuseIO collector, so it depends on AbuseIO's collector contracts, configuration and event pipeline to do useful work. Using it standalone would mean writing your own glue code around its lookups. If you only need DNSBL checks, a small dedicated script is usually simpler.
- Is abuseio/collector-rbl maintained, and where do I report issues?
- It is an open source AbuseIO project hosted on GitHub, so activity follows the AbuseIO community's release cadence. Report bugs and feature requests through the repository's issue tracker, and check existing issues before assuming a behaviour is intentional. Pull requests with tests are the fastest way to get fixes merged.
Weaver
How can I help you explore Laravel packages today?