You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by The Doctor <do...@doctor.nl2k.ab.ca> on 2005/07/06 02:41:30 UTC

Still need to work on Mail SpamAssassin 3.1.0

Spam Assassin 3.0.4 works with milter-spamc 0.25, smf-spamd and MailScanner
Current.

Spam Assassin 3.1.0 only works MailScanner Current less than 10% .

How can I help to determine where the source of the problem is?
 
-- 
Member - Liberal International	
This is doctor@nl2k.ab.ca	Ici doctor@nl2k.ab.ca
God Queen and country! Beware Anti-Christ rising!
Canada Day 1 July, USA Day 4 July - PARTY ON!

Re: Still need to work on Mail SpamAssassin 3.1.0

Posted by Raymond Dijkxhoorn <ra...@prolocation.net>.
Hi!

> Spam Assassin 3.0.4 works with milter-spamc 0.25, smf-spamd and MailScanner
> Current.
>
> Spam Assassin 3.1.0 only works MailScanner Current less than 10% .
>
> How can I help to determine where the source of the problem is?

I have no idea what you are talking about. Are you talking about 
MailScanner (www.mailscanner.info) ? If so, MailScanner doesnt use Spamc 
or anything. And works just fine here. running it on most of our 
production boxes (-per3) with MailScanner 4.44-1.

What do you mean with less then 10% ?

Bye,
Raymond.

Re: Still need to work on Mail SpamAssassin 3.1.0

Posted by Loren Wilton <lw...@earthlink.net>.
----- Original Message ----- 
From: "The Doctor" <do...@doctor.nl2k.ab.ca>
To: "Justin Mason" <jm...@jmason.org>
Cc: "Matt Kettler" <mk...@comcast.net>;
<us...@spamassassin.apache.org>
Sent: Friday, July 08, 2005 4:22 PM
Subject: Re: Still need to work on Mail SpamAssassin 3.1.0


> On Fri, Jul 08, 2005 at 02:32:43PM -0700, Justin Mason wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> >
> > The Doctor writes:
> > > FOund the problem.  From the logs:
> > >
> > > Thu Jul  7 21:55:45 2005 [4390] dbg: spamd: initial attempt to change
real uid failed, trying BSD workaround
> > >
> > > Thu Jul  7 21:55:45 2005 [4390] error: setruid() not implemented at
/usr/contrib/bin/spamd line 870.
> > >
> > > BSD HATES setruid().  I had to disable this in openwebmail
> > > for me to get openwebmail to work.  You may want to add code that
disables
> > > setruid in BSD.
> >
> > That might be tricky.  We don't have any code that *enables* it.
> >
> > : exit=1 Fri Jul  8 14:31:02 PDT 2005; cd /home/jm/ftp/spamassassin/t
> > : jm 29...; grep -r setruid ../lib ../spamd/spamd.raw
> > : exit=1 Fri Jul  8 14:31:07 PDT 2005; cd /home/jm/ftp/spamassassin/t
> > : jm 30...; grep -r setreuid ../lib ../spamd/spamd.raw
> > : exit=1 Fri Jul  8 14:31:10 PDT 2005; cd /home/jm/ftp/spamassassin/t
> > : jm 31...;
> >
> > We only use the perl builtins $> and $< to manipulate UIDs -- if there's
> > errors from that, you need to find a new perl that supports a working
form
> > of UID-changing on your platform.
> >
>
> This is the most current perl 5.8.7 .
>
> Next suggestion?

File a Perl bug report?

        Loren


Re: Still need to work on Mail SpamAssassin 3.1.0

Posted by Kai Schaetzl <ma...@conactive.com>.
The Doctor wrote on Fri, 8 Jul 2005 17:22:02 -0600:

> Next suggestion?

Take a long sleep and ask yourself if the attitude you are currently 
showing will get you any further.

Kai

-- 
Kai Schätzl, Berlin, Germany
Get your web at Conactive Internet Services: http://www.conactive.com
IE-Center: http://ie5.de & http://msie.winware.org




Re: Still need to work on Mail SpamAssassin 3.1.0

