asquirrel wrote:Doesn't work for me with either the IMAP or Yahoo settings (see my above post). It's stuck on either connecting (imap) or invalid username or password (yahoo). How do I fix this?
As I understand it, you are getting the the following error:
"account 1 Yahoo [1000: IMAP] ['imap.mail.yahoo.com' (993) SSL: 1] [Smtp: 'smtp.mail.yahoo.com' (465) SSL: 1] [Consec: 1]- Bad Connection"
when using "IMAP". So I am presuming that POP Peeper gets "stuck" for awhile using "IMAP" but eventually will stop attempting to "connect" and then produces this specific error, is this correct?
Have you enabled the "IDLE/Push" option? Generally "IMAP" works better with this enabled (lower right-corner of Account Edit interface).
What is your provider (i.e. AT&T, Comcast etc)?
It would appear that you are having other issues (possibly local to your area). Have you tried rebooting? This will clear cache which might help.
You may have security software or some other issues with your provider that is possibly interfering. Have you tried resetting your connections?
If your issue persists to look into this further you could try pinging the Yahoo IMAP Server.
Do the following steps to do this (see screen-shot example below):
1) Open a command/dos prompt (type '
command' into the start menu to find it)
2) Type in the command prompt:
ping imap.mail.yahoo.com
Considering the issue you are having, you will probably get something like this (which would mean you are apparently having Yahoo IMAP Server issues for some reason, in which case take a look at the bottom of this post for a possible resolution using POP3):
Pinging internal.imap.mail.g03.yahoodns.net [208.71.45.81] with 32 bytes of data:
Request timed out.
Ping statistics for 207.46.11.202:
Packets: Sent = 1, Received = 0, Lost = 1 (100% loss),
Control-C
Notice the "Packets: Sent = 1, Received = 0, Lost = 1 (100% loss)" line.
What I get is the following (which does not "time-out" with errors):
Code: Select all
C:\Users\user>ping imap.mail.yahoo.com
Pinging internal.imap.mail.g03.yahoodns.net [208.71.45.81] with 32 bytes of data
:
Reply from 208.71.45.81: bytes=32 time=48ms TTL=47
Reply from 208.71.45.81: bytes=32 time=50ms TTL=47
Reply from 208.71.45.81: bytes=32 time=48ms TTL=47
Reply from 208.71.45.81: bytes=32 time=48ms TTL=47
Ping statistics for 208.71.45.81:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 48ms, Maximum = 50ms, Average = 48ms
Screen-shot example:
If you do ping the server, notice the server name you get? There may be issues with this IMAP Server.....
As long as you ensure that "IDLE/push" is enabled for the problematic account, there is not much more that can be done. Alternatively you could try using "POP3", since in the case of Yahoo that protocol can sometimes be more reliable based on the historical record of Yahoo IMAP Server issues often occurring from time-to-time in some areas. Keep in mind of course that POP Peeper will have to re-download all messages each time you change the protocol so the first "Mail Check" after the change is made will necessarily always take longer (as I'm sure you have noticed
).
Good judgment comes from experience and a lot of that comes from bad judgment. - Will Rogers
That's because, put simply as far as what applies to this specific case, one of the main purposes of Peerblock is to block servers and sites known to be troublesome or even dangerous that are in many cases not necessarily an issue. Peerblock is intended to let the user choose what to block as well having the ability to also import or create user specific block-lists, so in that regard it's up to the user to determine what they want blocked and what to not block by either doing a right/left click via the Peerblock tray icon.
.