Closed
Bug 363522
Opened 19 years ago
Closed 17 years ago
IMAP can not create folder after folder in server deleted
Categories
(MailNews Core :: Networking: IMAP, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: thomas, Assigned: Bienvenu)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.8) Gecko/20061030 SeaMonkey/1.0.6
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.8) Gecko/20061030 SeaMonkey/1.0.6
If someone accidentally delete ./Maildir Folder then create Maildir again in the server, then seamonkey cant rebuild the folder even the account at seamonkey have been removed and created again, not until delete the account and exit the seamonkey program, probably cache problem ? but i already clear the cache
Reproducible: Always
Steps to Reproduce:
1. create some folder example: Cron Job using seamonkey
2. delete ./Maildir in the server ( I am using Courier 4.x )
3. recreate ./Maildir
4. try to access the folder
5. delete the folder
6. try clear cache
7. do the delete or recreate the folder
Actual Results:
no folder can be created
Expected Results:
the software should automaticly sync with the server without have to delete the account exit the program and create the account again, well at least we dont have to exit the program should be enough but well automatic sync is prefered
Comment 1•17 years ago
|
||
SeaMonkey v1.0.x is not supported anymore.
Can you reproduce with SeaMonkey v1.1.9 ?
Summary: IMAP Cant create folder after folder in server deleted → IMAP can not create folder after folder in server deleted
Version: unspecified → SeaMonkey 1.0 Branch
Comment 2•17 years ago
|
||
(1 month later)
No reply from reporter.
(Would have been "Incomplete", now is) R.Invalid
Reopen if you can reproduce with SeaMonkey v1.1.9.
Assignee: mail → bienvenu
Component: MailNews: Main Mail Window → Networking: IMAP
Product: Mozilla Application Suite → Core
QA Contact: networking.imap
Version: SeaMonkey 1.0 Branch → 1.8 Branch
Updated•17 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → INVALID
Comment 3•17 years ago
|
||
No bug / patch referenced as the fix.
-> WORKSFORME
Resolution: FIXED → WORKSFORME
Updated•16 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•