timecontrole difficulties

Hello Marion,

I answer between:


On 27.03.23 18:10, Marion wrote:
> Hello
>
> Sorry to contact you, I have a small problem that I can't solve.
> I have configured the timecontrol plugin as indicated. The sending of newsletters is ok. But there are some difficulties:
>
> - the number of simultaneous sending is not equal to my configuration (it sends by pack of 10 and in my configuration it is 50), and so it takes more than 15 hours to send to my subscribers...

I wonder, how You can determine, that BwPostman TimeControl sends in packages of 10. There is no real optical feedback of the sending process of BwPostman TimeControl. You can see the outstanding mails at the queue, but that is all.

Nevertheless BwPostman TimeControl uses the sending process and parameters of BwPostman. So if You set the numbers per step to 50, BwPostman and BwPostman Time Control sends 50 newsletters per step.

>
> - the newsletter has been sent 3 times to people (and I stopped the cron because I thought there was a problem). How to control this? if there is a problem sending the whole list is processed again?

BwPostman and BwPostman TimeControl can't do anything else than You asked them to do. So if the newsletter was send 3 times, You sent the newsletter 3 times. What You should know, because a newsletter, which is internally prepared for sending and is processed, so that it appears at the queue, gets the status sent an cannot be sent another time, except You copied it. As mentioned above, all emails of a newsletters prepared for sending, nevertheless You send with BwPostman or BwPostman TimeControl, appears at the queue. If an email is sent, it disappears from the queue. So You can see, which subscribers already got the newsletters. If something goes wrong with a specific subscriber, it will not disappear from queue, it will be tried to send second time. See the manual.

The time needed for sending all emails of a newsletter depends on the number of subscribers, the numbers per step, the entered delay between the steps and the size of the email. The average sending time for an average email is about 1 second or so. But if the newsletter contains big images and/or big attachments, the sending time for one email could could increase up to 1 minute and more. Paired with a delay of lets say 10 minutes, You may encounter such overall sending time.

Did You read the manuals of BwPostman < www.boldt-webservice.de/index.php/en/for...wpostman-manual.html > and BwPostman TimeControl < www.boldt-webservice.de/index.php/en/for...plugins.html?start=4 >?

By the way: I would like to answer support questions at the forum < www.boldt-webservice.de/index.php/en/bw-.../your-questions.html >, so other users may read my answers also.

Hth

Romana

thank you for your answer and sorry for not using the right channel.

For the multi-copy mailing it is indeed strange, I don't know what could have happened, but there was just one newsletter published.

For the number of manually processed mailings, I monitored the database and looked at the mailing list. It was decreasing at the right time interval, but not with the right number of subscribers. I also received error messages ("normal") that confirmed that the mailing was done at this rate. Just last night I did a send, and it was still the case (even though as indicated in the documentation, I stopped the cron, checked my settings, and restarted the cron).

Hello,

Romana schrieb:

How do You process mailing manually?

No sorry it's a bad translation, my English is not very good. I wanted to talk
about the number of elements processed simultaneously

Romana schrieb:

You looked at the database?

IT is my profession, and I went directly to the tables in Mysql to try to understand what was going on.

Anyway thanks in advance if you have time to look at/correct, that would be great!