- Add difficulty ratings (EASY/MODERATE/HARD) to each blacklist entry
- Show estimated delisting time for each listed blacklist
- Display removal URL directly next to each listed blacklist
- Improve summary with difficulty breakdown
- Add references to other diagnostic tools (email-diagnostics, history)
- Better guidance on delisting process based on difficulty level
Database format: rbl_host|name|removal_url|difficulty|time_estimate
New features help users prioritize delisting efforts:
- EASY listings can typically be removed same day
- MODERATE listings require 1-3 days, formal request process
- HARD listings may need 3-7+ days, complex procedures
Users now see actionable removal URLs directly in the output,
reducing need to search for delisting information.
Integration with email-diagnostics ecosystem for comprehensive
email troubleshooting workflow.
Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
- Records blacklist incidents in ~/.email-diagnostics-history.json
- Timestamps each incident with UTC timestamp
- Tracks which blacklists have blocked the server over time
- Initializes history database on first blacklist detection
- Provides statistics summary of historical trends
History Database Features:
- File location: ~/.email-diagnostics-history.json
- Persists across multiple diagnostics runs
- Identifies repeatedly problematic blacklists
- Helps detect systemic listing patterns
- Can be inspected with: cat ~/.email-diagnostics-history.json
Information Tracked:
- Server IP address
- Blacklist incident events
- Timestamp of each detection
- Event metadata for analysis
Benefits:
- Users can identify which blacklists persistently block them
- Helps determine if server has ongoing vs. one-time issues
- Provides historical context for troubleshooting
- Shows patterns that indicate systemic problems
Display shows:
- Total recorded incidents
- Unique blacklists detected historically
- Location of history file
- Instructions for viewing detailed history
Future enhancement can expand to:
- Resolution time tracking
- More detailed JSON structure with jq
- Automatic cleanup of old entries
- Statistics aggregation and reporting
Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
- Performs DNS queries to check current listing status on RBLs
- Reverses server IP octets for proper RBL query format
- Uses dig with 3-second timeout for responsive checking
- Only checks traditional RBLs (Spamhaus, Barracuda, SpamCop, SORBS, CBL)
- Skips email provider checks (not queryable via DNS RBL)
- Shows LISTED/CLEAN status with response codes for detailed info
- Verifies if delisting was successful or if IP still blocked
- Gracefully handles timeouts and DNS failures
Response codes indicate:
- 127.0.0.2: SBL (Spamhaus blocklist)
- 127.0.0.3: CSS (Spamhaus CSS)
- 127.0.0.10: PBL (Policy Blocklist)
- Other codes: Varies by RBL provider
Feature validates:
1. If IP extraction succeeded from rejection messages
2. Checks current status on active traditional RBLs
3. Provides clear indication of listing status
4. Suggests next steps based on results
Users can now verify if their IP is CURRENTLY listed on each RBL,
allowing them to confirm delisting success or identify remaining issues.
Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
- Provides copy-paste ready email templates for each blacklist operator
- Customized templates for major providers: Spamhaus, Microsoft, Gmail, Apple,
Barracuda, Yahoo, and generic template for other RBLs
- Templates include proper subject lines, server details, remediation steps
- Placeholders for server IP, hostname, admin name, and email
- Instructions for users to copy, customize, and submit requests
- Reduces friction in delisting process by providing professional templates
Each template covers:
1. Professional subject line appropriate for each provider
2. Server identification (IP, hostname)
3. Explanation of remediation actions taken
4. Reference to security/authentication measures
5. Clear call to action for delisting
Users can now quickly generate customized delisting requests without
needing to research what to include in each email.
Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
- Extended blacklist database entries with difficulty level (EASY/MODERATE/HARD)
- Added estimated time to delist for each blacklist (e.g., "Same day", "1-7 days")
- Updated detection logic to extract and pass difficulty/time metadata
- Display difficulty ratings in output alongside blacklist name
- Format: "• Spamhaus (ZEN/SBL/XBL) [HARD - 1-7 days]"
Ratings help users understand which blacklists are quick to resolve vs. long-term issues:
- EASY (Same day): Usually automatic or simple form submission
- MODERATE (1-3 days): Requires manual request but responsive organizations
- HARD (3-7+ days): Complex processes or slower response times
All 25 blacklist entries updated with appropriate difficulty levels based on
typical delisting timelines from industry documentation.
Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
- Exclude lines with 'saved mail to' (successful deliveries)
- Exclude lines with '=>' (delivery confirmations)
- Only show actual bounce/failure messages
- Updated both counting and display sections
This fixes the bounce section showing 'saved mail to INBOX'
which are actually successful deliveries, not bounces.
Improved accuracy:
- Bounces now only count actual SMTP delivery failures (550-554 codes)
- Excludes SMTP/IMAP/FTP authentication failures from bounce count
- Spam rejected now only counts actually rejected emails
- Excludes emails delivered to spam folder (those are successful deliveries)
- Updated display sections to match new filtering logic
This fixes the misleading "334 bounced" count that was actually
showing authentication failures, not email delivery problems.
The script now searches:
- /var/log/exim_mainlog (Exim delivery logs)
- /var/log/maillog (Dovecot auth + delivery)
- /var/log/messages (fallback)
This fixes the issue where only auth logs were found but actual
email deliveries were missed because they were in different log files.
Now properly separates delivery events from authentication events
across all log sources.
Key improvements:
- Add Quick Summary section at top for instant status
- Always show main metrics (sent/received/delivered) even if 0
- Fix contradictory "account not found" when successful logins exist
- Better verdict logic for authentication-only scenarios
- Clearer section headers ("Mailbox Access Activity" vs delivery)
- Group problems together, only show if they exist
- Improve status messages with context
Output now shows:
1. Quick Summary - instant understanding of status
2. Email Delivery Activity - always show main counts
3. Problems section - only if issues detected
4. Mailbox Access Activity - clarify IMAP/POP3 vs email delivery
5. Account Status - use successful logins as proof account exists
6. Better verdicts for auth-only, no-activity scenarios
Features:
- Check specific email address or entire domain
- Shows if emails are working with PROOF
- Displays recent activity with timestamps highlighted
- Categorizes: delivered, bounced, rejected, deferred
- Shows last 5 examples of each type from selected time period
- Clear verdict: Working / Partially Working / Has Problems
- Extracts bounce reasons and recommendations
- Saves full report for customer evidence
Usage: Email menu → Option 1 (Email Diagnostics)
Perfect for: 'Customer says they're not receiving emails'
Example output:
✅ EMAIL IS WORKING PROPERLY
Evidence: 15 successful deliveries in last 24 hours
PROOF - Recent deliveries with timestamps shown below
cschantz