They are Exim filters for viruses.

Tamarian -- will get that set up for you tonight when the guys at my host finish with the kernel upgrade (that should have been done when it was configured :speechless: ).

If my results differ from Paul's, please note that I am running ClamAV, so we may need to document that.

If you use the POP/IMAP method, the Exim config edit is not required, since you will not need to access the spool file directly.

I'll write up any Exim hints and tips you guys give me, since you have the cPanel+Exim setup. :)

Sent you a PM with some setup thoughts.

Do have a question on this though -- what does it do with bounced emails from new registrations? We delete registrations whose emails bounce and I don't want those to be included in the same tracking/warning as the ones who are subscribing to threads.

Second question -- does this (or will it plan to) address those who have email notifications on PMs in that it will remove this flag from their profile? I would even go as far as to say that if their email is bad, I would like ALL subscriptions and email notifications to be disabled.

You can exclude usergroups from the settings menu under "Protected usergroups" (to prevent usergroup changes" Or under "Untouchable usergroups" to prevent any actions such unsubscribing or PM's.

But if they register with a wrong email, you'd only get 1 or two bounces. If your bounce limit is 25 or 50, they wouldn't be affected.

It's doable if you guys really want it.

But the main purpose for vBouncer is to prevent server spikes due to the volume of emails generated during busy hours for new replies and subsequent notifications of new replies. Reducing this volume through unsubscribing bouncing members is the main purpose.

An occasional email to notify about a PM doesn't have that impact on the server

Update on the MD5 idea to check for forged bounced emails:

So far it seems most bounced emails will return the full original headers. The only exception I've seen so far is AOL, and only in the case when the AOL member in question rejects emails from your forum (i.e they are blocking your email from getting into their mail box.

So currently my upcoming version does the following:

1. Adds a new setting to enter your MD5 encryption string. If you leave it empty, it will not send the new header, and will process bounced emails as authentic. So it acts like an enable/disable option.

2. If you enter an MD5 encryption string, it will send the header out with outgoing email, but it will only check for them depending on the rules you set in vbouncer.inc pattern config file. This is done to allow the check to be turned on and off based on each pattern defined. If you define a pattern for AOL-sender-block (already defined in vbouncer.inc), you can set the check to no, so it will not ignore tham due to lack of the header.

3. If an MD5 header is defined, and the pattern requires the MD5 header, then it will ignore/skip bounced emails that do not have the header, or have the header but it did not match the MD5 key.

4. No additional manual queue to seperate which is which, since it's quite controllable by the settings, and only a small percentage (less than 1%) of bounced emails (in my logs at least) fall under this case.

So this is tested and running right now and ready for release as 1.0, let me know what you think.

I think I should read you post more carefully next time, I just re-installed it expecting to see this :(

LOL, c'mon, you don't even need to wait, I expect you already have a separate branch with a working version :) I plan to release it tomorrow, just wanted to confirm the stats with a decent sample of bounces.

I also get the following in my ACP

Warning: imap_open(): Couldn't open stream in /admincp/vbouncer.php on line 143

I'm not using the POP/IMAP option.

You mean in the diagnostics page? That should be fine, I just thought I'll let it show everything that can work or not work, regardless of chosen option, for fiagnostic purposes.

Um, okay - it's a bit distracting getting an error message for something I don't use.

Anyway, the diagnostics show this ;

vbouncer.ini file exists = Passed
vbouncer.ini file is readable = Passed

But the cron log shows this : vbounce.ini not found, or empty. Only processing standard reports.

The file in the zip, which I uploaded appears to be called vbouncer.inc (not ini)