Closed
Bug 730449
Opened 14 years ago
Closed 8 months ago
folder creation on imap account fails silently of name contains illegal characters
Categories
(MailNews Core :: Networking: IMAP, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: johannes.linke, Unassigned)
References
(Blocks 2 open bugs)
Details
to reproduce: create a folder in an IMAP account with a name containing & or + or other special characters.
result: nothing happens.
expected: the "new folder"-dialog should forbid entering such characters, accompanied by some warning.
Comment 1•14 years ago
|
||
(In reply to Johannes Linke from comment #0)
Can you log the IMAP session and report it here? https://wiki.mozilla.org/MailNews:Logging
| Reporter | ||
Comment 2•14 years ago
|
||
3404[c10f40]: 9324000:imap.gmx.net:A:ProcessCurrentURL: entering
3404[c10f40]: 9324000:imap.gmx.net:A:ProcessCurrentURL:imap://johannes%2Elinke%40gmx%2Ede@imap.gmx.net:993/create%3E/INBOX/unallowed+name: = currentUrl
3404[c10f40]: 9324000:imap.gmx.net:A:SendData: 17 create "INBOX/unallowed+name"
3404[c10f40]: 9324000:imap.gmx.net:A:CreateNewLineFromSocket: 17 NO unallowed folder
3404[c10f40]: 9324000:imap.gmx.net:A:SendData: 18 list "" "INBOX"
3404[c10f40]: 9324000:imap.gmx.net:A:CreateNewLineFromSocket: * LIST (\HasChildren) "/" INBOX
3404[c10f40]: 9324000:imap.gmx.net:A:CreateNewLineFromSocket: 18 OK LIST completed
this is what gets logged when creating the unallowed folder. not including the rest of the log because i have no idea what gets logged :)
Comment 3•14 years ago
|
||
Looks like + isn't supported on your server
Component: General → Networking: IMAP
Product: Thunderbird → MailNews Core
QA Contact: general → networking.imap
Updated•13 years ago
|
Blocks: folders-with-special-characters
Comment 4•10 years ago
|
||
Removing myslef on all the bugs I'm cced on. Please NI me if you need something on MailNews Core bugs from me.
Updated•3 years ago
|
Severity: normal → S3
Comment 5•8 months ago
|
||
This doesn't seem to be a general problem, WFM in Daily.
Status: UNCONFIRMED → RESOLVED
Closed: 8 months ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•