I'd like to get the dovecot-antispam plugin bumped to support the currently available releases of dovecot 2.* Here's Mercurial repo http://hg.dovecot.org/dovecot-antispam-plugin/ supporting 2.x Reproducible: Always
And here's the 1.4-RC releases from upstream: http://johannes.sipsolutions.net/download/dovecot-antispam/ Thanks!
Couldn't get the 1.4 RCs to compile ("antispam-storage.c:3:26: fatal error: antispam-storage-2.0.c: No such file or directory"). However, it seems it has been forked and is now hosted at dovecot.org: http://wiki2.dovecot.org/Plugins/Antispam Manpage from HG repo says: "This is the fork of the antispam dovecot plugin as the original one is aimed for dovecot versions before 2.0 and the respectful authors weren't going to update it." No releases yet, but I managed to compile revision 46:43880985e3dd from the HG repo. Haven't tested yet, though.
@net-mail: i've dropped this package into your herd. if you don't want it, reassign to m-n. thanks
Assigned to maintainer-needed
Created attachment 276877 [details] dovecot-antispam-9999 live ebuild Live (mercurial) ebuild for dovecot-antispam for dovecot > 2.0
Created attachment 276879 [details] dovecot-antispam-9999 metadata Drop USE flags from metadata; dovecot-antispam-9999 has no build time deps other than dovecot-2. It'll build *all* backends.
I've been running this plugin with the dspam backend of r46 for a week now. It's working fine, so here's a live ebuild.
I've tested this with the mailtrain backend and it is working fine for me.
Could we please have this one merged on the portage tree ?
Maybe it is not needed to create an extra ebuild but use a USE-Flag like 'antispam' in the ebuild for dovecot-2.x
You'll then another use flag then since antispam can use multiple backends. Unless it's build with all backends available ?
Since you choose the backend via configuration just using 'antispam' as USE flag would be sufficient in my eyes.
You're right. Well, anything as long as we can have this one added to portage :)
(In reply to comment #10) > Maybe it is not needed to create an extra ebuild but use a USE-Flag like > 'antispam' in the ebuild for dovecot-2.x No. I don't think that's a good idea. A separate ebuild is a necessity. The plugin is distributed separately, has no official (and no stable) releases, and users may very well wish to upgrade it independently from dovecot. I see no reason to *not* to have it as an ebuild (as it has lived in this form, in the tree, for some years!) and every reason to keep dovecot and this plugin separate. Having a USE-flag "antispam" that makes dovecot depend on dovecot-antispam is OK though. But that is a *separate* issue and does not need to be addressed immediately; for it has nothing to do with this ebuild. Someone who whishes such a USE-flag in the dovecot ebuild should open a new bug and offer a patch to said dovecot ebuild. Let's focus on getting this live ebuild in the tree. It's been over three months now since I posted dovecot-antispam-9999.ebuild and I haven't seen any comments indicating anything's wrong with the ebuild /per se/.
Latest snapshot now in CVS.
