question

JoshuaJLLogan-3344 avatar image
0 Votes"
JoshuaJLLogan-3344 asked 35247258 edited

"Send_an_email_from_a_shared_mailbox_(V2)" or similar do not allow for X-Entity-Ref-ID header rotation

Hello,

We currently have an on-premise mail server used within our API to send mails to our clients.
For our GMail users, if we do not generate a unique "X-Entity-Ref-ID" header per mail, GMail will automatically group mails together as a threaded "conversation".
This is very bad for our users as when they follow the "I forgot my password" process for example, the Password reset request mail will be grouped up with any previous request that was made possibly months/years ago, and users end up confused as to which mail is the most recent one.
Generating a unique "X-Entity-Ref-ID" for these types of emails is a perfect solution.

We recently migrated to Office 365 for business.
We can no longer use our previously coded solution using the SMTP Authentication protocol due to rate limitations on email sending (30 messages per minute, Recipient rate limit of 10,000 recipients per day) : https://docs.microsoft.com/en-us/exchange/troubleshoot/send-emails/smtp-submission-improvements#new-throttling-limit-for-concurrent-connections-that-submitmessages

We therefore would like to opt for an EventGridTopic + LogicApp solution which also makes sense with our future plans of migrating most automation services to EventGrid messaging.

However, the available connectors for Office 365 Outlook offer no means of setting the "X-Entity-Ref-ID" header, or requesting for the API to generate a new unique "X-Entity-Ref-ID" per mail send.

We're currently stuck, as we can't leverage SMTP Authentication which allows modifying the header to code the mail sending due to the rate limitations, and LogicApps don't offer any header customization at all.

Does anyone have any advice for how to proceed ?

Thank-you ahead of time.
Regards,

LOGAN Joshua

azure-logic-appsmicrosoft-graph-mailazure-event-grid
· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hi @JoshuaJLLogan-3344,
Developer issue, not desktop client issue. So I removed the Outlook tag here and added some related tags to better help solve your issue. Thanks for your understanding and support. Hope your issue could be resolved soon.

1 Vote 1 ·

1 Answer

PramodValavala-MSFT avatar image
0 Votes"
PramodValavala-MSFT answered JoshuaJLLogan-3344 commented

@JoshuaJLLogan-3344 While the action doesn't support custom headers itself and you could use the underlying Send Mail Graph REST API which supports including custom headers which you could call using the HTTP with Azure AD connector.

Also, please feel free to create a feature request to include support for custom headers in the action itself.


· 2
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Thanks. I'll give that a try and get back to you with the results.

0 Votes 0 ·

This indeed satisfies our requirements.
It's a shame the action itself doesn't allow for this as I'd expect it uses similar if not the same API under the hood, but at least we can get by now.

Thank-you for your assistance.

0 Votes 0 ·