Actually, the setting is on the email client. Eudora, for example, has
a setting where the user can specify whether or not to download the
message. There is also a setting to delete mail after x days (x is
user specified).
Of course, with Eudora, there are other problems. For instance, if the
user sets the option "Do not download any email more than xKB", once
the user downloads the first xKB of the email, Eudora (or Popper, I'm
not sure which is at fault here) thinks the mail has been read. What
the user really wanted to do was to defer downloading until they get to
a faster connection. What happens is that Eudora *never* downloads the
message again.
The only fix I have found is to log in to the mail server and use some
command line client ('pine' seems to work best), resend the message to
the user and delete the original message.
Another effect of this problem is that the "not downloaded" messages
cannot be deleted by the user. As far as the GUI is concerned, the
message is moved to the trash, but when the trash is "emptied", the
message is not deleted. It also never shows up in the "Inbox" pane
again... The user is happy. They got rid of a superflous message.
It's us admins that get unhappy because the user's spool keeps
growing.
Oh well, my own $0.02 worth.
Gregory Hicks
---------------------------------------------------------------------
A Cadence Postmaster | Principal Systems Engineer
Cadence Design Systems | Direct: 408.576.3609
555 River Oaks Pkwy M/S 6B1 | Fax: 408.894.3479
San Jose, CA 95134 | Internet: [EMAIL PROTECTED]
> Date: Thu, 28 Jun 2001 09:13:45 -0500
> From: Tim Olson <[EMAIL PROTECTED]>
>
> Boy do I ever 2nd this motion. ;)
> Maybe we should add it to Qpoppers wish list?
> I suppose someone's going to tell us next that it's a procmail issue.
>
> Tim Olson
>
> Daniel Senie wrote:
> >
> > I'd like to find some tools to go through mailboxes (mbox format, in
> > /var/spool/mail) and delete anything that's been read, and which is
more
> > than 30 days old. I've got some users who just won't set the "delete
from
> > server" switch, and it's time to take action. I really don't want to
do
> > quotas enforcement at this point, though.
> >
> > Anyone know of tools to do this? I'd love it if Qpopper had an
option for
> > this and would just perform the trim while it was doing its
processing, but
> > the only switch I find there is auto-delete.
> >
> > An alternative would be to add auto-delete on a per-user basis,
targetting
> > the abusive users only.
> >
> > Any thoughts or pointers to tools would be greatly appreciated.
> >
> > Dan
> > -----------------------------------------------------------------
> > Daniel Senie [EMAIL PROTECTED]
> > Amaranth Networks Inc. http://www.amaranth.com