On Sun, 22 Jun 2003, Michal Altair Valasek wrote: > 1. Manage the user mailproc.tab some way. This has limited features (ie. = > I > can't modify or discard the message) and is complicated. Because = > 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 = > have to > manage it somewhere outside the xmail and synchronize with xmail, which = > 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 = > own. > Write filter, which would run for every incoming message, would manage = > its > own configuration (probably in form of XML file) and do everything on = > its > own. It would be easier to implement to WAI, but it will cause every = > 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]
