Hello. At my organisation we use G Suite (now Google Workplace) for emails. I've just set up an error path to send me an email if there's an error with the workflow. It's working great. However with Gmail to get SMTP mail working you have to enable less secure apps. But Google will automatically turn off less secure apps if it hasn't been used in a while. So if no error emails from my workflow get sent in a while less secure app access will turn off and then I'll have to manually re-enable it to ensure if/when an error occurs I'll get an email about it.
An obvious workaround would be to use a different email provider to use SMTP mail with, but I'd prefer to use my work email with FFAStrans.
So potentially the best solution would be to have an OAuth option to connect the email to FFAStrans. I understand this would likely be a lot of work and would very likely be a very low priority feature. But just thought I'd let you know a good use case for it. I also know I could use localhost to send the email, but that might be more likely to end up in spam.
Also having a reply-to field in the 'Send e-mail' processor would be handy.
Option for OAuth with SMTP mail
Re: Option for OAuth with SMTP mail
Hey @Ben
interesting request about gmail and Oauth, i had a quick look into that. Due to it's complexity in the setup, i come to the conclusion that we should not attempt to do this unless the most used email tools out there support it, e.g. blat.exe. The reason for this is mainly because i feel it is kind of impossible to guide users how to set it up and it feels like it would need frequent updates in documentation and the code that does the authorisation.
I guess you would be the only one using that feature for a veeery long time.
An easy proposal for workaround would be to use e.g. the webinterface and a scheduled job to kick off a simple workflow that sibly sends one mail daily in order to prevent google from turning off less secure apps.
We will still need @admin to comment on the "reply-to" thing and/or the above.
interesting request about gmail and Oauth, i had a quick look into that. Due to it's complexity in the setup, i come to the conclusion that we should not attempt to do this unless the most used email tools out there support it, e.g. blat.exe. The reason for this is mainly because i feel it is kind of impossible to guide users how to set it up and it feels like it would need frequent updates in documentation and the code that does the authorisation.
I guess you would be the only one using that feature for a veeery long time.
An easy proposal for workaround would be to use e.g. the webinterface and a scheduled job to kick off a simple workflow that sibly sends one mail daily in order to prevent google from turning off less secure apps.
We will still need @admin to comment on the "reply-to" thing and/or the above.
emcodem, wrapping since 2009 you got the rhyme?
Re: Option for OAuth with SMTP mail
Yes you're right in that I may be the only person to benefit from it, which I totally understand. I want you guys only working on features that are important to a lot of people. But thanks for looking into it. I like your idea of a scheduled job to send of an email each day.
Thanks for your help.
Thanks for your help.
Re: Option for OAuth with SMTP mail
Hi Ben,
Adding "Reply to" is a hell of a lot easier than dealing with the OAuth stuff, so I agree with @emcodem here.
But yes, we can add "Reply to"
-steinar
Adding "Reply to" is a hell of a lot easier than dealing with the OAuth stuff, so I agree with @emcodem here.
But yes, we can add "Reply to"
-steinar
Re: Option for OAuth with SMTP mail
Hey Steinar,
Wonderful, thank you
Wonderful, thank you