The appearance of "Using Zoho Campaigns" next to your sender name in Gmail is indeed linked to the X-Mailer header. This header identifies the software used to send the email. While it can be a point of curiosity or even a minor branding concern for some senders, it generally has a negligible direct impact on your email deliverability rates. Google simply uses this information to provide transparency to the recipient regarding the sending platform. The core factors influencing whether your emails land in the inbox remain proper authentication (SPF, DKIM, DMARC), sender reputation, and content quality.
Key findings
Visibility: The "Using Zoho Campaigns" text is a display feature by Google, triggered by the X-Mailer header, which indicates the sending platform.
Deliverability impact: The X-Mailer header itself typically does not negatively affect email deliverability, provided your authentication records like SPF, DKIM, and DMARC are correctly configured. For more on this, consider our guide on a simple guide to DMARC, SPF, and DKIM.
ESPs and headers: Email Service Providers (ESPs) like Zoho Campaigns commonly add X-Mailer headers as part of their standard email metadata.
Control: Whether you can remove or modify this header depends on the specific settings and flexibility offered by Zoho Campaigns. Many ESPs do not allow users to alter standard headers.
Key considerations
Focus on fundamentals: Instead of worrying about the X-Mailer header, concentrate on established email deliverability best practices. Zoho themselves recommend focusing on authentication protocols and optimizing content, as detailed in their email deliverability guide.
Reputation: Maintain a strong sender reputation through consistent sending, low bounce rates, and high engagement to ensure optimal inbox placement. Explore how your email tool affects your email deliverability more broadly.
User perception: While the "Using Zoho Campaigns" tag is present, most recipients are unlikely to be concerned by it, as long as the email is relevant and legitimate.
What email marketers say
Email marketers widely agree that the X-Mailer header, including the specific "Using Zoho Campaigns" label, has minimal to no direct impact on email deliverability. Their primary concern lies with whether the email actually reaches the inbox, which is driven by factors far more critical than a piece of identifying software metadata. Many view it as a cosmetic detail rather than a deliverability hurdle. However, some acknowledge it could be a minor branding point.
Key opinions
No significant impact: Most marketers haven't observed any data suggesting that the X-Mailer header causes deliverability problems.
Google's behavior: It's understood that Google (and potentially other email clients) will often display the "Using..." text if an X-Mailer header is present.
Focus on core elements: The critical elements for deliverability are sender authentication, content relevance, and list hygiene, not minor header details. This aligns with advice on overall email deliverability issues.
Branding vs. technical: While some might prefer to remove it for aesthetic or branding reasons, it's not considered a technical barrier to inbox placement.
Key considerations
Prioritize major factors: Marketers should prioritize factors like sender reputation, content quality, and recipient engagement. For instance, consider how subject lines impact deliverability.
ESP limitations: Understand that many ESPs, including Zoho, have standard header implementations that might not be user-configurable.
Perception: The "Using Zoho Campaigns" text is generally benign and unlikely to cause recipient distrust or mark messages as spam.
Header importance: While the X-Mailer header isn't critical, other headers are vital for deliverability and preventing spam. Learn more about email headers in this ultimate guide to email headers.
Marketer view
Email marketer from Email Geeks states that they seriously doubt the presence of the X-Mailer header causes any deliverability issues. They would prefer to see the full message headers to confirm the issue.
07 Feb 2024 - Email Geeks
Marketer view
Email marketer from Email Geeks explains that the "via" tag that sometimes appears next to the sender name should not be confused with the X-Mailer display. The "via" tag typically signifies issues with DKIM setup, which is a different and more critical deliverability factor.
07 Feb 2024 - Email Geeks
What the experts say
Email deliverability experts concur that the X-Mailer header generally plays no direct role in email deliverability or spam filtering. They emphasize that its purpose is informational, identifying the sending software. While Google surfaces this information in the Gmail interface, it's not typically used as a signal for inbox placement, unless there's an unusual pattern associated with malicious activity that an ESP might specifically flag.
Key opinions
Informational purpose: The X-Mailer header's primary function is to simply tell the recipient or receiving server what program was used to send the email.
Minimal deliverability impact: Experts largely agree that this header does not, by itself, negatively impact deliverability. There's no inherent harm in its presence. This is consistent with what is known about whether X-Headers negatively impact email deliverability.
Conditional flagging: The only scenario where an X-Mailer header might cause problems is if specific email servers or spam filters are intentionally configured to flag a particular X-Mailer value, often associated with phishing attempts or known malicious software.
Google's transparency: Google's display of "Using..." is a feature to show the origin of the email, not an indicator of poor deliverability or spam risk. This information about email clients is further explained on the Mutant Mail blog about the X-Mailer header.
Key considerations
Authentication remains paramount: Ensure robust email authentication (SPF, DKIM, DMARC) is in place, as these are the true technical pillars of deliverability. Proper configuration is essential to boost email deliverability rates.
ESP control: The ability to remove or modify the X-Mailer header is usually determined by the ESP. In most cases, it's not configurable by the user.
Reputation signals: Mailbox providers primarily assess sender reputation based on engagement metrics, spam complaints, and adherence to authentication standards, not on the X-Mailer header.
Header review: While X-Mailer is minor, it is prudent to understand all your email headers. Pay close attention to headers that indicate personalization errors that could be problematic.
Expert view
Expert from Email Geeks states that the X-Mailer header simply identifies the program or software used to send an email. This is an informative field rather than one used for deliverability scoring.
07 Feb 2024 - Email Geeks
Expert view
An expert from Email Geeks assures that they have not encountered any data that suggests the X-Mailer header causes deliverability issues. Its presence is generally benign.
07 Feb 2024 - Email Geeks
What the documentation says
Email documentation, particularly RFCs (Requests for Comments) that define email protocols, establishes the framework for email headers. While they specify the structure and purpose of various headers, the X-Mailer header is often described as an optional, informational field. It exists to provide metadata about the client used to compose the message, but it's not a standard header used for routing or explicit spam filtering by default. Its role in deliverability is not formally defined or weighted by these foundational documents.
Key findings
Optional header: The X-Mailer header is typically classified as an optional, non-standard (or X-Header) in RFCs, meaning its inclusion is at the discretion of the sending application.
Informational content: Its purpose is to convey information about the Mail User Agent (MUA) or software responsible for originating the message, such as "Zoho Campaigns".
No direct deliverability role: RFCs and related documentation do not specify a role for the X-Mailer header in terms of email routing decisions, spam scoring, or inbox placement algorithms.
Contrast with standard headers: It differs from crucial standard headers like From, To, Date, and authentication headers (SPF, DKIM, DMARC), which are integral to email delivery. Delve deeper into this topic with what RFC 5322 says versus what actually works.
Key considerations
RFC compliance: Focus on ensuring your email infrastructure complies with relevant RFCs for core headers and authentication mechanisms rather than optional ones. Understanding advanced email authentication is key.
ESP behavior transparency: While RFCs define the theoretical framework, specific ESPs like Zoho Campaigns may choose to include or omit certain optional headers as part of their service offering.
Filtering reliance: Spam filters and mailbox providers rely on a complex array of signals, including sender reputation, content analysis, and authentication results, not typically on the identifying information in the X-Mailer header.
Standard headers: Prioritize the correct configuration and adherence to standards for required email headers, as these are universally evaluated by mail systems. For example, RFC 8058 outlines a new header for one-click unsubscribe, which directly impacts user experience and list hygiene.
Technical article
RFC 2822 (Internet Message Format) specifies that while some header fields are strictly defined, others, especially X-Headers, are for experimental or private use. The document implies that such headers are for information exchange between specific applications and do not dictate core message handling.
01 Apr 2001 - RFC 2822
Technical article
RFC 5322 (Internet Message Format) reiterates that the purpose of certain header fields is to convey information about the message's origin or path. It does not assign any specific deliverability or spam scoring weight to optional, non-standard headers like X-Mailer.