Skip to main content

Hi,

I’m experiencing an issue where the double opt-in confirmation email is not being sent, even though everything appears to be correctly configured.

Here’s what I’ve already verified:

Form Setup

  • Using a Klaviyo-hosted flyout form (not custom coded).

  • Form is correctly connected to the intended list.

  • After submission, the form proceeds to the next step as designed.

List Configuration

  • Double opt-in is enabled on the list.

  • A confirmation email template is live.

  • The list is actively used, and members are being added (but remain in "Never Subscribed" status).

Domain & Email Settings

  • Branded sending domain is verified (DNS settings for SPF, DKIM, DMARC, and Klaviyo verification are all passing).

  • Emails are sent from the verified subdomain.

  • No conflicting sender address is in use.

Testing & Issue

  • Tested with multiple new email addresses.

  • None receive the confirmation email.

  • As a result, welcome flow does not trigger due to “Never Subscribed” status.

I've followed all available documentation and forum suggestions. Still, the confirmation email is never delivered.

 

Would really appreciate support or insights — is there a setting that could be causing this?

 

Thanks in advance!

Hi ​@jenniemily,

From what you’re describing, it appears that you’ve done a good job setting up your form and connecting it to your list. You may have already checked this, but I don’t see it listed above, but did you check your spam folder or promotions tab to see if the double opt-in confirmation landed in either of those areas, rather than your primary inbox? When working with new accounts especially, I’ve noticed that the double opt-in email can occasionally land in spam. 

Also, have you tried testing this with different emails from different domains? I’d recommend testing again from your email domain, and after that, submitting an gmail.com email, then an outlook.com email, ect, to see if this issue is localized to one email domain, or many different ones.

Let me know if this helps, or if the issue persists.


Hi,

I actually upgraded my plan to get help and the customer service representative finally found a solution. Here is a brief summary of the solution:

 

DMARC is probably not working because your domain's DMARC policy has the aspf=s and adkim=s flags:

Update the DMARC policy so that it is in relaxed alignment mode rather than strict (e.g., adkim=r;aspf=r)

By updating the rules to a more lenient form, you can send messages from any sender address that is consistent with the root domain. This means that you can continue to use hello@xxxx.com address as the sender address without any problems.

 

I followed this advice and changed the DMARC policy, after which all messages started going through normally.


Reply