wasm-demo/demo/ermis-f/imap-protocol/cur/1600095073.22641.mbox:2,S

32 lines
1.2 KiB
Plaintext

MBOX-Line: From arnt at gulbrandsen.priv.no Fri Mar 21 04:59:57 2014
To: imap-protocol@u.washington.edu
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
Date: Fri Jun 8 12:34:52 2018
Subject: [Imap-protocol] IMAP SUBMIT Extension, take two
In-Reply-To: <1395369035.8071.97071749.6F2A6445@webmail.messagingengine.com>
References: <5f20eeec-c84b-4395-b89b-dfc243d9c465@flaska.net>
<66E46BE7-0C45-4EFD-B18F-5A6959AADAC4@gmail.com>
<db2cac03-876f-4966-bf1f-1a7f8d9f4536@flaska.net>
<219fd97c-e1fd-48e4-b8ae-fcf96537a9bb@gulbrandsen.priv.no>
<1395341331.29069.96929213.1F949AAB@webmail.messagingengine.com>
<39b431a9-93a6-42b1-9cbe-5788d5958f43@flaska.net>
<1395369035.8071.97071749.6F2A6445@webmail.messagingengine.com>
Message-ID: <abe79532-3a9d-4083-be13-7a4208ce3e37@gulbrandsen.priv.no>
On Friday, March 21, 2014 3:30:35 AM CEST, Bron Gondwana wrote:
> Let's not confuse things with more flags.
Or with making the client serve the server.
This is about making the server submit mail. So why should the client need
to do any locking? It's not particularly difficult to say "server should
lock the message appropriately to prevent duplicate or repeated submission"
and define an error code. Like this:
C: a submit foo bar
S: a NO [ALREADYSUBMITTED] blah
Arnt