Since upgrading to office 365 I have been unable to connect using the various ‘use microsoft outlook’ to rad and send emails. How do I configure to send and receive with outlook? Any ideas? It sounds as though Office 365 is not supported ATM.
I do have outlook installed on the local computer which connects fine but the option to select is still grayed out.
You are correct that Outlook through Office 365 is not supported at this time. There are ways to work around this limitation.
Email Input
First of all, instead of using Outlook you can still capture emails using POP3.
If that’s not an option for you, then it’s possible to configure Outlook to drop files in folders when certain emailing conditions are met. You’d then configure your processes to have “Folder Capture” inputs instead of “Email Input” inputs. We have an internal guide prepared on this, if you’re interested.
Email Output
The plugin that produces email output through Connect is called the “Create Email Content” plugin. The “Send Email” plugin is a legacy plugin that is included in Connect’s Workflow because Connect’s Workflow it is designed to be backwards-compatible when upgrading from Suite to Connect.
The Create Email Content plugin sends emails over SMTP, and it supports TLS encryption. If what you’re looking for out of sending through Outlook is to verify sent items, what you could do instead is have the sender also be a bcc recipient. So instead of checking the sent items, those emails would appear in the inbox. The bcc recipient of course doesn’t have to be the sender and you can easily set up rules in Outlook to filter those emails into a specific folder, instead of cluttering the main inbox.
The Send Email plugin supports SMTP emailing, but does not support TLS encryption.
If you want to send an email without going through the Connect plugins, and your email server requires TLS encryption, then your last option would be to send the email through a script using the “Run Script” task. We have script examples that we could provide, if you’re interested.
Many thanks for your reply it was very helpful. I do us Sparkpost for sending emails which works well and I do use both the send email options. The main problem is the incoming where Office 365 pop3 settings don’t work due to he security so I was needing to do that locally. It is a shame that the option to just select use Microsoft outlook does not appear to work anymore as that worked well. The guide and examples you have would be very useful to help me sort this.
I’m going to be looking into getting the “Capture emails from any Outlook version” guide made publicly available, but for the meantime if you provide me with your email address I can send it to you personally.
I have set up the outlook folders as suggested and it works well - the workflow picks up the file and creates the metadata required. As I mentioned before I manage to be able to send emails using the legacy ‘Send Emails’ plug in but I am having problems using the Create Email Content plugin. When I try in the design the email sends OK but in workflow I keep getting the error - unconfigured sending domain <example.com> and I don’t know where this domain is set. In the designer the files send fine and are configured via the WIndows|Preferences|General tab but I cannot get this to work for workflow.
When I test the configuration by clicking Test SMTP settings on the Email Info tab of the Create Email Content plug in I get 5.7.1 Unconfigured Sending Domain <example.com>.When I run the workflow then the the message I get back from Sparkpost is:-
The Preferences are set for the preferences|Behaviour|OLConnect and also in the Email Info tab of the plug in and you can set the from address but not the sending domain. Any ideas on this? This also applies when trying to get the OLsend example to work.
Thanks for you ongoing help with this one - I should have said that I have set the sender address field correctly and the other settings in the plug in. I should have attached a screen shot - which I have done now. I should also mention that this is a test and development licence - I don’t know of that makes any difference. Also attached is the feedback from spark post that shows the sender address. I really don’t understand where the sender address is coming from.
One other thing you may consider is using a proxy between PlanetPress and Office365. I’ve seen STunnel successfully used for this. STunnel could potentially run on the same server as PlanetPress providing the secure “tunnel” to O365 servers that PlanetPress needs for email capture (POP3) and email send (SMTP). The process is transparent to PlanetPress as it thinks it’s dealing with a local server. This would avoid having to use Outlook all together (if that’s important).
Here are some configurations that should work for STunnel. (Adapted from here)