Customer accessible whitelisting is now available via the Account Manager. We know many of you have been requesting this feature for a while, so we’re very happy we finally got this out the door!

To manage whitelists for your domains:

For ServerProtect customers, click the link on the Manage Packages tab for the server the domain is located on to bring up the server management window.  Find the domain in the list and click the domain name to bring up the domain management page.

For DomainProtect customers, click the link on the Manage Packages tab for the domain to bring up the domain management page.

Once on the domain mangement page, you’ll see the Whitelist section in the right column.  If you have active whitelists, they will be listed at the top of the column with a delete link next to each one.  At the bottom of the list there is a section that you can use to create new whitelists.

To create a new whitelist, select the radio button next to either Domain or Email Address, depending upon which criteria you wish to whitelist by.  Note that this is the domain or email address to whitelist, not your domain or email address.  Click the Add button below the form to add the whitelist.  It will now appear in the list of active whitelists.

Please note that if you have requested manual whitelists via support tickets in the past that they will NOT show up in this list, as we have not yet figured out a way to easily import existing whitelists into our Account Manager database.

Please let us know if you have any comments, questions or concerns about this new feature.

Gavin Clint Forstrom was born on August 24th at 7:35 pm, weighing 8 lbs. 6 oz. at 21 inches long.   Baby, mother and I are doing great.  Pics will be posted soon.

Easy Antispam will be exhibiting at Interop New York and we’d love to see you there!

If you use the priority code CMKFNN01 when you register you’ll get either a FREE EXPO PASS or save 20% on Conference Passes.  Register at www.interop.com.

It appears that the DNS propagation for ijnet.net to the new DNS servers has completed.  Please let our support department know if you are still experiencing issues with mail not being received due to "host not found" errors.

We’ve had a few customers report that they’re seeing timeouts connecting to eNom’s nameservers, which are what we’re currently using to serve the ijnet.net domain.  We aren’t seeing that on any of our networks here, but it’s possible there may be some type of networking issue on a backbone somewhere that’s causing this to happen to certain areas of the world. This is likely contributing to the issues we’ve been seeing regarding name resolution from certain providers.

We’ve switched to a new DNS provider and have put the change in place, though it may take up to 24 hours for the switchover to happen fully.  We will be monitoring the change over the next day to make sure there are no issues.  When it appears to be fully (or close to it, anyway) complete, we’ll post here to let you know so you can check to see if it resolves the issues some networks have been seeing.

After some further research, we’re still pretty confident that any DNS issues that are being experienced are not on our end.  From everything we can see, our DNS servers are all responding properly and are returning the proper IP addresses for our gateways.

A recent DNS cache poisoning vulnerability was announced in the last few weeks, and there are reports of it being exploited in the wild.  US-CERT VU#800113 contains details of the vulnerability.  We do not know whether this may be impacting certain ISPs DNS servers, but it is a supposition based on the evidence we have available to us at this time.

To show that our DNS is working properly, we’ve used DNS Stuff to compile a report for each of our gateways showing that all the root DNS servers list our DNS servers as authoritative and that each of our DNS servers is returning the proper response for our gateway addresses.  Click the link for each gateway to see the report.  You can use this report when talking with an ISP about them resolving the issue.

MF1

MF2

G1

G2