Hi,
Ok, regarding the use of a throttle with the code here from your previous message Dean:
if(($y % '100')==0 && $y <> sizeof($sendq)) sleep(25);
That did nothing, as I received the same number of clicks regardless of whether I used the throttle or not, so that's not the problem.
Back to the other issue, the number of removes does not make sense.
Here's some INTERESTING NEWS! I'm not 100% sure on which batch of 10,000 I had the throttle turned on for, but here's what I see between 2 batches, one had the throttle on, the other was with the throttle code removed and off, the number of removes in one of those batches is 128, that's the highest number yet, check out the other number of removes in these batches:
Batch - Batch Size - Removes
A - 10,000 - 17
B - 10,000 - 24
C - 10,000 - 18
D - 13,000 - 31
E - 8,000 - 43
F - 10,000 - 2
G - 100 - 3 (with SMTP trace bugs=1)
H - 1,000 - 14 (with SMTP trace bugs=1)
I - 10,000 - 1
J - 10,000 - 128 (with throttle code, delay 25 every 100)
Do you see the pattern here! When the code is slowed down, either by using SMTP tracing bugs=1, or by using the throttle code, the number of removes increases dramatically ,why is that? Is it because when the sending is going fast there are too many REMOVE clicks coming in at once for the script to handle it? It appears that could be the case, I've not had many people email me and say they have problems, but a few have emailed saying that the REMOVE code link does not work???
Here are sample outputs from my SMTP bugs=1 code, as you can see, it looks like everything is normal here, see anything wrong?:
250-ENHANCEDSTATUSCODES
250-PIPELINING
250-8BITMIME
250-SIZE
250-DSN
250-ETRN
250-DELIVERBY
250 HELP
pipelining support enabled.
NOOPmsg=250 2.0.0 OK
Delaying.. Please wait..
If your mailing stops for any reason, close the window or . Do NOT Refresh!
Sending Mail of 101..
PIPELINE-FROMmsg=250 2.1.0 ... Sender ok .
RCPT TO: <xxxxx@domainname.com>
RCPTmsg=250 2.1.5 ... Recipient ok
DATAmsg=354 Enter mail, end with "." on a line by itself .
SENDmsg=250 2.0.0 i45JbvSH023567 Message accepted for delivery .
PIPELINE-FROMmsg=250 2.1.0 ... Sender ok .
RCPT TO: <xxxxx@domainname.com>
RCPTmsg=250 2.1.5 ... Recipient ok
DATAmsg=354 Enter mail, end with "." on a line by itself .
SENDmsg=250 2.0.0 i45JbvSI023567 Message accepted for delivery .
PIPELINE-FROMmsg=250 2.1.0 ... Sender ok .
RCPT TO: <xxxxx@domainname.com>
RCPTmsg=250 2.1.5 ... Recipient ok
DATAmsg=354 Enter mail, end with "." on a line by itself .
SENDmsg=250 2.0.0 i45JbvSJ023567 Message accepted for delivery .
QUITmsg=221 2.0.xxxx closing connection .
Finished sending!
Well, again, as stated above, it appears when the code slows down, and the throttle is on, or the number of sends is slowed down with bugs=1 turned on the number of removes increases considerably, it seems a sure sign that on high speed, something is not working right when people try to remove themselves, or all of the emails are not getting sent out, though that really does not seem to be the case as I see almost the exact same number of clicks regardless of whether throttle is on, bugs=1, or normal sending!
Here's one more thing to think about. I did update my admin.php when I added the throttle code, is there anything in there which would affect the performance of the removes? If so, perhaps the udpated admin.php fixed the remove problems, I'll know soon enough when I start sending more batches, if I turn the throttle code off and still see a good number of removes I'll guess that the new admin.php solved the problem.
What are your thoughts Dean?