merchant:spf

SPF Records for USAePay

Problem: receipts are going to spam

This page aims to provide assistance to merchants who are having trouble with customer receipts being blocked as spam. The most common cause of this issue is the ability for merchants to change the “From” address that is used by the gateway when sending emails. By default, receipts are sent with a from address of “support@usaepay.com” or “noreply@usaepay.com”. Since usaepay.com designates its own servers as being allowed to send “@usaepay.com” email, these messages are not blocked. Once the merchant changes the from address on the settings screen in the console, the receipts are sent with the merchants email, for example: john@adams.com. When the customer's mail server receives the email, it checks that “adams.com” allows usaepay.com to send email on behalf of john@adams.com. If they do not, the message may be tagged as spam. Whether the message is blocked or not depends on whether adams.com has configured a “SPF” dns record and whether that record lists usaepay.

What is SPF

Sender Policy Framework (SPF) is an open standard that allows mail servers to verify that an email was sent by a source that has been permitted by the owner of the domain. Configuring SPF for your domain is a matter of adding a TXT record to your DNS. If you are not sure how to modify the DNS for your domain, consult your domain provider.

Allowing USAePay to Send Email

If a merchant is going to list their own email in the From setting, they will need to add usaepay to their SPF record. If the merchant does not control their domain and the domain owner is not willing to make the change, the merchant should either use a different email address or leave the from address blank.

The easiest way to list the usaepay mail servers is to add “include:spf.usaepay.com” somewhere before the “~all” or “-all”. For example, if your SPF record is currently:

   acme.org  TXT  "v=spf1 a mx ~all"

you would change it to:

   acme.org  TXT  "v=spf1 a mx include:spf.usaepay.com ~all"

If you prefer not to use our include, you can also list the mail server IPs directly. This approach is not recommended as your record will be out of date when our network expands/changes.

   acme.org  TXT  "v=spf1 a mx ip4:209.239.233.124 ip4:209.239.233.125  ip4:64.0.146.124 ip4:64.0.146.125  ip4:209.220.191.124 ~all"
   

How to Test

Once you have your rules setup correctly in DNS, there are a variety of web based tools that you can use to verify. For example, to test with the Beveridge Hosting SPF Test test tool, enter “209.239.233.124” in the “Sending IP Address”, the from address you are using in the console should go in the “Sender Email Address” field and “mx-ca4-01.usaepay.com” should go in the “Senders Computer Name” field. If all is configured correctly, you should see a “pass” and “sender permitted”.

But I'm using a @google.com, @hotmail.com, etc email address

USAePay does not recommend a public webmail based address in the From setting. There is no way to correctly configure these email addresses to be sent from the USAePay gateway and merchants will experience a number of customers who are not able to to receive receipts. The merchant should either leave the From setting blank or get their own domain for email.

merchant/spf.txt · Last modified: 2013/12/12 10:02 by tem

Page Tools