User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; .NET CLR 1.1.4322) Build Identifier: Version 0.9 (20041103) 1) Critical: Account setting import for Outlook imports account settings from Outlook Express instead. 2) Non-Critical: Email import does not like folder names with the '/' character in it. It seems to import the email but renames the folder to gibberish. Reproducible: Always Steps to Reproduce: First ----- 1. Tools --> Import 2. Settings 3. Outlook Second ------ 1. Tools --> Import 2. Mail 3. Outlook Actual Results: 1) Imported account from wrong program (Outlook Express instead of Outlook) 2) All imported OK but renamed folder names with the '/' character in it Expected Results: 1) Imported account settings from MS Outlook 2) Imported all folder names without renaming them
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.