While what Chris says is technically correct, it is not the advice
we're giving to end users. We don't want to confuse end users
with a client configuration that mixes the new mail.msu.edu
service for outgoing mail while using Pilot for incoming mail.
This could generate a lot of confusion for customers who,
for instance, have a problem sending or receiving mail and who
call the help desk seeking a diagnosis.
Moreover, a large fraction of customers use Webmail. They do not
have an option of choosing which SMTP server handles their mail;
the message would be especially confusing for them.
So the statement stands. Our advice to Pilot users who experience
problems sending mail to an aol.com address is to upgrade to
>At 11:55 AM 10/21/2003, Rich Wiggins wrote:
>>The solution for Pilot users who can't get mail through to
>>AOL correspondents is to upgrade to mail.msu.edu.
>Let me add a clarification--It isn't necessary to "upgrade to mail.msu.edu"
>in order to send mail through the mail.msu.edu SMTP server. Anyone who has
>an MSU NetID can set up their mail client software to send mail via
>mail.msu.edu while continuing to receive mail from pilot.msu.edu. We have
>set up several computers this way, and it works fine. You get the
>advantages of the authenticated SMTP mail server even if you're not ready
>to convert your whole mailbox and incoming mail to the new server.