Technical Coordinators Meeting August 3, 2004

Spam/Virus Blocking Blocking umn.edu and other “protected” sites if we mark them “insecure” (still protected from other blocks) Checking (but not yet blocking) based on the XBL ( xbl.spamhaus.org ) Now treating “inactive” MTA same as “never seen before”

Spam/Virus Blocking Require rDNS for all but 200 /16 nets –About 50 each in 207, 208, 209, 216 /8’s –Plenty of manual, semiautomatic exceptions AOL “Feedback Loop” and forwarding heck Investigating ClamAV –LISTSERV –Outgoing ( smtp, smtp-gw, relay )

Spam/Virus Blocking

Phase-out of non-SSL services Timeline remains: July 1, 2005 Unauthenticated SMTP gateway statistics

Phase-out of non-SSL services

Only SMTP stats now; telnet, FTP, POP, IMAP coming next month Finding misconfigured systems (should be using relay.tc.umn.edu ), viruses– don’t want to count those! notifications slated for Nov, Feb

Hardware Upgrades servers –Two servers on SAN with 1GB quotas –Two more, and premium/interactive (garnet) on SAN by start of Fall Semester –1GB quotas for everyone by start of Fall! –Solaris 9—prerequisite for longer Internet passwords…

Hardware Upgrades MX servers for umn.edu –3 x Sun V210 –One running in production since Thu Outgoing SMTP ( smtp.umn.edu, smtp- gw, relay ) –3 x Sun V210 –Not hurting for capacity here, so will phase in more slowly

Hardware Upgrades Internet Services – –x500.umn.edu (CAH) –*. .umn.edu DNS –RADIUS –X.500 lookups (finger, gopher, whois, ph) –Also 3 x Sun V210

Hardware Upgrades X.500 backend database server –Sun V240 –Last Solaris 2.6 machine!

Software Upgrades LISTSERV 1.8e –Niftier web interface Web-based moderation List configuration wizards –Content filtering Remove vacation messages Filter/restrict type of attachments –Precedence: list in headers ;) BIND 8.4.4

Software Upgrades Apache /mod_ssl PHP –Supports GD, mysql, openssl, XSLT (latter doesn’t work?) –5.0 just came out—too new Lynx (help no longer a porn portal) X.500 directory (in test; awaiting vendor bugfix before production)

Lyris Massmailing server Right now just “looking at it” IS would run server, U Relations would likely manage it (assign permissions, etc.) Would remove some workload off IS staff for doing massmailings

PKI Pilot scheduled to begin late Sept More details at Sept techc- and net- people

Questions?