mailing list archives

meli community discussions

⚠️ if something does not work as intended when interracting with the mailing lists,
reach out Github mirror Gitea repo @epilys:matrix.org

[Imap-protocol] RFC 6851 imap move

E-mail headers
From: Thomas Dreßler <thomas.dressler@1und1.de>
To: imap-protocol@u.washington.edu
Date: Fri, 08 Jun 2018 12:34:50 -0000
Message-ID: 510A5DB6.2090105@1und1.de permalink / raw / eml / mbox 
hi,

i have seen rfc6851 and i have a question.

example from rfc:
C: a UID MOVE 42:69 foo
S: * OK [COPYUID 432432 42:69 1202:1229]
S: * EXPUNGE
S: (more expanges)
S: a OK done

is the COPYUID response legal?

rfc3501:
resp-text = ["[" resp-text-code "]" SP] text

i see no "SP text" in that example.

ThomasD

-- 
Thomas Dressler
Software-Entwickler

1&1 Internet AG - Mail System Development
Brauerstrasse 48 DE-76135 Karlsruhe
Telefon: +49 721 91374-6790
thomas.dressler@1und1.de

Amtsgericht Montabaur / HRB 6484
Vorstaende: Henning Ahlert, Ralph Dommermuth, Matthias Ehrlich, Thomas Gottschlich, Robert Hoffmann, Markus Huhn, Hans-Henning Kettler, Dr. Oliver Mauss, Jan Oetjen
Aufsichtsratsvorsitzender: Michael Scheeren
Reply
E-mail headers
From: dave@cridland.net
To: imap-protocol@localhost
Date: Fri, 08 Jun 2018 12:34:50 -0000
Message-ID: CAKHUCzzXvUXCqfcqDzTDH+ojXoWD46u41Oyh65fST1P6jLo5Ew@mail.gmail.com permalink / raw / eml / mbox 
On 31 Jan 2013 12:08, "Thomas Dre?ler" <thomas.dressler@1und1.de> wrote:
> is the COPYUID response legal?
>
> rfc3501:
> resp-text = ["[" resp-text-code "]" SP] text
>
> i see no "SP text" in that example.

There are two SP characters before the EOL not visible.

Dave.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman13.u.washington.edu/pipermail/imap-protocol/attachments/20130131/77026a58/attachment.html>
Reply