SA Headers not on Ham

2005-07-17 Thread Mosenior Moses
Hello,

 We are running spamassassin with qmail/procmail. Spamassassin Version 3.0.1 on 
Fedora Core 2. 
The problem that I'm seeing is that Ham messages are coming through with out 
having the SA headers
being added to them. What's interesting is that messages are being filtered 
even still, as we have a spam mailbox
and I can see recently filtered spam in it. I've done quite a bit of searching 
around (google of course) and haven't been able 
to determine where the failure is occuring. Is there a configuration I might be 
missing somewhere?

Thanks,
Mosenior Moses
'Mo' 


Re: HELP: Looking for mac mail server software

2005-07-17 Thread Jeffrey Lee

try communigate pro
www.stalker.com

On Jul 16, 2005, at 9:21 PM, Jonathan Nichols wrote:




OS X uses Postfix by default (at least it does on my Powerbook   
running Tiger).  While it's not "graphical" per-sea, it's not   
difficult to set up.  I'm sure someone out there has written a  
GUI  for it.  Check out VersionTracker.




Postfix Enabler:

http://www.cutedgesystems.com/software/PostfixEnabler/


More good stuff here, even some SpamAssassin on OS X articles! :)

http://www.afp548.com/






Re[2]: Rule Advice

2005-07-17 Thread Robert Menschel
Hello dennis,

Friday, July 15, 2005, 10:08:56 PM, you wrote:

dsc> On Jul 15, 2005, at 3:19 PM, Loren Wilton wrote:
dsc> If that username starts with six digits, it hits that rule, as shown
dsc> in Loren's example.

dsc> Ah, here is the From header:
dsc> From: 360° Skin Care <[EMAIL PROTECTED]>
dsc> Not 6 digits, but maybe the degree symbol is contributing. I'll advise not
dsc> to start the username with 360°.

dsc> No, you misunderstood again.  The part the rule is hitting on is the ""
dsc> in the above example line.  Since the rule hit, I'm assuming this wan't
dsc> really "" in the original mail, but more like "10001monkeys" or the
dsc> like.

dsc> Nope. It's a four letter name, like FRED. It didn't seem to
dsc> be relevant to include the real full email address. Please let me
dsc> know if you need it.

dsc> This is also why I asked if you were referring to the
dsc> Message-Id header since that is the only address that starts with
dsc> six digits.

dsc> I'm not sure what I keep misunderstanding. Can you elaborate?

Nope.  From these discussions, your email is hitting a rule that
supposedly it should not hit. The code for the rule is very clear
about what and where it should be hitting, and you claim it isn't
there.

The only way we can resolve this is if you send a full, untarnished,
complete and unedited, email which demonstrates this problem, with all
headers, as an attachment, to someone who can do the full diagnostics
on it to figure out what's happening.

I'm willing to be that someone if you want.

Bob Menschel





[SARE] obfu1.cf updated

2005-07-17 Thread Robert Menschel
Just a quick note that
http://www.rulesemporium.com/rules/70_sare_obfu1.cf has been updated
to avoid a performance problem reported this week. 

Bob Menschel




HOWTO build milter-spamc on Mac/X "Tiger" part II

2005-07-17 Thread Dr Robert Young
I left out the second part of the milter-spamc 0.25 build from the  
first posting (sorry about that...my fault). The first posting was  
for the Libsnert library needed by milter-spamc. This one is for the  
"milter-spamc" itself.


In addition to the earlier changes (gcc 3.3 and -o) , you must  
also specify "--enable-startup-dir=" to the configure line (in  
this example /tmp, but in real life it should be something  
"useful" ) . Required items show up because I have not "installed"  
them as yet...I'm just happy to get configure working right now.




  LibSnert: required
  libmilter...: required
  ..Has reject & deliver patch: no
  Berkeley DB.: not found
  Run As User.: smmsp
  Run As Group: smmsp
  State directory root: /var/spool
  Startup script directory: /tmp
  CFLAGS..:  -D_REENTRANT -D_THREAD_SAFE -I../../ 
