This feature requires Author user level or higher.
You might notice that some email clients display “on behalf of mcsv.net” or “via mcsv.net” in the sender details section of your delivered campaign. This appears due to authentication, which is a way for email clients to verify that an email comes from a legitimate sender.
In this article, you’ll learn how authentication works and how to remove MailChimp authentication information from your campaigns.
Why Authentication Information Appears
To determine if an email is safe, email clients look at two addresses when they receive bulk email: the email address in the From field, and the sender address. The sender address is not always visible, but it is necessary to send email through MailChimp. It’s based on our sending servers, and usually contains mcsv.net, mcdlv.net, or rsgsv.net. Some email inboxes display both your information and our information in the sender details of an email.
How Authentication Affects Your From Name
Subscribers who use Gmail, Outlook, Hotmail, or another Microsoft webmail service may see an indication that your campaign was sent by MailChimp on your behalf.
For example, if you send a MailChimp campaign from email@example.com, we’ll authenticate it with our domain. Email clients display MailChimp sending domain information near your campaign’s From name to help recipients determine if an email is safe to open.
Here are some examples.
Remove “on behalf of” or “via mcsv.net” Information
The best way to remove this extra information from your campaign is to use a from email address associated with your own domain, and authenticate it. Domain Keys Identified Mail (DKIM) and Sender Policy Framework (SPF) are commonly used to authenticate email domains. These methods make campaigns appear to come from your servers within the email client, and ensure the removal of MailChimp information from the sender details section of the campaign.
While this works for most email clients, some email clients, like Outlook, may still display authentication information after custom DKIM is set up. This is specific to each email client and isn’t something we can prevent.
Check out these resources to find out if custom domain authentication is a good fit for your organization, and learn how to set it up.