Ethical Hacking Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package. | Computer Forensics Training at InfoSec Institute Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors. |

| Subject: | Re: Email Gateways |
|---|---|
| Date: | Fri, 18 Nov 2005 08:49:54 +0100 |
Good morning! On Thu, 17 Nov 2005 16:11:23 -0000 "Grant, John" <John.S.Grant@ds-s.com> wrote:
What's everyone using at the moment?
A well configured Postfix MTA with a number of RBLs plus a few custom access blocks, doing filtering via AV and bayes-spamfilter. On Linux. Rejection-rate early in SMTP dialogue at 95%, the ones getting through the first stage are ~20% SPAM (but get marked) and ~1% viruses (filtered).
All advice welcome.....gotta move towards a hardware based mail gw soon and wanna get some idea's from you lot please!
I've yet to see a "hardware-based" mail gw. I do know pre-packed servers and mail appliances (i.e. "all in a closed box" systems), but I've not seen any SMTP-in-ASIC (thus "real hardware") mail gateways. If I missed one, pointers are highly welcome. So why do you need a "hardware based" system? I think that is the wrong starting point. *First* list your *functional* requirements, ranked/priorized. *Then* look at systems that you fulfil your *functional* needs. I guess you either might have performance problems (myth: hardware is faster than software) or an admin that is not knowledgeable enough or only part-time available (myth: appliances are buy-and-run). Performance problems? Are you sure it's the mail server's "horsepower"? Or maybe it's your internet connection, that is congested? Or your architecture (forwarding-MTA without RBLs and the main mail server bouncing all the fake NDNs)? Architectural problems usually cannot be tackled with a different box anyway, so your selection may be moot. Feature or administration problems? Maybe a proper training for your admin can help - and usually will be cheaper and longer lasting than just buying a box. Or maybe you might decide to go for a managed mail solution (a la GMAIL for companies). For your boss "outsourcing the email service" probably will sound better than "we should use GMAIL". ;-) In short: don't focus on a solution before you defined and priorized your requirements. Bye Volker -- Volker Tanger http://www.wyae.de/volker.tanger/ -------------------------------------------------- vtlists@wyae.de PGP Fingerprint 378A 7DA7 4F20 C2F3 5BCC 8340 7424 6122 BB83 B8CB
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | RE: ISS Proventia Integrated Security Appliance, Zachary Richmond |
|---|---|
| Next by Date: | Cisco VPN Dialer to Netscreen-50, Mike Jones |
| Previous by Thread: | Re: Email Gateways, David Bonwick |
| Next by Thread: | RE: Email Gateways, ken zo |
| Indexes: | [Date] [Thread] [Top] [All Lists] |