 |
 |
While we are on the topic of mail.msu.edu: I have been getting ready to implement a new email filtering solution at our college. During testing I noticed that I had to turn off SPF checking, this was due to how forwarding from mail.msu.edu works (which 800+ users at our college currently use). Email forwarding breaks because mail.msu.edu forwards email without modifying the envelope sender (http://www.openspf.org/FAQ/Forwarding). It seems that the only two workarounds for this problem are to either whitelist mail.msu.edu or implement SRS (on mail.msu.edu). So I guess my question is if there are any plans for this issue to be addressed by the mail.msu.edu team? -- Stephen Bogdanski Network Support College of Veterinary Medicine Michigan State University >>> On 5/30/2007 at 9:35 AM, <[log in to unmask]> wrote: > It's true that ACNS is exploring the possibility of outsourcing student > email accounts, but we are very early in the process. We are learning about > options, and no decisions have been made. Some colleagues and I visited > Google's office in Ann Arbor last week to attend their Google Apps open > house. Attendees from MSU and other universities saw Google's > presentations. > > We are working on an RFI (Request for Information) which we will send to > various vendors. If we choose to pursue the outsourcing of student email, > we will follow the normal RFP process and work with members of the campus > community including various committees. > > We're also evaluating ways that we might improve the existing mail.msu.edu > service. We're especially focused on these issues: quotas, spam, features, > and > performance. > > -Ed