> The theory is probably that they can pump spam through faster if
> they utilize all an ISP's inbound MX machines :)
The theory is that most ISP don't run spam filters on their secondary
MX's because "all" smtp clients will hit the primary first and that
"always" works. The secondaries are only
At 01:42 19/03/2005, Martin Hepworth wrote:
I think the reason is that they think we might trust the secondary MX more
than anything else and therefore let it through without checks.
I don't know about that. I think its more just a matter of the way the bulk
mailing software works. A "normal" SM
Eric A. Hall wrote:
On 3/28/2005 2:07 PM, Daryl C. W. O'Shea wrote:
Better yet, is to not even bother running mail for that account through
SpamAssassin in the first place and instead just pipe it to sa-learn.
No point in filtering mail that you are positive is 100% spam.
except that he wants t
On 3/28/2005 2:07 PM, Daryl C. W. O'Shea wrote:
> Better yet, is to not even bother running mail for that account through
> SpamAssassin in the first place and instead just pipe it to sa-learn.
> No point in filtering mail that you are positive is 100% spam.
except that he wants to blacklist f
Eric A. Hall wrote:
On 3/28/2005 9:30 AM, Matt wrote:
That worked but your right it has no effect on the autolearn=spam. Any idea
how I get it to autolearn all email to a given address as spam?
can you pipe incoming mail for that account to sa-learn?
Even if you were to alter the tflags for the
Steve Prior wrote:
Gene Heskett wrote:
The point being that under those conditions, root doesn't have any
filtering. So, I located that section of code in /usr/bin/spamd, and
commented it out. I believe its now working. Locking root out of
using a valuable tool just to try and convince that u
On 3/28/2005 9:30 AM, Matt wrote:
> That worked but your right it has no effect on the autolearn=spam. Any idea
> how I get it to autolearn all email to a given address as spam?
can you pipe incoming mail for that account to sa-learn?
--
Eric A. Hallhtt
Hi,
I do it about the other way round: my first qmail deliver attempt is this one.
The second half triggers if someone has tagged the mail as spam before (even if
the
local SA would let it through)
Wolfgang Hamann
#!/bin/sh
if /usr/bin/spamc -c ; then
exit 0
else
exit 99
fi
if
Gene Heskett wrote:
The point being that under those conditions, root doesn't have any
filtering. So, I located that section of code in /usr/bin/spamd, and
commented it out. I believe its now working. Locking root out of
using a valuable tool just to try and convince that user not to run
as
On Thursday 24 March 2005 19:36, Gene Heskett wrote:
>On Thursday 24 March 2005 13:58, [EMAIL PROTECTED] wrote:
>>SA does not allow running it as 'root' user. It is considered a
>> security risk. SA files also should not be in 'root' user folder.
>> Should be in something like /var/filter/.spamassa
Scott Haneda wrote:
>I have been told SA can run as a standalone MTA, if that is the case, this
>is good news. If not, can someone point me to links that would help me with
>this install. I just barely know postfix, and this is all going to happen
>on OS X 10.3 client, so hopefully someone who h
On Thursday 24 March 2005 19:36, Gene Heskett wrote:
>On Thursday 24 March 2005 13:58, [EMAIL PROTECTED] wrote:
>>SA does not allow running it as 'root' user. It is considered a
>> security risk. SA files also should not be in 'root' user folder.
>> Should be in something like /var/filter/.spamassa
Here's how I'd do it:
You need one more peice to your puzzle: maildrop.
http://www.courier-mta.org/maildrop/
install maildrop then create your .qmail and .mailfilter files:
[EMAIL PROTECTED]:~$ cat .qmail
| spamassassin | /var/qmail/bin/preline /usr/local/bin/maildrop
[EMAIL PROTECTED]:~$ cat .
Chris Santerre <[EMAIL PROTECTED]>
wrote on 03/28/2005 10:44:41 AM:
>
>
> >-Original Message-
> >From: jdow [mailto:[EMAIL PROTECTED]
> >Sent: Friday, March 25, 2005 6:29 AM
> >To: users@spamassassin.apache.org
> >Subject: SARE suggestion
> >
> >
> >It seems there are a lot of anti-spam
>-Original Message-
>From: jdow [mailto:[EMAIL PROTECTED]
>Sent: Friday, March 25, 2005 6:29 AM
>To: users@spamassassin.apache.org
>Subject: SARE suggestion
>
>
>It seems there are a lot of anti-spam headers which if they are seen
>on incoming email is a fairly good indication that the me
I'm having issues rewriting mail.
In the case that spam has been found, the message rewrites fine.
In the case of real mail, I want the SA headers inserted, but it seems
that if I rewrite_mail on non-spam, the message loses all headers
(except SA headers) and improperly formats the message text
I have compiled the spamassassin and a qmail with Maildir working ...
How I have to do to enable the spamassassin to 1 mailbox to test it ? ?
Thanx in advance
Using a script and a crontab. That's about as automatic as you can get.
For example, we have several account aliases that we have intentionally
signed up on the remove lists and they all end up in a user account
called spam. There will never be any legitimate email going to this
account. So eve
That worked but your right it has no effect on the autolearn=spam. Any idea
how I get it to autolearn all email to a given address as spam?
Matt
score USER_IN_BLACKLIST_TO 100.0
or whatever score you want
Dunno if the bayes auto-learner works with blacklist_to rules; it doesn't
work with some wh
Okay... When it comes down to it, this question is a shell question... BUT! I'm
asking it here only because there may be a better way to do this than what I'm
thinking...
Spamassassin 3.0.1
Linux 2.4.20 (Slackware)
Using spamc/spamd -d -L -u alias
Using Qmail for my MTA
When spammers fish for ema
> After the scripts download the rules and try to merge them I get this error.
>
> >Lint output: config: SpamAssassin failed to parse line, skipping:
> >rewrite_subject 0
> >lint: 1 issues detected. please rerun with debug enabled for more
> >information.
To solve this remove from your rules fil
21 matches
Mail list logo
