Version: 3.8.001, by Paul M
Developer Last Online: Nov 2023
Category: Administrative and Maintenance Tools -
Version: 3.8.x
Rating:
Released: 01-09-2009
Last Update: Never
Installs: 295
Uses Plugins
Code Changes Additional Files Translations
No support by the author.
As of 24 Nov 2017 this modification has been withdrawn.
In default vBulletin, if you send a large number of e-mails, vbulletin either puts them in it's queue and attempts to send them as each user visits a page, or just simply tries to send them straight away (as is the case when you use the Administrators email users inteface).
The result of this can be that your server can gets seriously overloaded very quickly - or on many hosts, you get banned for exceeding their e-mail sending limits. This can make sending several thousand e-mails (like a newsletter) very difficult.
This modification does two things ;
1. The processing of the mail queue is set-up as a vbulletin cron item.
2. Allows you to add a small delay before each e-mail is sent (between 1 and 9 seconds).
3. E-mails from the ACP inteface are sent to the mail queue, not straight to the mail system.
Use option 2 carefully, otherwise you will slow your e-mail system right down.
For this to work, you must turn on e-mail queuing in the ACP options - set 'Use Mailqueue System' to 'Yes', and 'Number of Emails to Send Per Batch' to a realistic value (based on the cron setting, as below).
There are two options for the cron job, you can either set it to run every minute, and set the items to be processed to something small (like 10), or you can do what this modification does by default and set it to run every 10 minutes, and set the items to be processed to something larger (like 100).
Remember, 10 per minute = 600 per hour, 100 per 10 minutes is also 600 per hour. The numbers really depend on how quick you want large queues processed, and how much your mail server can handle in one go.
Once working, when using the ACP mail users inteface, remember you can set it to process 9999 at once (not 500 or whatever) as the mails will now go into the queue, not be sent directly.
Note: This modification will affect any queued e-mails such as subscription e-mails. It will not affect registration e-mails as they bypass queuing anyway.
This modification includes the code by Antivirus that displays the current size of the mail queue.
History:
v3.8.001 : First Release for vB 3.8.
Show Your Support
This modification may not be copied, reproduced or published elsewhere without author's permission.
Would be perfect if you could select what type of emails go into the mail que. Like newsletter emails that I send out manually to all members in the que...but new registration emails go out instantly
Fatal error: Out of memory (allocated 58720256) (tried to allocate 52 bytes) in /home/pythonim/public_html/codspot.com/includes/functions.php on line 4146
that is the error i'm getting? I've never gotten it before now..
Not a big deal but in scheduled tasks the title is "Process Mail Queue for vBulletin 3.7" not sure if you wanted this to reference version 3.8 or not.
My hosting is via godaddy and my limit is 800 smtp relays per 24 hours.
With the default scheduled task which run's every 10 minutes I set mine to send out 720 emails per 24 hours.
Here is my config
E-Mail Send Delay = 0
Number of Emails to Send Per Batch = 5
Some calculations to save others time:
60 seconds per minute
600 seconds per 10 minutes
3600 seconds per hour
86400 seconds per 24 hours
scheduled task cron runs every 10 minutes
scheduled task cron per hour = 6
scheduled task cron jobs per 24 hours = 144
I considered changing the scheduled task runs once every 12 hours then set the number of emails per batch to 400, but I think I like the 5 email trickle option a little more that way I will have less odds of being recognized as a spammer.
Cron based e-mail sending Details »»
About Developer
Visit Web Site
Uses Plugins 
No support by the author.
06-05-2010, 09:42 PM
