Matt Sergeant wrote:
I'm trying to clean up the code for relaying again. One thing I'm
trying to make easy is that my code for spam scanning (among other
things) does not get applied to relayed mail (because there are things
in there it will cause to get tripped). In order to achieve this I've
Gavin Carr wrote:
The rest of your log seems to be doing the right thing. Here in the
first part, the plugin's clearly recognising this is a new ip
address, but it looks as if the write to the db is failing somehow.
It's not a locking issue - the lock is already held at this point.
So I'm
Matt Sergeant wrote:
FWIW I've had very weird stability issues with db files of all
varieties (even DB_File). Especially under extreme load. I've had much
better success with SQLite.
Matt,
You may have hit on it. The server is under heavy load. It's replacement is
in the works, but until
frank wrote:
(note: I'm the author)
I have to agree with this guy here. Since I wrote the plugin, I've
been in
touch with at least 10 mail admins who were interested in bringing
their
server closer to spec. Course I'm not quite sure what spec is, I'm
just a
hacker who is sick of spam on
Charlie Brady wrote:
On Mon, 22 Mar 2004, Matt Sergeant wrote:
It probably has to be re-written with locking (though I haven't read
the code for the plugin - does it lock?)
Yes, it does lock. I didn't check that it will always remove the lock.
Behaviour probably depends on which form of the
Thanks to all the hard-workers fighting against the spam problem.
I just had to delete the .dbm database because it seemed to be stuck. I did
not see it growing over about a two hour time frame, even though everything
else in the logs looked normal except for the following.
There was one (that I
I implemented this plugin on a test domain, and it seemed great, but after
implementing on my production server, I had too many customers not getting
their email because of the 'no reverse lookup' part. For now I have
remarked that out and still use the badmailfromhost file.
The badmailfromhost
Steph,
Thank you for the reply. I have added your fix into
the plugins/spamassassin file, and that has
stopped the error in the logs. The next problem
is that the sub check_spam_reject is never triggering
and rejecting the spam.
I don't know perl, but I have been dinking with it, but
all I
This is the same error Matt has, but I can fill in some answers regarding my
system.
In brief, the error only occurs on email that exceedes the required hits.
The use_terse_report seems to change the error somewhat.
I am sorry that I am not more of a programmer, but for some reason this
looks
