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


GaryVS
2013-01-02T16:58:56Z
I would like to see a connection option for Office 365 online. We are moving away from in house Exchange servers. Currently we are wrapping calls via EWS for inhouse apps but for Visual Cron we have not been able to connect to 365 Exchange servers over https.

EDIT: This is in the context of email connections.
Sponsor
Forum information
Support
2013-01-02T17:34:20Z
What kind of operations would you like to see over Office 365?
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
GaryVS
2013-01-02T18:49:09Z
At this time we, for our immediate needs is simple email but picking the Office 365 servers.

The email functionality we would really want is the ability to pass different users credentials so that the mail sent appears in their email sent box. This would handle the standard IT notification account as well as 'Send on Behalf' functionality. This can be done with EWS Managed api.

Attachments: We don't use out of VC but I could see a use if we packaged log files, but that is me finding a problem to fit a solution. Others might want that.

Everything else we use we have already put together a WCF wrapper over the EWS managed API and use VC's web service calls for. This is for calendar items and contact management. So we wouldn't need, at this time, VC to do anything like that.



Support
2013-01-03T12:19:34Z
You are talking about this for sending email?

http://msdn.microsoft.co...628%28v=exchg.80%29.aspx 

Does not SMTP work for you?
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
GaryVS
2013-01-03T15:58:08Z
Yes, after further testing last night things are working fine with SMTP now, it turns our 365 indicates TLS as the required encryption method on their site but it had to be SSL in VC. I had received 77777 errors and attributed that to VC incorrectly.

And I suppose I was being lazy in wanting the ability to impersonate a user in VC for mail. Last night after discussing our needs we have decided to forgo attempting VC to send on behalf of users and continue on our path to more into WF/WCF. We have been making great progress with the api they have, it is a small step to handle email. Plus other departments need this and they don't have VC, so this gives us more traction with development efforts.

Thanks for your help and consideration of new functionality, even if it was from submitter's ignorance.
Support
2013-01-04T11:08:57Z
No problem - we are interested in investing time in new Features.
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
Scroll to Top