-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Jonas Eckerman writes:
>An alternative but also more complex way could be that user extensions need two
>functions. Like this:
>
>sub register_sa_user_function { #allways has this name, there has to be a separate
>file for each user extension
> # returns the rule name and what kind of data we wants to work on. The data
> types could be something like:
> # 'file', a path to the actual mail file.
> # 'body', the body in memory
> #' you can guess the rest.
> return ('MY_USER_FUNCTION_RULE_NAME','file');
>}
>
>sub sa_user_function($) {
> my ($mailfile) = @_;
> # call bogofilter or whatever
> return $was_a_hit;
>}
>
>With a hook like that, the SA devs doesn't have to maintain the interfaces to the
>external apps. They just have to maintain the much smaller code calls user functions
>and (as with all such interfaces) should change as seldom as possible.
Yeah, we are considering the API and object model for this -- with
any luck we should be getting some time to hack something up RSN,
so that admins can drop a .pm file into /etc/mail/spamassassin to
call external code. Plug-ins, basically.
- --j.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
Comment: Exmh CVS
iD8DBQE/9y6dQTcbUG5Y7woRAqiiAKCL+y26FgJMqddJxDhfap2eSY1GtQCgwI/D
QxrcvbOTbO0pcYae2YbT3hk=
=6KM+
-----END PGP SIGNATURE-----
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
_______________________________________________
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
