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.


paulnus
2019-05-08T22:08:02Z
Hello,
Running into an issue on both 8.3.6 and 8.5.0 with setting up an IMAP4 connection to Office365. I've sleuted through some of the older support forum items and could not solve the immediate error or issue I'm having.

I am getting a "Unhandled error: A0002 BAD Command Argument Error. 12" when testing or trying to connect to an Office365 mailbox.

I have logged into the mailbox, so I suspect the creds are correct.

Server
Address: outlook.office365.com
Port: 993
Timeout: 60
Code Page: Windows-1252

Authentication
Username: myemail@domain.com
Pass: MySuperSecurePass

SSL/TLS
Cryptographic protocol: SSL
Allowed SSL/TLS versions: SSL version 2 & SSL version 3

Thoughts?
Sponsor
Forum information
Support
2019-05-09T08:29:26Z
Try the Test button in the Connection if it works. If not it provides some useful output.
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
paulnus
2019-05-09T15:17:09Z
Originally Posted by: Support 

Try the Test button in the Connection if it works. If not it provides some useful output.



Same error...
"Connection Test Failed: Unhandled error: A0002 BAD Command Argument Error. 12"
Support
2019-05-09T19:01:44Z
Originally Posted by: paulnus 

Originally Posted by: Support 

Try the Test button in the Connection if it works. If not it provides some useful output.



Same error...
"Connection Test Failed: Unhandled error: A0002 BAD Command Argument Error. 12"



Not 100% sure but maybe this post points to the right direction.

https://social.technet.m...2quot?forum=exchange2010 

We could test from here but then you need to send us the Credentials to support@visualcron.com


Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
Knighty
2019-05-16T20:42:20Z
Originally Posted by: paulnus 

Hello,
Running into an issue on both 8.3.6 and 8.5.0 with setting up an IMAP4 connection to Office365. I've sleuted through some of the older support forum items and could not solve the immediate error or issue I'm having.

I am getting a "Unhandled error: A0002 BAD Command Argument Error. 12" when testing or trying to connect to an Office365 mailbox.

I have logged into the mailbox, so I suspect the creds are correct.

Server
Address: outlook.office365.com
Port: 993
Timeout: 60
Code Page: Windows-1252

Authentication
Username: myemail@domain.com
Pass: MySuperSecurePass

SSL/TLS
Cryptographic protocol: SSL
Allowed SSL/TLS versions: SSL version 2 & SSL version 3

Thoughts?



Hi - you should switch to using the EWS Exchange method, the url for which would be

outlook.office365.com/EWS/Exchange.asmx
port 443 (https)
TLS

outlook office 365 smtp and imap4 from vc is problematic na doften yields unhandled exceptions, switching to EWS worked fime for me and also circumvented opening additional ports in our infrastructure.
Knighty
2019-07-01T16:58:08Z
Originally Posted by: Knighty 

Originally Posted by: paulnus 

Hello,
Running into an issue on both 8.3.6 and 8.5.0 with setting up an IMAP4 connection to Office365. I've sleuted through some of the older support forum items and could not solve the immediate error or issue I'm having.

I am getting a "Unhandled error: A0002 BAD Command Argument Error. 12" when testing or trying to connect to an Office365 mailbox.

I have logged into the mailbox, so I suspect the creds are correct.

Server
Address: outlook.office365.com
Port: 993
Timeout: 60
Code Page: Windows-1252

Authentication
Username: myemail@domain.com
Pass: MySuperSecurePass

SSL/TLS
Cryptographic protocol: SSL
Allowed SSL/TLS versions: SSL version 2 & SSL version 3

Thoughts?



Hi - you should switch to using the EWS Exchange method, the url for which would be

outlook.office365.com/EWS/Exchange.asmx
port 443 (https)
TLS

outlook office 365 smtp and imap4 from vc is problematic na doften yields unhandled exceptions, switching to EWS worked fime for me and also circumvented opening additional ports in our infrastructure.



Perfect, Thanks!! that worked lovely 🙂
Scroll to Top