Chris Petersen writes:
I guess so. so I'd write one master filter that would then launch whatever else it wanted? Just seems like it'd be easier to install those other ones on their own - so I wouldn't have to customize each and everyPerl is sufficiently flexible enough to implement that on its own, without the need for me to reinvent the wheel.
Hint: a simple wrapper script that reads /etc/mail/filters, and loads all perl modules it finds there, which are then consecutively invoked for each message.
I don't need to do this. This is simple enough to handle entirely within Perl.
filter to work with my master routine (ie. some sort of standardization would be nice).Not sure what you're referring to.
Anyway, the documentation here is lacking. From what I can tell, the directory structure has changed since the docs were written. Am I wrong here, or is there somewhere else I can go for info on setting something up?
-------------------------------------------------------
This sf.net email is sponsored by: See the NEW Palm Tungsten T handheld. Power & Color in a compact size!
http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en
_______________________________________________
courier-users mailing list
[EMAIL PROTECTED]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
