Wow.. ok antispam_backend = mailtrain should be replaced with antispam_backend = pipe
I do not get what your problem is though. Maybe you feel cool that you can "contain" information from others - which should not be the "debian way" in any way. To answer your question, there are three (I'm sure there are more) versions of "dovecot-antispam": http://hg.dovecot.org/dovecot-antispam-plugin/ (the official version) http://johannes.sipsolutions.net/Projects/dovecot-antispam (the original version) https://anonscm.debian.org/cgit/users/ron/dovecot-antispam.git/ (debian / your version) You version is not referenced at dovecot.org and I just found it by chance via the bugtracker. You had twice the chance to give a simple "ehm wrong backend - check the docs" but each time you failed and instead bloated your ego. In any case, good software (as the official version does) will actually give a hint "mailtrain not supported" instead of yours just crashing the whole daemon. In any case. Regards, Gunter > Ron <mailto:r...@debian.org> > 05 April 2015 at 2:41 PM > > I don't believe this is true :) If you ever had this config working > at all, it wasn't with any package that ever shipped in any Debian > release. The changes since wheezy are minimal, and it would choke on > it in exactly the same way the current bpo version did. > > Next time you install a random fork from somewhere else, leave a note > for yourself that you expect things to break when you update the system > again ... because that's what happened here if this ever worked. > > Ron > > Ron <mailto:r...@debian.org> > 05 April 2015 at 1:13 PM > > Well, you might want to take a few deep breaths, and start again by > trying to include some actual information about what you did, or what > is special about your system that this started happening on it ... > > Since "it just does not work anymore" is plainly untrue, it's been > working without trouble for many people for many months now. And > you haven't at all shown how this "causes serious data loss". > > I understand you are upset, but there's not much anyone can do about > that if you don't tell us anything at all about what was previously > working for you, what you changed that made that stop, or why you > think it's this package which caused that ... > > > My first bet though is that you've copypasta'd a totally bogus > configuration, and in fact I'm confident enough of that to just > close this bug report right now, as it's not a bug in this package > at all. > > You might want to read the documentation about valid options for > antispam_backend. > > Ron > > > Gunter Grodotzki <mailto:guen...@weheartwebsites.de> > 05 April 2015 at 11:37 AM > Package: dovecot-antispam > Version: 2.0+20130912-1~bpo70+1 > Severity: critical > Justification: causes serious data loss > > Dear Maintainer, > > dovecot-antispam just does not work anymore with dovecot 2.2 > The error line reads: > Apr 5 10:10:54 hXXX dovecot: imap(XXX): Fatal: master: service(imap): > child 9207 returned error 3 > > When I deactivate the plugin it works again. > Using the following config: > plugin { > antispam_backend = mailtrain > antispam_spam = Spam > antispam_trash = Trash > antispam_mail_spam = learn_spam > antispam_mail_notspam = learn_ham > antispam_mail_sendmail = /usr/bin/rspamc > antispam_mail_sendmail_args = -h;127.0.0.1:11334 > } > > > -- System Information: > Debian Release: 7.8 > APT prefers stable-updates > APT policy: (500, 'stable-updates'), (500, 'stable') > Architecture: i386 (i686) > > Kernel: Linux 3.2.41-042stab092.3 (SMP w/1 CPU core) > Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) (ignored: > LC_ALL set to en_US.utf8) > Shell: /bin/sh linked to /bin/dash > > Versions of packages dovecot-antispam depends on: > ii dovecot-core [dovecot-abi-2.2.abiv13] 1:2.2.13-11~bpo70+1 > ii dovecot-imapd 1:2.2.13-11~bpo70+1 > ii libc6 2.13-38+deb7u8 > > dovecot-antispam recommends no packages. > > Versions of packages dovecot-antispam suggests: > pn crm114 | dspam <none> > > -- no debconf information
