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

[GNDI]

that because there have been huge changes within vB since this add was released. But if you just remember to use your "fake" e-mail address when you post, it does work, and collect properly. and then move the users to the banned group

[DannyITR]

Originally Posted by GNDI

that because there have been huge changes within vB since this add was released. But if you just remember to use your "fake" e-mail address when you post, it does work, and collect properly. and then move the users to the banned group

I don't understand what you mean by fake email address.

[GNDI]

Have you read the info about this hack and understood have it works?

[DannyITR]

Yes I do but I don't recall anything requieing me to use a fake email address to post messages.

[ibeblunt]

I have vBulletin running on one server, and my mail server running on another. When I run the diagnostics test, I get PASSED for everything except 'Your IMAP/POP settings can connect.'

As of right now, under IMAP/POP Connection I have '{xxxx.com:110/pop3}INBOX', followed by my username and my password. I have attempted to use my IP Address, mail.xxxx.com and postal.xxxx.com. All of these do not pass the test.

Does anyone have any suggestions?

[GNDI]

use this:

{mail.server.TLD:143/notls}INBOX 

or 

{mail.server.TLD:110/notls}INBOX

that should do it :alien:

[GNDI]

any one who have fixed this hack?

[ibeblunt]

Thanks! That did the trick.

I have this set up and it appears to be working EXCEPT that it's not moving the users to the new usergroup that I set up for them.

[t3nt3tion]

Is this vb 3.6.x compatible ??

[ibeblunt]

Not sure if this will help solve my problem, but here is a screenshot of my settings...

*certain info blocked intentionally.