Re: Warnings in procmail log
From: "Geoff Soper" <[EMAIL PROTECTED]>
Bart Schaefer wrote:
On 7/8/06, Geoff Soper <[EMAIL PROTECTED]> wrote:
.qmail contains the lines: | true ./Maildir/
Caveat: I don't use qmail, and don't even particularly like qmail,
so what I'm about to say are really educated guesses rather than
definitive answers.
which I've altered to: | true | /usr/bin/procmail -m ./.procmailrc
No, don't use the -m option. Just use
| /usr/bin/procmail
and let procmail figure out where the $HOME/.procmailrc file is on
its own. If you want any options to procmail there at all, you want
the "-d recipient" option (where you'll have to get the value for
"recipient" from qmail somehow, I don't know how).
I think I need to specify the .procmailrc as the .procmailrc file is per
e-mail address, not per user or even system-wide
This only works if the number of email addresses is equal to or fewer
than the number of users. The .procmailrc file must reside in the
user's home directory as "~/.procmailrc". Now you could bend, fold,
and mutilate a generic .procmailrc file into a global "/etc/procmailrc"
file. But you still need a place for Bayes and user_prefs. If you go
to the extent of having SQL based Bayes and user_prefs database then
you can, I believe, break free of this restriction. You still need
the mail spool files for delivery to the individual email addresses.
and in that .procmailrc : DIR="./Maildir/"
What exactly do you think that's accomplishing? If you never refer
to $DIR again anywhere, this is meaningless. If you want to change
directories, assign to MAILDIR. If you are trying to force procmail
to deliver in maildir format, I think what you want is
DEFAULT="$HOME/Maildir/"
I'm not sure about the $HOME part, but DEFAULT should never be a
relative path (never one starting with "./" or with no directory
reference at all).
The recipes (that I didn't quote) refer to $DIR when delivering to that
location or any child folders so I'm happy that this is OK, bear in mind
my only known problem is these errors relating to SpamAssassin, the
.procmailrc filtering side of things works just fine. It may not be the
most elegant set up as I'm not totally sure of what I'm doing but it
appears to work.
Out of addled curiosity what does procmail think is the $HOME when
it is running? Have you ever figured that out?
I've no desire to run different configurations for different users
or addresses, the single configuration is fine, I just want to
solve these errors I'm seeing in the procmail_log file.
Where is this "./.procmailrc" file that you are trying to read with
the -m option? That is, what do you expect the current directory
(./) to be at the time procmail runs?
the .procmailrc file is in /var/qmail/mailnames/domain.tld/test
alongside the .qmail file and the Maildir directory
And you REALLY think "./.procmailrc" points to that file? Off
hand I don't THINK so.
If you really want exactly this same config for all users, then you
should move that ./.procmailrc file (wherever it is) to
/etc/procmailrc (with no dot) and insert DROPPRIVS=yes somewhere
before the recipe that runs spamassassin, probably at the very top of
the file (unless you want all users to write to the same log file as
well). If you later add things to /etc/procmailrc, you'll need to
research whether they belong above or below the DROPPRIVS (below will
usually be safe, but not always correct).
Just to confirm, the .procmailrc file isn't common to all users but the
SA setup is.
All I can say is good luck and quit running procmail as root that way.
{^_^}
Re: set permission? how
From: "Matthias Fuhrmann" <[EMAIL PROTECTED]>
On Sat, 8 Jul 2006, hansje2000 wrote:
I realy tryed evrything on her, but still thate permission errors.
i reinstal it for 5 times now..
read about 100 pages of spammassassin but nothing specialy about settingup
for ussers to find just little pieces.. and did not reale help me out there.
The user spambucket is present on my box.
did 100 times spamd -u spambucket
did 100 times spamc -u spambucket
did 100 times spamass-milter -u spambucket
And still have thate no permision error.
How can i prevent this on the hard way to run as spambucket?
Is there some other command
no, its all invoked by those commands above (spamd/spamc).
have alook in your init script /etc/init.d/spamassassin. the line which
executes spamd looks like:
spamd -u spambucket ... ?
ensure spamd is runing as user spambucket while listing processes using:
ps -ef | grep spamd
if so, have a look in your /etc/mail/spamassassin/local.cf
did you defined things like:
bayes_path /home/spambucket/.spamassassin/bayes
auto_whitelist_path /home/spambucket/.spamassassin/auto-whitelist
hope this helps a bit,
For one thing he never dropped spamd into the daemon mode. So it's
not running when he tries to run spamc, which makes the whole exercise
futile.
The simplest way to run spamd is to take its defaults and run it as
"spamd -d". Then it will be running in the background. Of course, to
stop it you need to send its process a SIGKILL. And there is a
possibility that by now he has something lurking in the background
that needs the SIGKILL treatment. Do all this as root. Don't get
fancy and run as something else until you have its basics working.
Once he has spamd running, one basic process and its children processes,
he can try spamc. I don't remember what it was he was trying to accomplish
with the -u spambucket. But if he wants to test as user spambucket and
the /home/spambucket directory is present then he can copy some sample
messages to "/home/spambucket" and run "su -l spambucket" to get into
that account. Now he can sit and run the simplest instance of spamc,
"spamc < testmessage1" to run spamc against test message 1. Once this
much is working he can study it and start making the changes he wants.
{^_^}
Re: Strange problem
From: "Rick Macdougall" <[EMAIL PROTECTED]>
Hi,
I'm having a strange problem on one of my spamd servers since upgrading
to 3.1.3.
After awhile under heavy load, children are not exiting, ie the log show
BBBIII, and eventually it's all B.
I've started hupping the server every night but I do not have the same
problem on another server.
Server with the problem
Fedora core 4 diskless server
3 gigs of ram (never more than around 1 gig used, no swap)
auth-learn is off
Server without the problem
FreeBSD 4.8
1.5 gigs of ram (and swap)
auth-learn is enabled.
Both servers have exactly the same config except for the auto-learn and
bayes/user prefs are stored in mysql on the FreeBSD server.
Anyone else seeing anything like this ?
I've not seen it but I have a hunch you are seeing a file locking
problem. I think there are notes in the documentation loaded with
SpamAssassin and on the WIKI related to file locking. You might find
your answer there.
{^_^}
.doc only spam
I can see that the .gif only spam filters need to be broadened out
to handle .doc and probably proactively a bunch of other extensions.
{^_^}
Re: Warnings in procmail log
On 7/8/06, Geoff Soper <[EMAIL PROTECTED]> wrote: Bart Schaefer wrote: I think I need to specify the .procmailrc as the .procmailrc file is per e-mail address, not per user or even system-wide I think we've just uncovered a crucial bit of missing information. You're apparently running procmail in some kind of virtual-user environment, where there is no user login name corresponding to the email address being processed. You need to explain these sorts of things up front. All the answers so far have assumed you have a traditional unix/linux type environment where mail is delivered to individual user accounts that have /etc/passwd file entries, separate home directories, etc. So, forget everything that's been said, and let's start over. > Where is this "./.procmailrc" file that you are trying to read with > the -m option? That is, what do you expect the current directory > (./) to be at the time procmail runs? the .procmailrc file is in /var/qmail/mailnames/domain.tld/test alongside the .qmail file and the Maildir directory In that case you need to tell spamassassin to look for its configuration files in that location. There may be a way to finagle the options to "spamassassin" itself to make this work, but the easiest approach is to run spamd: spamd --create-prefs --virtual-config-dir=/var/qmail/mailnames/%d/%u (see "man spamd" for other options you might want to pass, such as "-m" to limit the number of simultaneous processes, etc.). This is a daemon that needs to run as a system service; you may already have an /etc/rc.d/init.d/spamassassin or similar script for managing this service. It depends on your OS and whether you built SA yourself or installed it with some kind of package management tool (other than CPAN). Then in each appropriate .procmailrc file, :0fw * < 256000 | /usr/bin/spamc -u [EMAIL PROTECTED] where you'll need to get the equivalent of "[EMAIL PROTECTED]" for each virtual address from somewhere; I don't know enough about qmail to tell you how, but if it's not in an environment variable, perhaps you can add it to the procmail command line after the ./.procmailrc and then refer to it here as $1. Just to confirm, the .procmailrc file isn't common to all users but the SA setup is. I'm no longer sure I understand what you consider to be "the SA setup."
Re: Warnings in procmail log
From: "Geoff Soper" <[EMAIL PROTECTED]>
jdow wrote:
From: "Geoff Soper" <[EMAIL PROTECTED]>
Hi,
I'm getting the following three warning in my procmail log (machine
name removed, just in case!), I assume I'm missing some configuration
somewhere but don't know where! Can someone advise?
Thanks,
Geoff
[8162] warn: config: cannot write to //.spamassassin/user_prefs: No
such file or directory
[8162] warn: config: failed to create default user preference file
//.spamassassin/user_prefs
[8162] warn: auto-whitelist: open of auto-whitelist file failed:
locker: safe_lock: cannot create tmp lockfile
//.spamassassin/auto-whitelist.lock.<>.8162 for
//.spamassassin/auto-whitelist.lock: No such file or directory
Somehow you have spamassassin's user setup to have a home directory
of "/". Fix that and you'll be happier. This may be in procmail since
that seems to be how you call SA.
Are you intending to run as a global Bayes and rules or are you
intending to run individual rules and Bayes? Discussion below
presumes individual rules and Bayes.
You need "DROPPRIVS=yes" somewhere near the front of your .procmailrc.
Then you need to call spamc. The sum total would look like this below.
Be sure to replace with the actual user or a macro that
is defined as the the user id.:
===8<---
DROPPRIVS=yes
# Other procmail rules to preprocess email before SpamAssassin
# go here.
# Then we run SpamAssassin via spamc. I run it this way because I
# sometimes put additional procmail rules inside the braces, I don't
# scan files larger than 500k, and I do not scan files to any of the
# spamassassin mailing lists.
:0
* < 50
* !^List-Id: .*(spamassassin\.apache.\org)
{
:0 fw: spamassassin.lock
| /usr/bin/spamc -t 150 -u
}
===8<---
The spamc part can be reduced to this at it's simplest:
===8<---
:0 fw: spamassassin.lock
| /usr/bin/spamc -t 150 -u
===8<---
I included the version I use for such educational value as it might
have.
{^_^}
and then...
Bart Schaefer wrote:
> On 7/5/06, jdow <[EMAIL PROTECTED]> wrote:
>> You need "DROPPRIVS=yes" somewhere near the front of your .procmailrc.
>
> No, you don't. By the time the .procmailrc is read, privileges have
> already been dropped. The only place you need DROPPRIVS=yes is in
> /etc/procmailrc in the event that you want to give up privileges
> before the end of that file has been reached.
>
> You should not have an /etc/procmailrc file at all unless you have
> carefully studied what belongs there.
>
I'm afraid this has left me somewhat confused as to what I should do to
solve my problem. Maybe it'll help to give more detail of my setup.
My web server (FC4) runs Plesk and Virtuozzo. Once I've used Plesk to
set up a domain (domain.tld for example) and an e-mail address (test,
for example) at that domain I have a directory along the lines of
/var/qmail/mailnames/domain.tld/test . In this directory I have the
following file structure:
drwx-- 4 popuser popuser 1024 May 24 22:50 .
drwx-- 4 popuser popuser 1024 May 24 22:50 ..
-rw--- 1 popuser popuser 18 May 24 22:50 .qmail
drwx-- 2 popuser popuser 1024 May 24 22:50 @attachments
drwx-- 9 popuser popuser 1024 Jun 1 22:43 Maildir
-rw--- 1 popuser popuser 55 May 24 22:50 user_prefs
.qmail contains the lines:
| true
./Maildir/
which I've altered to:
| true
| /usr/bin/procmail -m ./.procmailrc
and in that .procmailrc :
DIR="./Maildir/"
LOGFILE="./procmail_log"
...
#
# Pipe the mail through spamassassin (replace 'spamassassin' with 'spamc'
# if you use the spamc/spamd combination)
#
# The condition line ensures that only messages smaller than 250 kB
# (250 * 1024 = 256000 bytes) are processed by SpamAssassin. Most spam
# isn't bigger than a few k and working with big messages can bring
# SpamAssassin to its knees.
#
# The lock file ensures that only 1 spamassassin invocation happens
# at 1 time, to keep the load down.
#
:0fw: spamassassin.lock
* < 256000
| /usr/bin/spamassassin
I've no desire to run different configurations for different users or
addresses, the single configuration is fine, I just want to solve these
errors I'm seeing in the procmail_log file.
I'm not an expert in this kind of thing so appreciate any advice!
As far as I can see you are so far off into left field the right
fielder is complaining about you encroaching on the far right side
of HIS territory. I'm completely lost wrt what you are trying to do
in the first place.
Do you want per user Bayes and rules? Do you want global? What user is
qmail running as when it goes through procmail? Are you running inside
a jail?
If "user_prefs" is supposed to be the spamassassin user_prefs file then
you have it in the wrong place. You need a directory ".spamassassin"
with rwx permissions for the popuser for the user_prefs and Bayes files.
I notice there is no ".procmailrc" file in the popuser list above. So
I suspect these are all off someplace else which you are not showing
us. Maybe somebody else can make hea
Re: Warnings in procmail log
Bart Schaefer wrote: On 7/8/06, Geoff Soper <[EMAIL PROTECTED]> wrote: .qmail contains the lines: | true ./Maildir/ Caveat: I don't use qmail, and don't even particularly like qmail, so what I'm about to say are really educated guesses rather than definitive answers. which I've altered to: | true | /usr/bin/procmail -m ./.procmailrc No, don't use the -m option. Just use | /usr/bin/procmail and let procmail figure out where the $HOME/.procmailrc file is on its own. If you want any options to procmail there at all, you want the "-d recipient" option (where you'll have to get the value for "recipient" from qmail somehow, I don't know how). I think I need to specify the .procmailrc as the .procmailrc file is per e-mail address, not per user or even system-wide Incidentally, I have no idea what the purpose of that pipe to true is, and I suspect you should just remove it. I'll err on the side of caution and leave it there! and in that .procmailrc : DIR="./Maildir/" What exactly do you think that's accomplishing? If you never refer to $DIR again anywhere, this is meaningless. If you want to change directories, assign to MAILDIR. If you are trying to force procmail to deliver in maildir format, I think what you want is DEFAULT="$HOME/Maildir/" I'm not sure about the $HOME part, but DEFAULT should never be a relative path (never one starting with "./" or with no directory reference at all). The recipes (that I didn't quote) refer to $DIR when delivering to that location or any child folders so I'm happy that this is OK, bear in mind my only known problem is these errors relating to SpamAssassin, the .procmailrc filtering side of things works just fine. It may not be the most elegant set up as I'm not totally sure of what I'm doing but it appears to work. I've no desire to run different configurations for different users or addresses, the single configuration is fine, I just want to solve these errors I'm seeing in the procmail_log file. Where is this "./.procmailrc" file that you are trying to read with the -m option? That is, what do you expect the current directory (./) to be at the time procmail runs? the .procmailrc file is in /var/qmail/mailnames/domain.tld/test alongside the .qmail file and the Maildir directory If you really want exactly this same config for all users, then you should move that ./.procmailrc file (wherever it is) to /etc/procmailrc (with no dot) and insert DROPPRIVS=yes somewhere before the recipe that runs spamassassin, probably at the very top of the file (unless you want all users to write to the same log file as well). If you later add things to /etc/procmailrc, you'll need to research whether they belong above or below the DROPPRIVS (below will usually be safe, but not always correct). Just to confirm, the .procmailrc file isn't common to all users but the SA setup is. Thanks, Geoff
Re: Warnings in procmail log
On 7/8/06, Geoff Soper <[EMAIL PROTECTED]> wrote: .qmail contains the lines: | true ./Maildir/ Caveat: I don't use qmail, and don't even particularly like qmail, so what I'm about to say are really educated guesses rather than definitive answers. which I've altered to: | true | /usr/bin/procmail -m ./.procmailrc No, don't use the -m option. Just use | /usr/bin/procmail and let procmail figure out where the $HOME/.procmailrc file is on its own. If you want any options to procmail there at all, you want the "-d recipient" option (where you'll have to get the value for "recipient" from qmail somehow, I don't know how). Incidentally, I have no idea what the purpose of that pipe to true is, and I suspect you should just remove it. and in that .procmailrc : DIR="./Maildir/" What exactly do you think that's accomplishing? If you never refer to $DIR again anywhere, this is meaningless. If you want to change directories, assign to MAILDIR. If you are trying to force procmail to deliver in maildir format, I think what you want is DEFAULT="$HOME/Maildir/" I'm not sure about the $HOME part, but DEFAULT should never be a relative path (never one starting with "./" or with no directory reference at all). I've no desire to run different configurations for different users or addresses, the single configuration is fine, I just want to solve these errors I'm seeing in the procmail_log file. Where is this "./.procmailrc" file that you are trying to read with the -m option? That is, what do you expect the current directory (./) to be at the time procmail runs? If you really want exactly this same config for all users, then you should move that ./.procmailrc file (wherever it is) to /etc/procmailrc (with no dot) and insert DROPPRIVS=yes somewhere before the recipe that runs spamassassin, probably at the very top of the file (unless you want all users to write to the same log file as well). If you later add things to /etc/procmailrc, you'll need to research whether they belong above or below the DROPPRIVS (below will usually be safe, but not always correct).
Strange problem
Hi, I'm having a strange problem on one of my spamd servers since upgrading to 3.1.3. After awhile under heavy load, children are not exiting, ie the log show BBBIII, and eventually it's all B. I've started hupping the server every night but I do not have the same problem on another server. Server with the problem Fedora core 4 diskless server 3 gigs of ram (never more than around 1 gig used, no swap) auth-learn is off Server without the problem FreeBSD 4.8 1.5 gigs of ram (and swap) auth-learn is enabled. Both servers have exactly the same config except for the auto-learn and bayes/user prefs are stored in mysql on the FreeBSD server. Anyone else seeing anything like this ? Regards, Rick
Re: set permission? how
On Sat, 8 Jul 2006, hansje2000 wrote: > > I realy tryed evrything on her, but still thate permission errors. > > i reinstal it for 5 times now.. > read about 100 pages of spammassassin but nothing specialy about settingup > for ussers to find just little pieces.. and did not reale help me out there. > > The user spambucket is present on my box. > > did 100 times spamd -u spambucket > did 100 times spamc -u spambucket > did 100 times spamass-milter -u spambucket > And still have thate no permision error. > > How can i prevent this on the hard way to run as spambucket? > > Is there some other command no, its all invoked by those commands above (spamd/spamc). have alook in your init script /etc/init.d/spamassassin. the line which executes spamd looks like: spamd -u spambucket ... ? ensure spamd is runing as user spambucket while listing processes using: ps -ef | grep spamd if so, have a look in your /etc/mail/spamassassin/local.cf did you defined things like: bayes_path /home/spambucket/.spamassassin/bayes auto_whitelist_path /home/spambucket/.spamassassin/auto-whitelist hope this helps a bit, regards, Matthias
Re: percentage of spam getting through
I use spamassassin (last perl version, updated it last week) on a mail server, called from amavisd-new. I've set the $sa_kill_level_deflt to 5.00, if I lower this I get too many false positives. I haven't touched any of the rules. I regularly train the bayesian filter with false negative messages. I'm using local tests only. Claudia Burman Why are you using local tests only? Gary V _ Dont just search. Find. Check out the new MSN Search! http://search.msn.click-url.com/go/onm00200636ave/direct/01/
Re: percentage of spam getting through
Are you using the URIBLs? You should be doing better than that. - Original Message - From: "Claudia Burman" <[EMAIL PROTECTED]> To: Sent: Saturday, July 08, 2006 8:59 AM Subject: percentage of spam getting through | Hi, I'm new to the list and I guess this question was asked many times, | but I can't find this in the archives. | I use spamassassin (last perl version, updated it last week) on a mail | server, called from amavisd-new. I've set the $sa_kill_level_deflt to | 5.00, if I lower this I get too many false positives. | I haven't touched any of the rules. I regularly train the bayesian filter | with false negative messages. I'm using local tests only. | My statistics show that only 60-65% of the spam messages are correctly | tagged as spam. I would like to hear from another spamassassin users if | they get similar figures. | | Thanks. Sorry for my English. | | Claudia Burman | El Bolson, Patagonia Argentina | |
Re: percentage of spam getting through
I haven't touched any of the rules. I regularly train the bayesian filter with false negative messages. I'm using local tests only. My statistics show that only 60-65% of the spam messages are correctly tagged as spam. I would like to hear from another spamassassin users if they get similar figures. I think many users if not most users are using some extra rules and also running at least some net tests. Using some of the rules from www.rulesemporium.com can help quite a lot with the newrt image-only spams that are becoming quite popular. Using some of the assorted uribl type of net tests can also help a very large amount. I think most SA users that have net tests enabled and some SARE (rules emporium) rules are probably getting well over 90% spam catch rates with very few if any false positives. IKn addition to training Bayes with FN messages, you should regularly feed it a little ham and a little spam, just to keep reminding it what each one looks like. Training on FNs will improve the hits on these, but won't necessarily improve how Bayes does in general on spam. Almost all of your spam should be hitting Bayes_80 or better. If not, feed it some more representative spam. Also, most of your ham should be very close to bayes_00. Loren
percentage of spam getting through
Hi, I'm new to the list and I guess this question was asked many times, but I can't find this in the archives. I use spamassassin (last perl version, updated it last week) on a mail server, called from amavisd-new. I've set the $sa_kill_level_deflt to 5.00, if I lower this I get too many false positives. I haven't touched any of the rules. I regularly train the bayesian filter with false negative messages. I'm using local tests only. My statistics show that only 60-65% of the spam messages are correctly tagged as spam. I would like to hear from another spamassassin users if they get similar figures. Thanks. Sorry for my English. Claudia Burman El Bolson, Patagonia Argentina
Re: Warnings in procmail log
jdow wrote:
From: "Geoff Soper" <[EMAIL PROTECTED]>
Hi,
I'm getting the following three warning in my procmail log (machine
name removed, just in case!), I assume I'm missing some configuration
somewhere but don't know where! Can someone advise?
Thanks,
Geoff
[8162] warn: config: cannot write to //.spamassassin/user_prefs: No
such file or directory
[8162] warn: config: failed to create default user preference file
//.spamassassin/user_prefs
[8162] warn: auto-whitelist: open of auto-whitelist file failed:
locker: safe_lock: cannot create tmp lockfile
//.spamassassin/auto-whitelist.lock.<>.8162 for
//.spamassassin/auto-whitelist.lock: No such file or directory
Somehow you have spamassassin's user setup to have a home directory
of "/". Fix that and you'll be happier. This may be in procmail since
that seems to be how you call SA.
Are you intending to run as a global Bayes and rules or are you
intending to run individual rules and Bayes? Discussion below
presumes individual rules and Bayes.
You need "DROPPRIVS=yes" somewhere near the front of your .procmailrc.
Then you need to call spamc. The sum total would look like this below.
Be sure to replace with the actual user or a macro that
is defined as the the user id.:
===8<---
DROPPRIVS=yes
# Other procmail rules to preprocess email before SpamAssassin
# go here.
# Then we run SpamAssassin via spamc. I run it this way because I
# sometimes put additional procmail rules inside the braces, I don't
# scan files larger than 500k, and I do not scan files to any of the
# spamassassin mailing lists.
:0
* < 50
* !^List-Id: .*(spamassassin\.apache.\org)
{
:0 fw: spamassassin.lock
| /usr/bin/spamc -t 150 -u
}
===8<---
The spamc part can be reduced to this at it's simplest:
===8<---
:0 fw: spamassassin.lock
| /usr/bin/spamc -t 150 -u
===8<---
I included the version I use for such educational value as it might
have.
{^_^}
and then...
Bart Schaefer wrote:
> On 7/5/06, jdow <[EMAIL PROTECTED]> wrote:
>> You need "DROPPRIVS=yes" somewhere near the front of your .procmailrc.
>
> No, you don't. By the time the .procmailrc is read, privileges have
> already been dropped. The only place you need DROPPRIVS=yes is in
> /etc/procmailrc in the event that you want to give up privileges
> before the end of that file has been reached.
>
> You should not have an /etc/procmailrc file at all unless you have
> carefully studied what belongs there.
>
I'm afraid this has left me somewhat confused as to what I should do to
solve my problem. Maybe it'll help to give more detail of my setup.
My web server (FC4) runs Plesk and Virtuozzo. Once I've used Plesk to
set up a domain (domain.tld for example) and an e-mail address (test,
for example) at that domain I have a directory along the lines of
/var/qmail/mailnames/domain.tld/test . In this directory I have the
following file structure:
drwx-- 4 popuser popuser 1024 May 24 22:50 .
drwx-- 4 popuser popuser 1024 May 24 22:50 ..
-rw--- 1 popuser popuser 18 May 24 22:50 .qmail
drwx-- 2 popuser popuser 1024 May 24 22:50 @attachments
drwx-- 9 popuser popuser 1024 Jun 1 22:43 Maildir
-rw--- 1 popuser popuser 55 May 24 22:50 user_prefs
.qmail contains the lines:
| true
./Maildir/
which I've altered to:
| true
| /usr/bin/procmail -m ./.procmailrc
and in that .procmailrc :
DIR="./Maildir/"
LOGFILE="./procmail_log"
...
#
# Pipe the mail through spamassassin (replace 'spamassassin' with 'spamc'
# if you use the spamc/spamd combination)
#
# The condition line ensures that only messages smaller than 250 kB
# (250 * 1024 = 256000 bytes) are processed by SpamAssassin. Most spam
# isn't bigger than a few k and working with big messages can bring
# SpamAssassin to its knees.
#
# The lock file ensures that only 1 spamassassin invocation happens
# at 1 time, to keep the load down.
#
:0fw: spamassassin.lock
* < 256000
| /usr/bin/spamassassin
I've no desire to run different configurations for different users or
addresses, the single configuration is fine, I just want to solve these
errors I'm seeing in the procmail_log file.
I'm not an expert in this kind of thing so appreciate any advice!
Thanks,
Geoff
RE: RBL lookup error
> -Original Message- > From: John Ackley [mailto:[EMAIL PROTECTED] > Sent: Saturday, July 08, 2006 7:52 AM > To: users@spamassassin.apache.org > Subject: RBL lookup error > > > new to spamassassin > installed three weeks ago v. 3.1.3 on FC5 (domain server) > works great! catches 99+% of spam > > ran without errors but now getting many error messages in log > file like > > 49.187.163.66.bl.spamcop.net: RBL lookup error: Host or > domain name not found. Name service error for > name=149.187.163.66.bl.spamcop.net type=A: Host not found, > try again : 4 Time(s) > Normal internet stuff, unless spamcop's dns servers are under DOS attack. Nothing you can do.
Re: RBL lookup error
From: "John Ackley" <[EMAIL PROTECTED]>
new to spamassassin
installed three weeks ago v. 3.1.3 on FC5 (domain server)
works great! catches 99+% of spam
ran without errors but now getting many error messages in log file like
49.187.163.66.bl.spamcop.net: RBL lookup error: Host or domain name not found. Name
service error for name=149.187.163.66.bl.spamcop.net type=A: Host not found, try again :
4 Time(s)
I assume it is a complaint about a response from spamcop.net
What is the error?
How do I fix?
TIA
What does "host bl.spamcop.net" provide you for an address lookup?
Perhaps your DNS is broken?
{^_^}
RBL lookup error
new to spamassassin installed three weeks ago v. 3.1.3 on FC5 (domain server) works great! catches 99+% of spam ran without errors but now getting many error messages in log file like 49.187.163.66.bl.spamcop.net: RBL lookup error: Host or domain name not found. Name service error for name=149.187.163.66.bl.spamcop.net type=A: Host not found, try again : 4 Time(s) I assume it is a complaint about a response from spamcop.net What is the error? How do I fix? TIA
Re: set permission? how
I realy tryed evrything on her, but still thate permission errors. i reinstal it for 5 times now.. read about 100 pages of spammassassin but nothing specialy about settingup for ussers to find just little pieces.. and did not reale help me out there. The user spambucket is present on my box. did 100 times spamd -u spambucket did 100 times spamc -u spambucket did 100 times spamass-milter -u spambucket And still have thate no permision error. How can i prevent this on the hard way to run as spambucket? Is there some other command MAIL -LOG Jul 8 10:03:07 localhost sendmail[3630]: k68837Os003630: from=<[EMAIL PROTECTED]>, size=2991, class=0, nrcpts=1, msgid=<[EMAIL PROTECTED]>, proto=ESMTP, daemon=MTA, relay=smtp-vbr12.xs4all.nl [194.109.24.32] Jul 8 10:03:07 localhost spamd[3579]: spamd: connection from localhost.localdomain [127.0.0.1] at port 33254 Jul 8 10:03:07 localhost spamd[3579]: mkdir /root/.spamassassin: No permision at /usr/lib/perl5/site_perl/5.8.0/Mail/SpamAssassin.pm line 1486 Jul 8 10:03:07 localhost spamd[3579]: spamd: processing message <[EMAIL PROTECTED]> for root:508 Jul 8 10:03:07 localhost spamd[3579]: mkdir /root/.spamassassin: No permision at /usr/lib/perl5/site_perl/5.8.0/Mail/SpamAssassin.pm line 1486 Jul 8 10:03:07 localhost spamd[3579]: locker: safe_lock: cannot create tmp lockfile /root/.spamassassin/auto-whitelist.lock.ProdecoBoy.3579 for /root/.spamassassin/auto-whitelist.lock: No permision Jul 8 10:03:07 localhost spamd[3579]: auto-whitelist: open of auto-whitelist file failed: locker: safe_lock: cannot create tmp lockfile /root/.spamassassin/auto-whitelist.lock.ProdecoBoy.3579 for /root/.spamassassin/auto-whitelist.lock: No permision Jul 8 10:03:07 localhost spamd[3579]: spamd: identified spam (1001.3/5.0) for root:508 in 0.2 seconds, 3387 bytes. Jul 8 10:03:07 localhost spamd[3579]: spamd: result: Y 1001 - GTUBE,HTML_MESSAGE,MISSING_SUBJECT scantime=0.2,size=3387,user=root,uid=508,required_score=5.0,rhost=localhost.localdomain,raddr=127.0.0.1,rport=33254,mid=<[EMAIL PROTECTED]>,autolearn=no Jul 8 10:03:07 localhost sendmail[3630]: k68837Os003630: Milter add: header: X-Spam-Flag: YES Jul 8 10:03:07 localhost sendmail[3630]: k68837Os003630: Milter add: header: X-Spam-Status: Yes, score=1001.3 required=5.0 tests=GTUBE,HTML_MESSAGE,\n\tMISSING_SUBJECT autolearn=no version=3.1.3 Jul 8 10:03:07 localhost sendmail[3630]: k68837Os003630: Milter add: header: X-Spam-Level: ** Jul 8 10:03:07 localhost sendmail[3630]: k68837Os003630: Milter add: header: X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on ProdecoBoy Jul 8 10:03:07 localhost sendmail[3630]: k68837Os003630: Milter change: header Content-Type: from multipart/alternative;\n\tboundary="=_NextPart_000_001F_01C6A275.B3D76930" to multipart/mixed; boundary="--=_44AF66BB.45CF1F16" Jul 8 10:03:07 localhost sendmail[3630]: k68837Os003630: Milter message: body replaced Jul 8 10:03:08 localhost spamd[3568]: prefork: child states: II Jul 8 10:03:07 localhost sendmail[3633]: k68837Os003630: to=<[EMAIL PROTECTED]>, delay=00:00:00, xdelay=00:00:00, mailer=local, pri=37007, dsn=2.0.0, stat=Sent -- View this message in context: http://www.nabble.com/set-permission--how-tf1903359.html#a5229172 Sent from the SpamAssassin - Users forum at Nabble.com.
Re: reconfigure without restart
Pezhman Lali wrote: > hi > How can I Reconfigure SpamAssassin , with new local.cf 's items, > without kill and run spamd ? For all practical purposes, you can't. The closest you can get is to send spamd a SIGHUP, which is more-or-less the same as restarting it. (ie: spamd's PID may change) Spamd will re-read user_prefs files on a per-message basis, but in order to achieve a reasonable level of efficiency, all of the .pre and .cf files are only read at startup.
