220 likes | 237 Views
E-mail Technical Coordinators Meeting. Chris Bongaarts Steve Siirila October 13, 2004. E-mail Hardware. Two servers not yet on SAN One is not in use, ready for SAN install Other has fewer and less-intensive users Occasional load problems, fixed by redistributing heavy users.
E N D
E-mail Technical Coordinators Meeting Chris Bongaarts Steve Siirila October 13, 2004
E-mail Hardware • Two servers not yet on SAN • One is not in use, ready for SAN install • Other has fewer and less-intensive users • Occasional load problems, fixed by redistributing heavy users
Spam/Virus Blocking • All inbound and outbound mail is being virus-scanned (including LISTSERV) • New hardware is keeping up nicely • Outbound viruses reported to OITSEC • Inbound viruses logged to recipients’ block lists
Phase-out of non-SSL services • Protocols: • IMAP • POP • SMTP • FTP • telnet (currently umn.edu only) • Statistics
relay.tc.umn.edu changes • Relay-by-IP services is changing addresses due to hardware upgrades • New IP: 160.94.160.49 (was .10) • Old address stops working Nov. 1
relay.tc.umn.edu changes • “Registration” will be required for email servers using the relay.tc.umn.edu service when unauthenticated gateway goes away (July 1, 2005) • Current legitimate email servers will be automatically “preregistered” • New servers must request access to use relay service • Will eliminate vulnerability to compromised PC’s within University
X.500 changes • GDS 2003 upgrade delayed (again) due to additional problems discovered during testing • Three patches received, in testing • Backend DB upgrade delayed due to faulty hardware
X.500 password changes • Long Internet passwords are coming! • Requires backend DB upgrade • Must identify and test all affected systems/software (about a dozen)
X.500 password changes • passwd/chsh commands going away on premium/interactive server next Monday, October 18 • ALL password/shell changes must be done via web directory update
Central Active Directory Phase-out • Only two departments left in umn.edu forest • Plan: get rid of centrally-managed forest • Recommendation for departments: run your own forest • Will work with remaining departments to transition off
Lyris • Lyris ListManager is a system for sending out “e-mail marketing campaigns” • OIT/IS will manage the hardware • U Relations will manage the application (assigning user roles, etc.) • Will use Central Auth Hub for authentication
Lyris • Can access external databases to generate recipient lists • Will NOT replace LISTSERV • Interested departments should contact U Relations for access • Mass-mailing policies still in force (VP or U Relations approval required)
PKI • Currently in internal testing phase • Pilot phase begins in the next couple weeks • We will be contacting key people to enlist volunteers
Chris Bongaarts cab@umn.edu 5-1809 Steve Siirila sfs@umn.edu 6-0244 ‘Till next month…