Actually, I just tried my backport (1.19~rc3-1~bpo50+1) and it doesn't
seem to solve this problem, same error. 

Would this require the backend imap server to also be fixed for the
issue before it worked via perdition?

micah



-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to