jadolg / webpymail

Automatically exported from code.google.com/p/webpymail
GNU General Public License v3.0
0 stars 0 forks source link

imaplib2.imapp.Error: Don't know how to parse the LIST response: () "/" INBOX/Work #2

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Check out svn trunk rev 15
2. Change directory and follow log below, connecting to an Exchange 2007
imap server
3. Iterating over the Folder object results in the error below.

What is the expected output? What do you see instead?
Was expecting a list of folder objects. Got an exception instead.

What version of the product are you using? On what operating system?
Trunk revision 15, on Fedora 9, Python 2.5.1 against Exchange 2007 IMAP4
service.

Please provide any additional information below.
>>> import hlimap
>>> M = hlimap.ImapServer(server,ssl=True)
>>> M.login(username,password)
{}
>>> [ x for x in M.folders ]
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "hlimap/imapfolder.py", line 227, in __iter__
    self._getFolders()
  File "hlimap/imapfolder.py", line 211, in _getFolders
    result = self._imap.lsub(self.directory, self.pattern)
  File "imaplib2/imapp.py", line 689, in lsub
    pattern ))['list_response']
  File "imaplib2/imapp.py", line 431, in processCommand
    tag, response = self.send_command(command)
  File "imaplib2/imapll.py", line 270, in send_command
    return tag, self.read_responses(tag)
  File "imaplib2/imapll.py", line 328, in read_responses
    return self.parse_command(tag, response)
  File "imaplib2/imapp.py", line 248, in parse_command
    self._parse_untagged(tag, response['untagged'])
  File "imaplib2/imapp.py", line 242, in _parse_untagged
    meth( code, args )
  File "imaplib2/imapp.py", line 340, in LIST_response
    args )
imaplib2.imapp.Error: Don't know how to parse the LIST response: () "/"
INBOX/Work

Original issue reported on code.google.com by MattH...@gmail.com on 10 Dec 2008 at 12:07

GoogleCodeExporter commented 9 years ago
Thank you for your bug report!

I've made extensive changes on my svn repo where this issue is solved I'll 
commit 
all the changes ASAP.

Original comment by hguerreiro@gmail.com on 21 Jan 2009 at 12:54

GoogleCodeExporter commented 9 years ago
Fixed on r16.

Original comment by hguerreiro@gmail.com on 22 Jan 2009 at 10:37