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

[DannyITR]

Originally Posted by tamarian

Check the statistics, to see if they were caught. Then check the cron times when the task will be run, or run it from the cron manager.

My stats are completely empty:

Total bounced emails currently logged
Top bouncer [] - -
Last run with results 19:00, 31st Dec 1969

hmm:

Your IMAP/POP settings can connect Failed


I just hooked it up in outlook and I was able to access it fine. I had 500 emails to download. Why wont vbouncer do this?

[DannyITR]

I'm sure the problem lies here:

Leave empty if your prefer using the file method below. This setting allows you to define an IMAP or POP connection for vBouncer to access the bounced emails account for processing. Here are a few examples, replace the domain name with your own:
For local IMAP: {localhost:143}INBOX
For local POP: {localhost:110/pop3}INBOX
For remote POP: {myisp.com:110/pop3}INBOX

I have this in my box but I have no idea if its correct.

{mail.montrealracing.com:110/pop3}INBOX

[dutchbb]

how do I uninstall this asap?

My members don't receive any mails at all now. I just want to get rid of it asap please :s

Why is there no uninstall option anyway?

[tamarian]

Originally Posted by DannyITR

I'm sure the problem lies here:

Leave empty if your prefer using the file method below. This setting allows you to define an IMAP or POP connection for vBouncer to access the bounced emails account for processing. Here are a few examples, replace the domain name with your own:
For local IMAP: {localhost:143}INBOX
For local POP: {localhost:110/pop3}INBOX
For remote POP: {myisp.com:110/pop3}INBOX

I have this in my box but I have no idea if its correct.

{mail.montrealracing.com:110/pop3}INBOX

Make sure it's the same settings as your POP account, correct login and password. Might want to try with the notls option as someone tried a few posts above.

[tamarian]

Originally Posted by Triple_T

how do I uninstall this asap?

My members don't receive any mails at all now. I just want to get rid of it asap please :s

Why is there no uninstall option anyway?

Run the install script, it has an uninstall option, and remove the plugin and cron tasks.

[DannyITR]

Originally Posted by tamarian

Make sure it's the same settings as your POP account, correct login and password. Might want to try with the notls option as someone tried a few posts above.

It is and I tried this as you suggested

{127.0.0.1:110/pop3/notls}INBOX


but the connect still fails.

[DannyITR]

anyone can help?

[tamarian]

Danny, you must use your email's connection information. 127.0 IP may not be the right one, if you say you use an external email server.

[DannyITR]

Hey looks like its working!

[DannyITR]

Apparently if I send a user a normal email using the admincp and it bounces then it is not caught by vbouncer. I was going to use it as a way of getting anyone with a faulty email to change it.