Posted by The Doctor <do...@doctor.nl2k.ab.ca>.
On Fri, Jul 08, 2005 at 02:32:43PM -0700, Justin Mason wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> 
> The Doctor writes:
> > FOund the problem.  From the logs:
> > 
> > Thu Jul  7 21:55:45 2005 [4390] dbg: spamd: initial attempt to change real uid failed, trying BSD workaround
> > 
> > Thu Jul  7 21:55:45 2005 [4390] error: setruid() not implemented at /usr/contrib/bin/spamd line 870.  
> > 
> > BSD HATES setruid().  I had to disable this in openwebmail
> > for me to get openwebmail to work.  You may want to add code that disables
> > setruid in BSD.
> 
> That might be tricky.  We don't have any code that *enables* it.
> 
> : exit=1 Fri Jul  8 14:31:02 PDT 2005; cd /home/jm/ftp/spamassassin/t
> : jm 29...; grep -r setruid ../lib ../spamd/spamd.raw
> : exit=1 Fri Jul  8 14:31:07 PDT 2005; cd /home/jm/ftp/spamassassin/t
> : jm 30...; grep -r setreuid ../lib ../spamd/spamd.raw
> : exit=1 Fri Jul  8 14:31:10 PDT 2005; cd /home/jm/ftp/spamassassin/t
> : jm 31...;
> 
> We only use the perl builtins $> and $< to manipulate UIDs -- if there's
> errors from that, you need to find a new perl that supports a working form
> of UID-changing on your platform.
>

This is the most current perl 5.8.7 .

Next suggestion?
 
> - --j.
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.5 (GNU/Linux)
> Comment: Exmh CVS
> 
> iD8DBQFCzvD7MJF5cimLx9ARAm27AKCnMjejOCE4jHrBcbGDa7zz8PTTCgCdFN1u
> pjmRF4W31qxPvCFyNuNX8eo=
> =nEPp
> -----END PGP SIGNATURE-----
> 

-- 
Member - Liberal International	
This is doctor@nl2k.ab.ca	Ici doctor@nl2k.ab.ca
God Queen and country! Beware Anti-Christ rising!
Canada Day 1 July, USA Day 4 July - PARTY ON!

Re: Still need to work on Mail SpamAssassin 3.1.0

Posted by The Doctor <do...@doctor.nl2k.ab.ca>.
On Fri, Jul 08, 2005 at 11:11:40AM -0400, Matt Kettler wrote:
> At 04:29 AM 7/8/2005, Martin Hepworth wrote:
> >Well that's the problem then. You are starting spamd, which MailScanner 
> >does not use..
> >
> >Other people on the MailScanner list report no issues with SA 3.1/
> 
> And before anyone leaps to conclusions, MailScaner doesn't use the 
> "spamassassin" command line either. MailScanner is a perl program, so it 
> calls SA's perl API directly.
> 
> Since MailScanner's children stay loaded and get re-used for many messages, 
> MailScanner in effect acts as it's own spamd.
> 
> 

Back to the point .  Just fix the setruid issue.

-- 
Member - Liberal International	
This is doctor@nl2k.ab.ca	Ici doctor@nl2k.ab.ca
God Queen and country! Beware Anti-Christ rising!
Canada Day 1 July, USA Day 4 July - PARTY ON!

Re: Still need to work on Mail SpamAssassin 3.1.0

Posted by Matt Kettler <mk...@comcast.net>.
At 04:29 AM 7/8/2005, Martin Hepworth wrote:
>Well that's the problem then. You are starting spamd, which MailScanner 
>does not use..
>
>Other people on the MailScanner list report no issues with SA 3.1/

And before anyone leaps to conclusions, MailScaner doesn't use the 
"spamassassin" command line either. MailScanner is a perl program, so it 
calls SA's perl API directly.

Since MailScanner's children stay loaded and get re-used for many messages, 
MailScanner in effect acts as it's own spamd.



Re: Still need to work on Mail SpamAssassin 3.1.0

