Updated the app "Mail with OAuth2.0", and it seems like now mail with multiple recipients delimited by semicolon fails.
Any mail with one recipient succeeds, but if there is a semicolon in the recipient field, the mail fails with the message:
"Error while sending a mail: At least one recipient is not valid."
They are valid though.
Anyone else with this problem?
Mail With OAuth2.0
- billy.olvestad
- Member
- Posts: 66
- Joined: Mon Nov 19, 2018 10:08 pm
- Location: Sweden
- Contact:
-
paul_barker
- Member
- Posts: 32
- Joined: Thu Dec 08, 2022 2:25 pm
Re: Mail With OAuth2.0
I have exactly the same issue, have just started to change over from the inbuilt email app to the oauth2 version and it fails when there are multiple email addresses separated by a semicolon which works perfectly in the old email app. This is going to be a big issue as this is how some of our data come from our MIS and I have hundreds of instances of the email app too change over. Did you find as solution?
- billy.olvestad
- Member
- Posts: 66
- Joined: Mon Nov 19, 2018 10:08 pm
- Location: Sweden
- Contact:
Re: Mail With OAuth2.0
I ended up using the app "stringsplitter" to split the list of recipients on the semicolon and then the app "duplicate" to create copies of the job with each recipient on it's own. So a hack, but a hack that works.
-
paul_barker
- Member
- Posts: 32
- Joined: Thu Dec 08, 2022 2:25 pm
Re: Mail With OAuth2.0
Thanks Billy that works. Since I posted I have also found that if you use the String Replace app and replace the semicolon with \n (a line break) that then allows it send the email with the original private data key to all the recipients.
- billy.olvestad
- Member
- Posts: 66
- Joined: Mon Nov 19, 2018 10:08 pm
- Location: Sweden
- Contact:
Re: Mail With OAuth2.0
Ok. Good to know. Thank you.