Jeff wrote:lakrsrool wrote:So are these quicker mail checks in part a function of the different accounts working more smoothly and/or error free?
There are several factors involved, but if you have even 1 Yahoo account, then it looks to me like they've improved (for now). There's a setting in POP Peeper that tells how many accounts should be checked simultaneously. The default is '2' so if you had at least 2 slow (Yahoo) accounts, then they were bottle-necking the others and preventing other accounts from being checked. In general, '2' is an adequate value, but you can experiment by bumping it up a couple:
Tools / Options / Mail Check -- "Maximum simultaneous threads"
Note that "Advanced Options" on the General Options page must be enabled
We have 8 Yahoo accounts of the total of 30.
Good point regarding the "maximum simultaneous threads" setting, I've had this setting set to a maximum of "5" for a very long time now (it's been so long I can't even recall when I did originally set it). So of course that would speed things up, but in as much as this setting has been this way for a long time this presumably would not be a factor as far as what accounts for the perceived faster mail checks more recently so based on what you've said the improvement would be I guess due to "accounts working more smoothly and/or error free" that I mentioned above which would necessarily be related to for the most part improved Yahoo reliability presumably. When Yahoo was having the problems I'd often have 2-4 accounts come up with errors per mail check so that could have as you say been "bottle-necking" others accounts at the time. Btw, since the Yahoo problems I had increased two of the default "connection time outs" in PpTweaker from "60" to "90" thus matching the default "SMTP" "connection time out" setting of "90" which might be possibly helping in regards the occasional "time out" errors we were getting.
Of course the "maximum simultaneous threads" setting at "5" would account for why the "mail checks" are so very fast as of now with the Yahoo problems apparently resolved that is considering that there are a total of 30 accounts to check on each pass. Presumably my idea at the time in regards to "5" simultaneous threads in relation to 30 accounts was to divide them up in more or less equal groups of 6 accounts for each thread (5 threads, ~6 accounts each = the 30 accounts assuming threads are balanced which makes sense) to make mail checks that much faster thus accounting for why the mail checks are currently faster than one would intuitively expect (I had forgot about that setting of mine). Any ideas
why Yahoo at the time they were having issues was putting out "Error (Send)" errors on various Yahoo accounts at times even though we were not sending any mail at all during the time when those errors occurred? (my guess is that they were just erroneous errors produced by Yahoo presumably that caused the misleading error description). Btw, with mail actually arriving (7 new emails) for the mail check pass checking our 30 accounts it took 105 seconds this morning (5-24) w/ just one error, the "Error (Send)" that I mentioned above. Then later this morning it only took 25 seconds with 6 new emails arriving and with zero errors (less than half the elapsed time of the earlier mail check with one error), so while there are obviously other factors involved as well it does undoubtedly appear that errors can definitely slow down the time it takes to complete a mail check. Both mail checks are of course an accurate gauge to determine current mail check elapsed time since mail was actually arriving in these two examples as well as the fact that this also demonstrates how much longer a mail check can apparently take if and when errors do occur.
Addendum: Oh btw,
Jeff - I kind of figured you'd have a much better explanation regarding that "white box" issue:
Annoying issue since last upgrade". I should have suggested as an alternative for
itsmeintorre to consider waiting for a better explanation from you as to what the likely cause of the problem was which yours is of course.
Addendum 2: Say
Jeff, any idea what this error might mean (seem to typically be Outlook errors): "
Error (Select Command is not permitted in current state NotAuthenticatedServerError)"
They've been popping up now and then including this morning (5/23) again. The good thing is that these specific errors are not pervasive and are definitely not persistent as they typically clear on the very next mail check.
Since they do typically clear quickly do you agree that it's not worth switching back to "Hotmail/Outlook" server-type from "IMAP" to try and avoid them? (because these errors are not at all pervasive and do generally clear the very next mail check it's not worth starting a new thread on the topic)
Good judgment comes from experience and a lot of that comes from bad judgment. - Will Rogers
The errors are not the same for each account, though. One is reporting "Error ([SERVERBUG] FETCH Server error - Please try later)" and the others are reporting "[LIMIT]CAPABILITY Service is temporarily not available". To me, these seem like service response issues coming from the Yahoo server side (bad hair day for them!), but I could be wrong. I'm running 4.0.1.0 PP with everything updated. My Yahoo accounts are using the IMAP configuration and had been working up until within the last 12-24 hours. Anyone else seeing the same or similar? 
It morphed! 
)