Skip to content

RFC page: RFC 2180 COPY rule and RFC 5530 response codes - #240

Merged
0kaba0hub merged 2 commits into
mainfrom
docs/rfc-expunge-issued
Oct 30, 2026
Merged

0kaba0hub merged 2 commits into
mainfrom
docs/rfc-expunge-issued

Conversation

@0kaba0hub

Copy link
Copy Markdown
Contributor

Two IMAP rows for the 2.4.5 changes:

  • RFC 2180, partial: a COPY that meets a message another session expunged copies nothing and answers NO [EXPUNGEISSUED] (§4.4.1).
  • RFC 5530, partial: the response codes the server sends, listed; the others are not sent.

@0kaba0

0kaba0 commented Oct 30, 2026

Copy link
Copy Markdown
Collaborator

#240 (6331ede): two corrections in the RFC 5530 row before merge.

  • ALREADYEXISTS is listed as sent, but nothing in internal/imap or the imapserver library emits it; the only ALREADYEXISTS in the tree is the JMAP SetError. Either point me at the IMAP site or drop it from the list.
  • PARSE is sent (internal/imap/server.go:3411) and is missing from the list.

The RFC 2180 row reads right.

@0kaba0hub

Copy link
Copy Markdown
Contributor Author

ALREADYEXISTS removed: it is only sent by ManageSieve (managesieve/session.go), not by IMAP.

PARSE stays out of this row: it is an RFC 3501 response code (§7.1), not one RFC 5530 defines, and the 3501 row already covers it.

@0kaba0

0kaba0 commented Oct 30, 2026

Copy link
Copy Markdown
Collaborator

#240 (df508ac): APPROVED. Right about PARSE, it is RFC 3501 §7.1 and the 3501 row covers it; the 5530 list now matches what the server sends.

@0kaba0hub
0kaba0hub merged commit 7fcd20c into main Oct 30, 2026
1 check passed
@0kaba0hub
0kaba0hub deleted the docs/rfc-expunge-issued branch October 30, 2026 22:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants