From: "Daryl C. W. O'Shea" <[EMAIL PROTECTED]>
On 3/18/2006 10:34 PM, jdow wrote:
From: "Daryl C. W. O'Shea" <[EMAIL PROTECTED]>
On 3/18/2006 9:03 PM, jdow wrote:
Yah know, that does suggest there should be a "whitelist_to" option for
those who setup honeypot accounts.
(That way, Theo, spa
On 3/18/2006 10:34 PM, jdow wrote:
From: "Daryl C. W. O'Shea" <[EMAIL PROTECTED]>
On 3/18/2006 9:03 PM, jdow wrote:
Yah know, that does suggest there should be a "whitelist_to" option for
those who setup honeypot accounts.
(That way, Theo, spam COULD be sent to this list.
I'm pretty sure
From: "Daryl C. W. O'Shea" <[EMAIL PROTECTED]>
On 3/18/2006 9:03 PM, jdow wrote:
Yah know, that does suggest there should be a "whitelist_to" option for
those who setup honeypot accounts.
(That way, Theo, spam COULD be sent to this list.
I'm pretty sure SpamAssassin already has a similar fea
On 3/18/2006 9:03 PM, jdow wrote:
Yah know, that does suggest there should be a "whitelist_to" option for
those who setup honeypot accounts.
(That way, Theo, spam COULD be sent to this list.
I'm pretty sure SpamAssassin already has a similar feature. I think
it's called whitelist_to. :)
From: "jdow" <[EMAIL PROTECTED]>
From: "Philip Prindeville" <[EMAIL PROTECTED]>
Matt Kettler wrote:
Philip Prindeville wrote:
Grrr... Can we enable whitelisting for list members?
Read the archives, in short, no, because it's a blanket server that covers ALL
ASF email, not just th
From: "Philip Prindeville" <[EMAIL PROTECTED]>
Theo Van Dinter wrote:
On Sat, Mar 18, 2006 at 04:05:03PM -0500, Matt Kettler wrote:
Philip Prindeville wrote:
Grrr... Can we enable whitelisting for list members?
Read the archives, in short, no, because it's a blanket server t
From: "Philip Prindeville" <[EMAIL PROTECTED]>
Matt Kettler wrote:
Philip Prindeville wrote:
Grrr... Can we enable whitelisting for list members?
Read the archives, in short, no, because it's a blanket server that covers ALL
ASF email, not just this list.
There's no way that y
From: "MJ" <[EMAIL PROTECTED]>
>You can and probably should remove the journal file. These are
unlearned tokens, so they aren't affecting the classification of mail.
The journal is >so huge that it might take days to learn, and it also
indicates that you are accumulating new material fairly qui
I know there are varying opinions on whether the AutoWhiteList option is a
good idea or not, and I'm starting to have my doubts, but bare with me as I
attempt to describe problems I am having even maintaining it at what I would
consider an acceptable level as an administrator.
Firstly, I'm using
On Saturday 18 March 2006 4:38 pm, Theo Van Dinter wrote:
> On Sat, Mar 18, 2006 at 04:27:34PM -0600, Chris wrote:
> > However, this always results in an empty trust.cf file. I'm running it
> > from the ~/.spamassassin folder where my bayes files are located.
> > Could someone point out what I'm
On 3/18/06, mouss <[EMAIL PROTECTED]> wrote:
> Terry a écrit :
> > Actually,
> >
> > I got the ALL_TRUSTED I think but I cannot get the x-spam-status
> > header to show up to even start debugging.
>
> What tells you you "got the ALL_TRUSTED" if you don't get a header?
>
> SA is being called from
>
On Sat, 2006-03-18 at 15:00 -0500, Theo Van Dinter wrote:
> On Sat, Mar 18, 2006 at 01:40:23PM -0500, czar wrote:
> > [17437] dbg: config: using "/var/lib/spamassassin/3.001001" for sys
> > rules pre files
> > [17437] dbg: config: using "/var/lib/spamassassin/3.001001" for default
> > rules dir
>
On Sat, Mar 18, 2006 at 04:27:34PM -0600, Chris wrote:
> However, this always results in an empty trust.cf file. I'm running it from
> the ~/.spamassassin folder where my bayes files are located. Could someone
> point out what I'm doing wrong. I'm running SA 3.1.0 and the
> bayes_dump_to_trus
Trying to use this tool with the following syntax:
sa-learn --dump | ./bayes_dump_to_trusted_networks > trust.cf
However, this always results in an empty trust.cf file. I'm running it from
the ~/.spamassassin folder where my bayes files are located. Could someone
point out what I'm doing wron
Philip Prindeville wrote:
>>>
>>>
>> you can do that and more, but you'll first need to crack the ASF servers ;-p
>>
>>
>>
>
> And there's no way to get the admin on that system to tweak the local rules?
Erm.. No... Remember, this is a COMMON server that serves the lists for many, if
not A
On Sat, Mar 18, 2006 at 02:41:46PM -0700, Philip Prindeville wrote:
> >>>Read the archives, in short, no, because it's a blanket server that covers
> >>>ALL
> >>>ASF email, not just this list.
>
> And there's no way to get the admin on that system to tweak the local rules?
As Matt stated earlier
mouss wrote:
>Philip Prindeville a écrit :
>
>
>>Matt Kettler wrote:
>>
>>
>>
>>
>>>Philip Prindeville wrote:
>>>
>>>
>>>
>>>
>>>
Grrr... Can we enable whitelisting for list members?
>>>Read the archives, in short, no, because it's a blanket server th
Philip Prindeville a écrit :
> Matt Kettler wrote:
>
>
>>Philip Prindeville wrote:
>>
>>
>>
>>>Grrr... Can we enable whitelisting for list members?
>>>
>>>
>>
>>Read the archives, in short, no, because it's a blanket server that covers ALL
>>ASF email, not just this list.
>>
>>
>
>
> Ther
Theo Van Dinter wrote:
>On Sat, Mar 18, 2006 at 04:05:03PM -0500, Matt Kettler wrote:
>
>
>>Philip Prindeville wrote:
>>
>>
>>>Grrr... Can we enable whitelisting for list members?
>>>
>>>
>>Read the archives, in short, no, because it's a blanket server that covers ALL
>>ASF email, not
Matt Kettler wrote:
>Philip Prindeville wrote:
>
>
>>Grrr... Can we enable whitelisting for list members?
>>
>>
>
>Read the archives, in short, no, because it's a blanket server that covers ALL
>ASF email, not just this list.
>
>
There's no way that you can add a rule that says if the me
On Sat, Mar 18, 2006 at 04:05:03PM -0500, Matt Kettler wrote:
> Philip Prindeville wrote:
> > Grrr... Can we enable whitelisting for list members?
> Read the archives, in short, no, because it's a blanket server that covers ALL
> ASF email, not just this list.
Generally, instead of posting spam e
> -Original Message-
> From: Matt Kettler [mailto:[EMAIL PROTECTED]
>
> I had the same problem. I wound up implementing
> milter-greylist in a way that
> greylists these hosts, but lets most systems past. I'm not
> sure if you're using
> sendmail or not, but I found this VERY helpful.
>
Philip Prindeville wrote:
> Grrr... Can we enable whitelisting for list members?
Read the archives, in short, no, because it's a blanket server that covers ALL
ASF email, not just this list.
mouss wrote:
> Matt Kettler a écrit :
>> I had the same problem. I wound up implementing milter-greylist in a way that
>> greylists these hosts, but lets most systems past. I'm not sure if you're
>> using
>> sendmail or not, but I found this VERY helpful.
>>
>> The selective greylisting is possibl
Grrr... Can we enable whitelisting for list members?
The original message was received at Sat, 18 Mar 2006 13:57:43 -0700
from media.redfish-solutions.com [192.168.1.5]
- The following addresses had permanent fatal errors -
(reason: 552 spam score (12.2) exceeded threshold)
-
Matt Kettler a écrit :
> I had the same problem. I wound up implementing milter-greylist in a way that
> greylists these hosts, but lets most systems past. I'm not sure if you're
> using
> sendmail or not, but I found this VERY helpful.
>
> The selective greylisting is possible due to milter-grey
Bill Randle a écrit :
> On Sat, 2006-03-18 at 09:54 -0600, Terry wrote:
>
>>Actually,
>>
>>I got the ALL_TRUSTED I think but I cannot get the x-spam-status
>>header to show up to even start debugging. SA is being called from
>>amavisd. I have these settings in amavisd.conf:
>>
>>$sa_tag_level_de
Terry a écrit :
> Actually,
>
> I got the ALL_TRUSTED I think but I cannot get the x-spam-status
> header to show up to even start debugging.
What tells you you "got the ALL_TRUSTED" if you don't get a header?
SA is being called from
> amavisd. I have these settings in amavisd.conf:
>
> $sa_
On Sat, Mar 18, 2006 at 01:40:23PM -0500, czar wrote:
> [17437] dbg: config: using "/var/lib/spamassassin/3.001001" for sys
> rules pre files
> [17437] dbg: config: using "/var/lib/spamassassin/3.001001" for default
> rules dir
It looks like you tried to run sa-update but it wasn't able to complet
MJ a écrit :
> Hi Gary,
>
>
>>The user 'clamav' should have a home dir of /var/amavis otherwise I
>
> wouldn't
>
>>think the spamassasin files would end up in /var/amavis/.spamassassin.
>
>
>>what does this say?
>>cat /etc/passwd | grep clamav
>
>
> clamav:x:1005:103::/home/clamav:/bin/fal
On Sat, Mar 18, 2006 at 07:13:33PM +, Craig McLean wrote:
> I've tinkered with t/SATest.pm to help get "make test" working correctly
> in jails on FreeBSD. What's the best way to get this to the committers?
> bugzilla? the dev list?
All patches should go through Bugzilla. FYI: Any "decently
s
On Sat, 18 Mar 2006, czar wrote:
hI,
[...]
> # I try the CPAN test install of Mail::SpamAssassin, this MIGHT be the
> problem?
> $ perl -MCPAN -e shell
> $ test Mail::SpamAssassin
> [...]
> t ../masses/parse-rules-for-masses line 86, line 55.
> Malformed UTF-8 character (unexpected non-continuat
Dave Augustus wrote:
> Anyone point me in the right direction?
>
> I am just thinking of increasing the spam level counter based on whether
> they have a reverse IP address. I have tried to reject these outiright
> based on this criteria but that would cause too many false positives.
Slightly OT,
On Sat, 18 Mar 2006, Dave Augustus wrote:
>
> Anyone point me in the right direction?
>
> I am just thinking of increasing the spam level counter based on whether
> they have a reverse IP address. I have tried to reject these outiright
> based on this criteria but that would cause too many false p
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Folks,
I've tinkered with t/SATest.pm to help get "make test" working correctly
in jails on FreeBSD. What's the best way to get this to the committers?
bugzilla? the dev list?
Thanks,
C.
- --
Craig McLeanhttp://fukka.co.uk
[EMAIL PROTECTED
Hopefully some one could help me out with this SpamAssassin v3.1.1
upgrade issue.
Currently my Red Hat Linux server is using CPanel which automatically
updates via CPAN when a new release is announced (/scripts/cpup). Yet
for some reason this latest release of SA has caused the whole package
to
Anyone point me in the right direction?
I am just thinking of increasing the spam level counter based on
whether they have a reverse IP address. I have tried to reject these
outiright based on this criteria but that would cause too many false
positives.
I am already using alot of rules via rules_
On 3/18/06, Bill Randle <[EMAIL PROTECTED]> wrote:
> On Sat, 2006-03-18 at 09:54 -0600, Terry wrote:
> > Actually,
> >
> > I got the ALL_TRUSTED I think but I cannot get the x-spam-status
> > header to show up to even start debugging. SA is being called from
> > amavisd. I have these settings in
Hi Gary,
>The user 'clamav' should have a home dir of /var/amavis otherwise I
wouldn't
>think the spamassasin files would end up in /var/amavis/.spamassassin.
>what does this say?
>cat /etc/passwd | grep clamav
clamav:x:1005:103::/home/clamav:/bin/false
>To run sa-learn as this user (who does
On Sat, 2006-03-18 at 09:54 -0600, Terry wrote:
> Actually,
>
> I got the ALL_TRUSTED I think but I cannot get the x-spam-status
> header to show up to even start debugging. SA is being called from
> amavisd. I have these settings in amavisd.conf:
>
> $sa_tag_level_deflt = undef;
...
> The fir
On Tue, Mar 14, 2006 at 06:11:34PM -0500, Theo Van Dinter wrote:
> spamd is designed to really not do a lot in the parent (which runs as
> root), and farm processing and such out to the children (which setuid()
> to the appropriate user).
>
> - accept connection and figure out enough to setuid to
Terry wrote:
> Actually,
>
> I got the ALL_TRUSTED I think but I cannot get the x-spam-status
> header to show up to even start debugging. SA is being called from
> amavisd. I have these settings in amavisd.conf:
>
> $sa_tag_level_deflt = undef;
> $sa_tag2_level_deflt = 5.0;
> $sa_kill_level_def
Actually,
I got the ALL_TRUSTED I think but I cannot get the x-spam-status
header to show up to even start debugging. SA is being called from
amavisd. I have these settings in amavisd.conf:
$sa_tag_level_deflt = undef;
$sa_tag2_level_deflt = 5.0;
$sa_kill_level_deflt = 5.0;
$sa_dsn_cutoff_leve
Hi Gary,
>The user 'clamav' should have a home dir of /var/amavis otherwise I
wouldn't
>think the spamassasin files would end up in /var/amavis/.spamassassin.
>what does this say?
>cat /etc/passwd | grep clamav
clamav:x:1005:103::/home/clamav:/bin/false
>To run sa-learn as this user (who does
On Samstag, 18. März 2006 11:51 MJ wrote:
> No, there is another user for daemon with a false shell, can't be use
> to login as a normal user.
The user 'clamav' should have a home dir of /var/amavis otherwise I wouldn't
think the spamassasin files would end up in /var/amavis/.spamassassin.
wh
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Theo Van Dinter wrote:
> On Fri, Mar 17, 2006 at 08:18:35PM -0800, Dan Kohn wrote:
>> Anything else to try?
>
> Nothing comes to mind. It looks like a bug in IO::Zlib or perl on
> your platform.
>
> Anyone else on FreeBSD having simliar problems?
F
>You can and probably should remove the journal file. These are
unlearned tokens, so they aren't affecting the classification of mail.
The journal is >so huge that it might take days to learn, and it also
indicates that you are accumulating new material fairly quickly. So
losing the current journ
Title: RE: Huge size of bayes_journal
You can and probably should remove the journal file. These are
unlearned tokens, so they aren't affecting the classification of mail. The
journal is so huge that it might take days to learn, and it also indicates that
you are accumulating new material f
Title: RE: Huge size of bayes_journal
Hi Theo,
I manage to switch to that user and executed the sa-learn command but since it has it' own home directory it created new .spamassassin directory under it's home directory. Actually "/var/amavisd/.spamassassin" which has these files is not a hom
On Samstag, 18. März 2006 11:51 MJ wrote:
> No, there is another user for daemon with a false shell, can't be use
> to login as a normal user.
su -l $USER_AMAVIS_RUNS_AS -s /bin/bash
That way you can run as the user with bash.
mfg zmi
--
// Michael Monnerie, Ing.BSc --- it-management Michae
On Sat, Mar 18, 2006 at 01:51:45PM +0300, MJ wrote:
> Thanks for you quick response.
:)
> >The "#" implies you're running as root. Is that the same user as
> amavis runs as?
>
> No, there is another user for daemon with a false shell, can't be use to
> login as a normal user.
You need to someh
Hi Theo van Dinter,
Thanks for you quick response.
>The "#" implies you're running as root. Is that the same user as
amavis runs as?
No, there is another user for daemon with a false shell, can't be use to
login as a normal user.
>This isn't the same path as you posted before, so I'm not surpr
On Sat, Mar 18, 2006 at 01:07:30PM +0300, MJ wrote:
> I did but still the same size, following is the output.
> bash-2.03# /usr/local/bin/sa-learn -D --sync
The "#" implies you're running as root. Is that the same user as amavis
runs as?
[...]
> [17329] dbg: bayes: tie-ing to DB file R/O //.spam
Hi Theo Van Dinter
>I don't know if amavisd does something special wrt bayes,
Do you need me to send amavisd.conf? usually they (mailing list of
amavisd-new) suggest to post SA related issues to this list and not on
Amavisd-new list.
>As the appropriate user, run "sa-learn -D --sync" and see wh
On Sat, Mar 18, 2006 at 12:07:35PM +0300, MJ wrote:
> I am running postfix 2.2.4 on Solaris 8 with amavisd-new.2.3.2,
I don't know if amavisd does something special wrt bayes,
> reaching to 3.4 GB. I have read that this file should not be more than
> few KB, Can anyone help what could be the reas
Matt Kettler wrote:
> [EMAIL PROTECTED] wrote:
>
>> Well, then how do I get SA to read the headers and exclude
>> some IP addresses? Surely there is a command for that - or a
>> box to fill out - or a custom config. I need something to exclude
>> all those bothersome emails from Japan, Nigeria
Hi,
I am running postfix 2.2.4 on Solaris 8 with amavisd-new.2.3.2,
SpamAssassin 3.1.0 and Clamav 0.8.7.1 as an AV/AS gateway to my main
email system. The problem is that in our "/var/amavis/.spamassassin"
directory most of the files are increasing specially "bayes_jornal" is
reaching to 3.4 GB. I
On Sat, Mar 18, 2006 at 04:04:10AM -0500, Matt Kettler wrote:
> Admittedly it would be somewhat nice for SA to have this feature, but
> really you're 100% better off doing it at the MTA or firewall layer if
> you're going to do all the work of maintaining an IP address list.
FWIW, there is the Acc
[EMAIL PROTECTED] wrote:
> Well, then how do I get SA to read the headers and exclude
> some IP addresses? Surely there is a command for that - or a
> box to fill out - or a custom config. I need something to exclude
> all those bothersome emails from Japan, Nigeria, China, etc.
>
The normal w
Well, then how do I get SA to read the headers and exclude
some IP addresses? Surely there is a command for that - or a
box to fill out - or a custom config. I need something to exclude
all those bothersome emails from Japan, Nigeria, China, etc.
How to filter out emails from IP addresses and IP
60 matches
Mail list logo
