Hi Support

I have a task set up with a POP3 email Trigger with a connection to my company email services (an external provider).

Quite often the trigger fails with an '-ERR [IN-USE] internal login failure' error (see attached screen shot). I have checked the server log as suggested in the dialogue, and that just says:

'10/05/2012 10:13:30 Err Error occured: Error in Mail Trigger (1), ex: -ERR [IN-USE] Internal login failure. Refer to server log for more information.
- retrying to connect (retries left: 0)'

I understand that it is failing perhaps because the email service is temporarily locked at the provider. I have tried various timeout and reconnect settings (currently at timeout '180' and reconnect attempts - 6) but it still errors, and in fact the Server Log doesn't seem to indicate that it is trying to reconnect (it always says 'retries left : 0' where I have specified 6 attempts).

Is there anything I can do to ensure this does not error at all and therefore the trigger will not fail?

Cheers

Andy

p.s. I should add that this does work most of the time if I run it manually so I know the connection details are correct.

I've given up on this functionality.
I've come up with a work-around by setting up my outlook with rules to look for strings in emails and print the emails to a file (trigger.txt) in a specific folder.
I then have a job triggered when it sees the 'printer.txt' file.
The first task in this job is a .net script that reads through the file, looks for specific strings and generates trigger files that the main jobs are triggered by.

Hi Trevinom

That sounds like a neat work-around but it would be far more beneficial if the direct email triggers could provide the functionality we need. Hopefully support can come up with a solution :-)

Cheers

Andy

Hi Support

I have a task set up with a POP3 email Trigger with a connection to my company email services (an external provider).

Quite often the trigger fails with an '-ERR [IN-USE] internal login failure' error (see attached screen shot). I have checked the server log as suggested in the dialogue, and that just says:

'10/05/2012 10:13:30 Err Error occured: Error in Mail Trigger (1), ex: -ERR [IN-USE] Internal login failure. Refer to server log for more information.
- retrying to connect (retries left: 0)'

I understand that it is failing perhaps because the email service is temporarily locked at the provider. I have tried various timeout and reconnect settings (currently at timeout '180' and reconnect attempts - 6) but it still errors, and in fact the Server Log doesn't seem to indicate that it is trying to reconnect (it always says 'retries left : 0' where I have specified 6 attempts).

Is there anything I can do to ensure this does not error at all and therefore the trigger will not fail?

Cheers

Andy

p.s. I should add that this does work most of the time if I run it manually so I know the connection details are correct.

We would appreciate if you had another client connected (but that leaves mail on the server). It would be interesting to know how long "down period" you have. I mean if 6 * 180 seconds is shorter than down period then we need to increase attempts.

We will look at the x number of attempts left. This is probably not a part of the problem but should be fixed anyway.

If you turn on Extended debugging a file called "mailtrigger.txt" will be saved in the log folder. This will contain info about the error if you are interested in that.

---

Hi Henrik

Actually, I think that is the problem! I have my mail client also monitoring the same account as I'm using for the Trigger. That said, it is automatically checking mail every 5 minutes so VC is checking more often so it should 'beat' the mail client.

I have switched on extended logging so I will check that next time it happens. I will also set up a dedicated email address just for VC so that should remove the conflict.

Will let you know what the log reports.

Cheers

Andy

Hi Henrik

Okay - just got the failure which generated the log entries. The 'mailtrigger.txt' file looks fine and doesn't report any errors:

+OK Dovecot ready.
USER xxxxxxxxxxx+mavensystems.co.uk
+OK
PASS xxxxxxxxxxxxxx
+OK Logged in.
Resolving server ...
Server: mail.mavensystems.co.uk
Port: 110
AuthType: AuthLogin
User: xxxxxxxxxxx+mavensystems.co.uk
Password: xxxxxxxxxxx
SSLConnection: False
SSLType: ConnectSSLAuto
Protocol: Pop3
SocksProxyServer:
SocksProxyPort: 1080
SocksProxyUser:
SocksProxyPassword:
ProxyProtocol: Socks5

Create socket InterNetwork,Stream,Tcp ...
Start to connecting ...
76.74.128.30, 110
Connected



However, the extended debugging in the server log shows :

