Dan and list members, Outlook 2013 also removes header information when copying/moving from the INBOX to another IMAP folder. This is not good if you're training a spam filter. It screwed up our DSPAM database and we had to start over rebuilding the database from scratch.
Eric On 12/2/2013 9:33 AM, Dan McAllister wrote: > Sorry I'm so late on this one -- I took a 4-day weekend for the > Thanksgiving holiday! :-) > > I have bad news RE: _*Outlook 2013*_ and IMAP -- its _*broken*_, and > MS hasn't given any real signs (yet) that they're keen on fixing it. > > I'm sure by now you've Google'd IMAP and Outlook 2013 -- and you have > probably found what I did: Hundreds (thousands?) of /irate /users who > have found that Outlook 2013 completely re-wrote the IMAP part of the > application, and REALLY /*REALLY */messed it up. Among many other > changes, IMAP local PST files are now stored as OST files (the right > thing to do, IMHO -- just a bad implementation, not a bad idea). Also, > the ability to self-map the reserved folder functions (sent items, > trash, drafts, etc) is gone. Outlook 2013 will determine for you which > folder is the best one, and use that one... whether it is the right > one or not, and it cannot be overridden (at least that I could find). > Most of the problems I noted in my searches seem to stem from either > these automated folder mappings, or synch issues. To be honest, I'm > not at all sure why MS hasn't put the Outlook Development Team back on > this issue -- my guess is that a week of intensive debugging and > they'd find at least the major cause of these issues... but > apparently, they have other priorities. > > I have only a handful of clients on Outlook 2013 (fortunately, most on > Office 365). The ones who use Outlook.com and Exchange based email are > quite happy with it. But those who use QMT, GMail, or other IMAP based > mail services, are FURIOUS. NOTE: If you call MS support (you paid for > it with the Office365 subscription), and DEMAND it, they will > authorize you to download and use Outlook 2010 as part of your > Office365 subscription. ALSO OF NOTE: I did have one client who was so > irate that they declined the charge for the Office365 -- told their > credit card company the software was misrepresented and charged the > entire purchase back to MS... and they (MS) didn't contest it.... > speaks volumes, if you ask me. This particular client simply > re-installed Office 2010 Enterprise throughout, and while they WANT to > be using Word, Excel, etc under 2013, they're mollified by the fact > that Outlook actually works with their mail server. > > _*FWIW: In your case:*_ > - If the folder was renamed in Outlook 2013, it may or may not have > actually changed the name on the server. Use a webmail interface to check? > - If the folder was renamed in any other client (or from the webmail > interface), Outlook 2013 may or may not detect the change. What I have > done successfully in the past is to _delete the OST_ file for the > account, restart Outlook 2013, and let it completely re-synch the > account (e.g.: re-build the OST file from scratch). A ROYAL pain, I > know -- but its the only method I've found yet that actually makes > Outlook 2013 get it right (at least until something else changes on > the server that the Outlook client doesn't recognize). > > I hope this helps. > > Dan McAllister > IT4SOHO > > > > On 11/28/2013 9:48 AM, Eric Shubert wrote: >> On 11/28/2013 02:17 AM, Tommi Järvilehto wrote: >>> Have you guys seen Outlook 2013 working correctly when renaming imap >>> folders? >>> >>> While testing I have seen it working just couple of times. Most of the >>> times it just doesnt do anything. >>> Same problem is with both qmt courier-imap and dovecot-imap servers. >>> Thunderbird folder rename is working correctly with these servers. >>> >>> I have also tested it with another ISP that has some version of >>> dovecot/postfix server and its working correctly. >>> >> >> I have not seen O'13. >> Have you googled the problem? I expect it's strictly imap related. >> There's likely a fix of some sort for that, perhaps a workaround >> setting or a more recent version. >> >> Can you post your dovecot configuration? >> Verify version of dovecot with the other ISP that's working? >> > > > -- > > PLEASE TAKE NOTE OF OUR NEW ADDRESS > =================================== > IT4SOHO, LLC > 33 - 4th Street N, Suite 211 > St. Petersburg, FL 33701-3806 > > CALL TOLL FREE: > 877-IT4SOHO > > 877-484-7646 Phone > 727-647-7646 Local > 727-490-4394 Fax > > We have support plans for QMail! >
