Stops checking emails...hangs

[hillgreg]

It seems that pop checker stops checking emails for me... I think it is an error in the pop process that doesn't time out.  I've tried restarting the service to no avail.  A computer restart, however, does work.
The following is the log for pop connector, with my having altered the email address

2007-12-06T01:17:43: Processing account email@domain.com on server 127.0.0.1
2007-12-06T01:17:43: 1 messages on server

2007-12-06T14:43:44: Could not delete Message 1 on POP Server, aborting download
2007-12-06T14:43:44: 1 messages processed

The large gap in time between the message check and the aborting download was the down time.  It seemed to have done the abort AFTER I had to restart the computer.

I checked the logs of my email server, and it shows a successful login on the pop account, but I don't have any further info at that end.

Is there a missing timeout?  Or is there a setting that I have missed?

Thanks.  Any help appreciated.
Greg

[Eclarsys Support]

Hello,

please set the log level to "debug" and check for other error messages. What kind of POP3 and SMTP server are you using? Maybe we can reproduce your setup here to better help you.

Did you restart the POP3 Server, SMTP Server or the machine where PopGrabber is installed?

Regards,

Eclarsys Support

[hillgreg]

Thanks for the reply.  I have already set the logging to debug, but unfortunately I have to wait until it happens again.  I'm not sure what the sticking point was, as it worked fine after a total system restart.  I had tried to just restart the popgrabber service to no avail.
I am using your program to check argosoft's email program, then forward it to my exchange server.  It does, for one person's service, also go through an antispam program called zaep (sort of acts as a Pop relay, and should be transparent to your program).  Most pop users are on port 115, the zaep user is set to 111.  The exchange server is on port 27.  It actually was on the zaep user where it hung.  But if zaep was the problem, shouldn't your program have timed out at some point?

Hope this helps.
Thanks for the reply
Greg

[Eclarsys Support]

It is definitely strange that the program hung, since it does have a timeout on each send or receive operation (of around 10 seconds), and all errors are normally caught by the main program. I also cannot understand why a server restart was necessary to correct the problem. By stopping the service all connections are automatically closed.

If the problem happens again we may be able to trace it using the log file.

Regards,

Eclarsys Support

[hillgreg]

Happened again.
There was a large email that it was trying to retrieve (7mb), but the pop server is on the same computer, and I would think would transfer very quickly, and there is no threat of connection loss.  This time, stopping and restarting the service DID resume the email checking.  Here is the popgrabber log
2007-12-10T00:53:12: Disconnected from POP Server 127.0.0.1
2007-12-10T00:53:12: Finished Processing 4 accounts.
2007-12-10T00:55:12: Processing account email@domain.com on server 127.0.0.1
2007-12-10T00:55:12: Login to POP Server 127.0.0.1 on port 111
2007-12-10T00:55:12: Using regular authentication
2007-12-10T00:55:12: 1 messages on server
2007-12-10T00:55:12: Processing email 1

Then stops. 
I don't know if this helps.  The port of 111 is correct, as this is the account that is going through the zaep antispam relay.
Appreciate any help.
Greg

[Eclarsys Support]

Hi again,

we will have to test this more thoroughly. Which version of zaep are you using? Anything older than 2.0.0.3 will have compatibility problems with PopGrabber because of the way it handles line feeds.

If you are using anything newer, we will install it and test it in our server.

Regards,

Eclarsys Support

[hillgreg]

Thanks.  Using zaep version 5.1.0.3
Greg

[Eclarsys Support]

We haven't been able to reproduce the problem with Zaep and PopGrabber today, however, we did notice that the connection was timing out sometimes on large emails and this probably leads to the problem you are having. Strangely, this problem occurred in our tests only when PopGrabber was installed in the same machine as the POP3 Server. By increasing the connection timeout the problem disappears.

PopGrabber release 1.0.3 is available in the customer area, please try this version and let us know if it solves your problems. Apart from the connection timeout being increased, some small bugs in the installer were fixed and Windows Vista compatibility improved.

Regards,

Eclarsys Support

[hillgreg]

So far so good.  Thanks so much for the very prompt action.
Greg