Posted by Martin Hepworth <ma...@solid-state-logic.com>.
The Doctor wrote:
> On Tue, Jul 05, 2005 at 09:01:25PM -0600, The Doctor wrote:
> 
>>On Tue, Jul 05, 2005 at 10:23:45PM -0400, Matt Kettler wrote:
>>
>>>At 08:41 PM 7/5/2005, The Doctor wrote:
>>>
>>>>Spam Assassin 3.0.4 works with milter-spamc 0.25, smf-spamd and MailScanner
>>>>Current.
>>>>
>>>>Spam Assassin 3.1.0 only works MailScanner Current less than 10% .
>>>>
>>>>How can I help to determine where the source of the problem is?
>>>
>>>
>>>There is no such thing as 3.1.0 yet...
>>>
>>>did you mean 3.1.0-pre1, 3.1.0-pre2 or 3.1.0-pre3 or a SVN build?
>>>
>>>In general, all of these are unreleased, so may have some minor issues. 
>>>Certainly MailScanner is most likely to be impacted by these, as 
>>>MailScanner is an API layer caller. You might also check on the MailScanner 
>>>mailing list to see if Julian is working on some adjustments for 3.1.0 
>>>support.
>>>
>>>Also what do you mean by "only works MailScanner Current less than 10%?". 
>>>Do you mean it is only marking 10% of your spam?
>>>
>>>
>>>
>>>
>>>
>>
>> 
>>pre3 and yes about the marking.
>>
> 
> 
> FOund the problem.  From the logs:
> 
> Thu Jul  7 21:55:45 2005 [4390] dbg: spamd: initial attempt to change real uid failed, trying BSD workaround
> 
> Thu Jul  7 21:55:45 2005 [4390] error: setruid() not implemented at /usr/contrib/bin/spamd line 870.  
> 
> BSD HATES setruid().  I had to disable this in openwebmail
> for me to get openwebmail to work.  You may want to add code that disables
> setruid in BSD.
>  
> 
>>-- 
>>Member - Liberal International	

Well that's the problem then. You are starting spamd, which MailScanner 
does not use..

Other people on the MailScanner list report no issues with SA 3.1/

-- 
--
Martin Hepworth
Snr Systems Administrator
Solid State Logic
Tel: +44 (0)1865 842300

**********************************************************************

This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.

This footnote confirms that this email message has been swept
for the presence of computer viruses and is believed to be clean.	

**********************************************************************


Re: Still need to work on Mail SpamAssassin 3.1.0

Posted by The Doctor <do...@doctor.nl2k.ab.ca>.
On Tue, Jul 05, 2005 at 09:01:25PM -0600, The Doctor wrote:
> On Tue, Jul 05, 2005 at 10:23:45PM -0400, Matt Kettler wrote:
> > At 08:41 PM 7/5/2005, The Doctor wrote:
> > >Spam Assassin 3.0.4 works with milter-spamc 0.25, smf-spamd and MailScanner
> > >Current.
> > >
> > >Spam Assassin 3.1.0 only works MailScanner Current less than 10% .
> > >
> > >How can I help to determine where the source of the problem is?
> > 
> > 
> > There is no such thing as 3.1.0 yet...
> > 
> > did you mean 3.1.0-pre1, 3.1.0-pre2 or 3.1.0-pre3 or a SVN build?
> > 
> > In general, all of these are unreleased, so may have some minor issues. 
> > Certainly MailScanner is most likely to be impacted by these, as 
> > MailScanner is an API layer caller. You might also check on the MailScanner 
> > mailing list to see if Julian is working on some adjustments for 3.1.0 
> > support.
> > 
> > Also what do you mean by "only works MailScanner Current less than 10%?". 
> > Do you mean it is only marking 10% of your spam?
> > 
> > 
> > 
> > 
> > 
>  
> pre3 and yes about the marking.
>

FOund the problem.  From the logs:

Thu Jul  7 21:55:45 2005 [4390] dbg: spamd: initial attempt to change real uid failed, trying BSD workaround

Thu Jul  7 21:55:45 2005 [4390] error: setruid() not implemented at /usr/contrib/bin/spamd line 870.  

BSD HATES setruid().  I had to disable this in openwebmail
for me to get openwebmail to work.  You may want to add code that disables
setruid in BSD.
 