10/05/2012 14:43:43 Err Error occured: Error in Mail Trigger (1), ex: -ERR POP3 protocol doesn't support the operation! - retrying to connect (retries left: 5)
10/05/2012 14:44:43 Err Error occured: Error in Mail Trigger (1), ex: -ERR POP3 protocol doesn't support the operation! - retrying to connect (retries left: 4)
10/05/2012 14:45:43 Err Error occured: Error in Mail Trigger (1), ex: -ERR [IN-USE] Internal login failure. Refer to server log for more information.
- retrying to connect (retries left: 3)
10/05/2012 14:46:43 Err Error occured: Error in Mail Trigger (1), ex: -ERR POP3 protocol doesn't support the operation! - retrying to connect (retries left: 2)
10/05/2012 14:47:43 Err Error occured: Error in Mail Trigger (1), ex: -ERR POP3 protocol doesn't support the operation! - retrying to connect (retries left: 1)
10/05/2012 14:48:43 Err Error occured: Error in Mail Trigger (1), ex: -ERR POP3 protocol doesn't support the operation! - retrying to connect (retries left: 0)
10/05/2012 14:49:43 Err Error occured: Error in Mail Trigger (1), ex: -ERR POP3 protocol doesn't support the operation! - exiting/deactivating Trigger (retries left: 0)
10/05/2012 14:49:43 Debug Mail trigger event has been ended, trigger: POP3 Trigger for Cutas
10/05/2012 14:49:43 Err Trigger error: Error in Mail Trigger (1), ex: -ERR POP3 protocol doesn't support the operation!
10/05/2012 14:49:43 Debug Trigger was expired and inactivated


So not sure if that provides any more information???

Cheers

Andy

Thanks, we will look into that. If you can provide us with login info to that server it would help a lot as well (support@visualcron.com).

---

Hi Henrik

I will set up a new 'test' account and try that to see if I still get the errors - if I do then I will email the account details to you.

Cheers

Andy

Ok,

please try the following:

1. turn Extended debugging off if you you have it on (Server tab->Log settings)
2. check use "default folder" in mail trigger

Do you still get an error?

---

Hi Henrik

These were the options I had set anyway so yes, 'default folder' does still create the error.

Cheers

Andy

Hi Henrik

I set up a dedicated POP3 test account with no conflict from my Mail Client, and I am still getting the errors.

I have sent an email to support with the test account credentials. If you need anything else then please let me know

Cheers

Andy

Thanks Andy,

we are getting the same error and it happens internally at connection level. We may need some days to figure out why this happens. Thank you for your patience.

---

Apparently this is a common error with dovecot:

http://www.directadmin.c...d.php?t=28942&page=1 
http://www.directadmin.c...t=internal+login+failure 

It seems to be the pop3 service dying on the remote end. Another one suggests that password file is in old format.

I suggest looking at pop3 server logs after this happens to get the exact reason.

---

Hi Henrik

Okay - I will raise a support ticket with my hosting service provider. In the meantime I have changed the protocol to IMAP rather than POP3 and will see if the problem still occurs. If not then I can just use IMAP instead.

Will let you know if I get any progress.

Cheers

Andy

I got another response from this support request. Here is his explanation:

It means that your mailbox is in use.
(somebody is downloading emails in it, accessing it by IMAP/POP3 or something similar)

It can happen if you have more clients accessing the same mailbox. It seems that your POP3 server allows only one client at the same time.
If you are configured this way there is no problem. (it happens if a client's login while another is logged in)

---

Hi Henrik

The email address I set up is a standalone address and is not defined to a Client at all, only a single Visual Cron connection - I suppose it receive's emails but that is the only activity i.e. Emails in, and VC reading it.

So far since changing the protocol to IMAP the problem hasn't re-occurred, though it is early days yet. Fingers crossed though.

Would it be possible to change the Email Trigger options so that the Trigger is never disabled if there is a problem with connecting? At the moment, if there is a problem the trigger is disabled which means you have to go back in to the job and enable it and that could easily be missed.

Cheers

Andy

Hi Support

Seems that there is a different problem now that I have switched to an IMAP4 email trigger. I am getting the following error in the server log file:

---

14/05/2012 09:05:05 Err Error occured: Error in Mail Trigger (2), ex: A socket operation failed because the destination host was down - exiting/deactivating Trigger (retries left: 0)
14/05/2012 09:05:05 Err Trigger error: Error in Mail Trigger (2), ex: A socket operation failed because the destination host was down
14/05/2012 09:05:05 Debug Trigger was expired and inactivated
14/05/2012 09:05:06 Err Trigger error: Error in Mail Trigger (2), ex: A socket operation failed because the destination host was down
14/05/2012 09:05:06 Debug Trigger was expired and inactivated

---

I then had another problem (which I don't think was related) that caused the Client to 'hang' which meant I had no clear indication that there was a problem:

---

14/05/2012 09:11:53 Debug Saving Jobs
14/05/2012 10:10:57 Info Job started: Ping mavenaa1
14/05/2012 10:10:57 Info Task started: Ping maven VPS (6354)
14/05/2012 10:10:57 Info Task completed: Ping maven VPS (6354)
14/05/2012 10:10:57 Info Job completed: Ping mavenaa1
14/05/2012 10:11:53 Debug Saving Jobs

---

So it seems as though it hung as VC was automatically saving Jobs.

Any other ideas?

Regards

Andy

The reason for hanging is probably something else. Like it is waiting for a reply from the VisualCron Server.

We have no detailed error handling in the Event Triggers like Email. I think you should request that as a Feature with all details you want to control. Only way right now is to increase retry times and retry interval.

---