IMAP Bug - Mail Headers are killed during folder move operation

Întrebare IMAP Bug - Mail Headers are killed during folder move operation

  • Tuesday, December 18, 2012 7:39 PM
     
     

    I've noticed a strange behavior with IMAP in Outlook 2013.

    If I move Mail from my Inbox to another IMAP folder the Mail Headers were killed. Our Mail-Server is inserting some special X-Headers, which are used by our self-coded Outlook AddIn. Works great in Outlook 2007 and Outlook 2010. It also works in Outlook 2013, but if we move the Mail to another folder (or to Sent Items, or to Trash), the Mail Headers are removed by Outlook during transfer.

    I assume this is not an intended feature of OL 2013, looks like a bug :-) !

    I also noticed that OL 2013 IMAP sync fails from time to time. Deleted Mails (moved to Trash and then deleted in Trash) show up again if my IMAP Inbox folder if I connect with OL 2010 from another machine. That's really bad for a RTM version.

    Please tell me how I can contact the Outlook Dev-Team to file bug reports for these 2 bugs.

All Replies

  • Thursday, December 20, 2012 9:57 AM
    Moderator
     
     

    Tested in Outlook2010 with IMAP account but not got such behavior yet. I will install Outlook 2013 in my test machine to check if I can reprodue it. Thanks.

    Cheers,
    Tony Chen
    Forum Support
    ________________________________________
    Come back and mark the replies as answers if they help and unmark them if they provide no help.
    If you have any feedback on our support, please contact tnmff@microsoft.com.

  • Friday, December 21, 2012 9:45 AM
    Moderator
     
     

    Tried in Windows 7 with Outlook 2013. The headers is not removed in IMAP account. Is it possible that your self-coded is not compatible with Outlook 2013 and damage the headers in this situation? Please disable it to try the result. Better to capture some necessary screenshots and post here for further researching. Thanks.

    Cheers,
    Tony Chen
    Forum Support
    ________________________________________
    Come back and mark the replies as answers if they help and unmark them if they provide no help.
    If you have any feedback on our support, please contact tnmff@microsoft.com.

  • Monday, December 24, 2012 2:04 AM
    Moderator
     
     

    Hello, any update?

    Cheers,

    Tony Chen

  • Thursday, December 27, 2012 11:35 PM
     
     

    Hello Tony!

    Our Add-In does nothing with the Mail! No modification! I am running Windows 8 RTM, not Windows 7. Maybe I should test it on Win 7?

    FYI: we do not use an Exchange Server, we are using Courier IMAP (http://www.courier-mta.org/imap/) on Linux (for years).

    As I said: Outlook 2007/2010 works as expected!

    I am currently using Windows 7/Outlook 2010 to move my mails from my Inbox to certain folders. If I access the Mails in the folders via Outlook 2013 (after moving with W7/OL2K10) the mail headers are present (only a move in Outlook 2013 kills the headers). It's annoying to boot up my old system for mail moves :-( ...

  • Friday, December 28, 2012 7:41 AM
    Moderator
     
     

    As you say, you may find a Windows 7 to check if the moving header issue is caused by OS site.

    And you may also check if we can reproduce the issue if you setup a Gmail IMAP account.

    We'd better to connect the Courier IMAP support if the issue only happens in this Courier IMAP Server.

    Feel free to post back.

    Cheers,
    Tony Chen
    Forum Support
    ________________________________________
    Come back and mark the replies as answers if they help and unmark them if they provide no help.
    If you have any feedback on our support, please contact tnmff@microsoft.com.

  • Monday, December 31, 2012 2:19 AM
    Moderator
     
     

    Hi,

    Just checking in to see if the information was helpful. Please let us know if you would like further assistance.

    Cheers,
    Tony Chen
    Forum Support
    ________________________________________
    Come back and mark the replies as answers if they help and unmark them if they provide no help.
    If you have any feedback on our support, please contact tnmff@microsoft.com.

  • Thursday, January 03, 2013 1:50 AM
    Moderator
     
     

    Hi,

    I'm marking the reply as answer as there has been no update for a couple of days.
    If you come back to find it doesn't work for you, please reply to us and unmark the answer.

    Cheers,
    Tony Chen
    Forum Support
    ________________________________________
    Come back and mark the replies as answers if they help and unmark them if they provide no help.
    If you have any feedback on our support, please contact tnmff@microsoft.com.

  • Saturday, February 09, 2013 1:14 PM
     
     

    This issue still exists. (Using Outlook 2013 on Windows 7 with the latest updates, version 15.0.4420.1017)

    Steps to reproduce:

    1. Access email in Outlook from a non-Exchange account (e.g. IMAP) that were delivered from any non-Microsoft mailserver (e.g. Gmail) and go into "Message Options" to view the message headers.
    2. Copy message headers to textfile / notepad for comparison, look out for any X-* message headers.
    3. Move aforementioned email using Outlook into different folder (tested move between different imap accounts).
    4. Re-open email and go into "Message Options" again to view message headers.
    5. Compare with previously copied headers from textfile...
    6. ... in Outlook 2013, all X-* message headers disappeared (but this is where it gets crazy) and X-Mailer gets rewritten (!) to Outlook 15.0

    Moving email is not meant to change its content. It is meant to change the location of content.
    Moreover, any additional "Received*" headers are removed as well, which sometimes may provide helpful diagnostics information.

    Using Outlook 2010 the email headers stay the same (=expected behaviour), using Outlook 2013 email headers are removed and a few are rewritten (!).

    Please answer the following:

    1. How do you justify changing the semantics of the "move" operation in this context?
    2. Does Microsoft intend to fix this behaviour or provide a workaround (e.g. registry setting or something similar) to change this default behaviour?
    3. If there is a workaround or fix that will be provided, can you give an estimate of when to expect this fix to be delivered?

    If there is no way to rectify this, I have to recommend my clients to stay with Outlook 2010 and at some point (end of support) migrate to a different client.

    Thank you.


    • Edited by Ben E. S Saturday, February 09, 2013 1:26 PM added Outlook 2013 version information
    •  
  • Tuesday, February 19, 2013 1:35 AM
     
     

    Thank you so much, Ben, for confirming my findings!

    I couldn't have described it better myself! :)

    Let's hope we 'll get an answer to your three questions. It's very important for us, too. Currently, we also recommend our Clients to stay with Outlook 2010 until Microsoft has fixed this BUG (YES, it is a BUG!!).

    Thank you!

  • Tuesday, February 19, 2013 4:30 PM
     
     

    @Tony Chen:

    Does the Dev.-Team of Outlook 2013 read this thread? - or: how can we contact them? ...or is there any possibilty to file a bug report? ...or: would you please be so kind to forward this to the right people?

    Thank you in advance!

  • Thursday, March 14, 2013 1:54 AM
     
     

    No answer is also an answer :-( !

    Okay, if no one is willing to make Outlook 2013 bug free, respectively help me to contact the Outlook team (come on guys: can no one provide me a link to a bug submitting form or an email-address of the Outlook Dev-Team?), I'll have to develop my own folder move operation via our Outlook AddIn.

    Of course, this is ridiculous. Having a commercial product like Outlook, which isn't capable of correctly moving Mails between IMAP-Folders without destroying mail headers, so I have to code my own solution :-( ...

  • Thursday, March 14, 2013 11:02 PM
     
     

    I have to admit I'm mentally preparing myself that this won't be fixed.

    When handling large amounts of emails via IMAP, I'm evaluating Claws-Mail.
    Should no alternative come up by mid-2013 I'll consider customizing its UI to make it more userfriendly for my customers.

    Everything else stays at Outlook 2010, given the necessity of Exchange-access (for tasks/calendar&scheduling/contacts and sometimes shared folders.)

    Using two so different products side-by-side is by no means ideal, but a lot better than losing information.

    It's sad that a only slightly deficient product (in terms of IMAP support) like Outlook 2010 was replaced by a much more performant, but buggy (given the bug described above) product - Outlook 2013.