1 / 8

Spam Filtering at ASU Ronald Page

Spam Filtering at ASU Ronald Page. Maricopa Association Of Governments Telecommunications Advisory Group 23 September 2004. Agenda. Requirements List Product Selected Server Architecture Infrastructure Integration Usage Statistics Questions. Requirements. Server-based solution

terry
Télécharger la présentation

Spam Filtering at ASU Ronald Page

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Spam Filtering at ASURonald Page Maricopa Association Of Governments Telecommunications Advisory Group 23 September 2004

  2. Agenda • Requirements List • Product Selected • Server Architecture • Infrastructure Integration • Usage Statistics • Questions

  3. Requirements • Server-based solution • Work for all e-mail systems (e.g. Exchange, IMAP) • Standalone appliance • Integrate with existing infrastructure • Authentication, Mail Delivery, Aliases • Individual User “Opt In” • Quarantine rather than delete (2-week rollover) • Individually configurable “white/black lists”

  4. Product Selected Active SMTP (ASMTP) from ESCOM (http://www.escom.com) ESCOM's patented technology dynamically identifies techniques used by spammers -- including SMTP direct clients, open relays, and forged e-mail addresses it has never seen before -- and quarantines or rejects junk mail sent using these and other techniques • ASU does not use spam “content filtering” in ASMTP • The anti-virus utility is not used either, although viruses are typically caught as spam • E-mail is not stored (even temporarily) on the ASMTP device (thus expensive disk is not required) • We can easily remove spam filtering from the infrastructure

  5. Server Architecture

  6. Infrastructure Integration • Web interface for managing quarantine and black/white lists rewritten at ASU (using ASMTP API). • Integrated into single sign-on web environment. • Able to manage all e-mail aliases in one spot • Tied to Computer Accounts process • Allows new user to enable filtering when joining University • Automatically clean-up databases when user leaves • MX records* for Exchange and IMAP servers moved to ASMTP (to enable filtering on those addresses). * MX records (a.k.a. mail exchange records) are DNS entries, used only by e-mail systems, that define where e-mail is sent for a particular domain name.

  7. Spam Filter Statistics • 40,000 Active IMAP Accounts, 9,000 Exchange Accounts • 15,000 aliases have opted in • 575,000 avg. messages processed per day • 425,000 delivered / 150,000 quarantined • Quarantined messages are kept for up to 2 weeks. There is 25G of quarantined e-mail.

  8. Questions? Ronald Page Ron.Page@asu.edu 480-965-2986

More Related