Hello from snowy Maine, US... Since every writer benefits from an editor, I would be grateful if anyone has any comments on the proposed email system configuration below. ::Background:: Our corporate email server is a FreeBSD virtual host at Interland to which we have root access. To date we just POP the email down and do virus, spam and folder filtering at the client level. The clients are not laptops... We now find we are traveling more, and we would like to be able to send/receive/view email via the web from hotels, client sites, etc. Our corporate email server at Interland runs sendmail, UW IMAP, and Squirrelmail over SSL, so this is set up already, but with two big problems. ::Problems:: First, Interland does no spam filtering and although we can install our own application software, the virtual server configuration does not support spamassasin, clamav, nor any other daemonized anti-virus/anti-spam products. Furthermore, Interland have told us we cannot use procmail filtering on the server. Since we subscribe to a lot of high-traffic mailing lists (like this one) and tend to get several hundred spam/virus emails per day, no server-side filtering makes for unmanageable Inboxes for all of us. ::Proposed Solution:: We are thinking about setting up a SuSE 9.2 Pro box in our data center with a combination of apacheSSL, postfix, cyrus+sieve+sasl, spamassasin, clamav and whatever else gets us a web-enabled IMAP server with server-side filtering into the nearly 200 mail subfolders each of us maintains. We've set up a few systems like this before; there are some very good HOWTOs on the web, so doing the setup is not a concern for us. What is a concern is that we'd like to keep this SuSE IMAP email server as private as possible, and here's where we'd like your comments please. Although the SuSE IMAP server will have a fixed public IP address (and an A record in public DNS if necessary), we'd like not to give it an MX nor a PTR record. We'd like the virtual server at Interland to remain the "front lines" for us, and configure procmail on the SuSE IMAP server to collect, clean and filter from the Interland server all new email, leaving a copy of all email on the Interland server. We would manually purge old emails from the Interland server periodically. (This is a DR requirement for us; we like "belt and suspenders" support.) One additional reason for this proposed setup is that Interland is promising spam/virus filtering at some point, and apparently I have not been the only one asking them about server-side email folder filtering. So, for the day if/when Interland comes through, we'd like not to have to change much on the Interland side, and also be able to repurpose the SuSE IMAP email server quickly. Anything you see that can be improved in this setup? Something that might not work? TIA, and Happy New Year to all, Mark -- _______________________________________________________________ A Message From... L. Mark Stone Reliable Networks of Maine, LLC "We manage your network so you can manage your business." 477 Congress Street Portland, ME 04101 Tel: (207) 772-5678 Web: http://www.RNoME.com