2 messages in net.sourceforge.lists.courier-usersRe: [courier-users] Got one question
FromSent OnAttachments
xxyDec 4, 2001 10:50 pm 
Tim HoskingDec 5, 2001 6:54 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: [courier-users] Got one questionActions...
From:Tim Hosking (ti@trhosking.com)
Date:Dec 5, 2001 6:54:51 am
List:net.sourceforge.lists.courier-users

on 5/12/01 1:05 am, xxy at xx@adoir.com wrote:

Hey!

I noticed that courier modified the filename of mail archives from

992187574.11359_1.linux,S=4036:2

to 992187574.11359_1.linux,S=4036:2,S or 992187574.11359_1.linux,S=4036:2, RS

or 992187574.11359_1.linux,S=4036:2,ST

I really got confused at that point! : What does it mean?

From my own investigation, courier will do the modification after my enterring the IMAP or POP3 accessing my emails. Is there any specific reason for doing this?

Anybody please give me some hints,

Thank You!

xxy 12/05/2001r?

Read the maildir spec at:

<http://cr.yp.to/proto/maildir.html>

It says:

When you move a file from new to cur, you have to change its name from uniq to uniq:info. Make sure to preserve the uniq string, so that separate messages can't bump into each other.

info is morally equivalent to the Status field used by mbox readers. It'd be useful to have MUAs agree on the meaning of info, so I'm keeping a list of info semantics. Here it is.

info starting with "1,": Experimental semantics.

info starting with "2,": Each character after the comma is an independent flag.

* Flag "R" (replied): the user has replied to this message. * Flag "S" (seen): the user has viewed this message, though perhaps he didn't read all the way through it. * Flag "T" (trashed): the user has moved this message to the trash; the trash will be emptied by a later user action. * Flag "D" (draft): the user considers this message a draft; toggled at user discretion. * Flag "F" (flagged): user-defined flag; toggled at user discretion. New flags may be defined later. Flags must be stored in ASCII order: e.g., "2,FRS".