Print

Print


I've got messages queuing in Exchange to send to mail.msu.edu.  On hold with ATS now.

The msu.edu queue is listing this as the error: 451 4.4.0 Primary target IP address responded with: "421 4.2.1 Unable to connect." Attempted failover ro alternate host, but that did not succeed.  Either there are no alternate hosts, or delivery failed to all alternate hosts.

So FYI if you have your own servers.  Mail may be queuing.

Jon Galbreath
MCSE/Security+
Systems Administrator
International Studies and Programs
Ph: 517-884-2144
[log in to unmask]

-----Original Message-----
From: Gary Schrock [mailto:[log in to unmask]] 
Sent: Tuesday, September 14, 2010 9:36 AM
To: [log in to unmask]
Subject: Re: [MSUNAG] mail.msu.edu certificate

On 9/14/2010 9:31 AM, Fishbeck, John wrote:
> In ATS' defense, they announced that this was going to happen several times over the past month via the [log in to unmask] listserv.
>
>    

Ah, apparently I overlooked that email list.  Thanks, I'll make sure I subscribe to that.

Gary

> Regards,
>
> John Fishbeck
> Physical Plant Computer Systems&  Networking Group
>
>
> -----Original Message-----
> From: Gary Schrock [mailto:[log in to unmask]]
> Sent: Tuesday, September 14, 2010 9:26 AM
> To: [log in to unmask]
> Subject: [MSUNAG] mail.msu.edu certificate
>
> I'm sure people have already started to run into this today, but just 
> to warn you, your users might be asking about this.  Apparently they 
> updated the mail.msu.edu ssl certificate this morning.  The Service 
> Status history suggests that "Many clients will not be affected", but 
> so far that's not my experience.  Outlook users doing sends here are 
> getting prompted to accept a certificate that can't be verified.
> (Checking mail doesn't seem to prompt this, but sending mail 
> definitely does seem to be.)
>
> (Personally, I'm seeing this on a Windows 7 machine running Office 
> 2007, all updates installed, and so far everyone that I know using 
> outlook that I've asked has seen it.  So I'd have to wonder about the 
> "Many clients will not be affected.").
>
> One other note, I honestly don't remember seeing any sort of 
> communication that this was happening, did I miss it?
>
> Gary
>
>
>