> -- 
> Member - Liberal International	
> This is doctor@nl2k.ab.ca	Ici doctor@nl2k.ab.ca
> God Queen and country! Beware Anti-Christ rising!
> Canada Day 1 July, USA Day 4 July - PARTY ON!

-- 
Member - Liberal International	
This is doctor@nl2k.ab.ca	Ici doctor@nl2k.ab.ca
God Queen and country! Beware Anti-Christ rising!
Canada Day 1 July, USA Day 4 July - PARTY ON!

Re: Still need to work on Mail SpamAssassin 3.1.0

Posted by The Doctor <do...@doctor.nl2k.ab.ca>.
On Tue, Jul 05, 2005 at 10:23:45PM -0400, Matt Kettler wrote:
> At 08:41 PM 7/5/2005, The Doctor wrote:
> >Spam Assassin 3.0.4 works with milter-spamc 0.25, smf-spamd and MailScanner
> >Current.
> >
> >Spam Assassin 3.1.0 only works MailScanner Current less than 10% .
> >
> >How can I help to determine where the source of the problem is?
> 
> 
> There is no such thing as 3.1.0 yet...
> 
> did you mean 3.1.0-pre1, 3.1.0-pre2 or 3.1.0-pre3 or a SVN build?
> 
> In general, all of these are unreleased, so may have some minor issues. 
> Certainly MailScanner is most likely to be impacted by these, as 
> MailScanner is an API layer caller. You might also check on the MailScanner 
> mailing list to see if Julian is working on some adjustments for 3.1.0 
> support.
> 
> Also what do you mean by "only works MailScanner Current less than 10%?". 
> Do you mean it is only marking 10% of your spam?
> 
> 
> 
> 
> 
 
pre3 and yes about the marking.

-- 
Member - Liberal International	
This is doctor@nl2k.ab.ca	Ici doctor@nl2k.ab.ca
God Queen and country! Beware Anti-Christ rising!
Canada Day 1 July, USA Day 4 July - PARTY ON!

Re: Still need to work on Mail SpamAssassin 3.1.0

Posted by Matt Kettler <mk...@comcast.net>.
At 08:41 PM 7/5/2005, The Doctor wrote:
>Spam Assassin 3.0.4 works with milter-spamc 0.25, smf-spamd and MailScanner
>Current.
>
>Spam Assassin 3.1.0 only works MailScanner Current less than 10% .
>
>How can I help to determine where the source of the problem is?


There is no such thing as 3.1.0 yet...

did you mean 3.1.0-pre1, 3.1.0-pre2 or 3.1.0-pre3 or a SVN build?

In general, all of these are unreleased, so may have some minor issues. 
Certainly MailScanner is most likely to be impacted by these, as 
MailScanner is an API layer caller. You might also check on the MailScanner 
mailing list to see if Julian is working on some adjustments for 3.1.0 support.

Also what do you mean by "only works MailScanner Current less than 10%?". 
Do you mean it is only marking 10% of your spam?






Re: Still need to work on Mail SpamAssassin 3.1.0

Posted by Kai Schaetzl <ma...@conactive.com>.
The Doctor wrote on Tue, 5 Jul 2005 18:41:30 -0600:

> Spam Assassin 3.1.0 only works MailScanner Current less than 10% .

What do you mean by that? MailScanner latest plus SA 3.1.0-pre-something 
works. No problems at all.

Kai

-- 
Kai Schätzl, Berlin, Germany
Get your web at Conactive Internet Services: http://www.conactive.com
IE-Center: http://ie5.de & http://msie.winware.org




Re: Still need to work on Mail SpamAssassin 3.1.0

Posted by Andy Jezierski <aj...@stepan.com>.
The Doctor <do...@doctor.nl2k.ab.ca> wrote on 07/05/2005 07:41:30 PM:

> Spam Assassin 3.0.4 works with milter-spamc 0.25, smf-spamd and 
MailScanner
> Current.
> 
> Spam Assassin 3.1.0 only works MailScanner Current less than 10% .
> 
> How can I help to determine where the source of the problem is?
> 

Don't know what you mean. I have milter-spamc 0.25 working just fine with 
the latest 3.1 SVN release.

Andy