-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Theo Van Dinter writes: > On Tue, Aug 03, 2004 at 06:14:48PM +0800, Yusuf Goolamabbas wrote: > > As soon as I started spamd via spamd -Lx -p 7830. I get the following > > displayed in the terminal > > > > 6166c359a351a9ad990c05334ea520ec > > From: [EMAIL PROTECTED] > > Message-Id: <[EMAIL PROTECTED]> > > > > Is there a way to prevent this message from invoking plugins ? > > No. spamd wants to get everything precompiled before processing messages, > so it makes a fake message (as above) and sends it through a "check" > to get it all set to go. > > I don't recall off hand if there's an easy way to tell if you're in > "compile_now" mode or not. I don't think there is right now. That would be my preferred fix -- add a boolean member variable to the Mail::SpamAssassin object which plugins can test to see if compile_now() is active. (and document that this is what happens, and that plugins should expect it.) > > Also, when I pass the message to spamc and redirect fd 4 to a file, > > the output doesn't seem to go there unlike the invocation with > > spamassassin. An empty file is created with the following invocation > > Yeah. spamc != spamassassin... spamd is the one actually doing the > processing, so the fd 4 bit happens in spamd. spamc has absolutely no > capability of dealing with that. BTW for checking large numbers of messages with a plugin, mass-check might be useful for this. - --j. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) Comment: Exmh CVS iD8DBQFBD8crQTcbUG5Y7woRAsPpAKDFJEmK1GfJqGCI5gkpJqlgErEcTwCgiMEG I8NAEHd9/jJyFFdvM3WiAGk= =oRjv -----END PGP SIGNATURE-----
