Skip to content
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

Imap bug with deleting of inbox and renaming folder to existing name #399

Closed
filtsin opened this issue Jun 27, 2021 · 1 comment · Fixed by #400
Closed

Imap bug with deleting of inbox and renaming folder to existing name #399

filtsin opened this issue Jun 27, 2021 · 1 comment · Fixed by #400
Labels
Milestone

Comments

@filtsin
Copy link
Contributor

filtsin commented Jun 27, 2021

  1. I have a question about the command "DELETE" with the argument "INBOX". As described in RFC3501 "It is an error to attempt to delete INBOX". However, greenmail allows this operation and removes INBOX permanently.
c: a02 LIST "" *
s: * LIST () "." "INBOX"
s: a02 OK LIST completed.
c: a03 DELETE inbox
s: a03 OK DELETE completed.
c: a04 LIST "" *
s: a04 OK LIST completed.

I think it is strange that we can delete INBOX.

  1. As described in RFC3501 "It is an error to attempt to rename from a mailbox name that does not exist or to a mailbox name that already exists."

Example with "INBOX" but it works in the same way with other names.

c: a02 LIST "" *
s: * LIST () "." "INBOX"
s: a02 OK LIST completed.
c: a03 CREATE zoo
s: a03 OK CREATE completed.
c: a04 RENAME zoo inbox
s: a04 OK RENAME completed.
c: a05 LIST "" *
s: * LIST () "." "INBOX"
s: * LIST () "." "INBOX"
s: a05 OK LIST completed.

It is definitely the bug that we have multiple folders with the same name.

I think I can fix it by myself if you want.

@apinske
Copy link
Contributor

apinske commented Jun 27, 2021

@filtsin Thanks for analysing this. You are very welcome to provide a PR for a fix. We'd appreciate it!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants