1 / 22

E-mail Technical Coordinators Meeting

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.

mab
Download Presentation

E-mail Technical Coordinators Meeting

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. E-mail Technical Coordinators Meeting Chris Bongaarts Steve Siirila October 13, 2004

  2. 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

  3. 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

  4. Phase-out of non-SSL services • Protocols: • IMAP • POP • SMTP • FTP • telnet (currently umn.edu only) • Statistics

  5. 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

  6. 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

  7. 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

  8. X.500 password changes • Long Internet passwords are coming! • Requires backend DB upgrade • Must identify and test all affected systems/software (about a dozen)

  9. 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

  10. 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

  11. 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

  12. 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)

  13. PKI • Currently in internal testing phase • Pilot phase begins in the next couple weeks • We will be contacting key people to enlist volunteers

  14. Chris Bongaarts cab@umn.edu 5-1809 Steve Siirila sfs@umn.edu 6-0244 ‘Till next month…

More Related