Error messages on email signup page

ℹ️ Support
1

I am now getting the following error messages at the top of my email signup page. I’m sure I have an error in the configuration but I’m having a hard time fixing it.

Notice: Constant MAILQUEUE_BATCH_SIZE already defined in /home/artwac5/public_html/songside.com/emaillist/config/config.php on line 331

Notice: Constant MAILQUEUE_BATCH_PERIOD already defined in /home/artwac5/public_html/songside.com/emaillist/config/config.php on line 343

The email registration still works though. Any help would be appreciated.

This is the link to the subscribe page: http://www.songside.com/emaillist/?p=subscribe&id=1

Thanks much,
Art

2

I am still getting the Notices on my signup page. Why would I get MAILQUEUE notices on the signup page?

My ISP directed me to enable throttling, which I did. Any help in finding my errors would be greatly appreciated.

The throttling section from my config.php is as follows:

the number of criterias you want to be able to select when sending a message.

Useful is is to make it the same as the number of selectable attributes you enter in the

system, but that is up to you (selectable = select, radio or checkbox)

define (“NUMCRITERIAS”,2);

if you do not require users to actually sign up to lists, but only want to

use the subscribe page as a kind of registration system, you can set this to 1 and

users will not receive an error when they do not check a list to subscribe to

define(“ALLOW_NON_LIST_SUBSCRIBE”,0);

batch processing

if you are on a shared host, it will probably be appreciated if you don’t send

out loads of emails in one go. To do this, you can configure batch processing.

Please note, the following two values can be overridden by your ISP by using

a server wide configuration. So if you notice these values to be different

in reality, that may be the case

if you send the queue using your browser, you may want to consider settings like this

which will send 10 messages and then reload the browser to send the next 10. However, this

will not restrict the sending to any limits, so there’s a good chance you will

go over the limits of your ISP

define(“MAILQUEUE_BATCH_SIZE”,100);
define(“MAILQUEUE_BATCH_PERIOD”,30);

if you send the queue using commandline, you can set it to something that complies with the

limits of your ISP, eg 300 messages an hour would be

define(“MAILQUEUE_BATCH_SIZE”,1000);

define(“MAILQUEUE_BATCH_PERIOD”,3600);

and then you need to set the cron to run every 5 minutes

define the amount of emails you want to send per period. If 0, batch processing

is disabled and messages are sent out as fast as possible

define(“MAILQUEUE_BATCH_SIZE”,100);

define the length of one batch processing period, in seconds (3600 is an hour)

Please note: this setting has two consequences:

1. it will enforce that the amount of emails sent in the period identified here does not exceed the amount

set in MAILQUEUE_BATCH_SIZE

2. there will be a delay of MAILQUEUE_BATCH_PERIOD when running the queue.

number 1 is mostly when using commandline queue processing (strongly recommended)

number 2 is when using browser queue processing. The browser will reload to send the next

batch after the amount of seconds set here

define(“MAILQUEUE_BATCH_PERIOD”,30);

to avoid overloading the server that sends your email, you can add a little delay

between messages that will spread the load of sending

you will need to find a good value for your own server

value is in seconds, and you can use fractions, eg “0.5” is half a second

(or you can play with the autothrottle below)

define(‘MAILQUEUE_THROTTLE’,.5);

Thank you!!!

3

it looks like there are two definitions of MAILQUEUE_BATCH_SIZE in the config.php file. There must be only one so you need to remove one of them.

4

Thank you so much. So simple. I feel like a dummy.

Art