Greetings to ya!
As a customer (and account manager) who has domains on both the venus and mercury servers, I must say that I (we) am/are very pleased with the email filtering ability of Cpanel.
1.) As a very minor item to add here first, at the top of the Cpanel screen after it gives the Welcome, there was a message saying that my contact email was needed..... it took me a little while to figure out that it was not one of the "Function Icons" that was to be used to update my "contact information"..... as it said "Please update your contact information here."
Using IE 6.0 SP1 as browser, that line just appeared as normal (bold?) font without any typical link-effect (usually the underscore for text links), thus it took me a short while to realize, by moving my cursor along that line to the word "here" (when it then changed colour), that the last word on the line was the spot to use to go update the contact info, which of course I did.
That's only a tiny item that may or may not confuse someone else, but one might look at Cpanel (after login to one of the servers). Might be just my browser or it might be just a minor font/format/css bug or oddity. Just thought I would mention that one.
2.) My main desire of "adding" this topic, though is that I have seen a discrepancy in the FORMAT of email headers, a difference between that of the venus server (where I handle email for two domains on it) and that of the mercury server. Whereas this particular "field" is sometimes used for email filtering, finding that it is "missing" on the mercury server, I thought that I would mention it here.
Example and description (for a typical/example email header for one of the domains on venus server a snippet of the header might look like this.
Return-path: <
maggie@russianriver.com>
Envelope-to:
myemail@mydomain.comDelivery-date: Wed, 14 Jan 2004 12:48:59 -0800
Received: from [128.121.231.119] (helo=cherry2b.cb-solutions.net)
by venus.lunarpages.com with esmtp (TLSv1:DES-CBC3-SHA:168)
(Exim 4.24)
id 1Agrwh-0000My-5R
for myemail@mydomain.com; Wed, 14 Jan 2004 12:48:59 -0800
Received: from chamber (rp42.pm3a.monitor.net [65.214.144.170])
(authenticated bits=0)
by cherry2b.cb-solutions.net (8.12.10/8.12.9) with ESMTP id i0EKjX7L086784;
Wed, 14 Jan 2004 13:46:22 -0700 (MST)
Message-ID: <002901c3dade$fe16ae40$aa90d641@chamber>
From: "Maggie" <
maggie@russianriver.com>
To: "Russian River Chamber of Commerce & Visitor Center" <
info@russianriver.com>
Subject: Fw: Shape our Tourism Future and Attend the Russian River Tourism Summit - Please
The very first or topmost Received: line is what the venus server inserts.
In this example it "does show" correctly (similar/same structure/format for both domains on venus) correctly with the "for email" followed by the date and time.
Conversely, what I have discovered/found or just realized is that for email coming into the domain on the mercury server that the "for email" field in the first/topmost Received: line does not exist. Thus, where I sometimes filer All Headers looking to match (regex) using
for\ (sales\@|webmaster\@|billing\@|etctypicalspammersuse\@)
does not work for the mercury server because that field is missing or not there.
It might be possible that such "for email" field was overlooked or may have been commented out at some time, but where mercury was one of the initial servers for lunarpages it could have been just a minor goof or whatever too, and lots of work and effort has gone into lunarpages.com since its beginning days.
But, I thought I would mention this item for the email Received: line of the header for emails on the mercury server.
Note, in my example header I substituted "
myemail@mydomain.com" for privacy, but otherwise no change on that header. If an admininstrator could take a peek at that some time in the future would be appreciated and its no biggie or anything really service effecting but it does inhibit filtering with regex for that field (not always is someone's email in the To or the Envelope fields, thus filtering for a "typical spam name@" in that field does come in handy.
Thanks much for any time.
PS: Again, I do have say that the features and abilities are superb, and I really do love to block "most" spam (versus using the other spam program)... this way I have just said "no" for IPs from "major" sources of spam that I (we) just don't have any contact with. For many users, though, this means of blocking may be beyond their capabilities.... but for lunarpages to have it "available and usable" is ABSOLUTELY GREAT!!!
(Regex, regular expression, is "not" exactly "regular" for most people.)
Thanks.
