About

The Abuse package retrieves abuse reports via IMAP from an email account and distributes the reports to the appropriate server tenants based on server IP. It adds a frontend to SynergyCP that allows Clients and Administrators to see and comment on reports.

Setting up

1. Go into the SynergyCP application and modify the Settings for Abuse to reflect the authentication details for the email account receiving abuse reports.
2. Your abuse reports will be automatically synced every 5 minutes. You can check on the status of existing abuse reports by visiting the Network > Abuse Reports page.

Changelog

v2.2.7

• Prevent null value crash when clearing archive folder setting in admin UI

v2.2.6

• Fix migration to use correct settings table column name (name)

v2.2.5

• Fix migration to detect settings table column name dynamically

v2.2.4

• Fix null archive folder setting crashing admin settings page (migration converts null to empty string)

v2.2.3

• Fix crash when archive folder setting is cleared (null value triggers Setting accessor TypeError)

v2.2.2

• Add archive folder setting label and auto-detect description to admin UI

v2.2.1

• Auto-detect archive folder: Gmail/Google Workspace uses [Gmail]/All Mail, others default to Archived, overridable via setting

v2.2.0

• Archive processed emails to configurable IMAP folder (default [Gmail]/All Mail) instead of relying on seen flags or date filtering
• New setting: pkg.abuse.auth.archive_folder

v2.1.10

• Skip already-processed emails by marking all as seen and fetching only unseen from IMAP

v2.1.9

• Handle duplicate report race conditions and deduplicate extracted IPs

v2.1.8

• Fix IpService pass-by-reference error in attachment IP extraction

v2.1.7

• Fix email sync to always look back full threshold period instead of narrowing to latest report date

v2.1.6

• Add detailed logging to abuse email sync (start/complete, email counts, IP extraction source, report creation, errors)

v2.1.5

• Extract source IP from XARF JSON and XML email attachments before scraping body

v2.1.4

• Add View Report button URL to suspension warning and suspended emails

v2.1.3

• Fix server ID in abuse emails to use srv_id field instead of database primary key

v2.1.2

• Add server ID (e.g. srv1023) alongside server nickname in suspension emails
• Update GitHub Actions (actions/checkout, actions/setup-node) from v4 to v5 for Node.js 24 compatibility

v2.1.1

• Fix negative days and excessive decimal places in suspension warning emails (Carbon 3 / Laravel 11 compatibility)

v2.1.0

• Update deprecated Laravel APIs for Laravel 11 compatibility

v2.0.0

• Initial Laravel 11 release