Wed 07/11/2012 - Some Mail Being Rejected: On Monday, we experienced an issue that caused the idcomm mail server to be unreachable. For those of you who may be wondering, this issue was in no way related to the FBI shutting down the rogue DNSChanger name servers. That issue was fixed, but unknown to us at the time, the fix created another condition that caused some mail servers to begin rejecting mail from the idcomm server. This second condition has been identified, and a fix should be in place sometime today. We sincerely apologize for any inconvenience this has caused, and we appreciate your patience, understanding, and continued patronage.
06/08/2012 - SSL Connection Errors Solved: In the last few days, some users have been getting errors from their email programs saying that an SSL connection to the server can't be made. Last night we discovered that the cause of these errors is not the server or users' email settings. It's Avast Antivirus! That's right, Avast perhaps due to a program update, is now deciding rather arbitrarily it would seem, that some email connections should be made using SSL. If you're getting these errors and you're using Avast as your antivirus program, please click here for instructions on how to change this in your Avast settings. Instructions include screen shots, so if anyone has any trouble following them, please let us know.
05/11/2012 - New SSL Certificate In Place: The SSL Certificate for the webmail server has been updated, and you should no longer be seeing the security warning from your browsers.
05/09/2012 - Webmail Security Errors: The SSL Certificate for the webmail server has expired, which is causing web browsers to show security warnings and to advise users not to continue to the site. This is a temporary condition, and it is safe to click continue and to view your email through the webmail interface. We apologize for any confusion this may be causing and hope to alleviate this condition shortly.
04/21/2012 - Attention Avast Users: Avast appears to be prompting users to upgrade to a new version. It is ok to to do this, as long as you keep a few things in mind during the process. First during the install, if you're using the free version, you will be presented with screens that attempt to nudge you toward using the paid version. In our opinion, the paid version is somewhat overkill and an unnecessary expense. So please pay attention to the screens to follow the links for the free version. Links for the paid version will be more colorful, while links for the free version will be more gray. We believe the free version is labeled "Basic Protection", which really is all you need. At the end of the install, you'll need to reboot, which is normal. After the reboot, Avast will show a screen about finishing the update. On this screen, there are 2 boxes you need to uncheck: One for participating in the Avast Community, and one for installing the Google Toolbar. Once that's done, you should be all set.
IMAP Server Errors.
We've been getting a few reports of MS Outlook
giving an error about the IMAP server closing the connection. While we don't know
exactly what is causing this problem, we believe it's related to Outlook wanting to maintain
an open connection with the server. Our mail server primarily is a POP3 server, which
is the normal protocol for programs like Outlook Express, MS Outlook, and Mozilla
Thunderbird. However it appears that, for some reason, Microsoft changed the default
protocol for Outlook to IMAP as of version 2010 (possibly 2007). The server does
support the IMAP protocol, but this is intended for use by our webmail programs and your
mobile devices. In terms of postal mail, IMAP would be like you going to your local
post office and reading it there, never bringing an actual copy home. POP3 would be
more like normal where your mail is delivered to your home. Webmail and mobile devices
open a connection, do what they need to do, and close the connection. Apparently MS
Outlook does not do this when set to us IMAP, but rather tries to maintain a more constant
To see older posts, please click here.