Jump to content


Photo

ALE Not Checking email


  • Please log in to reply
9 replies to this topic

#1 csapp

csapp

    Newbie

  • Members
  • Pip
  • 5 posts

Posted 05 November 2014 - 09:42 PM

I've setup ALE to check a pop3 account for remote control. I get notification of the locked out email but when I reply with the passcode nothing happens. I check the email account that ALE should be checking and all the emails are still in the inbox. I've tested this install on 2 devices and both installations have the same results.

#2 jeffb

jeffb

    Advanced Member

  • Administrators
  • PipPipPip
  • 384 posts
  • Gender:Male

Posted 05 November 2014 - 11:04 PM

csapp,

Could you please take a screenshot of the remote control settings and locate the alservice.log file from the products install directory and upload both to www.netwrix.com/upload and put Forum-ALE Not Checking Email in the subject?

-Jeff

#3 csapp

csapp

    Newbie

  • Members
  • Pip
  • 5 posts

Posted 06 November 2014 - 01:17 AM

Files uploaded

#4 jeffb

jeffb

    Advanced Member

  • Administrators
  • PipPipPip
  • 384 posts
  • Gender:Male

Posted 07 November 2014 - 12:43 PM

csapp,

Sorry for the delay. I am attempting to get some extended tracing from development as the exception being thrown isn't being presented in the tracing.

-Jeff

#5 csapp

csapp

    Newbie

  • Members
  • Pip
  • 5 posts

Posted 11 November 2014 - 08:22 PM

csapp,

Sorry for the delay. I am attempting to get some extended tracing from development as the exception being thrown isn't being presented in the tracing.

-Jeff


Jeff, Have we found out anything on the exception?

#6 dsmirnov

dsmirnov

    Advanced Member

  • Root Admin
  • PipPipPip
  • 58 posts
  • Gender:Male

Posted 13 November 2014 - 07:19 PM

Jeff, Have we found out anything on the exception?


csap,

We are still working on it.

The thing is that exception message was just a general message, so we are looking for a way to extended it and find out what is going on in details.

For now it looks like the product can connect, but cannot read emails in the mailbox.

#7 dsmirnov

dsmirnov

    Advanced Member

  • Root Admin
  • PipPipPip
  • 58 posts
  • Gender:Male

Posted 21 November 2014 - 04:14 PM

Jeff, Have we found out anything on the exception?


csapp,

upon further research we found that the exception you have might be caused by SSL options set for POP3.
Is it set to require SSL connection?

Also, could you pleas e extend the product tracing for the maximum level by doing the following:

(1) Stop the Netwrix Account Lockout Examiner service via Services snap-in,
(2) Run Registry Editor (regedit),
(3) Go to HKLM\Software\[Wow6432Node]\NetWrix\Account Lockout Examiner (Wow6432Node only for x64 OS),
(4) Create a new DWORD called "trace_settings" with value of 3FFFF hexadecimal,
(5) Navigate to the Tracing subfolder of the Account Lockout Examiner installation directory,
(6) Delete or rename existing ALEService.log,
(7) Start the Netwrix Account Lockout Examiner service via Services snap-in,
(8) Reproduce the issue.

#8 csapp

csapp

    Newbie

  • Members
  • Pip
  • 5 posts

Posted 21 November 2014 - 08:07 PM

csapp,

upon further research we found that the exception you have might be caused by SSL options set for POP3.
Is it set to require SSL connection?

Also, could you pleas e extend the product tracing for the maximum level by doing the following:

(1) Stop the Netwrix Account Lockout Examiner service via Services snap-in,
(2) Run Registry Editor (regedit),
(3) Go to HKLM\Software\[Wow6432Node]\NetWrix\Account Lockout Examiner (Wow6432Node only for x64 OS),
(4) Create a new DWORD called "trace_settings" with value of 3FFFF hexadecimal,
(5) Navigate to the Tracing subfolder of the Account Lockout Examiner installation directory,
(6) Delete or rename existing ALEService.log,
(7) Start the Netwrix Account Lockout Examiner service via Services snap-in,
(8) Reproduce the issue.



I've tried using SSL enabled but it still doesn't work. I've extended tracing and uploaded the new log file.

#9 dsmirnov

dsmirnov

    Advanced Member

  • Root Admin
  • PipPipPip
  • 58 posts
  • Gender:Male

Posted 16 December 2014 - 06:55 PM

I've tried using SSL enabled but it still doesn't work. I've extended tracing and uploaded the new log file.


Csapp,

Sorry for the delayed reply.

We had to get access to iMail test server to verify.
Actually the issue is in the reply iMail returns.

When connecting to iMail via POP3, the server response is:

+OK X1 NT-POP3 Server %domain% (IMAil %ver%)

The issue here is that Account Lockout Examiner parses all messages in brackets as error messages, and throws an exception.

That is why your log has the server response as a text of error message which confused us.

We are looking to fix this in one of future versions.

As a workaround you can just change the Hello message.
To do it:
  • in iMail console go to Services
  • Select POP3 service and click Configure Services button
  • Under General options specify Hello message. It can be any, just make sure no brackets
  • Save changes
  • Restart the POP3 service

Hope this helps

#10 csapp

csapp

    Newbie

  • Members
  • Pip
  • 5 posts

Posted 16 December 2014 - 07:36 PM

This worked perfectly after changing the Hello message. Thanks for your help!




0 user(s) are reading this topic

0 members, guests, anonymous users