Does Scalix allow an end user or admin to "retract" a message once it's been sent? Some systems, including Groupwise, allow you to do this.
Thanks,
Ben Chapman
Retracting Messages?
Moderators: ScalixSupport, admin
-
bchapman
- Posts: 11
- Joined: Tue Nov 01, 2005 1:24 pm
- Contact:
Retracting Messages?
Ben Chapman
Asst Dean for Information Technology
Emory University School of Law
Asst Dean for Information Technology
Emory University School of Law
-
ScalixSupport
- Scalix
- Posts: 5503
- Joined: Thu Mar 25, 2004 8:15 pm
-
kanderson
Retraction...
This isn't totally accurate.
You can also add me to the list of people who'd like to see a retract feature added, but in the mean time, an admin can retract a message from the command line using OMTIDYU and/or OMTIDYALLU.
type man omtidyallu to see the instructions, but basically, this would allow an admin to delete a message from the message store based on criteria (age, subject, size, etc)
It certainly isn't as simple as Groupwise's retract, but it would work (on a server by server basis).
Kev.
You can also add me to the list of people who'd like to see a retract feature added, but in the mean time, an admin can retract a message from the command line using OMTIDYU and/or OMTIDYALLU.
type man omtidyallu to see the instructions, but basically, this would allow an admin to delete a message from the message store based on criteria (age, subject, size, etc)
It certainly isn't as simple as Groupwise's retract, but it would work (on a server by server basis).
Kev.
-
ScalixSupport
- Scalix
- Posts: 5503
- Joined: Thu Mar 25, 2004 8:15 pm
-
jch
- Scalix
- Posts: 202
- Joined: Thu Mar 25, 2004 10:25 am
Message retration has some security issues that revolve around sending a message, waiting for it to be read by some potential recipients and then restracting it when the desired level of damage has been achieved -- and leaving little trace of the evidence in the process. Tech savvy users can do the same thing without retraction, but the point here is that message retraction opens up the possibility of this kind of vindictiveness to a wider audience.
That, of course, assumes that message retraction can be made to work at all. There are several cases where implementations either fail completely or behave badly (depending on the implementation). For example:
A message appears in the summary list while you're looking at it and then disappears before you get the chance to click on it (sender has quick reactions); your interest is piqued and you then get to waste time finding out what the message was.
Retractions don't work outside of the organisation: there's no way to retract a message sent externally, although I know some Exchange users believe that there's magic involved that allows this to happen.
Messages in Scalix (and others, these days) are delivered very quickly, often with sub-second delays. This gives a recipient chance to reply to the message before the sender retracts it. You're then in the rather odd position of having one or more replies to a message that no longer exists, much to the confusion of the users that weren't in at the time.
It's quite possible to have an auto-action, server side or client side, that prints messages as the arrive. Retract that (to paraphrase Trinity).
These cases, and others like them, make me very wary of message retraction.
jch[/list]
That, of course, assumes that message retraction can be made to work at all. There are several cases where implementations either fail completely or behave badly (depending on the implementation). For example:
A message appears in the summary list while you're looking at it and then disappears before you get the chance to click on it (sender has quick reactions); your interest is piqued and you then get to waste time finding out what the message was.
Retractions don't work outside of the organisation: there's no way to retract a message sent externally, although I know some Exchange users believe that there's magic involved that allows this to happen.
Messages in Scalix (and others, these days) are delivered very quickly, often with sub-second delays. This gives a recipient chance to reply to the message before the sender retracts it. You're then in the rather odd position of having one or more replies to a message that no longer exists, much to the confusion of the users that weren't in at the time.
It's quite possible to have an auto-action, server side or client side, that prints messages as the arrive. Retract that (to paraphrase Trinity).
These cases, and others like them, make me very wary of message retraction.
jch[/list]
Who is online
Users browsing this forum: No registered users and 30 guests