Thanks to everyone who helped with this. A variant of Benny's suggestion
works, and can be implemented through plesk without editing the config files
directly:
1. Whitelist all acceptable sources.
2. Blacklist *...@*.*
3. Set the reject score to a moderate value, e.g. 10
My whitelisted sources w
On Sun, 2010-06-13 at 11:35 -0400, Charles Gregory wrote:
> On Sat, 12 Jun 2010, Karsten Bräckelmann wrote:
> > There are just a very few rules "scanning" non-textual parts of a mail.
> > Large-ish binary attachments don't have much of an impact on
> > performance. Large-ish textual attachments po
Hi,
I want to check some mails for their char count (will be part of a meta
rule) but spamassassin does hit the rule, even if the mail has less chars
than defined in regex.
The regex was tested in Perl and was working fine, so what did I miss?
bodyMY_BODY_SHORT_MAIL
Nataraj wrote:
I would also think there would be some good header tests, such as having
a list-id header, but the problem here is that if this became used
universally, spammers could easily add false headers.
I've already seen List-id and related headers in spam. :/
-kgd
Daniel Lemke wrote:
> Hi,
>
> I want to check some mails for their char count (will be part of a meta
> rule) but spamassassin does hit the rule, even if the mail has less chars
> than defined in regex.
>
> The regex was tested in Perl and was working fine, so what did I miss?
>
> body
On Mon, 2010-06-14 at 07:41 -0700, Daniel Lemke wrote:
> I want to check some mails for their char count (will be part of a meta
> rule) but spamassassin does hit the rule, even if the mail has less chars
> than defined in regex.
You mean *more* chars, no? Less than zero isn't possible, and the RE
Bowie Bailey wrote:
> Daniel Lemke wrote:
>
>> Hi,
>>
>> I want to check some mails for their char count (will be part of a meta
>> rule) but spamassassin does hit the rule, even if the mail has less chars
>> than defined in regex.
>>
>> The regex was tested in Perl and was working fine, so what
Hi to all,
i have a problem with the command sa-update.
When i try to do the command:
"sa-update -D --nopgp"
The script return this error/warning:
"Argument '1.26_01' isen't numeric in subroutine entry at in sa-update
line 80"
after this the sa-update return "Exit Code 0" (so it seem that the
u
On Mon, 14 Jun 2010, Daniel Lemke wrote:
I want to check some mails for their char count (will be part of a meta
rule) but spamassassin does hit the rule, even if the mail has less
chars than defined in regex.
bodyMY_BODY_SHORT_MAIL /\A.{0,150}\z/s
describe
SA is correctly assigning a high score to an email (Content analysis details:
(12.0 points, 3.5 required)) but the X-Spam-Status header reads: No,
score=0.0 required=3.5 tests=HTML_MESSAGE,MIME_BASE64_TEXT,
MIME_QP_LONG_LINE,NO_RELAYS,T_HTML_ATTACH autolearn=unavailable
version=3.3.1... any hints?
On Mon, 14 Jun 2010, dannoz wrote:
>
> SA is correctly assigning a high score to an email (Content analysis details:
> (12.0 points, 3.5 required)) but the X-Spam-Status header reads: No,
> score=0.0 required=3.5 tests=HTML_MESSAGE,MIME_BASE64_TEXT,
> MIME_QP_LONG_LINE,NO_RELAYS,T_HTML_ATTACH auto
> From: Bowie Bailey [mailto:bowie_bai...@buc.com]
> Sent: Monday, June 14, 2010 5:18 PM
>
> I see now. It's hitting on long messages too. I saw it match the subject
> line
> rather than the body. I'm not quite sure why. It works if you change it to a
> rawbody match.
>
Thanks a lot that solv
12 matches
Mail list logo