Google is touting their Google Apps offering for business with a new post on the official Google Blog (link). The post presents a link to a gonegoogle.com site, which runs you through a calculator of how much cash you can save by "Going Google". The calculator seems to be based on industry averages for things like uptime, storage costs, remote access, etc., and presents a nice little summary poster at the end. An example is given from guest poster smartfurniture.com. A nice little surprise comes up, though, when you click on the link to view the sample poster for Smart Furniture…

We’ve been working on some major upgrades to our Exchange environment over the last while. During the course of that, we started receiving NDR’s for messages sent to mail-enabled public folders. Initially, these were “MapiExceptionNotAuthorized” messages, which are related to permissions. Those were sorted out without too much trouble, as the NDR is at least somewhat descriptive. But then we started receiving a very generic NDR of #550 4.4.7 QUEUE.Expired; message expired ##. ...not really much to go on. Exchange 2007 does give some more “in plain English, please!” information in its NDR’s, but that also wasn’t much help: Delivery has failed to these recipients or distribution lists: [user display name] Microsoft Exchange has been trying to deliver this message without success and has stopped trying. Please try sending this message again, or provide the following diagnostic text to your system administrator. Wow...that was helpful…

As part of some mail filter testing, I needed to install ESET Mail Security onto a Debian 4.0 Etch VPS running on Virtuozzo. As a side-note, I found that the install package for ESET’s Gateway Filter, Mail Security, and File Server Security for Linux is all the exact same package; the functionality is basically just controlled/activated by means of licensing the appropriate component. Anyway, the download comes as an installation script called esets.i386.deb.bin. Running that script outputs a license agreement that you have to accept, produces a .deb package called esets.i386.deb, and outputs instructions on how to install the .deb package by using dpkg and import the license file. The .deb package installed just fine on another Debian test box, but when I attempted to run dpkg –i esets.i386.deb on the Virtuozzo VPS, tar squawked at me that it could not open /dev/stdin and the installation bailed: hostname:/usr/local/src/eset# dpkg -i esets-3.0.11.i386.deb Selecting previously deselected package esets. (Reading database ... 24639 files and directories currently installed.) Unpacking esets (from esets-3.0.11.i386.deb) ... Setting up esets (3.0.11) ... Unpacking esets modules ... tar: /dev/stdin: Cannot open: No such file or directory tar: Error is not recoverable: exiting now dpkg: error processing esets (--install): subprocess post-installation script returned error exit status 2 Errors were encountered while processing: esets…