User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.4) Gecko/20030624 Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.4) Gecko/20030624 Usualy, I work with mozilla MailNews, but some time I need to use Apple Mail. I use two email accounts with IMAP, on 1 Exchange Server. When I switch from a MUA to An other, IMAP folders are some time moved, deleted or renamed. Reproducible: Sometimes Steps to Reproduce: 1. IMAP account configured on Apple Mail & Mozilla MailNews 2. create folders (Mozilla) 3. put mails in folders (Mozilla) 4. quit Mozilla 5. starting Apple Mail 6. create folders (Apple Mail) 7. put mails in folders (Apple Mail) actually, a bug may occur with apple mail on IMAP folders 8. quit Apple Mail 9. Start Mozilla MailNews Actual Results: folders are moved, renamed or deleted
can you attach an imap protocol log and give an example of what you mean? It's unclear to me from the bug report. Mozilla doesn't rename/delete/move folders on the server unless you issue the appropriate command with the client, so something else is going on. Here's how to generate a protocol log: http://www.mozilla.org/quality/mailnews/mail-troubleshoot.html#imap thx.
Status: UNCONFIRMED → NEW
Ever confirmed: true
I use MACOS X and Mozilla doesn't create logfile. I followed the instructions on the webpage ( I create the right file with the right content in the right place ). I also tried to use env variables. nothing works.
I've heard that the Unix instructions work for Mac OS/X, though it sounds like you tried that.
I have tried again with this version of mozilla : Mozilla 1.6 Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; fr-FR; rv:1.6) Gecko/20040113 I followed the procedure to generate a log file. No thing happened. is there another procedure to generate the log file ( like command line args ) ? the problem does not happen with ThunderBird 0.4
reporter appears to be gone => incomplete
Status: NEW → RESOLVED
Last Resolved: 11 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.