When users delete mail, I want it to be moved to Trash.

[Erik Enge]

Rob Siemborski <rjs3 at andrew.cmu.edu> writes:

> It's not a server-side responsibility.  You need to have a client that
> does it.

This makes no sense to me.

Let me use an analogy so you perhaps understand me better.  On my Unix
server(s), I am root and I rule and dictate as I want - as I should.
For example, I believe users are inherently clueless, so I have (I
haven't really, but to illustrate my problem) replaced /bin/rm with a
shell script that moves the file instead of deleting it.  Unless you are
also root on that server, you cannot override that.

This is good.  I can manipulate the system.  I can hook into things
without the user having to know about it.  I can make sure that data
that needs to be available actually is available.

With Cyrus, this does not seem to be the case.  It's my data and it's my
hardware and still I cannot tell the users how I want business to be
conducted on my systems.  I think this is a bug.  Cyrus should let me
hook into it in some way so that I can use it in ways the authors never
expected me to.

I cannot believe this (no-delete) is not the policy for most corporate
users of Cyrus.  For legal and other reasons, keeping mail around is
vital.  Configuring all the clients (Outlook, Outlook Express, Gnus,
Mozilla, KMail and Evolution) to move stuff into Trash whenever it is
deleted (which not all of them do by default - and some even EXPUNGE by
default) turns into a major administration hassle.

I want to hinder the users in deleting the mail from the server.  Is
that such an unreasonable request?

Erik.