Re: Exchange, sigh
JD Liddil <[email protected]> Tue, 12 May 2015 21:29:22 -0400
| Newsgroups | gmane.mail.mulberry.user |
|---|---|
| Message-ID | <CAN9soBZVnCKstDiyVnxHi64Jqf2c6+AeT+uERPOO9s3vSWOecw@mail.gmail.com> |
Can I please be unsubscribed? I completed the process on mulberry but keep getting messages On Tue, May 12, 2015 at 9:22 PM, Bill MacAllister <[email protected]> wrote: > Many moons ago I tried to use Mulberry to connect to an Exchange > mailbox using IMAP and hit a problem where there were messages that > caused Exhange to drop the connection. When I first encountered this > I just quit using Exchange. Stanford is in the throws of a project to > move to Office 365 and I am seeing the problem again. I don't really > have the option to stop using Exchange this time around. > > Looking at the debugging log I see Mulberry issue the command to > retrieve header information, i.e. > > A00013 FETCH 1406:1448 (FLAGS RFC822.SIZE UID INTERNALDATE ENVELOPE > BODYSTRUCTURE) > > then data is returned for each message until the poison message is > accessed and Exchange hangs up the phone. Have others seen this > problem? Is there a work around? > > Bill > > -- > > Bill MacAllister > Tech Lead, Stanford University > > >