If the footer did not say Beta before it means the beta engine was not being used.

Upgrade to 4.6 and the new sending engine will be used by default. After sending with 4.6 let us know how it goes.

The piece of BETA engine code has been added to the engine.inc file prior to sending. Nothing shows in the footer, except for powered by, version number, and copyright notice. There is no text saying using BETA engine of any sort. I will upgrade to 4.6 and see what happens. cheers samoir

Please submit a support ticket so we can take a look at what is going on with your install. Please be sure to provide FTP access (if you can) so we can upload some test files in order to find out what is making it send twice.

Whatever changes that’s implemented on the latest .8 (rc1) release it has done miracles to my installation.
What normally could sometimes take a full day including stalls and re-queues was now done in less than 10 minutes.

I use the pop-up window method with 15 messages per process and 4 for amount of time per process, and I use the default mail() sending method.

So for me on my web hotel Surftown.com it is now working brilliant.

Great work!

Regards

Hokan

Actually, I might have been wrong re the settings – it’s set as default on the specific list (I’ve got a few different installs for 12All across several clients so it’s hard to keep track) so that’s 40 messages, then 3 second pause.

By my calculations that’s an optimum mailout to 4,400 address in 5.5 minutes. In reality, it took about 50 minutes to complete, which seems “normal”, but whether that’s different or not as compared to not using the BETA engine, I must admit, I have no idea – I don’t generally watch the queue, as I’m not in a hurry, and I just need to know that the broadcast was sent successfully, which I have never had a problem with

So, while I can’t verify speed, and I must admit that I hadn’t throttled the queue from default, the severe spike on the MTA is still the crux of the issue.

I’ll set up a test list anyway, as I’m sure it’s always useful to see how your baby is performing in the wild.

I am really glad to hear this!
Although, the beta engine should take your settings into consideration, so I would really like to test this somehow, just to find out why those settings were not used on your server. Would you mind if we troubleshoot that, let’s say on a small list with under 10 recipients, where we would set it to make a 5 second pause after every subscriber? That would be real nice. If you could do that, then please open a support ticket and I will test it right away.

We are currently including additional settings for this sending engine, (which will include Throttling too, among other things), which should make sending even faster in certain cases (that depends on the server). But I would sure like to fix this, if there are any bugs in beta.

I just tested this again from my test install (7 subscribers, 5 seconds break after each), and that is exactly what happened, worked as expected.

Well, finally got to test out the new BETA engine last night with a small run of 4400 subscribers – sent my server manager into a spin. He told me that normally the server is idling with overhead around 1.0 to 2.0; when I initiated the broadcast, the overhead punched up to a peak of 47, so he was wasn’t happy. Apparently the MTA was grinding a hole big enough to threaten the other services on the server.

Hey, but it went out faster! Over 50% faster, for sure. You’ve certainly not oversold that feature . . .

Unfortunately, I won’t be using this feature on our setups as it seems to override the limit I set of x messages per minute to keep the server from getting ruffled, and in any case, I am quite happy to send out stuff in a gentlemanly fashion.

But for people with dedicated servers for their broadcasts and large lists, they will be very happy to play with this toy. I just hope you keep it as an option, as even if it’s enabled and is controlled by the limits in the settings re how many mails per x amount of time, it would still send sharp little process spikes through the server, or so it seems to me.

However, I think that the BETA sending engine was not turned on at the time of sending, since that error message is generated by old sender, not new one.

You can see if your Beta engine is turned on in footer of every page in admin panel (unless in Branding Options you chose to hide the version number). If it is on, it is displayed right next to the 1-2-All version number.