eEye Digital Security

** This method is not required anymore, new release is available, please read: http://forums.eeye.com/forums/p/883/3774.aspx#3774

Sorry for the inconvenience you have.  We are gathering debugging information to solve this issue.

Please gather debugging log using following method:

Enable debugging executing following command from command prompt.

reg add HKEY_LOCAL_MACHINE\SOFTWARE\eEye\Blink /v Blinksvc /t REG_DWORD /d 2

Perform the task that is causing the problem.

Disable debugging executing following command from command prompt.

reg add HKEY_LOCAL_MACHINE\SOFTWARE\eEye\Blink /v Blinksvc /t REG_DWORD /d 0

See and send the log c:\Program Files\eEye Digital Security\Blink\blinksvc.log to moh@eeye.com.

Thanks for your patience.

 I would be glad to send a debugging log in order to help solve this problem.  However, on my machine Blink is installed on a D: drive instead of C:   In such a case will the enable/disable method for the log be different than what you have described?  Thanks.

Yes, "C" drive is used for general case. It'll be created on any directory you installed Blink. Thanks.

 Anyone wants to test the fix, please mail to moh@eeye.com.

We found that the problem happens only in rare cases. And it was very hard for us to make it happen in house.

So anyone wants to try the hot fix, please drop me a mail.

I'll give you further instructions.

Thanks.

 Here's quick workaround until fix is out.

Open up "C:\Program Files\eEye Digital Security\Blink\Config\apiex.ini" using notepad and put following 3 lines to your apiex.dat. If you're using other mail clients, you can use their executable name in place of the filename.

*thunderbird.exe;;IPS;0

*outlook.exe;;IPS;0

*msimn.exe;;IPS;0

PS. I changed the apiex file name from .dat to .ini, because this is temporary solution.

moh:

 Here's quick workaround until fix is out.

What was the issue that you found?

Second of all, if a user enables debugging, can you leave it on until a issue is reproduced and then turn it off, or can you only have it enabled for so long before the log overwrites itself?

As of last week, after updating to the latest version of Blink, I too have the same problem with RoadRunnerRoadRunner (Time Warner) email using Outlook 2007 or Outlook Express. What's odd is that I can download the email headers no problem, but not the actual email. And I too can get Outlook to download all emails by Blink's Intrusion Protection.

The settings for this email account are basic:
* pop-server.roadrunner.com
* smtp-server.roadrunner.com
* Incoming port 110
* SMTP port 25
* SPA OFF
* SSL OFF
* authentication OFF
* encrypted connection NONE

Outlook will access all of my other non-RoadRunner accounts fine. It's just RoadRunner.

----------

Update: I took the advice above and added *outlook.exe;;IPS;0 -- not in the apiex.dat file as suggested, but at the top of apiex.ini instead.

Result: I restarted Blink and I can now download the email from RoadRunner once again.

 The problem was that we enhanced POP3 processor in this release. And looks like there are some conditions that we think the mail message is not fully retrieved and it was blocking the download of the message.

We found the problem and fixed it and doing internal tests. It should be released ASAP.

Anyone who wants to try this hotfix for the time being, please let me know.

Thanks.

Hi,

Regarding outlook POP3 issue.  To fix the mail retrieval issue that I have, I follow the "hotfix" Config\apiex.ini instructions given?

This will work now?  Or wait for the "official" fix (update)?  Do you have a projected readiness time/date?

Mike K

 The fix will be available soon. I think it will be within several days.

During the time you can use apiex.ini to avoid that problem.

 Tried fix to apiex.ini using "outlook express" in-lieu of "outlook".  Placed below the "rules" ################.  Did not work.  OE still attempts to retrieve e-mails seeing that there are "X" number to be recieved, but attempt to retrieve even the first of the "x" of e-mails fails and times out.  What must I do differently to accomplish this?

Mike

 Before releasing official release, we are providing beta release which is fixing the pop3 issues.

Please change your AutoUpdate configuration to point to beta link.

Go to menu and select Tools -> Check for Updates 

From the Auto-Update wizard, press "Configure" button.

Change the value inside Server input box to the following:

 https://update02.eeye.com/updateserverbeta/

And perform update by proceeding with the Auto-Update wizard.

After the successful update you can rollback the update server to the original value:

https://update02.eeye.com/updateserver/

Thanks for your patience.

That fixed the Thunderbird issue.

Thanks!

Smith,

     On another note, make sure you change back your update server to what it was before (otherwise you will not continue to get AV updates, etc).

I though about that before I switched to the patch URL and placed a copy of the original URL in a text file.

I just switched it back.

Thanks for the reminder.