All Collections
Best Practices for Email marketing
Update your email settings per the new Google and Yahoo! requirements
Update your email settings per the new Google and Yahoo! requirements
Updated yesterday

Please be aware that as of February 1, 2024, Gmail and Yahoo! require domain authentication and a DMARC record for sending emails to customers from a branded email address.

In the absence of action, your sender email will be automatically changed to '[email protected]' to meet the minimum requirements, ensuring uninterrupted email communication with your customers.

Changing your sender email address

The sender email is the one your customers see and engage with. It appears in the From field of automatic notification emails, order confirmations, and any marketing emails sent from your Marsello account.

Some domains may demand additional authentication, failing which your sender email address may show 'via' or as '[email protected]'.

If you need to update your sender email address, follow this guide.

Ensure you take the necessary actions to authenticate your domain and set up a DMARC record to comply with the new requirements from Gmail and Yahoo, maintaining seamless communication with your customers.

Authenticating your third-party domain

If you're using a third-party domain, it is crucial to authenticate your sender email address. This prevents your email messages from being marked as spam and ensures their successful delivery to your customers.

To authenticate your sender email address, add the following records to your third-party domain:

  • CNAME record

  • DMARC record

Here are some instructions for editing DNS records with popular domain providers. If your service isn't listed here, log in to your provider's site and search their help articles, or contact their customer support team.

You can then authenticate your changes within the Marsello app by following our guide on this page. Please note that changes to your CNAME or DMARC records may take 24 hours to take effect.

Configure your DMARC policy (via your domain provider)

DMARC (Domain-based Message Authentication, Reporting, and Conformance) is an email authentication protocol designed to enhance the security of email domain owners by mitigating email spoofing and unauthorized use of their domain.

When configuring a DMARC record, it allows inbox providers to determine how to handle emails originating from your domain that do not pass SPF and DKIM checks. Additionally, DMARC provides a reporting mechanism for domain owners to gain insights into how frequently recipient servers worldwide receive emails from their domain, along with the percentage properly authenticated.

To set up a DMARC policy, add a TXT record in your DNS provider settings, specifying a value that can include the following semicolon-separated properties:

  • v: DMARC version.

  • p: Policy type dictating the action for non-passing emails. Options include:

    • none: Collect feedback and gain visibility into email streams without affecting existing flows.

    • quarantine: Filter non-passing emails into the recipient's quarantine.

    • reject: Bounce non-passing emails.

  • sp: Apply a policy to a subdomain of the DMARC record.

  • pct: Percentage of total unique sends that failed authentication to apply the policy to. For instance, if your DMARC record includes p=reject; pct=25, and 100 emails fail authentication, only 25 will be bounced, while the remaining 75 will be delivered to recipients. Defining this property helps gradually implement your authentication policy to ensure it functions as intended. Note that certain inbox service providers may ignore this parameter.

  • ruf & rua: Optional parameters specifying an email address to send DMARC reporting data to, provided in URI mailto format (e.g., mailto:[email protected]). Reporting data sent varies based on the parameter:

    • rua: Aggregate report of all your domain traffic.

    • ruf: Failure reporting data, including redacted copies of individual messages that failed authentication.

  • adkim & aspf: Specifies the alignment mode for DKIM and SPF, both set to r (relaxed alignment) by default. A relaxed alignment is recommended for DMARC in DNS services.

An example of a neutral DMARC policy without additional parameters:

v=DMARC1; p=none;

Once you've added and verified the DMARC record with your DNS provider, all receiving email servers can authenticate incoming emails from your domain and handle any failures according to your specified policy.

πŸ“ Note: Marsello Support cannot assist with DMARC record setup. The DMARC policy configuration is unique to your business needs and your DNS provider. Consult your IT administrator or DNS settings manager for assistance. Third-party DMARC consulting or reporting services can also provide additional support if needed.

After incorporating these DNS records and ensuring their verification by Marsello and your DNS provider, the DKIM signature will be incorporated into the headers of your dispatched emails. This alignment corresponds to the configured CNAME entries associated with the signature.

Taking these actions will safeguard your emails from potential spam flags and guarantee that your messages reach your customers seamlessly. Make sure to adhere to these guidelines to maintain effective communication through your branded email address.

Merchants also searched for: February, Febu, custdomain, domian, domi, sehder email

Did this answer your question?