RES: RES: MESSAGE TO BIG?
Well I am looking at list and Google and I didnt read nothing about how to change this configuration.. Where I change this? Any help? The most funny is that when I receive a message outside my Email server or from my web mail ( IMP HORDE) everything work fine.. This just happens when I use an Email client using a SMTP or pop direct connection. So!! If anyone know a good way to solve this.. Please let me know.. THANKSS so much... :-) -Mensagem original- De: Rick Macdougall [mailto:[EMAIL PROTECTED]] Enviada em: quarta-feira, 8 de março de 2006 18:13 Para: [EMAIL PROTECTED] Cc: users@spamassassin.apache.org Assunto: Re: MESSAGE TO BIG? [EMAIL PROTECTED] wrote: > Iam using spamassassin last one.. > Slackware and qmail.. > last time iam receiving this mesages when i try to send a email with > atachements or images at body.. > By default SA does not scan anything over 250k, it's not a problem. Regards, Rick
Re: RES: RES:
> But I think that some times ago I got some rules and when I made > upgrade to new version it stop to worked. > > 20_porn.cf > bogus-virus-warnings.cf > chickenpox.cf > evilrules.cf local.cf-new > antidrug.cf br_rules.cf > DomainDigits1.cf > viruses.cf Many of these are common files. Unless they have been corrupted they should not be problems: > bogus-virus-warnings.cf > chickenpox.cf > antidrug.cf > DomainDigits1.cf These are much less common files. There could be a problem in one of these: > 20_porn.cf > evilrules.cf > local.cf-new > br_rules.cf > viruses.cf I would expect a grep for /n.nn/ to show up in one of these. Loren BTW, if you are using 3.x, you should NOT be using antidrug.cf. It is already built into SA.
Re: RES: RES:
Marcos Manhanes wrote: Actually, to be more specific, you need to find a score statement which literally has "n.nn" in it instead of an actual score. I'd venture to guess someone copy-pasted *directly* out of the manpage. grep score /etc/mail/spamassassin/*.cf |grep "n\.nn" grep score ~/.spamassassin/user_prefs |grep "n\.nn"
Re: RES: RES: RES:
Marcos Manhanes wrote: > When I made it command not show nothing. > > But I think that some times ago I got some rules and when I made > upgrade to new version it stop to worked. > > Did you see it's rules ? > > 20_porn.cf > bogus-virus-warnings.cf > chickenpox.cf > evilrules.cf local.cf-new > antidrug.cf br_rules.cf > DomainDigits1.cf > viruses.cf You definitely should delete antidrug.cf. Antidrug is only intended for users of SA 2.6x and older. These rules are built-in to SA 3.0.0 and higher, so by adding antidrug you could be downgrading your config if the SA main-line ever improves or tweaks these rules. For reference, I am the author of antidrug.cf, so I speak with at least some authority about it. I can't really speak for the other rule files, but you might want to try moving them all out of the directory and adding them back one at a time to see which one triggers the problem.
Re: RES: RES:
Marcos Manhanes wrote: > It information arrived to you ? I don't need your conf.pm. That just proves my assumption about your version was correct. I need your score statements from your config files. I need the output of these two commands: grep score /etc/mail/spamassassin/* grep score ~/.spamassassin/user_prefs > > ## Conf.pm # . > > > -Mensagem original- > De: Matt Kettler [mailto:[EMAIL PROTECTED] > Enviada em: segunda-feira, 13 de fevereiro de 2006 14:13 > Para: Marcos Manhanes > Cc: spamassassin-users@incubator.apache.org > Assunto: Re: RES: > > > Marcos Manhanes wrote: >> Friends, >> >> I'm running SpamAssassin version 3.1.0 with Perl version 5.8.0. >> >> It's a copy of the file Conf.pm > > Ok, so it's DEFINITELY a score command.. So follow my advice with the grep > statements from the previous email I posted from my comcast.net account. >
RES: RES: RES:
When I made it command not show nothing. But I think that some times ago I got some rules and when I made upgrade to new version it stop to worked. Did you see it's rules ? 20_porn.cf bogus-virus-warnings.cf chickenpox.cf evilrules.cf local.cf-new antidrug.cf br_rules.cf DomainDigits1.cf viruses.cf I removed it for to try fix the problem. -Mensagem original- De: Matt Kettler [mailto:[EMAIL PROTECTED] Enviada em: segunda-feira, 13 de fevereiro de 2006 15:19 Para: Marcos Manhanes; users@spamassassin.apache.org Assunto: Re: RES: RES: Marcos Manhanes wrote: Actually, to be more specific, you need to find a score statement which literally has "n.nn" in it instead of an actual score. I'd venture to guess someone copy-pasted *directly* out of the manpage. grep score /etc/mail/spamassassin/*.cf |grep "n\.nn" grep score ~/.spamassassin/user_prefs |grep "n\.nn" -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.375 / Virus Database: 267.15.5/256 - Release Date: 10/2/2006 -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.375 / Virus Database: 267.15.5/256 - Release Date: 10/2/2006
Re: RES: RES:
Marcos Manhanes wrote: It information arrived to you ? It did, twice. Now do what Matt said and grep for n.nn in your config files, probably in /etc/mail/spamassassin Daryl
RES: RES:
It information arrived to you ?
## Conf.pm #
245 # Set the actual scoreset values appropriately
246 for my $index (0..3) {
247 my $score = $relative ?
248 $self->{scoreset}->[$index]->{$rule} + $scores[$index] :
249 $scores[$index];
250
251 $self->{scoreset}->[$index]->{$rule} = $score + 0.0;
252 }
253 }
254 else {
255 my $msg = "config: score configuration option without actual
scores, skipping: $line";
256
257 if ($self->{lint_rules}) {
258 warn $msg."\n";
259 } else {
260 info($msg);
261 }
262 $self->{errors}++;
263 return $MISSING_REQUIRED_VALUE;
264 }
265 }
266 });
267
###
-Mensagem original-
De: Matt Kettler [mailto:[EMAIL PROTECTED]
Enviada em: segunda-feira, 13 de fevereiro de 2006 14:13
Para: Marcos Manhanes
Cc: spamassassin-users@incubator.apache.org
Assunto: Re: RES:
Marcos Manhanes wrote:
> Friends,
>
> I'm running SpamAssassin version 3.1.0 with Perl version 5.8.0.
>
> It's a copy of the file Conf.pm
Ok, so it's DEFINITELY a score command.. So follow my advice with the grep
statements from the previous email I posted from my comcast.net account.
--
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.1.375 / Virus Database: 267.15.5/256 - Release Date: 10/2/2006
--
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.375 / Virus Database: 267.15.5/256 - Release Date: 10/2/2006
