On Fri, Oct 07, 2022 at 10:58:07AM +0200, Matus UHLAR - fantomas wrote:
I have configured my personal user_prefs to process options for extracttext.
so far, spamd complains:
Oct 7 09:29:05 fantomas spamd[26887]: spamd: setuid to uhlar succeeded
Oct 7 09:29:05 fantomas spamd[26887]: config
On Fri, Oct 07, 2022 at 10:58:07AM +0200, Matus UHLAR - fantomas wrote:
> Hello,
>
> I have configured my personal user_prefs to process options for extracttext.
>
> so far, spamd complains:
>
> Oct 7 09:29:05 fantomas spamd[26887]: spamd: setuid to uhlar succeeded
>
Hello,
I have configured my personal user_prefs to process options for extracttext.
so far, spamd complains:
Oct 7 09:29:05 fantomas spamd[26887]: spamd: setuid to uhlar succeeded
Oct 7 09:29:05 fantomas spamd[26887]: config: failed to parse line in
/home/uhlar/.spamassassin/user_prefs
> and -u on spamd is not usefull if user_prefs is needed or enabled
It is if you have virtual users.
or dovecot droppriveleges to not serve daemonsd
as root later, this is very easy to see in top, for apache that there is
ONE apache running as root, but multiple apache not running as root
spamd does the same seen from spamc
and -u on spamd is not usefull if user_prefs is needed or enabled
exactly w
ater, this is very easy to see in top, for apache that there is
ONE apache running as root, but multiple apache not running as root
spamd does the same seen from spamc
and -u on spamd is not usefull if user_prefs is needed or enabled
sted within one
single line of two opposite clear-text options:
"""
-x, --nouser-config, --user-config
Turn off(on) reading of per-user configuration files (user_prefs) from
the user's home directory. The default behaviour is to read per-user
configuration from the user&#
/*
drwxrwx--- 2 wwspamd 4096 11. Sep 11:40 .spamassassin
-rw-rw 1 wwspamd 10387456 27. Aug 14:19
.spamassassin/auto-whitelist
-rw--- 1 spamd spamd6 27. Aug 14:19
.spamassassin/auto-whitelist.mutex
-rw-rw 1 wwspamd 8667 11. Sep 11:40 .spamassassin/user_prefs
ww
4096 11. Sep 11:40 .spamassassin
-rw-rw 1 wwspamd 10387456 27. Aug 14:19 .spamassassin/auto-whitelist
-rw--- 1 spamd spamd6 27. Aug 14:19
.spamassassin/auto-whitelist.mutex
-rw-rw 1 wwspamd 8667 11. Sep 11:40 .spamassassin/user_prefs
ww@tango012 ~ $
2. I nevertheless
Am 09.09.2015 um 15:01 schrieb Matus UHLAR - fantomas:
how do you plug spamassassin into your mail flow? How do you call
spamassassin? mta, mail client ... ?
On 09.09.15 16:11, Marc Richter wrote:
I'm running postfix as my MTA. In it's master.cf there is configured
to pipe my mail through a sc
Marc Richter writes:
> Hi KAM,
>
> why not - spamassassin seems to respect the user_prefs file. Of course
> I'd like to stick ti spamc, but if there is no solution for the
> user_prefs - issue, it fits only half of my needs.
Sorry for jumping in the conversation, I h
I can't disagree as I was answering the why it exists.
What are using user prefs to accomplish because I prefer using sql based prefs?
Regards,
KAM
On September 11, 2015 5:50:43 AM AST, Marc Richter
wrote:
>Hi KAM,
>
>why not - spamassassin seems to respect the user_prefs f
Am 11.09.2015 um 11:35 schrieb Marc Richter:
Guess this means that I have to run "spamassassin" instead of spamc,
don't I?
I do not understand the reason for spamc to exist then
uhm because it does the real work?
in the case below milter -> spamd -> spamc preforkers
[root@mail-gw:~]$ syste
Hi KAM,
why not - spamassassin seems to respect the user_prefs file. Of course
I'd like to stick ti spamc, but if there is no solution for the
user_prefs - issue, it fits only half of my needs.
Best regard,
Marc
Am 11.09.2015 um 11:47 schrieb Kevin A. McGrail:
Spamc exists to save st
Spamc exists to save startup compilation time.
If you have real users and use procmail then spamc will be much faster and pass
along the username.
If you use a glue or have virtual users, you might need logic to call spamc or
spamassassin with a desired username. But for me, I would anticipate
Guess this means that I have to run "spamassassin" instead of spamc,
don't I?
I do not understand the reason for spamc to exist then - but based upon
the conversation result, it seems like the way to go ... hope my host
can handle the load.
Am 10.09.2015 um 12:50 schrieb Marc Richter:
Hi @
Hi RW,
When I issue "spamassassin --test-mode -D" as the user the filter.sh
- runs as, I get this in the long output:
dbg: config: read file /var/lib/spamassassin/.spamassassin/user_prefs
So, it tries to read the user_prefs from the daemon's home, what is
clear, because it c
Hi @ all,
maybe I'm doing it wrong here - I do not insist on being unfailable.
But what's the correct way to do it then?
Best regards,
Marc
Am 10.09.2015 um 01:48 schrieb RW:
On Wed, 9 Sep 2015 14:48:14 -0700
jdow wrote:
On 2015-09-09 13:51, RW wrote:
On Wed, 9 Sep 2015 17:27:54 +0200
Marc
On Wed, 9 Sep 2015 14:48:14 -0700
jdow wrote:
> On 2015-09-09 13:51, RW wrote:
> > On Wed, 9 Sep 2015 17:27:54 +0200
> > Marc Richter wrote:
> >
> >> Hi RW,
> >>
> >>> Do you mean that ww is a unix user? The normal way to do this is
> >>> to run spamd as root and run spamc as the unix user. Passin
On 2015-09-09 13:51, RW wrote:
On Wed, 9 Sep 2015 17:27:54 +0200
Marc Richter wrote:
Hi RW,
Do you mean that ww is a unix user? The normal way to do this is to
run spamd as root and run spamc as the unix user. Passing -u to
spamc is really intended for virtual users, I'm not sure whether it
w
On Wed, 9 Sep 2015 17:27:54 +0200
Marc Richter wrote:
> Hi RW,
>
> > Do you mean that ww is a unix user? The normal way to do this is to
> > run spamd as root and run spamc as the unix user. Passing -u to
> > spamc is really intended for virtual users, I'm not sure whether it
> > works for unix u
3 hours), along with other jobs like sa-learn, sa-update and
sa-compile.
> On 09.09.2015 11:12 Matus wrote:
>
> have you tried running spamassassin -D ? maybe there's somethign
> invalid in SA's configuration or your user_prefs
When I issue "spamassassin --test-mode
Hi RW,
Do you mean that ww is a unix user? The normal way to do this is to run
spamd as root and run spamc as the unix user. Passing -u to spamc is
really intended for virtual users, I'm not sure whether it works for
unix users. Are you sure it worked before?
ww is a unix user, yes. And it wo
Hi Matus,
Am 09.09.2015 um 15:01 schrieb Matus UHLAR - fantomas:
On 09.09.15 13:47, Marc Richter wrote:
Regardless if it's necessary or not, I have done so. It also happens
regularly by cron (all 3 hours), along with other jobs like sa-learn,
sa-update and sa-compile.
reload should be enough,
than once a day?
On 09.09.2015 11:12 Matus wrote:
have you tried running spamassassin -D ? maybe there's somethign
invalid in SA's configuration or your user_prefs
When I issue "spamassassin --test-mode -D" as the user the filter.sh
- runs as, I get this in the long output:
On Wed, 9 Sep 2015 13:47:01 +0200
Marc Richter wrote:
> > On 09.09.2015 11:12 Matus wrote:
> >
> > have you tried running spamassassin -D ? maybe there's somethign
> > invalid in SA's configuration or your user_prefs
>
> When I issue "spamassas
PS:
I just did the following test:
As the user, filter.sh is executed as, I did test the following:
1. /usr/bin/vendor_perl/spamc -x -E -u ww < /tmp/spam
As the user, who owns the user_prefs, I did test the following:
2. /usr/bin/vendor_perl/spamc -x -E < /tmp/spam
3. spamassassin
pamassassin -D ? maybe there's somethign
> invalid in SA's configuration or your user_prefs
When I issue "spamassassin --test-mode -D" as the user the filter.sh -
runs as, I get this in the long output:
dbg: config: read file /var/lib/spamassassin/.spamassassin/user_prefs
So,
On 09.09.15 01:16, jdow wrote:
I presume you restarted spamd, right?
restarting spamd should not be needed for changes in user_prefs, should it?
On 2015-09-08 23:46, Marc Richter wrote:
I'm running SA 3.4.1 with Perl 5.22.0 .
It works quite well, but since a few weeks, it looks li
I presume you restarted spamd, right?
{^_^}
On 2015-09-08 23:46, Marc Richter wrote:
Hi everyone,
I'm running SA 3.4.1 with Perl 5.22.0 .
It works quite well, but since a few weeks, it looks like my user_prefs isn't
taken into account by SA anymore. Let's show this by exam
Hi everyone,
I'm running SA 3.4.1 with Perl 5.22.0 .
It works quite well, but since a few weeks, it looks like my user_prefs
isn't taken into account by SA anymore. Let's show this by example:
There are *lots* of blacklist_from entries in there; one of them is:
On 26.05.15 11:34, Forrest wrote:
Subject: Re: user_prefs custom rules, not matching
On 5/21/15 1:41 PM, Axb wrote:
does this work?
headerLIST_ID_MARKET_EEKList-ID =~ /emarketeerz/
I've tried this, and it doesn't appear to be working. I just
received another message t
eems quite likely that you're putting rules in a file that SA isn't
using, because SOME of these should match. Are you sure that your server
is configured to use SA in a manner that includes looking at the
specific user_prefs file you are trying to use?
I would think that a simple m
On 5/21/15 1:41 PM, Axb wrote:
does this work?
headerLIST_ID_MARKET_EEKList-ID =~ /emarketeerz/
I've tried this, and it doesn't appear to be working. I just received
another message today, here are the headers (sanitized).
I would think that a simple match on "emarketeerz" woul
estingly, SA puts mine /usr/local/perl-5.14.1/etc/mail/spamassassin
But, that doesn't account for the ~/.spamassassin/user_prefs file, which
I presume should be located anyhow, where I have my custom rules. I
compiled SA from source using my own similarly-compiled perl, which is
probably
Thanks a lot!
22.05.2015 15:40, Kevin A. McGrail пишет:
On 5/22/2015 8:24 AM, RW wrote:
On Fri, 22 May 2015 08:13:05 -0400
Kevin A. McGrail wrote:
On 5/22/2015 4:35 AM, Dmitry Baronov wrote:
I use spamassassin with CommuniGatePro cgpsa helper, .
With Spamassassin 3.3.2 I had ability to cust
On 5/22/2015 8:24 AM, RW wrote:
On Fri, 22 May 2015 08:13:05 -0400
Kevin A. McGrail wrote:
On 5/22/2015 4:35 AM, Dmitry Baronov wrote:
I use spamassassin with CommuniGatePro cgpsa helper, .
With Spamassassin 3.3.2 I had ability to customize default values
in local.cf file.
With 3.4.x I lost
On Fri, 22 May 2015 08:13:05 -0400
Kevin A. McGrail wrote:
> On 5/22/2015 4:35 AM, Dmitry Baronov wrote:
> > I use spamassassin with CommuniGatePro cgpsa helper, .
> >
> > With Spamassassin 3.3.2 I had ability to customize default values
> > in local.cf file.
> > With 3.4.x I lost this ability i
On 5/22/2015 4:35 AM, Dmitry Baronov wrote:
I use spamassassin with CommuniGatePro cgpsa helper, .
With Spamassassin 3.3.2 I had ability to customize default values in
local.cf file.
With 3.4.x I lost this ability i can't find again :/
Nothing in 3.4.x has removed any such feature.
I would
s!
I use 3.4.1 freebsd version with compiled rules.
Please, give me advice how I could use local config file to override
downloaded default values?
All my attemps were unsuccessful.
I placed local.cf and user_prefs files in /root/spamassassin
/etc/mail/spamassassin /usr/local/etc/mail/spamassassin
On 21 May 2015, at 17:36, Benny Pedersen wrote:
On May 21, 2015 11:08:28 PM "Bill Cole"
wrote:
On 21 May 2015, at 14:42, Benny Pedersen wrote:
> Note that plus addressing, users can only subscribe, is 2 + valid
in
> mailto: ?
Sure, why not? See RFC's 821, 822, 2821, 2822, 5321, and 5322
On 2015-05-21 16:47, Forrest wrote:
On 5/21/15 5:36 PM, Benny Pedersen wrote:
On May 21, 2015 11:08:28 PM "Bill Cole"
wrote:
On 21 May 2015, at 14:42, Benny Pedersen wrote:
> Note that plus addressing, users can only subscribe, is 2 + valid in
> mailto: ?
Sure, why not? See RFC's 821, 822,
On 5/21/15 5:36 PM, Benny Pedersen wrote:
On May 21, 2015 11:08:28 PM "Bill Cole"
wrote:
On 21 May 2015, at 14:42, Benny Pedersen wrote:
> Note that plus addressing, users can only subscribe, is 2 + valid in
> mailto: ?
Sure, why not? See RFC's 821, 822, 2821, 2822, 5321, and 5322 :)
The
On May 21, 2015 11:08:28 PM "Bill Cole"
wrote:
On 21 May 2015, at 14:42, Benny Pedersen wrote:
> Note that plus addressing, users can only subscribe, is 2 + valid in
> mailto: ?
Sure, why not? See RFC's 821, 822, 2821, 2822, 5321, and 5322 :)
There is nothing special about '+' in an email a
On 21 May 2015, at 14:42, Benny Pedersen wrote:
Note that plus addressing, users can only subscribe, is 2 + valid in
mailto: ?
Sure, why not? See RFC's 821, 822, 2821, 2822, 5321, and 5322 :)
There is nothing special about '+' in an email address in SMTP or in the
email data format. It is on
Note that plus addressing, users can only subscribe, is 2 + valid in mailto: ?
Reject list-id in mta stage, and this template have no unsubscribe links,
what a catcher
to the panel to report the domain.
In any case, I wrote a couple of simple rules in user_prefs that
/should/ match, but they don't. I set the score really high, so it
would get rejected by spamass-milter. Here they are:
header SPAM_MARKETEERS1 To =~/emarketeerz/
describe SPAM_MARKETEERS
I'm having a problem with a spammer who is using Google Groups as a
base. They manage to re-subscribe people, etc., and it's hosted on a
private domain, so I can't get to the panel to report the domain.
In any case, I wrote a couple of simple rules in user_prefs that
/should/
On Thu, 21 May 2015, Dmitry Baronov wrote:
Hello folks!
I use 3.4.1 freebsd version with compiled rules.
Please, give me advice how I could use local config file to override
downloaded default values?
All my attemps were unsuccessful.
I placed local.cf and user_prefs files in /root
Am 21.05.2015 um 15:48 schrieb Dmitry Baronov:
Hello folks!
I use 3.4.1 freebsd version with compiled rules.
Please, give me advice how I could use local config file to override
downloaded default values?
All my attemps were unsuccessful.
I placed local.cf and user_prefs files in /root
Hello folks!
I use 3.4.1 freebsd version with compiled rules.
Please, give me advice how I could use local config file to override
downloaded default values?
All my attemps were unsuccessful.
I placed local.cf and user_prefs files in /root/spamassassin
/etc/mail/spamassassin /usr/local/etc
That worked, many thanks..
Missing @ makes a difference ;)
-RIckH
-Original Message-
From: RW [mailto:rwmailli...@googlemail.com]
Sent: Thursday, March 12, 2015 11:44 AM
To: users@spamassassin.apache.org
Subject: Re: whitelist_from in user_prefs is not being processed.
On Thu, 12 Mar
On March 12, 2015 11:10:13 PM "Rick Hantz \(TirNanOg\)"
wrote:
In my user_prefs file, I have: (see resulting header below)
whitelist_from mailto:*@sailthru.com
read perldoc Mail::SpamAssassin::Conf
note whitelist_from allows forged senders, if possible use whitelist_auth
instaed
Am 12.03.2015 um 23:06 schrieb Rick Hantz (TirNanOg):
In my user_prefs file, I have: (see resulting header below)
whitelist_from mailto:*@sailthru.com
whitelist_from mailto:*@e.washingtonpost.com
Do I also need
whitelist_from mailto:*@*.sailthru.com ?
Return-path:
i guess all that
In my user_prefs file, I have: (see resulting header below)
whitelist_from mailto:*@sailthru.com
whitelist_from mailto:*@e.washingtonpost.com
Do I also need
whitelist_from mailto:*@*.sailthru.com ?
Appreciate all the help.
-RickH
Return-path:
Envelope-to: rickhan
On Thu, 12 Mar 2015 11:23:33 -0700
Rick Hantz \(TirNanOg\) wrote:
>
> However, none of the whitelist seems to get processed. Mail that
> should have a high negative number doesn't and ends up in the spam
> folder.
>
> whitelist_from 23andme.com
> ...
> whitelist_from *.aarp.com
try:
w
distribution whitelist_from can be overridden in a local.cf
file, or
an individual user can override a whitelist_from entry in their own
"user_prefs" file. The specified email address has to match exactly
(although case-insensitively) the address previously
while, the tokens files get corrupt, so I delete them and start
over. (I start getting a lot of spam missed).
To filter most everything, I set the spam level at -1.
I maintain a whitelist in user_prefs, so I can easily start over.
However, none of the whitelist seems to get processed. Mail that
m and start
over. (I start getting a lot of spam missed).
To filter most everything, I set the spam level at -1.
I maintain a whitelist in user_prefs, so I can easily start over.
However, none of the whitelist seems to get processed. Mail that should have
a high negative number doesn't and
On Sat, 7 Mar 2015, Forrest wrote:
whitelist_from_rcvd *@spamcop.net vmx.spamcop.net
whitelist_from_rcvd *@spamcop.net spamcop.net
DKIM_SIGNED,DKIM_VALID,RCVD_IN_DNSWL_MED,SPF_PASS,T_RP_MATCHES_RCVD,URIBL_BLACK,URIBL_DBL_SPAM,URIBL_JP_SURBL,URIBL_SBL_A,URIBL_WS_SURBL
DKIM_VALID and SPF_PASS
On 03/07/2015 08:32 PM, Forrest wrote:
Since upgrading to 3.4, I've been having an annoying problem with
SpamCop mails being (seemingly) randomly bounced and/or miscategorized;
that is, despite being specifically configured in user_prefs and local.cf.
Here's what I've placed
Since upgrading to 3.4, I've been having an annoying problem with
SpamCop mails being (seemingly) randomly bounced and/or miscategorized;
that is, despite being specifically configured in user_prefs and local.cf.
Here's what I've placed in the configs
# spamcop
whit
On 11/21/2014 12:32 PM, Bowie Bailey wrote:
> bayes_path is considered to be an administrator setting and is not
> allowed to be specified in user_prefs.
Ah, that's what I get for grepping through the man page instead of paging
through in order. Thanks very much.
On 11/21/2014 2:51 PM, Starchy Grant wrote:
Hello,
I'm working on a limited test of a global bayes databases on Debian
Wheezy with spamassassin 3.3.2, and trying to set bayes_path in my
user_prefs file. When I add the line
bayes_path /var/spamassassin/bayes_db/bayes
I see the following i
Hello,
I'm working on a limited test of a global bayes databases on Debian
Wheezy with spamassassin 3.3.2, and trying to set bayes_path in my
user_prefs file. When I add the line
bayes_path /var/spamassassin/bayes_db/bayes
I see the following in the logs:
Nov 21 10:58:31 mail2 spamd[
On 08 Nov 2013, at 13:42 , Kris Deugau wrote:
> man Mail::SpamAssassin::Conf and scroll down to the "RULE DEFINITIONS
> AND PRIVILEGED SETTINGS" section.
Oh, well, crap. Yeah, that's not going to happen.
OK, time to come up with another way of doing this...
ZZ
er.. right.
--
"What if your
On 08 Nov 2013, at 13:42 , Kris Deugau wrote:
> If you want to put full rules in user_prefs files, you'll need to set
> allow_user_rules in the main configuration.
>
> man Mail::SpamAssassin::Conf and scroll down to the "RULE DEFINITIONS
> AND PRIVILEGED SETTINGS"
LuKreme wrote:
>
> I would like to add a score in user_prefs based on the To header (I have an
> email that collects several email addresses and I want to add some
> spamishness indicators).
>
> Does the user_prefs understand the same syntax as the local.cf file? And what
&
I would like to add a score in user_prefs based on the To header (I have an
email that collects several email addresses and I want to add some spamishness
indicators).
Does the user_prefs understand the same syntax as the local.cf file? And what
would be the best way to say:
If the to field
On 11/11/2011 10:56 PM, li...@nerdbynature.de wrote:
> On Fri, 11 Nov 2011 at 12:03, Martin Gregorie wrote:
>>> Using "per user" AS configuration by receiving MTA is "tricky",
>>> consider e.g. message to multiple local recipients.
> I don't have that many local users on the system and incoming mai
On Fri, 11 Nov 2011 at 12:03, Martin Gregorie wrote:
> > Using "per user" AS configuration by receiving MTA is "tricky",
> > consider e.g. message to multiple local recipients.
I don't have that many local users on the system and incoming mail is
hardly ever addressed to more than one local user.
On Fri, 11 Nov 2011 at 02:36, David B Funk wrote:
> How are you telling spamc who the user is? For per-user specific
> rules spamc has to know who the user is to go get their rules.
> This is accomplished by one of two methods, either use the '-u username'
Hah! Perfect, thank you! I've added "-u $
On Fri, 2011-11-11 at 10:56 +0100, Andrzej Adam Filip wrote:
> li...@nerdbynature.de wrote:
> > [...]
> > The setup is as follows:
> >
> > * fetchmail fetches mail from a remote server,
> > * delivers to postfix (localhost:25)
> > * Postfix delivers to clamsmtpd (for virus-checking) which passes
li...@nerdbynature.de wrote:
> [...]
> The setup is as follows:
>
> * fetchmail fetches mail from a remote server,
> * delivers to postfix (localhost:25)
> * Postfix delivers to clamsmtpd (for virus-checking) which passes
>the message back to postfix, which in turn
> * passes it to a spama
On Thu, 10 Nov 2011, li...@nerdbynature.de wrote:
Hi there,
my spamd seems to ignore the ~/.spamassassin/user_prefs file.
I've searched the archives about this issue, the closest one[0] I came
across was:
> [...] users can add new rules for their own use in the
> "
Hi there,
my spamd seems to ignore the ~/.spamassassin/user_prefs file.
I've searched the archives about this issue, the closest one[0] I came
across was:
> [...] users can add new rules for their own use in the
> "~/.spamassassin/user_prefs" file, if they like.
> If the same (user) settings work in site-wide config, but not in
> user_prefs, the issue most likely is that the user_prefs are not used
> for some reason.
Key for debugging is to have a sample, and to reproduce the issue by
passing the sample to SA exactly as your mail processing chain
On 9/18/2010 4:57 PM, Chuck Campbell wrote:
> I have SA set up and working (mostly) on my mail machine, however I've put the
> following into my user_prefs:
>
> whitelist_from *...@zyngamail.com
> and
> whitelist_from_rcvd *...@zyngamail.com zyngamail.com
> and
t be
turned off as user settings for that matter.
If the same (user) settings work in site-wide config, but not in
user_prefs, the issue most likely is that the user_prefs are not used
for some reason.
There are some relevant spamd command line options, that might cause
this. And of course, using s
> >
> > Try putting those white-list statements in the global "local.cf" config
> > file (do a --lint check & what ever steps are necessary to restart SA so
> > that it will see the changes) and then test to see if the whitelist works.
>
> Done this in /etc/mail/spamassassin/local.cf
>
> waitin
> > info avaialble to SA so the per-user prefs don't work).
> > Have you checked to make sure that your user_prefs are available/readable
> > to the SA daemon?
>
> How do I test this?
Assuming you're running spamd with standard logging enabled, look at the
spamd l
On Sat, Sep 18, 2010 at 06:46:18PM -0500, Dave Funk wrote:
> On Sat, 18 Sep 2010, Chuck Campbell wrote:
>
> >I have SA set up and working (mostly) on my mail machine, however I've put
> >the
> >following into my user_prefs:
> >
> >whitelist_from *...@zy
On Sat, 2010-09-18 at 18:46 -0500, Dave Funk wrote:
> On Sat, 18 Sep 2010, Chuck Campbell wrote:
> > I have SA set up and working (mostly) on my mail machine, however I've put
> > the
> > following into my user_prefs:
> > I don't see any reference to my
On lør 18 sep 2010 23:26:45 CEST, Karsten Bräckelmann wrote
whitelist_from *...@zyngamail.com
This generally is not a good idea, and it is much better to use the con-
strained variants, whitelist_from_rcvd or whitelist_auth. Besides, it
renders the following entries redundant... ;)
i will vote
On Sat, 18 Sep 2010, Chuck Campbell wrote:
I have SA set up and working (mostly) on my mail machine, however I've put the
following into my user_prefs:
whitelist_from *...@zyngamail.com
and
whitelist_from_rcvd *...@zyngamail.com zyngamail.com
and
whitelist_allows_relays *...@zyngamai
On Sat, 2010-09-18 at 15:57 -0500, Chuck Campbell wrote:
> I have SA set up and working (mostly) on my mail machine, however I've put the
> following into my user_prefs:
>
> whitelist_from *...@zyngamail.com
This generally is not a good idea, and it is much better to use
I have SA set up and working (mostly) on my mail machine, however I've put the
following into my user_prefs:
whitelist_from *...@zyngamail.com
and
whitelist_from_rcvd *...@zyngamail.com zyngamail.com
and
whitelist_allows_relays *...@zyngamail.com
when email comes in from them it is flagg
I installed
postfix-2.6.5
amavis-new-2.6.4
spamassassin-3.3.0
amavis home is /var/spool/amavisd
I create /var/spool/amavisd/.spamassassin (drwx--)
Now I want create in this directory auto-whitelist and user_prefs files.
How can I do?
Thanks
Andrea
27;me'. Postfix does not.
> m...@haggis:~$ grep user_prefs SA-debug.output.txt
> Mar 5 11:32:48.538 [11220] dbg: config: using \
> "/home/me/.spamassassin/user_prefs" for user prefs file
You are seeing pure DEBUG messages there. This will not be outp
On Fri, 2010-03-05 at 11:19 -0600, Ron Johnson wrote:
> On 2010-03-05 10:14, Karsten Bräckelmann wrote:
> > I'd suggest to do it right from the beginning. That is, exclusively use
> > the constraint rcvd or auth whitelisting variants. Also, is there any
> > valid reason you need this to be per-use
Ron Johnson wrote:
>
> My wife and I don't need to white-list the same people.
But if it simplifies the configuration, is there any harm in having
everything on a global whitelist? How often are you likely to receive
spam from someone your wife wanted whitelisted?
--
Bowie
erwise. I
set this up years ago, and only now care about whitelisting.
Definitely looks like SA isn't being run from the individual users's
accounts.
m...@haggis:~$ spamassassin -D --lint 2> SA-debug.output.txt
m...@haggis:~$ grep user_prefs SA-debug.output.txt
Mar 5 11:32:
On 2010-03-05 10:14, Karsten Bräckelmann wrote:
On Thu, 2010-03-04 at 15:41 -0600, Ron Johnson wrote:
On 2010-03-04 15:13, Karsten Bräckelmann wrote:
[snip]
How is SA called?
(Lines manually "continued" for easy reading.)
# grep spam /etc/postfix/master.cf
smtp inet n - n -
On Thu, 2010-03-04 at 15:41 -0600, Ron Johnson wrote:
> On 2010-03-04 15:13, Karsten Bräckelmann wrote:
> > On a related note, the plain whitelist_from without a rcvd or auth
> > constraint is dangerous to use. If possible, always use the constraint
> > ones, and the plain one strictly as a fall-b
d the real problem (if any) goes by unnoticed.
Right. I wanted to get the "simple stuff" working first; then the
more complicated configurations.
This is what my various config files look like:
$ tail -n1 /etc/spamassassin/local.cf
allow_user_rules1
$ cat ~/.spa
etc/spamassassin/local.cf
> allow_user_rules1
>
> $ cat ~/.spamassassin/user_prefs
> headerL_TO_ME ToCc =~ /ron\.l\.johns...@cox\.net/
> describe L_TO_ME Email addressed to me
> score L_TO_ME 0.010
For this, you need allow_u
Hi,
I want my users (it's a small at-home setup of fetchmail, postfix,
SA and courier-imap) to be able to whitelist certain users.
This is what my various config files look like:
$ tail -n1 /etc/spamassassin/local.cf
allow_user_rules1
$ cat ~/.spamassassin/user_
On Fri, 3 Apr 2009, Dennis German wrote:
I have had
required_score 3.97
since 4/1/09 but spamassassin email says
X-Spam-Report:
...
Content analysis details: (18.4 points, 4.0 required)
also MISSING_DATE 3.0 should be 2.97 and
MISSING_MID 3.0 should be 2.97
I h
ideas??
ls -l /var/run/spamd
-rw-r--r-- 1 5 Apr 3 12:02 spamd.pid
Current user_prefs can always be seen at
http://www.real-world-systems.com/mail/user_prefs.html
Thanks
1 - 100 of 273 matches
Mail list logo
