-
Notifications
You must be signed in to change notification settings - Fork 64
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error when creating folders with spaces on GMail's IMAP server #58
Comments
This trick might be ok in usual python code. However, this requires to check how it's translated by imaplib2 and if this is IMAP-compliant. |
thekix
added a commit
to thekix/offlineimap3
that referenced
this issue
Aug 7, 2021
This patch adds support to create and delete folders with the space character. When the folder includes spaces, all the folder name must be quoted. Close: OfflineIMAP#58 Signed-off-by: Rodolfo García Peñas (kix) <kix@kix.es>
5 tasks
Hi @piyueh ! please, could you try now? Thanks a lot, |
@thekix Yes, it works for me now! Thanks! |
5 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
General informations
offlineimap -V
):offlineimap -V
: offlineimap v7.3.0, imaplib2 v3.06, Python v3.9.2, OpenSSL 1.1.1j 16 Feb 2021-o -a test -c ${HOME}/config.test
Configuration file offlineimaprc
Logs, error
Steps to reproduce the error
Step 1: create a test maildir
Step 2: run offlineimap
Description
When
offlineimap
tried to create a folder on GMail's IMAP server, and when that folder had spaces in its folder name, the creation failed.Temporary solution
I have a workaround on my machine: wrapping folder names with double-quotes. However, I believe this workaround is not robust. If a folder name already has double-quotes in its name, I don't know if this workaround is going to work (though I doubt how many people have quotation marks in their folders' names). Here's my workaround:
Replace line 839 in
repository/IMAP.py
:offlineimap3/offlineimap/repository/IMAP.py
Line 839 in 1e7ef9e
with
The text was updated successfully, but these errors were encountered: