Semi-Automated Whitelisting

January 29th, 2007 | Category: Blog,,

Welcome to part 3 of my series on Anti-Spam and Whitelisting. My last post referred to a method which makes it easier for email senders and recipients to request and complete the whitelisting process. I just wanted to take a moment to elaborate on that procedure now that its available for our customers.

Normally when an email is bounced back to the sender, the error message can often be a little cryptic and difficult to understand for those of us who are a little less technical. This is also the case when your email is bounced due to an RBL blacklist. We’ve attempted to alleviate this by sending a more user-friendly error message which explains the reason why the email wasn’t delivered. This error message will also contain a URL, which when followed will lead to a web page where the sender can request that they be whitelisted.

After following the link, the individual will then be asked to provide their email address and the email address they were attempting to contact. Once the request is submitted, an email is sent to the web hosting account owner or the hosted exchange account owner. The email will also contain a link which will lead directly to the Whitelist administration page, where they can quickly approve the request.

Once approved, the sender will be able to send email to the original recipient - bypassing the RBL blacklist completely. Although this procedure isn’t fully automated, the steps take only seconds to complete and are completely painless. Neither party needs to spend any time figuring out which IP Address needs to be whitelisted, and only minor input is required.

We hope that all of our customers will enjoy this new feature.


Tim Attwood
Product Manager
SoftCom Technology Consulting Inc.

One Response to “Semi-Automated Whitelisting”

  1. John Algeo says:

    This sounds like a big improvement. When blacklist problems crop up, help is hard to come by. A few months ago, I bought a new laptop and had it (and only it) blacklisted. The cure finally turned out to be deletion and re-entry of all Outlook Express accounts on that machine.