Xplorex Block List Policy
Xplorex, in response to the increasing amount of incoming spam to our network, has provisioned additional resources to reduce the amount of spam our clients receive. This new policy is designed to alleviate the ever-growing issue of incoming abusive spam attacks on our mail infrastructure.
If someone sends an e-mail message and the sender's IP address or SMTP (mail) server is on one of these lists, then the incoming e-mail is blocked. This tool may result in the inadvertent blocking of some e-mail that is not traditional spam.
The lists which are currently in use are:
- MAPS Realtime Blackhole List (http://mail-abuse.org/rbl)
- MAPS Relay Spam Stopper (http://mail-abuse.org/rss)
- MAPS Dialup User List (http://mail-abuse.org/dul)
- MAPS Open Proxy Stopper List (http://mail-abuse.org/ops)
- Spamhaus Block List (http://www.spamhaus.org/sbl)
- Spamhaus Exploits Block List (http://www.spamhaus.org/xbl)
These six lists, coupled with an internal block list, will filter all inbound SMTP (e-mail) traffic. If an incoming e-mail is denied, a system message is sent back to the sender.
Xplorex subscribes to these lists to help us control the amount of spam entering our network. This is a decision which is made here at Xplorex; the list owners do not make this decision. The list does not block email – all they do is tell us which IP addresses are suspect in their mailing practices. Xplorex has the ability to make the final determination, as well as technical ability, to choose whether or not to accept e-mail from any Internet entity, including those listed in the MAPS or Spamhaus Lists.
Xplorex uses the information in these lists to block email coming from IP addresses which abuse Internet resources by sending massive quantities of unsolicited commercial or bulk email. This helps us to keep a significant amount of unwanted commercial e-mail from entering our system, and assists us in solving a problem that is negatively impacting our clients.
Xplorex also maintains an internal block list, separate from these lists. This list is used mainly in cases of denial-of-service spam attacks, as an immediate reactive measure to stop an incoming spam attack. We will work with the ISP involved to address each situation.
For those entities currently on one of the third-party lists, they must contact the third-party list directly to be removed. Many times a party can be removed from a list via telephone, or via the home pages of those lists. In most cases, a system that is on one of the lists is easily removed, following some simple steps. If you would like to know if a mail server is located on the lists that Xplorex utilizes, please see the URLs above.
Xplorex Inbound Sending Policy
- All e-mail servers connecting to Xplorex's relay servers must have valid reverse DNS entries (i.e. all sending IP addresses must have active corresponding domain names in DNS).
- All e-mail servers connecting to Xplorex's mail servers must be secured to prevent unauthorized use (may not be an open proxy, router, or relay).
- Connections from dynamically assigned IP addresses (dial-up accounts) will not be accepted to Xplorex's relay servers.
- Organizations may not hardcode Xplorex's mx records into their configuration files.
- Organizations must immediately unsubscribe any Xplorex e-mail addresses that receive a permanent failure e-mail bounce from Xplorex's mailer-daemon.
E-mail formatting Guidelines:
- Organizations must not do anything that tries to hide or forge the sender of the e-mail and sending site of e-mail.
- Each mailing must specifically state how the Xplorex clients' e-mail addresses were obtained (i.e. purchase from Acme tools, sign up for Travel discounts, etc.) and must state whether this is a one-time mailing or a reoccurring mailing. Additionally, such details as the date and time when the e-mail address was obtained along with the IP address must be available upon request.
- All mailing should contain simple and obvious unsubscribe mechanisms. While we recommend that this be in the form of a (working!) link to a one-click unsubscription system, a "reply to:" address may also be used. In this case we require that the address receiving those replies be valid.
- All e-mail must have valid non-electronic contact information for the sending organization in the text of each e-mail (phone number, physical mailing address, etc.). If this is not readily feasible, there must be a link in each e-mail to such information on the sending organization's website.
Policy & Procedural Guidelines:
- All e-mail to Xplorex's client base must be solicited (i.e. there is an existing and provable relationship between the e-mail recipient and the sender).
- If an organization generates complaints, Xplorex may implement blocks until a reconfirmation mailing is sent.
- In no way does the posting of these guidelines imply any affiliation, membership, sponsorship or endorsement of business or activities/practices of an organization by Xplorex.
- Xplorex reserves the right to discontinue delivery of e-mail from an Internet sender if Xplorex's service is impaired or for other reasons.