95+% of the mail performance issues are due to instant notifications. Those are only sent once per thread, until the member's next visit. If they don't visit often, they will not generate instant notifications, so adding more code for those who have not visited lately will have little impact.

Thanks for th note.

Maybe you do not know my site and thus do not see the same concerns. (Not that you would know the site.)

We see over 65,000 unique people a day with over 3000 showing as on-line most of the day. Over 190,000 register with about 250-300 new registrations a day based on what is going on. Over 6.5 millions posts and under 4000 in Alexa. :)

Running the clean once a week does not work. In 3 days we could have someone already over the other limit and thus to late for any warning notice for it would have already taken action. The site is very, very active and a lot of mail goes out.

I mentioned the idea to check the last visit date because looking at some of the users that have bounced mail, they have not been to the site in over 6 months. You see, we have threads that are active still for years.

Oh, the image path. Ys, I had seen that line but would not know what edit out to stop the ../ part.

Thanks

vBouncer was written for large sites. Smaller sites have no use for it, so I'm aware of the load issues, that's why I wrote it :)

You don't need to run the "clean" cron once a week, but hourly is an overkill, and provides no benefits, unless your warning period is defined as hourly. The interval should be no less than your warning interval, can be 2 days, 3 days.

Users who have not visited for a month or more, will never get instant notification emails. It's either the daily digest, or the weekly digest. If you set your digests to run in the off hours, then 99% of the mail load damage is caused by instant notifications, which is done by active members only.

have i had to much crack today or does my vb have no email.php?

mail.php, not email.php :)

Hello...

I have been using this for some time now and it works great.

However I just moved my mail to a new mail server and I have run into an issue. Here is the error that is reported...

Failed to access email, please check vBouncer mail settings.
Last error: Certificate failure for mail.tivocommunity.com: self signed certificate: /C=US/ST=Unknown/L=Unknown/O=Unknown/OU=Unknown/CN=cambridge.micfo.com/emailAddress=ssl.net
Unable to clear bounced emails, exiting.

The question is, is their any way to ingnor this error and contiune on? The POP3 account does work just fine but it seems SSL is getting in the way for PHP is using IMAP.

Please help.

Thank you.

Try adding "notls" into the connection string.

Anybody up to trying to get this updated for 3.6.x?

Can you please fix code suggested for mail.php? Because as it is in the notes, there are some curly brackets missing, and since the time I did that suggested change, all email from my sites were stopped.

Also, if one of the guys/gals who posted in this, have installed this hack and it is working, can you please tell me how you modified your mail.php file?

One more thing. I am trying to use the file method for this hack. The file /var/spool/mail/rejects (or whatever you call the account name), is owned by rejects and the group is mail. The permissions are set to 666, but as soon as procmail delivers mail to it, it is reset to 600. Also, I do not see anything in my php configuration, regarding pop. All I see is :

mod_php4, mod_setenvif, mod_so, mod_auth, mod_access, mod_alias, mod_userdir, mod_actions, mod_imap, mod_asis, mod_cgi, mod_dir, mod_autoindex, mod_include, mod_status, mod_negotiation, mod_mime, mod_log_config, mod_env, http_core

Is mod_imap the required procedure to access the email account via POP3? If so, why do I get a Failed in diagnostics?

"Your PHP installation supports IMAP/POP Failed"

Thanks

Anyone can answer the above please??