[SalesForce] Does Messaging.SendEmail() not work in a Platform Event trigger context

I can't figure out why an email isn't being sent. I've got a Platform Event trigger which ultimately is supposed to send an email. Most of the code isn't directly relevant, but here's the surrounding code, called by the trigger handler (cut down for demonstration):

public static void sendEmails() {
    System.debug(Limits.getEmailInvocations());

    Messaging.SingleEmailMessage sem = new Messaging.SingleEmailMessage();
    sem.toAddresses = new List<String>{'myEmailAddress'};
    sem.subject = 'testsubject';
    sem.htmlBody = '<p>test Body</p>';
    Messaging.sendEmail(new List<Messaging.SingleEmailMessage>{sem});

    System.debug(Limits.getEmailInvocations());
}

Debug:

20:22:26.0 (273270760)|USER_DEBUG|[47]|DEBUG|0

20:22:26.0 (346734155)|USER_DEBUG|[55]|DEBUG|1

Yet no email is received (not in Spam either). It's a sandbox, with Deliverability set to "All Email". No exceptions are thrown and I've tried my personal & work email addresses. When executing the Email send code above anonymously, it arrives in my inbox just fine.

EDIT: After further investigation, I've found the following in our server logs:

Our system has detected that this message is 550-5.7.1 not RFC 5322 compliant: 550-5.7.1 'From' header has non compliant domain name. 550-5.7.1 To reduce the amount of spam sent to Gmail, this message has been 550-5.7.1 blocked.

So, now my question is…given that this is an Automated Process user and thus cannot be set to use an Org-Wide Email Address (there's no profile to enable on the address), how can I resolve this?

Best Answer

Limitation

Sadly, there is no apex email support from platform events. Per the documentation:

Sending an email message from a platform event trigger using the Messaging.SingleEmailMessage class is not supported. The email can’t be sent because the sender is the Automated Process entity, which has no email address.

Workaround

You can, however, send emails via email alert where the From Email Address is NOT "Current User's Email Address" but rather some other organization-wide email or default workflow user.

The reason, as outlined in this answer, "emails sent by the Automated Process user was "autoproc@YOURORGID" with no ".com" appended. This meant that Gmail would ignore it and the email wasn't being delivered."

In Apex, you might be able to use the SingleEmailMessage.setOrgWideEmailAddressId method to set the org-wide email and thereby the email be sent from a user other than the automated process user.

Related Solutions

[SalesForce] Queueable Apex not working in Platform Event Trigger

After struggling with this for longer than I'd like to admit, I found a method that enables us to test Platform Event Triggers that enqueue Queueable jobs. The magical method is:

Test.getEventBus().deliver();

What you need to do is call Test.getEventBus().deliver() after you have called EventBus.publish(platformEvents). Just make sure you do this between Test.startTest() and Test.stopTest()

The gotcha is that YOU MUST call Test.getEventBus().deliver() before Test.stopTest()

Here's some code to illustrate:

Test.startTest();

// Publish a platform event that will enqueue a `Queueable` job
EventBus.publish(new Some_Platform_Event__e(Foo__c = 'bar'));

// Deliver the platform event RIGHT NOW
Test.getEventBus().deliver();

// Let's see what happened
List<AsyncApexJob> asyncApexJobs = [
    SELECT Id, Status
    FROM AsyncApexJob
    WHERE JobType = 'Queueable'
];

// We have 1 Queueable job that has been Queued
System.assertEquals(1, asyncApexJobs.size());
System.assertEquals('Queued', asyncApexJobs[0].Status);

Test.stopTest();

// Now let's see what happened after stopping the test
asyncApexJobs = [
    SELECT Id, Status
    FROM AsyncApexJob
    WHERE JobType = 'Queueable'
    AND Id = :asyncApexJobs[0].Id
];

// The Queueable has completed!
System.assertEquals('Completed', asyncApexJobs[0].Status);

[SalesForce] Platform Event subscriber not sending email to gmail domain

We had a similar issue pertaining to email. What we found was that emails generated from Workflow were not reaching email addresses (specifically on the Gmail domain). Using the Email Log Files we determined that the sending user for emails sent by the Automated Process user was "rsandoval@ourorgid" with no ".com" appended. This meant that Gmail would ignore it and the email wasn't being delivered.

For this scenario the answer was to update the Email Alert's setting for "From Email Address" to use "Default Workflow User's email address" instead of "Current User's Email Address".

What is particularly interesting is that in each Org that uses the Automated Process user, the associated email is "Rsandoval@ourorgId". I'm guessing that "RSandoval" was the engineer that created the Automated Process global user when it was first created? Weird.