I agree with Davide...
On the mailproc, the way you had it in the previous xmail-wai was =
nice...
basically allow the system admin (not the PO mgr) to define what =
mailproc
actions may be taken (document out what they should look like, or build =
a
tool to help configure the mailproc action) and allow the post office =
admins
and users to select actions... =20
Some ideas:
- vacation/autoresponder with editable text
- objectionable word filter (tie in with xscanner with a short list
(up to 100 words or so editable by the user)
- user based blacklist (editable of course, again, you could tie
into an existing piece of software, or we could author one..)
In any case, all that we would be doing would be to take the template
defined by the system admin and place it in the users mailproc when it =
is
selected.
David Byte
Owner, Byte Computer Services
[EMAIL PROTECTED]
ICQ# 50227527
918-230-2771
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] =
On
Behalf Of Davide Libenzi
Sent: Sunday, June 22, 2003 9:48 AM
To: XMail mailing list
Subject: [xmail] Re: Filter/mailproc ideas (was RE: Re: XMail-WAI 3.0
(.NET))
On Sun, 22 Jun 2003, Michal Altair Valasek wrote:
> 1. Manage the user mailproc.tab some way. This has limited features =
(ie. =3D
> I
> can't modify or discard the message) and is complicated. Because =3D
> allowing
> users to manage their mailproc.tab completely would be security hole
> (allowing to run arbitrary programs), I must wrote something, that =
would
> limit them - list of allowed commands, their management etc. I would =
=3D
> have to
> manage it somewhere outside the xmail and synchronize with xmail, =
which =3D
> can
> lead to problems (see old version WAI's documentation, where this is
> described).
You don't want the user to directly enter commands like netcatting
/etc/passwd in mailproc.tab. You likely want to have a "list" of =
services
available through mailproc.tab where each service name expand to an
external command+parameters that *you* setup through a name->command
mapping.
> 2. Completely bypass the XMail mailproc etc. architecture and write my =
=3D
> own.
> Write filter, which would run for every incoming message, would manage =
=3D
> its
> own configuration (probably in form of XML file) and do everything on =
=3D
> its
> own. It would be easier to implement to WAI, but it will cause every =
=3D
> message
> to be processed trough this filter.
You do *not* need to process each message with the filter since
filters.in.tab is there for a reason.
- Davide
-
To unsubscribe from this list: send the line "unsubscribe xmail" in
the body of a message to [EMAIL PROTECTED]
For general help: send the line "help" in the body of a message to
[EMAIL PROTECTED]
---
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.491 / Virus Database: 290 - Release Date: 6/18/2003
=20
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.491 / Virus Database: 290 - Release Date: 6/18/2003
=20
-
To unsubscribe from this list: send the line "unsubscribe xmail" in
the body of a message to [EMAIL PROTECTED]
For general help: send the line "help" in the body of a message to
[EMAIL PROTECTED]
