vBouncer: reduce server load by unsubscribing bouncing members from threads

vBouncer is a handy tool for busy forums (or those that do not require email verification) to control the amounts of bogus emails sent from and to your server.

What vBouncer does: vBouncer monitors your mail spool file, and identifies members responsible for large amounts of bounced emails. It then issues a PM warning, and when the unsubscribe threshold is met, it will will unsubscribe them for all threads, and sets them to the "no email" subscription level.

After a couple of runs, this should significantly reduce your server load.

Features:
o Manual or auto processing option
o Collect logs via IMAP/POP or mail spool file
o Custom filters to match patterns in bounced emails
o Uses vB's cron files (Scheduled tasks)
o Uses encrypted header for authentication (suggested by Paul M).
o Stats on members with bouncing emails, and error codes
o Tuning options
o Verbose cron logs for diagnostics
o Option to send PM warning prior to reaching the limit
o Option to send PM notifications after reaching the limit
o Option to change the member's subscription default
o Option to all thread subscriptions to "no email"
o Option to all forum subscriptions to "no email"
o Option to move offenders to a different primary usergroup
o Option to process 5.0.0/550 errors (email unknown) upon a single email, isntead of observing the bounce limit

Installation:
1. Extract the files into the corresponding directories (admincp => admincp, includes => includes)
2. Run the installation script in the admincp
3. Fill out the settings menu in the vBouncer section of the admin panel (see the how-to post below)
4. Import and activate the plugin file through the plugin manager.
5. Once ready, add the cron scripts to your scheduled tasks: vbouncer-collect.php (should be run daily, or more frequently) and vbouncer-clean.php (weekly, equal to Bounce limit period)
6. If you are using vB's SMTP email option, make sure to also enable the "-f" option.

Change log:

- August 12, 2005 v1.3 Update to the cron files to match new changes in vB's cron/tasks. To upgrade, just re-upload the contents of includes/cron.

- July 11, 2005 v1.2 Bug fix for some server/PHP setups; resolve aliases for return keys, otherwise some aliases would be considered forged.

- July 5, 2005 v1.1 Bug fix in standard report pattern matching

- July 4, 2005 v1.0 Added encrypted header for authentication (suggested by Paul M).

- July 3, 2005 v0.9.1 fixed a bug preventing IMAP/POP log collection.

- July 2, 2005 v0.9 added IMAP/POP option and custom filters file vbouncer.ini

- June 27, 2005 v0.5 Added custom header setting option, for re-written headers.

- June 26, 2005 v0.4 Found a way to make it work as a plugin, without code edits (thanks to Paul M)

- June 26, 2005 v0.3 No changes, just removed the plugin

- June 25, 2005 v0.2 Added NDR/Reply code errors to stats, and option to act upon 5.0.0/550 (user unknown)

- June 21, 2005: v 0.1 Initial release. Marked beta, but it's working fine on PostFix and SendMail. Need to hear from those who tried on QMail and Exim

[tamarian]

Antiblank, if no bounced emails are found, the stats will be blank. That's normal. If you're asking why there are no bounced emails, you need to check the diagnostics and error messages, and provide some details.

[Antiblank]

Well as I stated I intentionally created a bad email address for a test user. Then triggered some emails to be sent to it. The email isn't found so a the message ends back up in my return-path mailbox. Vbouncer connects, attempts the collection, processes the one email it found. But says no bounced emails. Then deletes the email from the box.

Forgive me if I'm wrong but wouldn't this constitue as an email that vBouncer should be triggered off of.

As for my diagnostics:

vBouncer sender email
Test Result
Valid vBouncer email account (subscriber_notify@********.com) Passed
vBouncer email account (subscriber_notify@********.com) differs from webmaster account Passed

vBouncer Spool File Diagnostics (ignore if using IMAP/POP)
Test Result
vBouncer email spool file () exists Failed
vBouncer email spool file () is writable Failed
vBouncer email spool file () is readable Failed

vBouncer pattern config file diagnostics
Test Result
vbouncer.inc file exists Passed
vbouncer.inc file is readable Passed

vBouncer IMAP/POP Diagnostics (ignore if not using IMAP/POP)
Test Result
Your PHP installation supports IMAP/POP Passed
Your IMAP/POP settings can connect Passed

As for my Cron Logs for example:

vBouncer Collect 04:02, 27th Jul 2006 Status:
Processed 2 emails No bounced emails found.

I am using IMAP and the connection, reading and deleting of the emails is functioning. There is absoulty no reason any email should be entering this box outside of the return-path function added to the emails since I installed vBouncer.

Anything else you need to see? Thanks.

[Scott MacVicar]

Just to inform you that this hack is producing invalid Mail headers.

$headers = preg_replace('/Return-Path.*/', 'Return-Path: ' . $vbulletin->options['vbouncer_spool_account'], $headers, 1);

That will match up to the \r and replace it, the end result is that the header has \n instead of \r\n.

If you could fix this it would be awesome, if you can't or aren't around any more i'll speak to Marco about manually updating your hack for you.

This affects Qmail installs and potentially the SMTP mail sender.

Quick Fix, i think but haven't tested is adding $

$headers = preg_replace('/Return-Path.*$/', 'Return-Path: ' . $vbulletin->options['vbouncer_spool_account'], $headers, 1);

[ChrisBaktis]

Is this still being supported because I cannot get this to work for the life of me.

[cerebro]

some1 try in Vb 3.6.0 final??

[dinodonk]

anyone have try on 3.6.0???

[alfaowner]

my IMAP settings fails, although I can login through y mail client okay?, however, it is showing installed within cpanel, I have rebuilt PHP and but still nothing?

Ideas anyone?

Your PHP installation supports IMAP/POP Passed
Your IMAP/POP settings can connect Failed

[alfaowner]

dont worry, i fixed it, i had left off a { when I copied the 143inbox etc...

[Eagle Creek]

Do we have a 3.6.0 ?

[kontrabass]

Originally Posted by TraumTeam
A short help from me for users with the problems of imap/pop access:

I the access does not work and all settings are correct try:
{127.0.0.1:110/pop3/notls}INBOX

There could be a certificate failure with the internal IMAP Access on the server.

Perhaps its interesting for the FAQ ...

Rob

Wow thanks for this bit of info. Using an externail mailserver - this info saved me after many failed attempts