The greylisting plugin

As you may or may not know, I'm the new maintainer of the sa-exim Debian 
package. As you also may or may not know, sa-exim (the package) is designed 
such that SpamAssassin doesn't have to be installed on the same machine as 
SA-Exim and of course Exim. Except if you want to use the greylisting module 
for SpamAssassin, that is, unless you manually copy Greylisting.pm to the 
right place, which isn't too hard to do but it's not pretty and it's not 
Right.

The greylisting code exists as a SA plugin (and a patch for ancient SA 
versions) for two reasons, AFAIU: It's easier to code in Perl and it also 
makes the module usable with other software. But it also has drawbacks; in 
particular the X-SA-Exim-* headers that have to be added by the local_scan 
code before sending the mail to SA, and that can't be removed if report_safe 
is used.

To fix the packaging I'll have to split the package into two, plus a 
transitional metapackage by the original name. I would rather write the 
greylisting code in C and drop the SA plugin.

So what I want to ask now is whether anyone is using the greylisting plugin 
without the main SA-Exim local_scan() plugin. Hm, well, I guess you can 
continue doing so in that case. Any other comments?

-- 
Magnus Holmgren        [email protected]
                       (No Cc of list mail needed, thanks)

_______________________________________________
SA-Exim mailing list
[email protected]
http://lists.merlins.org/lists/listinfo/sa-exim

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQBFpDcRk7mRNn1h4+YRAqlMAJ9C44jy120cxmDfpOO+sSCS2DV23ACfWgnW
WfZu6eRbvsLSbxnX4gz39ng=
=kppF
-----END PGP SIGNATURE-----