Hello together!
I ´ve got following problem with my spamassassin which I couldn´t solve.
When I use
su vscan -c '/usr/local/bin/sa-learn -D --force-expire --sync'
I got this error message:
[72597] dbg: bayes: token_expiration: SQL error: Deadlock found when trying
to get lock; try
hello everybody,
I apologize to ask an off-topic question, and feel free to point me to
any other resources on the net.
I'm setting up an SMTP server (centos + qmail) on a dell quad core
machine for sending out a periodic newsletter (10 millions a month).
In order to avoid any possible
On 19.09.07 12:07, mizzio wrote:
hello everybody,
I apologize to ask an off-topic question, and feel free to point me to
any other resources on the net.
I'm setting up an SMTP server (centos + qmail) on a dell quad core
machine for sending out a periodic newsletter (10 millions a month).
mizzio wrote:
I'm setting up an SMTP server (centos + qmail) on a dell quad core
machine for sending out a periodic newsletter (10 millions a month).
In order to avoid any possible blacklisting problem, I'm looking for all
the best practices. Right now I've set up:
You need EXPLICIT
Gentlemen, imaging reviewing your daily spambox as I do,
. 1 070918|5.4| :
. 1 070919|5.4|Timmy Strd:* zzz(( :![zzz
. 3 070919|12.8|Nizzle Schzzzi:Nicole Scher goes zzz-less
.1 070919|6.1|Nizzle Szzerzi:
.1 070919|13.2|Niczze Sci:
Thank you (very good reading).
Would you suggest postfix then ?
Thanks
Maurizio
On mer, 2007-09-19 at 12:30 +0200, Matus UHLAR - fantomas wrote:
On 19.09.07 12:07, mizzio wrote:
hello everybody,
I apologize to ask an off-topic question, and feel free to point me to
any other
* mizzio [EMAIL PROTECTED]:
hello everybody,
I apologize to ask an off-topic question, and feel free to point me to
any other resources on the net.
I'm setting up an SMTP server (centos + qmail) on a dell quad core
machine for sending out a periodic newsletter (10 millions a month).
If you don't want to annoy a lot of people your spamming (oops,
newsletter sending) software needs to deal with NDRs back from
recipient's domains and either put their subscription on hold after a
small number of failures or automatically cancel them.
There's nothing worse than mailing lists
* Randal, Phil [EMAIL PROTECTED]:
If you don't want to annoy a lot of people your spamming (oops,
newsletter sending) software needs to deal with NDRs back from
recipient's domains and either put their subscription on hold after a
small number of failures or automatically cancel them.
pennywise wrote:
Hello together!
I ´ve got following problem with my spamassassin which I couldn´t solve.
When I use
su vscan -c '/usr/local/bin/sa-learn -D --force-expire --sync'
I got this error message:
[72597] dbg: bayes: token_expiration: SQL error: Deadlock found when
Ralf Hildebrandt wrote:
* Randal, Phil [EMAIL PROTECTED]:
If you don't want to annoy a lot of people your spamming (oops,
newsletter sending) software needs to deal with NDRs back from
recipient's domains and either put their subscription on hold after a
small number of failures or
jonathan,
so given that amavisd is already daemonized... does this suggest that
there would be minimal gains in moving to spamd called from postfix?
Yes, practically no difference in throughput, possibly even some loss
in throughput due to spamc/spamd being invoked once per recipient,
and
On Wed, 19 Sep 2007, Matt Kettler wrote:
PS.: Ideas welcome for catching the characteristic Subject of
those spams, which look like 'just random tty line noise'!
Something like this might be a first shot:
header NO_ALPHA_SUBJECT Subject !~ /[a-zA-Z0-9]/
I've seen some of those.
On Wed, 19 Sep 2007, mizzio wrote:
I'm setting up an SMTP server (centos + qmail) on a dell quad core
machine for sending out a periodic newsletter (10 millions a
month).
In order to avoid any possible blacklisting problem, I'm looking
for all the best practices.
As others have said,
Kris Deugau wrote:
Ralf Hildebrandt wrote:
* Randal, Phil [EMAIL PROTECTED]:
If you don't want to annoy a lot of people your spamming (oops,
newsletter sending) software needs to deal with NDRs back from
recipient's domains and either put their subscription on hold after
a small number of
Hi,
I'm updating SA exploring/cleaning Bayes DBs on a slighty 'dusty' box.
after update to latest SA 32x-branch, --lint is OK.
but, currently, i get:
sa-learn --force-expire -D
...
[19416] dbg: bayes: found bayes db version 3
[19416] dbg: bayes: opportunistic call
On Wed, 2007-09-19 at 00:54 -0400, Matt Kettler wrote:
Chr. v. Stuckrad wrote:
Seemingly our spamc (3.1.9, not yet 3.2.*) can not
transfer a special kind of current spam to a remote
spamd. Those Mails always produce '0/0' instead
of usable reports.
You can see something like the
Hi,
Thanks.
That Robtex is pretty nice. Saw other info that was
interesting..
ANYWAY, it doesn't look like my server is in the lists,
BUT..The IP I send from (RR.COM) is blacklisted here :
dnsbl.sorbs.net
dul.dnsbl.sorbs.net
dynablock.njabl.org
* mizzio [EMAIL PROTECTED]:
hello everybody,
I apologize to ask an off-topic question, and feel free to point me to
any other resources on the net.
I'm setting up an SMTP server (centos + qmail) on a dell quad core
machine for sending out a periodic newsletter (10 millions a
I have an extremely confusing SPF_FAIL issue that I have been looking up for
around 3 hours now trying to figure out. My current setup is a single server
that does everything mail related all from the same box. SMTP, POP, IMAP,
MX, SpamAssassin, ClamAV, everything mail-related is all done on the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[This question may be more appropriate for the dev-list, please move as
required]
Hi list,
When I originally wrote the experimental ASN plugin (since then
SpamAssassin-ized and improved by the dev team), my impression was that
headers added by an
Tuc at T-B-O-H.NET wrote:
ANYWAY, it doesn't look like my server is in the lists,
BUT..The IP I send from (RR.COM) is blacklisted here :
dul.dnsbl.sorbs.net
dynablock.njabl.org
These are not really blacklists but are a list of dynamic IP
addresses. Many sites will not accept mail
Tuc at T-B-O-H.NET wrote:
dynablock.njabl.org
Oh, and this one is obsolete.
http://njabl.org/dynablock.html
Bob
if I recall correctly, most of the code works fine without using
DNS; it's just that most of the code currently *using* it works
with DNS.
--j.
Giampaolo Tomassoni writes:
Dears,
my belief was that the Async support in SA was somehow of general-purpose
type.
I see instead that most code
if I recall correctly, most of the code works fine without using
DNS; it's just that most of the code currently *using* it works
with DNS.
Almost. One of the biggest problems I see is that one can't register a
socket with AsyncLoop.pm. Thereby, when DNS lookups are finished, the whole
loop
On Wed, Sep 19, 2007 at 03:23:50PM -0600, Mr. Gus wrote:
The file bayes_seen has grown in size to 256GB! (274992939008)
How do I cap the size limit of this file? I want to have it not grow larger
then say 800mb at the most!
You need to expire old bayes tokens. The limit is set not as a
On Wed, Sep 19, 2007 at 02:11:19PM -0700, mfahey wrote:
SpamAssassin-3.2.0
Freebsd6.2
The file bayes_seen has grown in size to 256GB! (274992939008)
How do I cap the size limit of this file? I want to have it not grow larger
then say 800mb at the most!
You need to expire old bayes
On Wed, 19 Sep 2007 at 15:23 -0600, [EMAIL PROTECTED] confabulated:
On Wed, Sep 19, 2007 at 02:11:19PM -0700, mfahey wrote:
SpamAssassin-3.2.0
Freebsd6.2
The file bayes_seen has grown in size to 256GB! (274992939008)
How do I cap the size limit of this file? I want to have it not grow
SpamAssassin-3.2.0
Freebsd6.2
The file bayes_seen has grown in size to 256GB! (274992939008)
How do I cap the size limit of this file? I want to have it not grow larger
then say 800mb at the most!
Thanks.
--
View this message in context:
Hey all!
Getting this:
Sep 19 15:49:50 vineyardgateway spamd[26422]: Malformed UTF-8 character
(unexpected continuation byte 0xb0, with no preceding start byte) in pattern
match (m//) at /etc/mail/spamassassin/70_sare_specific.cf, rule
SARE_SPEC_REPL_OBFU4, line 1.
A lot today lately. Any
-Messaggio originale-
Da: mfahey [mailto:[EMAIL PROTECTED]
Inviato: mercoledì 19 settembre 2007 23.11
A: users@spamassassin.apache.org
Oggetto: bayes_seen = 256GB
SpamAssassin-3.2.0
Freebsd6.2
The file bayes_seen has grown in size to 256GB! (274992939008)
How do I cap the
Theo and all. I know this topic comes up on occasion, but I am not sure
I've ever seen an explanation as to why the bayes_seen file is not auto
pruned along with the bayes db file. Since tokens expire in the main DB
file, what is the purpose of having a seen file to unlearn tokens which
may have
On Wed, 19 Sep 2007, Karsten Bräckelmann wrote:
How so? Since these mails are killing spamd, what use is it to throw yet
another rule at it?
Well, in the time since I wrote the mail to the list,
I circumvented the problem by prefixing my 'spamc' by
a little 'awk-filter' to get rid of those
mfahey wrote:
SpamAssassin-3.2.0
Freebsd6.2
The file bayes_seen has grown in size to 256GB! (274992939008)
How do I cap the size limit of this file? I want to have it not grow larger
then say 800mb at the most!
Thanks.
You can 'rm' the file or use MySQL for your backend and write a
Dave Koontz wrote:
Theo and all. I know this topic comes up on occasion, but I am not sure
I've ever seen an explanation as to why the bayes_seen file is not auto
pruned along with the bayes db file. Since tokens expire in the main DB
file, what is the purpose of having a seen file to
hi Matthias --
could you open this as a bug in bugzilla? It should definitely be
part of the Bayes tokens, and if it's not, that's a bug.
--j.
Matthias Leisi writes:
[This question may be more appropriate for the dev-list, please move as
required]
Hi list,
When I originally wrote the
Brian S. Meehan wrote:
Hi,
There's the option rewrite_header Subject in the local.cf file, however,
I've been observing when looking through the spam folder that sorting by
subject is more helpful when looking for incorrectly caught emails since
many emails often have the same subject and
-Messaggio originale-
Da: Michael Parker [mailto:[EMAIL PROTECTED]
In order to expire from bayes_seen you have to know that there are no
longer any tokens from a given msg in the bayes_token database. This
is
a hard problem, mapping tokens to msgs, so it wasn't done.
This could
Thanks Michael. I don't see anything in bugzilla, so I am adding that
this to the list. (see Bug 5652)
BTW, the link on the submission page for bug writing guidelines
generates a 404 error. So I will take my best guess here.
My request is below. I'd love to take this on myself, but I am far
where it just 'sits' for awhile -- no errors in logs -- and,
eventually, 'releases' and completes without error.
What are the messages when that happens? It shouldn't just exit.
Here's a recent example,
sa-learn --force-expire -D
...
[19725] dbg: bayes: can't use estimation method
On Wed, Sep 19, 2007 at 05:55:20PM -0400, Dave Koontz wrote:
Theo and all. I know this topic comes up on occasion, but I am not sure
I've ever seen an explanation as to why the bayes_seen file is not auto
pruned along with the bayes db file. Since tokens expire in the main DB
file, what is
On Wed, Sep 19, 2007 at 04:41:46PM -0700, snowcrash+sa wrote:
where it just 'sits' for awhile -- no errors in logs -- and,
eventually, 'releases' and completes without error.
What are the messages when that happens? It shouldn't just exit.
[19725] dbg: bayes: can't use estimation
Yeah, that's the expiry first pass. As it said, it couldn't find a
good atime delta to use for expiry, so it didn't anything.
ok, so it's expected. read on ...
man sa-learn has a large amount of information about how all of this works.
Arguably not in normal-human-english, but, yes.
The
Thanks for all the posts. We are running global bayes filtering. Im gathering
then the only way is to removal bayes* and restart spamd. I've tried
expiring tokens before and it doesnt not reduce the size of bayes_seen. Can
someone post the relevent info
to the dev list, maybe it will get
If tokens are expired from the DB based on time, and assuming *all* tokens
older than some date are expired, wouldn't it be reasonable to prune
bayes_seen to the expiry date after the expiry run?
Of course this assumes bayes_seen has date stamps in the sequential data,
which may well not be
You missed the critical posts. Just manually rm bayes_seen and keep going.
bayes_seen isn't the bayes database.
Loren
- Original Message -
From: mfahey [EMAIL PROTECTED]
To: users@spamassassin.apache.org
Sent: Wednesday, September 19, 2007 7:29 PM
Subject: Re: R: bayes_seen =
46 matches
Mail list logo
