top of page

Why My Emails are Going To Spam PT1 (TECH REASON, DKIM, SPF & DMARK)

ntaitt

Google and Yahoo recently announced their plan to implement new email authentication and spam-prevention policies. Starting February 2024, the two major email providers yahoo & Google will begin to block and aggressively filter incoming email traffic.


Why did google and yahoo changed their email authentication

Google and Yahoo made significant changes to their email authentication policies in February 2024 to enhance security and reduce spam. Here are the key reasons behind these changes:

  1. Improved Security: By enforcing stricter authentication protocols like SPF, DKIM, and DMARC, they aim to prevent email spoofing and phishing attacks.

  2. Better Email Deliverability: These changes help ensure that legitimate emails reach recipients' inboxes rather than being marked as spam.

  3. User Experience: Making unsubscribe options more accessible and honoring unsubscribe requests promptly improves the overall email experience for users.

  4. Compliance: Aligning with legal requirements and best practices, such as the CAN-SPAM Act, helps businesses maintain compliance and avoid penalties.

These updates are designed to create a safer and more efficient email ecosystem for both senders and recipients. Do you think these changes will impact your email usage?


What does this potentially mean for you.

Your legitimate emails you send can potentially got to spam instead of the desired in box.


Here are some technical steps you can take to correct this issue by ensuring your DNS has the following SPF, DKIM, and DMARC,












Step 1:

🔵Add an SPF Record - SPF: Specifies the servers and domains that are authorized to send email on behalf of your organization.


Create a Text record - TXT record name: In the first field, under the DNS Host name, enter: @


TXT record value: In the second field, enter the text for your SPF record,

Example:

v=spf1 include:_spf.google.com ~all



Step 2:

🟣Add A DKIM Record - DKIM: Adds a digital signature to every outgoing message, which lets receiving servers verify the message actually came from your organization.


a: Get your DKIM key in your Admin console

b: Add your DKIM key at your domain provider

c: Turn on DKIM in your Admin console

d: Verify DKIM signing is on





Step 3:

🟡Add A DMARC Record - DMARC: Lets you tell receiving servers what to do with outgoing messages from your organization that don’t pass SPF or DKIM.


Create a Text record - TXT record name: In the first field, under the DNS Host name, enter: _dmarc


TXT record value: In the second field, enter the text for your DMARC record,

Example: v=_DMARC1; p=none; sp=none; rua=mailto:youremail@yourdomain.com





0 views0 comments

Recent Posts

See All

コメント


bottom of page