include  -fvolatile

  LDFLAGS.:  -L../../lib
  LIBS: -lpthread



HOWTO build milter-spamc on Mac/X "Tiger"

2005-07-17 Thread Dr Robert Young

Just as an update to those who have an interest,

gcc 4.0 and higher will cause problems with milter-spamc release  
0.25. The configure script puts in params that changed between gcc  
3.x and 4.x (specifically the -fvolatile ). It also has a problem  
with the -V .


gcc: argument to `-V' is missing
cc1: error: unrecognized command line option "-fvolatile"

Mac/X "Tiger"  has the 3.3 compiler installed as well, although 4.0.0  
is the default.

Use "gcc_select -force 3.3" to make 3.3 the default.

Edit the configure script to make "-o" into "-o " (note the space).  
Otherwise it will error on


/usr/bin/ld: unknown flag: -oconftest

Now it will build (of course in this example I still have to make  
libmilter & the Berkeley DB)


  Mutex: POSIX_API
  Shared Memory: POSIX_API
  Time.: BSD_API
  Berkeley DB..: not found
  libmilter: no
  CFLAGS...:  -D_REENTRANT -g -Wall -fvolatile
  LDFLAGS..:
  LIBS.: -lpthread

But at least it gets to the end without bombing out!!

Thanks to Anthony Howe for his help in pointing me in the right  
direction.







Dr. Robert Young
ALI Database Consultants
1151 Williams Dr
Aiken SC 29803
USA

WWW: http://www.aliconsultants.com
Tele: 1-803-648-5931
Toll free in US: 1-866-257-8970 Fax:1-803-641-0345
Email: [EMAIL PROTECTED]
"Source of Rdb Controller, software for database analysis &   
performance tuning"





RE: SPAMD dies

2005-07-17 Thread Herb Martin
>  I run into this as well, sometimes it will run along great, 
> and then just out of the blue die with no reason or errors 
> that I can find.  Actually happened to me this morning, woke 
> up to a pile of spam in my mailbox, and thought guess spamd 
> died off, time to restart it.

My SpamD didn't die literally, but would stop functioning,
just seeming to hang when asked to classify spam.

I am running on Cygwin and put it down to the OS-environment,
but on testing the cvs snapshots (3.10pre4+) my initial, very 
brief evaluation (and hope) is that the problem is reduced
(or eliminated.)


--
Herb Martin




RE: SPAMD dies

2005-07-17 Thread Howard Leadmon

 I run into this as well, sometimes it will run along great, and then just out
of the blue die with no reason or errors that I can find.  Actually happened
to me this morning, woke up to a pile of spam in my mailbox, and thought guess
spamd died off, time to restart it.

I have it running on FreeBSD 4.x and 5.x servers, and now actually 6.x
servers, and all of them seem to do this from time to time, and have with any
of the SA3.x releases up to the most current 3.0.4 version.  FYI, I use
procmail to invoke spamc and process via spamd, as sendmail uses procmail as
my delivery agent.

So though I don't have a solution, your sure not the only one that sees this
happen..  :)


---
Howard Leadmon 


> -Original Message-
> From: Daryl C. W. O'Shea [mailto:[EMAIL PROTECTED]
> Sent: Friday, July 15, 2005 2:03 AM
> To: Thomas Kinghorn [MTNNS -Rosebank]
> Cc: users@spamassassin.apache.org
> Subject: Re: SPAMD dies
> 
> Thomas Kinghorn [MTNNS -Rosebank] wrote:
> > Good morning list.
> >
> > I am having issues with SPAMD just dying and no info being shown in the
> > logs to help troubleshoot.
> >
> 
> > The system is running Redhat 9, Latest versions of Exim  & spamassassin.
> > Spamassassin uses pyzor, razor & dcc.
> 
> What "latest version" of SpamAssassin are you using?  Have you (or a
> distribution maintainer) applied any patches to it?
> 
> Daryl