Recent changes to this wiki:
Changed pages:
specification/issues/Rethink mandatory inbox tag
Changed by: dave
Commit type: git
Date: 13:15:25 08/27/11
Thoughts on "inbox" tag.
Changed pages:
specification/issues/Should LISTMSG output contain tags?/comment 1 e6c4c5649b3ccfc66eecba399c1775b7
Changed by: dave
Commit type: web
Date: 11:56:04 08/27/11
removed
Changed pages:
specification/issues/Should LISTMSG output contain tags?
Changed by: dave
Commit type: git
Date: 11:41:08 08/27/11
Include comment in main issue.
I don't like the way comments work with my issue workflow. Need to go
back to including comments in the issue itself. Don't know if I need to
go back to discussion pages, or consult with the comment author.
Thought required.
I don't like the way comments work with my issue workflow. Need to go
back to including comments in the issue itself. Don't know if I need to
go back to discussion pages, or consult with the comment author.
Thought required.
Changed pages:
specification/issues/Should LISTMSG output contain tags?/comment 1 e6c4c5649b3ccfc66eecba399c1775b7
Changed by: dave
Commit type: git
Date: 11:38:27 08/27/11
Comments need links to "done" as well.
If comments are used in an "issue tracking" scenario, then they are
still shown when their parent is "done". Something to work on when time
allows.
If comments are used in an "issue tracking" scenario, then they are
still shown when their parent is "done". Something to work on when time
allows.
Changed pages:
specification/issues/Should LISTMSG output contain tags?
Changed by: dave
Commit type: git
Date: 11:36:26 08/27/11
Issue done - no tags in LISTMSG output.
Changed pages:
specification/issues/Should LISTMSG output contain tags?/comment 1 e6c4c5649b3ccfc66eecba399c1775b7
Changed by: dave
Commit type: web
Date: 11:33:44 08/27/11
Added a comment: Upon futher ponderance...
Changed pages:
specification/issues/Should LISTMSG output contain tags?
Changed by: dave
Commit type: git
Date: 21:23:35 08/26/11
Correct wrong format, stupid fingers.
Changed pages:
specification/issues/Should LISTMSG output contain tags?
Changed by: dave
Commit type: git
Date: 21:21:46 08/26/11
Pro/con list: Drop tags from LISTMSGS output?
Changed pages:
specification/issues/Is setattr command needed?
Changed by: dave
Commit type: git
Date: 21:05:10 08/26/11
ID should not be a tag, size should.
Changed pages:
specification/issues/Add tag-name to formal syntax
Changed by: dave
Commit type: web
Date: 21:04:39 08/26/11
Add note about tag-name.
Replace MVFOLDER with RENTAG.
Add detail to RMTAG ex, lowercase "TAG".
Remove RMFOLDER.
Remove MKFOLDER.
Don't use tag-id, just tag.
Use "mail store", add note re: RMTAG actions.
Replace RMDIR with RMTAG.
Remove MKDIR.
Missed one instance of LISTDIRS.
Convert LISTDIRS to LISTTAGS.
Not a type: A name.
Better show the server name.
Include required formats in possible responses.
Remove LOGIN example, AUTH-type not used.
Remove redundant descriptions, clarify AUTH use.
Consolidate cmd response-lines, explain up front.
Refer to IMF not specific RFC.
Changed pages:
specification/issues/Revise Data Format and Line Endings
Changed by: dave
Commit type: git
Date: 20:00:40 05/29/11
Comment on what needs to be revised.
Changed pages:
specification/issues/Is LF-only required?
Changed by: dave
Commit type: web
Date: 19:45:18 05/29/11
Add link to data format issue
Changed pages:
specification/issues/Revise Data Format and Line Endings
Changed by: dave
Commit type: web
Date: 19:44:13 05/29/11
Revision of data format/line endings issue add
Changed pages:
specification/issues/Is LF-only required?
Changed by: dave
Commit type: web
Date: 19:41:15 05/29/11
Document thoughts about LF vs. CRLF
Standardize positive response use in states.
Changed pages:
specification/issues/Do we need a secured state?
Changed by: dave
Commit type: web
Date: 00:36:21 05/29/11
Secured state necessary?
Adjust opening state descriptions.
- Opening state waits for AUTH or STARTTLS.
- Rephrase limit failed client AUTH attempts section.
- MAY require STARTTLS to AUTH.
- Opening state waits for AUTH or STARTTLS.
- Rephrase limit failed client AUTH attempts section.
- MAY require STARTTLS to AUTH.
Changed pages:
specification/issues/Move description of server SEND refusal
Changed by: dave
Commit type: web
Date: 18:32:12 05/28/11
Raise issue re: description of server refusal of SEND command
Happy to glad changes in MESSAGE-SIZE description.
Remove remaining authentication traces.
Tags should be separated by commas.
Remove extraneous capability tokens.
As pointed out by the IETF reviewers a "simple" protocol should not have
this many authentication methods. Remove all except PLAIN and
ANONYMOUS. Given STARTTLS will be included, this gives a reasonable
option for implementation authors to secure the authentication process.
Should other authentication options be needed in the future, adding them
will be possible using the experimental capability token prefix ("X-").
As pointed out by the IETF reviewers a "simple" protocol should not have
this many authentication methods. Remove all except PLAIN and
ANONYMOUS. Given STARTTLS will be included, this gives a reasonable
option for implementation authors to secure the authentication process.
Should other authentication options be needed in the future, adding them
will be possible using the experimental capability token prefix ("X-").
Split a paragraph, make more succinct.
Minor clarification, grammar fix.
Revert SPAM.
This reverts the following commits.
d47ec15d91865b0ecce91cc7d24d50526bac449b
c56ec4191ba3608976042974f9eeb6e2f80cd9c6
84d3b5759642e7d29f5d0096bb3e7bb1086b083a
4fa721c8c7677f79afeec8e23c0b7e80480eae74
41d94a0edd53cc038ac37c6ee9ff3dd7b549c0a4
d92c2d2980f1334e262e4884216f9cad5e8459e1
c11ca9de34e03eb8e6958261918315e5c7b26d02
5100264dafd867930e09211469d295d400efa67a
2278e32544b742a787b925eb9efc91f8cb411af6
60b9ba7bf03517602c534187ac4deba7f2a4e80c
5fcb767dd7a3a52562ee677d1739db59c760cb9f
06438c83975bcf7e384439b6751bf3adfc25688b
17ea2f2a33144610449a2df6d421a04da25fd0b3
193ca9d66d22f9271cd95c123847c33128caa3db
2e761917b3a806ca235831424448e71dd8cc08f0
38015f71b80acf59c9f21b3d696f69509156dd62
3b7118ac1f4298b02b2720a17f51ce56ea6d13d9
5739a11d4b13f21b0bd1a433f96110a308aaa9fb
5eba3d3e7e66bda55e6de670f6ed11bc394d1a2d
ada590a99258210b0ff9355ad1bc27acef93d815
b910fac094440019bbb15d08cd4ef13619b1ddcc
d6954a645d5d837e772f276f297e3a61dd577f39
ffda4dfe1494c0087f4bdcc68dbb8c3563cacbd0
This reverts the following commits.
d47ec15d91865b0ecce91cc7d24d50526bac449b
c56ec4191ba3608976042974f9eeb6e2f80cd9c6
84d3b5759642e7d29f5d0096bb3e7bb1086b083a
4fa721c8c7677f79afeec8e23c0b7e80480eae74
41d94a0edd53cc038ac37c6ee9ff3dd7b549c0a4
d92c2d2980f1334e262e4884216f9cad5e8459e1
c11ca9de34e03eb8e6958261918315e5c7b26d02
5100264dafd867930e09211469d295d400efa67a
2278e32544b742a787b925eb9efc91f8cb411af6
60b9ba7bf03517602c534187ac4deba7f2a4e80c
5fcb767dd7a3a52562ee677d1739db59c760cb9f
06438c83975bcf7e384439b6751bf3adfc25688b
17ea2f2a33144610449a2df6d421a04da25fd0b3
193ca9d66d22f9271cd95c123847c33128caa3db
2e761917b3a806ca235831424448e71dd8cc08f0
38015f71b80acf59c9f21b3d696f69509156dd62
3b7118ac1f4298b02b2720a17f51ce56ea6d13d9
5739a11d4b13f21b0bd1a433f96110a308aaa9fb
5eba3d3e7e66bda55e6de670f6ed11bc394d1a2d
ada590a99258210b0ff9355ad1bc27acef93d815
b910fac094440019bbb15d08cd4ef13619b1ddcc
d6954a645d5d837e772f276f297e3a61dd577f39
ffda4dfe1494c0087f4bdcc68dbb8c3563cacbd0
Changed pages:
specification/issues/Is setattr command needed?
Changed by: dave
Commit type: web
Date: 19:50:21 02/07/11
Address the topic. 
Changed pages:
specification/issues/Is setattr command needed?
Changed by: dave
Commit type: web
Date: 19:49:33 02/07/11
Do we need attributes or just tags?
Grammar in recipient, revise sender.
Revise Envelope Recipient Attribute.
- Simplify requirements.
- Eliminate non-standard header dependency.
- Simplify requirements.
- Eliminate non-standard header dependency.
Revise Message Size Attribute.
Revise timestamp attribute.
- Refer to the proper BikINI (protocol vs. server).
- Rephrase to increase clarity.
- Expand first use of acronyms.
- Refer to the proper BikINI (protocol vs. server).
- Rephrase to increase clarity.
- Expand first use of acronyms.
Make example clear.
Change "flag" to "tag".
Changed pages:
specification/issues/3.4.1. make Message Identifier unique in mailstore
Changed by: dave
Commit type: web
Date: 19:54:42 01/05/11
Fixed in ea7df3b3dc29eb7afbf4b6987eb245cb01eab2d0.
Implement tags, remove flags.
This doesn't fully implement tags, because work is still required on the
commands to do the implementation. However, this is a start.
This doesn't fully implement tags, because work is still required on the
commands to do the implementation. However, this is a start.
Make Message Identifier unique w/in mail store.
Fix issue "make Message Identifier unique in mailstore".
Fix issue "make Message Identifier unique in mailstore".
Mail store architecture just got a lot simpler!
Remove extra words, use angle-brackets w/ ABNF.
Remove duplicate word.
Add ref. to additional information sections.
Tighten response code descriptions.
- Remove reference to additional information section in individual
response code descriptions.
- General phrasing corrections (be specific).
- Remove reference to additional information section in individual
response code descriptions.
- General phrasing corrections (be specific).
Standardize phrasing.
Response codes are not response lines.
Correct/rearrange/clarify.
- Move "server's don't speak out of turn" message up front.
- Clarify multiple sections, reduce possibility of multiple
interpretations.
- Correct some formatting errors.
- Move "server's don't speak out of turn" message up front.
- Clarify multiple sections, reduce possibility of multiple
interpretations.
- Correct some formatting errors.
Clarify/bulletize client -> server section.
- Update list of cases in which a complete command is not a single line.
- Pull list out of paragraph, and place in bullet form.
- Update server responses with three, not two, cases.
- Update list of cases in which a complete command is not a single line.
- Pull list out of paragraph, and place in bullet form.
- Update server responses with three, not two, cases.
Clean-up and add definitions.
- Add IMF and define.
- Change definition of message to message content (includes headers,
MIME-parts).
- Add reference to requested port number.
- Remove reference to initial server greeting (doesn't exist).
- Clarify Commands and Responses section.
- Add IMF and define.
- Change definition of message to message content (includes headers,
MIME-parts).
- Add reference to requested port number.
- Remove reference to initial server greeting (doesn't exist).
- Clarify Commands and Responses section.
Adjust terminology.
- Remove directory/folder entries.
- Add RFC822 as valid message format.
- Remove directory/folder entries.
- Add RFC822 as valid message format.
Simplify/rephrase design considerations.
Rephrase abstract.
Remove extraneous words.
Rephrase items in objective/design considerations.
Revert spam.
This reverts commits b4040f9cbada377ea1b9d4faad4d2cb067bf7467,
ab2b734eb90984f4092b73a97a5aa79064e81a41, and
ae712abc0b709b2df3c6f04ff5a6c722c56f0439.
This reverts commits b4040f9cbada377ea1b9d4faad4d2cb067bf7467,
ab2b734eb90984f4092b73a97a5aa79064e81a41, and
ae712abc0b709b2df3c6f04ff5a6c722c56f0439.
Some minor changes
Minor formating changes and removed spam link
deleted spam
Changed pages:
specification/issues/Add tagging for messages
Changed by: dave
Commit type: git
Date: 22:11:49 04/13/10
More issues regarding tags/flags.
Changed pages:
specification/issues/Evaluate necessity of MVMSG and Trashed flag
Changed by: dave
Commit type: git
Date: 22:09:37 04/13/10
Will the trashed flag be needed?
Grammar.
Changed pages:
specification/issues/Add tagging for messages
Changed by: dave
Commit type: git
Date: 09:56:17 03/29/10
Add comments on removal of folders.