Test email not working

Oliver Häusler 0 Reputation points
2024-05-12T09:52:45.2733333+00:00

I have

  • configured a domain (SPF, DKIM, DKIM2 all showing green)
  • connected it to communication services
  • created a suppression list
  • etc.

and all seems good but when I go to

  • Try email to send a test email

it says

  • "Email successfully queued"
  • and after a few seconds "Email sent successfully!"

but there is no email anywhere:

  • not under Activity or in the logs
  • not in my inbox
  • not in spam

When I configured this a few weeks ago, nothing seemed to work. Now, as M$ seems to have fixed their stuff, email still isn't working. What else can I check?

Azure Communication Services
Azure Communication Services
An Azure communication platform for deploying applications across devices and platforms.
704 questions
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. Oliver Häusler 0 Reputation points
    2024-05-12T10:55:32.8766667+00:00
    2za0JJUxS-JS.js:177 Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'id')
        at t.<anonymous> (2za0JJUxS-JS.js:177:40667)
        at yrrgBoMFvnlc.js:17:4222
        at Object.next (yrrgBoMFvnlc.js:17:4327)
        at yrrgBoMFvnlc.js:17:3232
        at new Promise (<anonymous>)
        at __awaiter (yrrgBoMFvnlc.js:17:2977)
        at t.showServiceDropdown (2za0JJUxS-JS.js:177:40282)
        at t.<anonymous> (2za0JJUxS-JS.js:177:6484)
        at yrrgBoMFvnlc.js:17:4222
        at Object.next (yrrgBoMFvnlc.js:17:4327)
        at yrrgBoMFvnlc.js:17:3232
        at new Promise (<anonymous>)
        at __awaiter (yrrgBoMFvnlc.js:17:2977)
        at t.initialize (2za0JJUxS-JS.js:177:6010)
        at t.<anonymous> (2za0JJUxS-JS.js:178:20578)
        at yrrgBoMFvnlc.js:17:4222
        at Object.next (yrrgBoMFvnlc.js:17:4327)
        at a (yrrgBoMFvnlc.js:17:3034)
    11:41:29.506 nkFSANKVecM1.js:40 [Microsoft_Azure_Support]  11:41:29 AM GenericFlightData Flight expression by tag name AutoSuggestFlights for trackingId: 366cb2eb-a966-4bf7-a832-139dd26e8a03 Failed message: Cannot read properties of undefined (reading 'payload')
    name: TypeError
    stack: TypeError: Cannot read properties of undefined (reading 'payload')
        at t.isGenericFlightPayloadDto (https://afd-v2.hosting.portal.azure.net/azuresupportextension/Content/Dynamic/nkFSANKVecM1.js:78:2544)
        at t.<anonymous> (https://afd-v2.hosting.portal.azure.net/azuresupportextension/Content/Dynamic/nkFSANKVecM1.js:78:2239)
        at https://portal.azure.com/Content/Dynamic/yrrgBoMFvnlc.js:17:4222
        at Object.next (https://portal.azure.com/Content/Dynamic/yrrgBoMFvnlc.js:17:4327)
        at a (https://portal.azure.com/Content/Dynamic/yrrgBoMFvnlc.js:17:3034)
    t @ nkFSANKVecM1.js:40
    11:41:29.508 SLSnxCCvRau1.js:1 [Microsoft_Azure_Support]  11:41:29 AM Microsoft_Azure_Support 0 Microsoft_Azure_Support: Flight expression by tag name AutoSuggestFlights for trackingId: 366cb2eb-a966-4bf7-a832-139dd26e8a03 Failed Object message: Cannot read properties of undefined (reading 'payload')
    name: TypeError
    stack: TypeError: Cannot read properties of undefined (reading 'payload')
        at t.isGenericFlightPayloadDto (https://afd-v2.hosting.portal.azure.net/azuresupportextension/Content/Dynamic/nkFSANKVecM1.js:78:2544)
        at t.<anonymous> (https://afd-v2.hosting.portal.azure.net/azuresupportextension/Content/Dynamic/nkFSANKVecM1.js:78:2239)
        at https://portal.azure.com/Content/Dynamic/yrrgBoMFvnlc.js:17:4222
        at Object.next (https://portal.azure.com/Content/Dynamic/yrrgBoMFvnlc.js:17:4327)
        at a (https://portal.azure.com/Content/Dynamic/yrrgBoMFvnlc.js:17:3034)
    a @ SLSnxCCvRau1.js:1
    

    This doesn't look like an error on my side. Looks more like insufficient error handling.


  2. ajkuma 22,766 Reputation points Microsoft Employee
    2024-05-16T10:11:13.8366667+00:00

    @Oliver Häusler , Thanks for the follow-up and sharing additional info.

    Regarding the error codes. Sending emails is async operation, and the 202 means that your request has been accepted and you can get the delivery result by either log diagnostic or event grid, however, when the email is added to the suppression list, typically, you will start to receive the email drop error if all the recipients in the suppression list and email is dropped.

    For the logs to return values, you need ensure that you have enabled the Log Diagnostic and make sure it's being saved into Log Analytics workspaceUser's image

    Navigate to the ACS resource:

    1. Go to "Diagnostic settings" blade
    2. Select "+ Add diagnostic settings"
    3. Ensure that you selected email logs

    User's image

    and that the destination is set to Log Analytics

    User's image

    After enabling the above setting', the email logs will be saved and can be found under the Log Analytics or Logs blade under the ACS resource, and you should be able to see the suppression reason (SmtpStatusCode and EnhancedSmtpStatusCode). It may take a while for the logs to appear.

    Just to highlight. Need to wait for the cool down period until that particular email being removed from the suppression list automatically which can take up to 2 weeks depending on how many times one tried to send emails to that alias.
    Managed suppression list | lifecycle of email addresses that are suppressed

    --
    If the answer helped (pointed, you in the right direction) > please click Accept Answer

    0 comments No comments