What are the URLs and IP addresses of our mailservers?
Outgoing SMTP Servers
URL | IP Address |
outbound.volunteer2mail.com | 209.15.205.180 |
o2.ptr4681.prod.volunteer2mail.com | 149.72.203.165 |
o3.ptr4183.prod.volunteer2mail.com | 159.183.220.81 |
Transactional
URL | IP Address |
o2.trans.volunteer2mail.com | 198.21.7.99 |
The transactional email server is used for password resets, system notifications, and similar types of email.
These servers are on the allow lists and registered in feedback loops with major providers such as Hotmail, Yahoo and AOL in accordance with bulk-sending best practices. We also continuously monitor the sending reputation of these servers to ensure optimal delivery.
If possible, it is recommended that you add our outbound mail servers to your allow list to ensure deliverability. These are dedicated IP addresses that are used for the sole purpose of sending mail from our application (we do not send any form of advertising or marketing mails from these servers).
What is volunteer2mail.com?
volunteer2mail.com is a dedicated domain used to send emails from the Better Impact family of products
What do we do to ensure mail deliverability?
We support SPF, Sender ID, DKIM and DomainKeys for email being sent from the volunteer2mail.com domain.
Our mail server is on the allow lists and registered in feedback loops with major providers such as Hotmail, Yahoo, AOL and Comcast.
What “Return-Path” header value are our messages sent with?
How are bounces processed?
We utilize a custom service to process and send notifications of bounces that are received at [email protected] to notify the original sender of the bounce; this is done in accordance with recommended SPF guidelines
What do our email headers look like?
When we send mail through our service, the headers are as follows:
Return-Path: <[email protected]>
From: “Your Name” <[email protected]>
To: “Recipient Name” <[email protected]>
Under some circumstances, to ensure deliverability, we need to use the following headers to send the mail instead (note the addition of the “Reply-To” header and the use of “[email protected]” in the “From” header):
Return-Path: <[email protected]>
From: “Your Name” <[email protected]>
Reply-To: “Your Name” <[email protected]>
To: “Recipient Name” <[email protected]>
Reasons why this is done are as follows:
The sender’s domain contains a DMARC (link to: https://dmarc.org/) record with a policy of either: “reject” or “quarantine”.
We detect (via an MX lookup) that the sender’s email is being hosted in Office 365. This is done to avoid message such as “This Sender Failed Our Fraud Detection Checks and May Not Be Who They Appear to Be” from showing to your recipients.
We detect a TXT record in the sender’s domain with the value of “_betterimpact-rewrite-sender”. Note: this can be used to force the use of a “Reply-To” header for your domain in circumstances where the “From” header would cause issues with fraud detection / spoofing in your email environment.
Typical Email Header Text (for reference purposes)
Return-Path: <[email protected]>
Received: from [209.15.205.180] ([209.15.205.180:65508]
helo=outbound.volunteer2mail.com) by smtp51.gate.dfw1a.rsapps.net
(envelope-from <[email protected]>) (ecelerity 2.2.3.46 r(37554))
with ESMTP id 2F/94-09431-B184BFD4; Fri, 17 Jun 2011 08:27:07 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed;
s=s1024;d=volunteer2mail.com;
h=from:to:sender:date:subject:mime-version:content-type:message-id;
bh=wixYDQhFU6dOc6HhkA2YYmdhV0s=;
b=lapra2B3liMDpfGSzY5TNbXuPIOb8Ep+98dp8+uDLjPmZxElgAo4o5IvdsDbBXfdsLKIMoHf
bHFKiFmugrV/DnRlTi4RMOK3l+xvtPR8dfrXqcnERQdOKSDNaU6XUnqRFEDj0xNg8s5DsnAW
WGnVAETTXAYtaraReENUgITtWtY=
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
s=s1024;d=volunteer2mail.com;
h=from:to:sender:date:subject:mime-version:content-type:message-id;
b=GGLkdKj1hCa8HE8MS0WLcOONj3IzyfwP7cm8uAbNa1OU762gusqtHlNHI4/XleIv1fwqn2vU
XoGJa/ElYw691XsDYTlPoyJ0nhnS24CwP6MNa8tUtJQmXmaoEx8+FWRpv3nxfgZK4FFshpF3
73tj2e15C8Nk04d3jnMO6ieq5eQ=
Received: from mail pickup service by outbound.volunteer2mail.com with Microsoft SMTPSVC;
Fri, 17 Jun 2011 08:27:06 -0400
From: <[email protected]>
To: <[email protected]>
Date: Fri, 17 Jun 2011 08:24:46 -0400
Subject: Subject
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary=”_=aspNetEmail=_d6ef38fc43584694bd897c3367f0c448″
X-Mailer: aspNetEmail ver 3.7.0.10
Message-ID: <vol2web1697b83fd01bc4e819c576c84dfeccf4e@vol2web1>