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).

Instructions:

  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: 4.5.0.9002

2 Responses to “AOL/AIM error in POP Peeper (fix available)”

  1. I’m still having the issue with the AOL error within Pop Peeper AND my reg email client Eudora Pro (yes, I still love it and use it)
    Can you tell me anything new that I’m not seeing in the forum? No new posts I see since 2/23.
    Thanks!
    Eric

  2. What error does POP Peeper report — press the yellow ‘!’ button on the bottom-right of the main window.

    If it’s something along the lines of a “connection error” make sure that your server settings are correct:
    https://www.esumsoft.com/products/pop-peeper/faq/?q=AolImap

    Specifically, make sure that you’re using SSL (not “No SSL” and not “STARTTLS”).

    Also, someone reported an issue with their virus scanner (GData) and they had to get an update from them to fix the issue.

Leave a Reply