Community forum

Please note that VisualCron support is not actively monitoring this community forum. Please use our contact page for contacting the VisualCron support directly.


matrixIII
2011-03-08T22:47:03Z
This is my first time setting IMAP4 trigger. Our exchange wasn't set up for IMAP before but all the related services are now started. I can connect to the IMAP account using Thunderbird.

Now, when I use the same credentials with VisualCron, I get the following...
3/8/2011 4:17:03 PM Err Trigger error: Error in Mail Trigger (1), ex: A0003 BAD Command received in Invalid state.

Any idea what could be going on? Does this have anything to do with SSL? If so then which of the following will work with VisualCron?

1. Set-ImapSettings -LoginType PlainTextLogin
2. Set-ImapSettings -LoginType PlainTextAuthentication
3. Set-ImapSettings -LoginType SecureLogin

Thunderbird does indicate that its connecting using 'STARTTLS'.

Any help would be appreciated!


EDIT: Thunderbird can also connect using the 'SSL' option instead of 'STARTTLS' but not using 'None'.

I found the following in your change logs..
Quote:

5.4.7 [2009-11-28] -FEATURE] Client/Server: Added TLS and explicit/implicit method for SMTP (Google SMTP requirements TLS+implict+port 465). Note, if you previously used SSL in IMAP/POP3/SMTP you need to select SSL in Encryption tab of Connection settings and press update on your Connection.


My problem could be that I am not seeing a "Encryption" tab in IMAP... It only exists in SMTP.

When I telnet to port 143 and issue command ". login <username> <password>", I get the same error back -- "BAD Command received in Invalid state"

Thanks


Sponsor
Forum information
Support
2011-03-10T21:46:59Z
This was later resolved by exposing a hidden property and changing to port 993.
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
matrixIII
2011-03-12T04:01:55Z
Thanks to Support for resolving this. The [Encryption] tab was missing in IMAP4. Setting it to "SSL" in the server config file and changing the port from default to 993 worked!

Thanks
Scroll to Top