Yahoo IMAP issue

February 17, 2018

Update: Yahoo has fixed the problem.

Yahoo’s IMAP server is currently reporting the following error:

This is a server-side error and it affects all IMAP clients. They are aware of the issue:

In the meantime, you can consider switching POP Peeper to access your account using POP3 or WebMail (edit the account and change the ‘server type’ to ‘POP3’ or ‘Yahoo’) but be aware that POP Peeper will need to download all existing email in your inbox whenever you change the protocol. If you had been using OAuth2, be sure to enter your password when accessing with POP3 or WebMail.

You can track the issue here:


AOL/AIM error in POP Peeper (fix available)

January 19, 2018

Update (Jan 20): AOL has discovered the problem and fixed it on their end, so this patch is no longer necessary.  However, this change will be included in future versions of POP Peeper in case it ever happens again (with any IMAP service).

Today, AOL/AIM accounts that use IMAP have started reporting an error in POP Peeper, typically a “time out” error.  The reason for this is because a response from the aol server includes an invalid null character and this prevented POP Peeper from parsing the response correctly.  A patch is available for download so that you can get your aol and aim accounts working properly again.  Most likely, a full update (POP Peeper v4.5.1) will occur soon in response to this issue (and will address a couple of other issues, as well).


  1. Download the patch
  2. Exit POP Peeper
  3. Open the zip file you downloaded in step #1 and copy Imap.dll to the folder where you have installed POP Peeper.  This is typically:
    C:\Program Files (x86)\POP Peeper\
  4. Restart POP Peeper
  5. Test your AOL/AIM accounts
  6. If you still have an issue, make sure that you applied the patch correctly:
    • From the main menu, select Help / About
    • Find “IMAP” in the list and the ‘Current’ column should be:

POP Peeper v5 more details

December 12, 2017

Yesterday, I posted a screenshot that showed 2 features:






The “obvious” one is the capability to search your inboxes.  This will be an indexed search on the local messages which means that it will return results very quickly.  This is one of the biggest features that will be added in v5 so you can expect more information about this before the release.

The other feature is hidden in the Accounts List, on the left.  If you had the same accounts in POP Peeper v4, the order would be: Local01, Local02, etc.  v5 adds the ability to re-order the accounts simply via drag & drop.  No more having to rename your accounts to get the order you want!

More features will be announced after the new year.  Are you happy to see these features?  Let me know what you’d most like to see added to POP Peeper.


POP Peeper v5 Sneak Peep

December 11, 2017

Now that POP Peeper v4.5 is out, v5.0 is on the horizon.  I’m usually tight-lipped about what features will make it into the next version until the features have a “better-than-not” chance of actually making it in (some features may be more complicated than anticipated and it’s better to delay them for another version rather than delay the release), but with v5 well under way, I’ll start releasing some information about what you can expect.

In this first preview, two of the most requested features are shown — can you spot them?  One should be very obvious, the other is more subtle.  I’ll provide more details tomorrow.

Click the thumbnail for full-screen image.







October 11, 2017

If you have an AOL or AIM account, you may be getting a message saying you need to update your security settings by November 7, 2017.  For this, you need to make sure that your AOL/AIM accounts are using either “SSL/TLS” or “STARTTLS” for both your incoming and outgoing servers (update: incoming server must use SSL/TLS).

To check these settings in POP Peeper:
– edit each of your AOL/AIM accounts
– Near the bottom-right (to the right of “server type”), set the SSL dropdown selection to “SSL/TLS” (if it’s set to STARTTLS, that will also work Update: STARTTLS no longer works, it must be SSL/TLS)
– Select the “Send Mail” page, on the left
– On the top-right, set the SSL dropdown selection to “STARTTLS” (if it’s set to SSL/TLS, that will also work)
– Press the “Update” button on the bottom