Summary
The 'via' warning in emails indicates that the email was sent from a server different from the domain in the 'From' address, often when using third-party services. This raises trust concerns and can affect deliverability. Internal 'via' warnings might stem from multiple domain setups, or issues within platforms like Marketing Cloud. Resolutions involve implementing SPF, DKIM, and DMARC for proper authentication. This includes ensuring correct SPF syntax, DMARC alignment (From domain matching DKIM/SPF domains), monitoring sender reputation, and using testing tools. For Google Workspace and AWS SES, specific configurations are needed. By authenticating sending servers, addressing authentication problems, and maintaining a solid domain reputation, the 'via' tag can be eliminated.
Key findings
- Third-party Sending: 'Via' warnings often appear when emails are sent through a third-party service, as the sending server differs from the 'From' domain.
- Authentication Importance: Proper email authentication (SPF, DKIM, DMARC) is crucial for preventing 'via' warnings and improving deliverability.
- DMARC Alignment is Key: Proper DMARC alignment, where the 'From' domain matches the DKIM or SPF domain, is essential for eliminating the 'via' tag.
- Syntax and Validation: Ensuring the correct syntax in SPF records and using email testing tools for validation are critical.
- Monitor and Improve: Regularly monitoring sender reputation and deliverability metrics help to proactively identify and address issues.
Key considerations
- SPF Record Setup: Set up SPF records to authorize third-party services to send emails on your behalf, and ensure all authorized senders are included.
- DKIM Configuration: Configure custom DKIM records to reduce the likelihood of emails being flagged as suspicious and improve deliverability.
- DMARC Implementation: Implement DMARC policies to instruct email receivers on handling unauthenticated emails and prevent spoofing.
- Specific Platform Configuration: Configure SPF, DKIM and DMARC properly when using platforms like Google Workspace, AWS SES and Marketing Cloud.
- Domain Reputation Management: Maintain a good domain reputation through proper email practices to avoid deliverability issues and 'via' warnings.
What email marketers say
8 marketer opinions
The 'via' warning in emails indicates that the email was sent through a server different from the domain specified in the 'From' address, often when using third-party email services. This can affect email trustworthiness and deliverability. To fix this, it's crucial to implement proper email authentication methods like SPF, DKIM, and DMARC. Ensuring DMARC alignment, monitoring sender reputation, using email testing tools, and configuring custom DKIM records can further help eliminate 'via' warnings and improve overall email deliverability.
Key opinions
- Cause of 'via': The 'via' tag appears when the sending server differs from the 'From' domain, commonly when using third-party email services.
- Impact on Deliverability: If not properly configured with SPF/DKIM, 'via' tags can negatively affect email trustworthiness and deliverability.
- Importance of Authentication: Proper email authentication (SPF, DKIM, DMARC) is crucial for preventing 'via' warnings and improving deliverability by verifying the authenticity of the sender.
- DMARC Alignment: Ensuring DMARC alignment, where the 'From' domain matches the DKIM or SPF domain, is essential for eliminating the 'via' tag.
- Proactive Monitoring: Regularly monitoring sender reputation and deliverability metrics helps identify and address issues that may cause 'via' warnings.
Key considerations
- SPF Record Setup: Set up SPF records to authorize third-party services to send emails on your behalf.
- DKIM Configuration: Configure custom DKIM records to reduce the likelihood of emails being flagged as suspicious.
- DMARC Implementation: Implement DMARC to specify how email receivers should handle unauthenticated emails and prevent spoofing.
- Email Testing: Use email testing tools to check the authentication setup before sending campaigns and resolve configuration issues.
- Domain Reputation: Maintain a good domain reputation through proper email practices to avoid deliverability issues and 'via' warnings.
Marketer view
Email marketer from SendGrid shares that regularly monitoring your sender reputation and deliverability metrics helps you to identify issues that may cause 'via' warnings. You should proactively address any issues before they affect your email delivery.
17 Sep 2022 - SendGrid
Marketer view
Email marketer from MailerLite shares that configuring custom DKIM records and using a dedicated IP address can reduce the likelihood of your emails being flagged as suspicious, which helps in avoiding 'via' warnings and improving overall deliverability.
21 Mar 2023 - MailerLite
What the experts say
5 expert opinions
The 'via' warning on internal emails arises from authentication issues, particularly when emails are sent from a different server or domain than expected, or when using Marketing Cloud with forwarding through RMM. Google's system alerts employees to potentially unauthenticated emails claiming to be from coworkers, often due to misalignment or authentication as Salesforce/ExactTarget. While the 'via' tag doesn't always directly impact deliverability, broader authentication problems can lead to emails being marked as spam, especially with evolving Yahoo/Google standards. Maintaining a solid domain reputation and implementing SPF, DKIM, and DMARC records are crucial for proper authentication and preventing these warnings, while also safeguarding against scams.
Key opinions
- Internal VIA Warning Cause: Internal 'via' warnings are often triggered by multiple domains setup, bouncing emails, or forwarding through RMM in environments like Marketing Cloud.
- Google's Alert System: Google's system alerts users when an email claims to be from a coworker but lacks proper authentication, signifying potential misalignment.
- Authentication Impact on Deliverability: Broader authentication issues can lead to emails being marked as spam or blocked, especially with new email standards.
- Role of SPF: Implementing SPF records can authorize sending servers, preventing the 'via' tag and ensuring email authentication.
- Domain Reputation Importance: Maintaining a strong domain reputation is vital to avoid deliverability problems, including the display of 'via' tags.
Key considerations
- Check Domain Setups: Examine domain configurations and email routing to prevent issues arising from multiple domains.
- Authenticate Properly: Implement and align SPF, DKIM, and DMARC records to verify email authenticity.
- Regular Monitoring: Continuously monitor and manage your domain's reputation to avoid deliverability issues.
- Protect Against Scams: Addressing authentication problems is crucial for protecting against scams and securing email delivery.
- Marketing Cloud Configuration: If using Marketing Cloud, pay attention to authentication setups, especially when forwarding through RMM.
Expert view
Expert from Email Geeks shares that while the specific internal warning might not directly affect deliverability, broader authentication issues can cause emails to be marked as spam or blocked, especially with new Yahoo/Google standards. Addressing authentication problems is crucial to protect the company from scams and ensure proper email delivery.
1 Nov 2021 - Email Geeks
Expert view
Expert from Spam Resource explains that the 'via' tag typically shows when an email is sent through a different server than the sender's domain. Implementing SPF (Sender Policy Framework) records helps to authorize the sending server, thus preventing the 'via' tag and ensuring the email is properly authenticated.
11 Feb 2022 - Spam Resource
What the documentation says
5 technical articles
The 'via' warning in emails can be eliminated by implementing and properly configuring email authentication protocols. Specifically, ensuring your domain's SPF record includes all authorized senders (including Google Workspace servers and third-party services), setting up SPF, DKIM, and DMARC records across all email systems, and properly implementing DMARC policies to handle unauthenticated emails. Additionally, it's crucial to ensure the SPF record's syntax is correct, and when using services like AWS SES, your sending domain must be verified, and corresponding SPF and DKIM records configured within your AWS account.
Key findings
- SPF Inclusion: Ensuring your SPF record includes all authorized senders, such as Google Workspace servers and third-party services, is critical for removing 'via' warnings.
- Complete Authentication: Setting up SPF, DKIM, and DMARC records across all email systems is the recommended approach to stop 'via' warnings.
- DMARC Implementation: Implementing DMARC allows domain owners to specify how to handle unauthenticated emails, preventing spoofing and aiding in the removal of 'via' warnings.
- SPF Syntax Importance: Ensuring the correct syntax in SPF records is crucial for proper interpretation by mail servers.
- AWS SES Configuration: When using AWS SES, verifying the sending domain and configuring SPF and DKIM records within the AWS account are necessary to prevent 'via' notices.
Key considerations
- Authorize Senders: Update your SPF record to include all authorized senders for your domain.
- Implement DMARC: Implement DMARC policies to instruct email receivers on handling unauthenticated emails.
- Validate SPF Syntax: Double-check SPF records for correct syntax and avoid common errors like incorrect IP addresses or missing 'include:' statements.
- Service-Specific Setup: Ensure proper SPF and DKIM configuration within services like AWS SES after verifying the sending domain.
- Email System Coverage: Configure SPF, DKIM and DMARC for all email systems used by the organisation.
Technical article
Documentation from Microsoft Support explains that setting up SPF, DKIM, and DMARC records are the best steps to stop a 'via' warning. Ensure all your email systems are configured with these records.
9 Feb 2023 - Microsoft Support
Technical article
Documentation from DMARC.org explains that implementing DMARC, along with SPF and DKIM, allows domain owners to specify how email receivers should handle unauthenticated emails, preventing spoofing and phishing. Properly configured DMARC policies can help eliminate 'via' warnings by ensuring email legitimacy.
9 Dec 2021 - DMARC.org
Do Gmail reply-to domains need to match the from domain?
How can I implement a strict DMARC policy without blocking Google Workspace emails?
How does Google Workspace manage outbound authentication with multiple domains?
How to remove the 'via' message in Gmail when sending from a subdomain?
Should I authenticate my primary domain if it's only used for internal communications?
Why does Gmail show 'via' even when DMARC passes?
