Just wondering if someone can help me understand how the emails that are sent from firstname.lastname@example.org are generated?
For some reason it looks like the mail protection service in our organization is flagging the links contained in emails that get generated by the Power Automate email that are sent.
Looking at the properties of the email it looks like the properties of the email it looks like the from address is being suffixed by something called sendgrid, so it resembles something like email@example.com.
Just wondering whether this seems normal? Is sendgrid at all related to the delivery of emails coming from power automate?
I had this happen to me around December. I was getting the emails from that address every 30 seconds at a certain time per day.
I spoke to the Support team about this. They had said my email somehow got into a Test DL by Microsoft. The issue is now gone. I no longer get these emails.
if this is a concern to you. I would suggest creating a ticket.
Ah, that's pretty interesting.
Thank you for the insight @Jcook , appreciate the speedy response :]
I think your suggestion sounds like a plan, I'll proceed to log a ticket with MS.
Just wanted to add some clarification to this - the 'Send an Email V3' notification uses SendGrid to mail and spoofs teh address firstname.lastname@example.org within the Header From.
If your email software is heavy-handed and looks very strictly at the Envelope From vs Header From on mails, then the discrepancy between Envelope from somereallylongbouncebackmailaddress.sendgrid.net and microsoft.powerapps.com will be flagged as potential spam/spoofing.
According to the documentation page, they cannot enable SPF auth currently:
"Notification emails may be treated by your email service as forging and unsafe, because SPF authentication is disabled. Due to security reasons we can't enable SPF now. If email verification is mandatory we recommend use regular email connectors: Outlook, Gmail, SMTP, etc."
What I have done to test as a workaround is to alter our mail interceptor and permit all mails sent with Header From email@example.com and have bypassed anti-spam checks from that header address.
You should be able to do similar to enable the mails to not get caught in the interim until SPF-auth is resolved by Microsoft.
Please 'Mark as Solution' if someone's post answered your question and always 'Thumbs Up' the posts you like or that helped you!
Many congratulations to the Season 1 2021 Flownaut Crew!
Check out our new profile badges recognizing authored solutions!
Check out the community blog page where you can find valuable learning material from community and product team members!