Re: Preserving flags, and their global nature
--On Tuesday, November 19, 2002 5:09 PM + Ian McDonald <[EMAIL PROTECTED]> wrote: Over the weekend, it struck me that a patch to make 'seen' global could be as simple as commenting out the calls to the code that treats '\Seen' as a special-case global variable, and adding 'Seen' to the list of global flags. Somewhere. Unfortunately, when I had a look at the source code, I could find libraries dealing with Seen, but no list of global flags or obvious hook for the 'seen' per-user code. Is it that simple? Where should I be looking? Well, you can change the libraries dealing with seen to not pay attention to the username. If you want it to be stored with the other global flags it is somewhat more complicated. To do this right, you want an option to store FLAG_SEEN as part of system_flags in the cyrus.index file. (Likewise, you probably want an option to store FLAG_DELETED as per-user state---so really you want to abstract out the idea of \Seen being special.) Larry
Re: Preserving flags, and their global nature
Over the weekend, it struck me that a patch to make 'seen' global could be as simple as commenting out the calls to the code that treats '\Seen' as a special-case global variable, and adding 'Seen' to the list of global flags. Somewhere. Unfortunately, when I had a look at the source code, I could find libraries dealing with Seen, but no list of global flags or obvious hook for the 'seen' per-user code. Is it that simple? Where should I be looking? - Original Message - From: <[EMAIL PROTECTED]> To: "Ian McDonald" <[EMAIL PROTECTED]> Cc: "Lawrence Greenfield" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Sunday, November 17, 2002 12:28 AM Subject: Re: Preserving flags, and their global nature > >How difficult would it be to hack Cyrus to either make Seen global, or make > >Seen globally visible? > > Agree, a global seen attribute would be wonderfully useful. Out marketing > deptartment was terribly disappointed to discover that other flags (answered) > were global but seen was either personal, or not saved at all. They need > someone to read a message, so the ability to see that anyone has at least read > the message would be terribly usefule.
Re: Preserving flags, and their global nature
Unfortunately for me, I think that my client (the Mail::IMAPClient perl module) only supports LOGIN. - Original Message - From: "Rob Siemborski" <[EMAIL PROTECTED]> To: "Ian McDonald" <[EMAIL PROTECTED]> Sent: Friday, November 15, 2002 7:45 PM Subject: Re: Preserving flags, and their global nature > On Fri, 15 Nov 2002, Ian McDonald wrote: > > > So central is this requirement to my helpdesk application, that I'm > > considering storing all the passwords in plain text in order to do just that > > :( :( :(. > > Administrative users can authorize as any user they want without needing > the user's password (sort of like root can su to whatever userid it > wants). > > You just need a SASL mechanism that supports authorization (basically, all > of them except LOGIN and CRAM-MD5). > > -Rob >
Re: Preserving flags, and their global nature
>How difficult would it be to hack Cyrus to either make Seen global, or make >Seen globally visible? Agree, a global seen attribute would be wonderfully useful. Out marketing deptartment was terribly disappointed to discover that other flags (answered) were global but seen was either personal, or not saved at all. They need someone to read a message, so the ability to see that anyone has at least read the message would be terribly usefule.
Re: Preserving flags, and their global nature
--On Friday, November 15, 2002 7:47 PM + Ian McDonald <[EMAIL PROTECTED]> wrote: How difficult would it be to hack Cyrus to either make Seen global, or make Seen globally visible? Well, it's not clear in IMAP how to show the status of other user's seen flags. While it wouldn't be impossible to make the seen flag global (probably could do it with writing a new seen_ backend) it would probably be a nuisance. Maybe a day of work for me? Larry
Re: Preserving flags, and their global nature
How difficult would it be to hack Cyrus to either make Seen global, or make Seen globally visible? (Given the difficultly of compiling Cyrus in the first place, not my favourite solution ...) - Original Message - From: "Lawrence Greenfield" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]>; "Ian McDonald" <[EMAIL PROTECTED]> Sent: Friday, November 15, 2002 7:08 PM Subject: Re: Preserving flags, and their global nature >From: "Ian McDonald" <[EMAIL PROTECTED]> >Date: Fri, 15 Nov 2002 19:09:14 - > >Is there any way for an admin user to read, or write, another users Seen >flags? > > No. > >Do any other flags behave like this? > > No. \Delete probably should be a per-user flag but it isn't. > > Larry
Re: Preserving flags, and their global nature
On Fri, 15 Nov 2002, Lawrence Greenfield wrote: >From: "Ian McDonald" <[EMAIL PROTECTED]> >Date: Fri, 15 Nov 2002 19:09:14 - > >Is there any way for an admin user to read, or write, another users Seen >flags? > > No. Well, technically you could authorize as the alternate user and issue the commands as that user, but I doubt this is what Ian meant. -Rob -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Rob Siemborski * Andrew Systems Group * Cyert Hall 207 * 412-268-7456 Research Systems Programmer * /usr/contributed Gatekeeper
Re: Preserving flags, and their global nature
From: "Ian McDonald" <[EMAIL PROTECTED]> Date: Fri, 15 Nov 2002 19:09:14 - Is there any way for an admin user to read, or write, another users Seen flags? No. Do any other flags behave like this? No. \Delete probably should be a per-user flag but it isn't. Larry
Re: Preserving flags, and their global nature
Is there any way for an admin user to read, or write, another users Seen flags? Do any other flags behave like this? - Original Message - From: "Lawrence Greenfield" <[EMAIL PROTECTED]> > > You can argue about whether or not it should happen. The design of > Cyrus makes it awfully difficult to change that this does happen and > it's not always clear what the users want. (Maybe I want a message to > appear unseen in a mailbox if someone has moved it there? Maybe not?) > > Cyrus will perserve the \Seen flag in copies for the user doing the > copy. To all other users the \Seen flag will _not_ be set on the > destination message. > > Larry
Re: Preserving flags, and their global nature
From: "Ian McDonald" <[EMAIL PROTECTED]> Date: Fri, 15 Nov 2002 18:07:59 - When I move (copy and delete) messages between shared folders, the (\Answered) and (\Flagged) flags are preserved, but the (\Seen) flag seems to be removed. The user doing the moving is some housekeeping software, and is not the same userid as the user which has examined the email. Is this meant to happen? You can argue about whether or not it should happen. The design of Cyrus makes it awfully difficult to change that this does happen and it's not always clear what the users want. (Maybe I want a message to appear unseen in a mailbox if someone has moved it there? Maybe not?) Cyrus will perserve the \Seen flag in copies for the user doing the copy. To all other users the \Seen flag will _not_ be set on the destination message. Larry
Preserving flags, and their global nature
When I move (copy and delete) messages between shared folders, the (\Answered) and (\Flagged) flags are preserved, but the (\Seen) flag seems to be removed. The user doing the moving is some housekeeping software, and is not the same userid as the user which has examined the email. Both of those users have 's' and 'w' rights on both of the folders concerned. My client is the perl module Mail::IMAPClient. Is this meant to happen?
