Cannot send mail after 13.0.12 update

[st15jap]

Hello all, I am new to this forum, however i am not new to the product. I have been using it for many months now.

The issue occured about a week ago, we were not able to send out any type of mail. New subscribers were not being notified, nothing is going out at all. I am the only user of the program.

After doing my research i updated form 13.0.11 to 13.0.12. The same issue is still occuring. I decided to backup the database and removed everything. After starting from scratch it still wont work. Just to make sure it wasnt the server i used the php mail function and was able to create a script to send mail using that method (which was successful)

Also i am using the basic config.php if that helps.

Does anyone know what might have happened? Or how to fix it?

Thanks in advance for any help.

[chrisdunn111]

http://www.wwiireenactmentsouthwest.co.uk/phplist/

13.0.12

I have had a Server move and an upgrade. I can only send 3 e-mailes at a time. I then have to completely stop the send (not pause), then resend. It sends 3 then counts down and says "waiting" . I have been driving Server team nuts. Today we are going back to an older php version php5.3. The new server had 5.4.
I've used phplist for years, I've changed all the throttling/queuing settings and played around. No joy. Tuesday it was sending 4 at a time, now only 3!!!

HELP!!!!

[Dragonrider]

Just curious, where did you two obtain a version 13?

If it's an illegal spur from 3.0.12 then phplist.com will need to take legal action.

[chrisdunn111]

Hello,

You are kidding! It's a simple mistake. I was hoping for an answer.

[Dragonrider]

@st15jap

The issue occured about a week ago, we were not able to send out any type of mail.

Something has obviously changed at that time. You need to find out what in fact changed. Someone may have attacked your site, or your host may have changed something.
Or you have changed something in phpList, it won't have changed all by itself. Can you find something that changed?

@chrisdunn111

I have had a Server move and an upgrade.

If your problems started after the server change/upgrade, then it sounds like something the host has done has altered the email sending settings or limits, Get back to them and see if they can offer suggestions.

[chrisdunn111]

I have been working with the Server for a week and we tried numerous things. They went up to php5.4 so we went back to a 5.3 Server and tried it and it didn't work either, unless I ran a batch of 1 at 15 second intervals. (230/hour)

We returned to the new Server and the same, it seems to run in a flakey fashion on 1 message, 15 seconds. It requires a stop and re-queue a time or 2. Unfortunately I upgraded to phplist3.0.12 at a similar time. So I wondered if it was that. Reloaded an old version and same problem on the older Server too. So I'm flummoxed. I won't have a message for a week or so on that Server, but I will soon for another on older version php5.3 Server and on phplist3.0.11 so NOT upgraded. If that works, I'll upgrade and maybe try the test run, which I haven't done before.

[chrisdunn111]

I added1 user to a list and sent 2 messages on it. The "process" page sits there saying processing, there's no text to say anything is happening. The campaign list says "submitted" and it sits there telling me nothing. I stopped and re- queued a couple of times over 30 minutes and it now appears to have sent. This is not good. Trying to run a campaign on this is not working. I've had phplist for a few years and the past week it is failing me for some reason.

[chrisdunn111]

I have re-loaded a new version of PHPlist on the new Server (PHP5.4) using Softaculous. I then created a new database and filled it with the original data. I expected it to work, but it does not.

I don't know where to go or what to do with this. It takes me about 20 minutes to send 20 e-mails stopping and re-queuing, tweaking a load management setting and getting 1 mail off , then it waits.

Currently just 2 to get out. This is the loading config -
======================================================
# If you set up your system to send the message automatically (from commandline),
# you can set this value to 0, so "Process Queue" will disappear from the site
# this will also stop users from loading the page on the web frontend, so you will
# have to make sure that you run the queue from the commandline
# check README.commandline how to do this
define ("MANUALLY_PROCESS_QUEUE",1);

# 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

# max messages to process
# if there are multiple messages in the queue, set a maximum to work on
define('MAX_PROCESS_MESSAGE',50);

# 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",10);

# define the length of one batch processing period, in seconds (3600 is an hour)
define("MAILQUEUE_BATCH_PERIOD",16);

# 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',0);
================================================================

This has been over a week now and there is no answer to the problem.

[chrisdunn111]

Also on the
"?page=processqueue"
Page, I am rarely getting any information, only occasionally does it show that.

[chrisdunn111]

OK I have an answer -

It would appear that the process was PHP timing out, despite the Server going up to 60 secs from 40. The queue then waited. The Cronjob was set at 0817 which meant that when I have the time in the evenings to fiddle, nothing was happening and the time-outs meant I was re-loading and firing 1/2 at a time.

Instead of going for small batches I will set it to take all of it and I can move the Cronjob to where I want it.

I think PROBLEM SOLVED. I bet there are many PHPLIST guys out there with severe headaches and this could be the solution.