| Author |
 Topic  |
|
|
Bruce23
Canada
134 Posts |
 Posted - Dec 09 2012 : 22:15:26
|
I am using MLK 11 business. I have set the maillist king ISP limit for 700 in an hour. The other two settings are left blank.
Sometimes the program works and sends 700 in an hour and then waits but other times it does not stop but just keeps sending without following the limit. It does not stop after the first 700 messages.
What could be causing this or what am I doing wrong. It is intermittent. Thanks. |
|
|
xequte
7042 Posts |
|
|
Bruce23
Canada
134 Posts |
Posted - Dec 15 2012 : 22:27:14
|
It happened again tonight. The problem is I am with a company and they will not allow me to send a debugfile that contains email addresses of contacts and sensitive information. if you can advise me what you need to send from the log file I would appreciate it.
Meanwhile I have changed the setting to
don't send more than 650 recipients per 1 hour and it stops sending and then within a few minutes starts sending all the rest again. I have to manually pause it.
When I use the Stagger Delivery, and mark to send 1 message every 5 seconds, it works for about 400 messages and then I get a sending error indicating that the SMTP server cannot be contacted.
Bruce23 |
 |
|
|
Bruce23
Canada
134 Posts |
Posted - Dec 19 2012 : 01:43:07
|
Any follow up on this from Nigel?
What portions of the debug log should I send? Can I simply strip out all the email address information and confidential info and will that then give you the information you need?
I would like to get this copy of the business edition version 11 fixed. Thanks Nigel.
Bruce23 |
|
|
|
xequte
7042 Posts |
Posted - Dec 19 2012 : 01:47:11
|
Hi
I have emailed you details on how to strip out the email addresses.
Nigel
Xequte Software
www.xequte.com
nigel@xequte.com
|
|
|
|
Bruce23
Canada
134 Posts |
Posted - Dec 19 2012 : 02:02:31
|
That does not seem to be a wildcard method to strip out the email addresses. I get a "NOT FOUND" error in Word as per your suggestion.
Please walk me through the settings I need to set for sending 700 messages every 75 minutes. Perhaps I am missing something. I don't see how as it is a straight forward method but maybe there is something I am missing.
I am not using send "1 every 5 seconds". I have just set send 700 messages and 75 minutes. That's all the settings I have on in ISP Limitations. Thanks Nigel
Bruce23 |
|
|
|
xequte
7042 Posts |
|
|
Bruce23
Canada
134 Posts |
Posted - Dec 23 2012 : 23:01:29
|
Not sure what details you are referring to.
Anyway I am still looking into figuring out how to send the log without the email addresses, but as I say we have 3 licenses and all 3 are doing the exact same thing. The other managers don't care since they do not have any restrictions and can send as many as they like.
Has anyone else used the ISP limit feature for large mailings of more than 2500 and found that setting the limit does not always work?
Bruce23 |
|
|
|
Bruce23
Canada
134 Posts |
Posted - Mar 03 2013 : 09:24:56
|
Just to update this thread. The problem with the ISP limits is being addressed by Nigel who plans to put in a strict ISP limiting option. This will correct this issue when sending individual emails.
I am updating this as I know a number of other businesses have emailed me from this forum regarding the same issue which they also experienced and were trying to resolve.
What we have uncovered is that the timing of not sending a specific number of emails within a certain time frame actually does not work as the time frame does not take into account the length of time between when the job is created and when each batch of emails are sent.
For example if we have a mailing list of 2500 emails and an isp limit of 1000 in an hour, we could set the sending limit at 250 every 15 minutes. In other words "Don't send to more than 250 recipients per 15 minutes" is checked.
However the software schedule does not take into account the amount of time it takes to send the emails. Therefore when 250 emails are sent in the first 15 minutes it takes about 4 minutes for MLK to actually send the 250. That means if we started at 1:00 PM for example, the program is not done sending the first 250 until 1:04. Therefore the next 15 minutes should be 1:19, but instead the program simply adds 10 minutes to the start time so the next delivery is at 1:15 PM when it should be 1:19 PM.
This means that by 1:45 the program is already entering the final first hour of delivery as it will send the remaining 250 at 1:45 which reaches the 1000 emails within an hour limit.
However the program at 2:00 PM will start again to send emails which is actually over the ISP limit since the original sending by MLK did not stop until 1:04 PM. So when MLK starts again to send emails it is already sending the next 250 emails at 2:00 PM when it should be starting no sooner than 2:04 PM to not go over the ISP limit of 1000 within 60 minutes.
After weeks of having emails rejected by the mail server, debugging and discussing this with Nigel, we called the ISP provider who looked at the emails and discovered the error in the scheduling. The work around for the time being that we are using is adding the additional time to the sending.
For example, for 1000 emails in an hour, if we know that it will take 4 minutes to send 250 in 15 minutes, we set up the ISP limit as "Don't send to more than 250 recipients per 17 minutes". This adds additional time to the overall sending and delays the sending just enough to stay within your ISP limits. By adding this extra time for example, instead of sending at 1:15, the second sending is at 1:17 and the third at 1:34 and the 4th at 1:51 PM
Therefore by the time 2:00 comes you are actually sending at 2:08 PM which stays within the guidelines of the ISP.
Another issue, beyond what MLK can assist in and which you may wish to speak with your provider about is the delay many mail servers sending email have as so many people within a hosting company are sending email. Our ISP provider advised us of this as we kept hitting their limit at various times since sometimes when sending we would be sending at the same time as many other emailers and our mail would be delayed. The delay meant as far as the provider was concerned that we were continually going over their limit. We discussed this with the provider who then extended the number of emails we could send from 1000 to 1050 an hour to accommodate possible delays at their server and advised us not to increase the sending from 1000 to 1050 but to leave this as a buffer.
So there you have it. Nigel has advised he will put a strict sending limit in the next update which should address this problem especially for those of us with very large mailing lists.
Bruce |
|
|
|
xequte
7042 Posts |
Posted - Mar 05 2013 : 22:26:43
|
Hi
Just to clarify, MLK is working as it was designed, which is to achieve an average sending rate which does not exceed your limits. However the problem, as Bruce outlined, is that this means that if sending occurs at the end of a limiting period then when the new period starts and sending recommences the limits may be exceeded for a time (even though this will even out over the rest of the day to ensure the average sending rate is achieved).
The new option will initiate the sending period at the end of the sending batch to ensure that at no time the ISP limit is exceeded.
Nigel
Xequte Software
www.xequte.com
nigel@xequte.com
|
|
|
|
Bruce23
Canada
134 Posts |
Posted - Mar 05 2013 : 23:19:34
|
Hi nigel
Thanks for the update. I wish we had known this was an average sending rate rather than a true limitation. This would have saved a lot of work on our part. The problem is for those of us with large mailing list, the averaging out doesn't cut it when it comes to constantly going over the ISP limitation. As explained, once the ISP limitation is broken the more emails being sent continue to be rejected. The limitation of a specific number within a specific time frame should be exact not average as the ISP doesn't give an "average" but a specific amount. Therefore when we choose for example 700 messages in an hour we would expect exactly that amount within exactly 60 minutes and not have it averaged out during the day. ISP's don't average out the allowed hourly limit.
Bruce |
|
|
|
xequte
7042 Posts |
Posted - Mar 06 2013 : 12:45:59
|
At the time when we designed the features the limits were much softer than they are now, and the ISP's generally looked at your overall sending patterns to determine if you were "spamming" or not.
By using an averaging mechanism we were able to maximize MLK's throughput without exceeding your imposed limits on average.
Clearly now many ISP's are much more rigid with their limits and indeed the server itself will often physically reject a user when the limits are exceeded. The new option should significantly improve things in this area.
Nigel
Xequte Software
www.xequte.com
nigel@xequte.com
|
|
|
| |
Topic |
|
ISP Limit Not Being Followed By MLK
