No, that's not it. The mail machines have been moved to a (new?) vm
system, I think.
What I don't yet understand is how the state information got lost for
pop clients.
--STeve Andre'
On 11/23/15 15:20, David McFarlane wrote:
> Maybe the MSU mail team is deprecating POP3 support (and hasn't told
> anyone)?
>
> -- dkm
>
>
> At 11/23/2015 02:15 PM Monday, Jalal Jaleel wrote:
>> There are add ons for Outlook and Thunderbird to delete duplicate
>> emails. The bigger problem I saw is on Thunderbird where deleted
>> emails re-appeared in the Inbox.
>>
>> Jalal
>>
>> Jalal Jaleel
>> Computer Services
>> W.K. Kellogg Biological Station
>> Michigan State University
>> helpdesk: 269-671-2100
>> office: 269-671-2215
>> cell: 202-906-0748
>>
>> On 11/23/2015 1:49 PM, David McFarlane wrote:
>>> No, they can't. I just called, and they only said that something
>>> indefinite happened, it's fixed, and the only recourse that users
>>> have is to delete the duplicates. No further details.
>>>
>>> -- dkm
>>>
>>>
>>> At 11/23/2015 10:38 AM Monday, Murray, Troy wrote:
>>>> The MSU IT Service Desk could tell you what, if any, changes were
>>>> made.
>>>>
>>>> Troy Murray
>>>> Solutions Architect
>>>> Michigan State University (MSU) Information Technology
>>>> Hannah Tech Center (HTC)
>>>> 4700 S Hagadorn Rd Ste 152
>>>> East Lansing, MI 48823
>>>> (e) <mailto:[log in to unmask]>[log in to unmask]
>>>> (p) <tel:517-884-3031>517-884-3031
>>>> (f) <tel:517-432-6680>517-432-6680
>>>> (w) <http://tech.msu.edu>tech.msu.edu
>>>>
>>>>
>>>>
>>>>
>>>> On Mon, Nov 23, 2015 at 7:36 AM -0800, "STeve Andre'"
>>>> <<mailto:[log in to unmask]>[log in to unmask]> wrote:
>>>>
>>>> On 11/23/15 09:39, Bill Park wrote:
>>>>> Was something changed over the weekend with MSU mail? We're
>>>>> seeing a lot of users that are downloading mail via POP to a local
>>>>> client having all of their mail retrieved from the MSU mail server
>>>>> again creating a lot of duplicates in the inbox.
>>>>> So far we've seen this in Outlook and on iOS so it doesn't seem to
>>>>> be a problem with any specific client.
>>>> Yes, we've seen it as well.
>>>>
>>>> --STeve Andre'
>
|