I'm using spamassassin 3.2.5. Now, I must a whitelist_from containing *@
foo.com in my local.cf.
However, there are still 1 email that has been tagged as spam. In my
understanding, if a domain was in whitelist_from, even if it was tagged as
spam, it will delivered to the recipient. I restart the
On 29.10.08 17:18, Nelson Serafica wrote:
I'm using spamassassin 3.2.5. Now, I must a whitelist_from containing *@
foo.com in my local.cf.
However, there are still 1 email that has been tagged as spam.
Only one? show the headers or upload it somewhere..
In my understanding, if a domain
On Wed, October 29, 2008 10:18, Nelson Serafica wrote:
Is this the right way to whitelist? As I check, when using 3.2.5, this is
the right way of whitelisting a domain.
the more i hear about whitelist_from the more i want to make a bug on it,
whitelist_from should imho newer have being
Nelson Serafica wrote:
I'm using spamassassin 3.2.5. http://3.2.5. Now, I must a
whitelist_from containing [EMAIL PROTECTED] http://foo.com in my local.cf
http://local.cf.
However, there are still 1 email that has been tagged as spam. In my
understanding, if a domain was in whitelist_from,
Benny Pedersen wrote:
On Wed, October 29, 2008 10:18, Nelson Serafica wrote:
Is this the right way to whitelist? As I check, when using 3.2.5, this is
the right way of whitelisting a domain.
the more i hear about whitelist_from the more i want to make a bug on it,
whitelist_from
On Wed, Oct 29, 2008 at 08:24:25AM -0400, Matt Kettler wrote:
There are some messages you can't whitelist in SA using any other method.
(ie: when the sender's server doesn't have reverse DNS).
You can use trusted_networks + ALL_TRUSTED to whitelist. Given of course
that there aren't any
From: Matt Kettler [EMAIL PROTECTED]
Date: Wed, 29 Oct 2008 08:24:25 -0400
Benny Pedersen wrote:
On Wed, October 29, 2008 10:18, Nelson Serafica wrote:
Is this the right way to whitelist? As I check, when using 3.2.5, this is
the right way of whitelisting a
Jeff Mincy [EMAIL PROTECTED] writes:
Agreed. whitelist_from sucks. However, it's there as a method of
last-resort. There are some messages you can't whitelist in SA using any
other method. (ie: when the sender's server doesn't have reverse DNS).
Since whitelist_from is
On Wed, 29 Oct 2008, Matt Kettler wrote:
Benny Pedersen wrote:
the more i hear about whitelist_from the more i want to make a bug on it,
whitelist_from should imho newer have being implemented
Agreed. whitelist_from sucks. However, it's there as a method of
last-resort. There are some
On Wed, 2008-10-29 at 07:52 -0700, John Hardin wrote:
I'm going to suggest again that, given how much pain it causes noobs,
perhaps the use of whitelist_from should generate a lint _warning_ that it
should only be used if no other whitelist method will work...
The thing with noobs and
On Wed, 29 Oct 2008, Karsten Br?ckelmann wrote:
On Wed, 2008-10-29 at 07:52 -0700, John Hardin wrote:
I'm going to suggest again that, given how much pain it causes noobs,
perhaps the use of whitelist_from should generate a lint _warning_ that it
should only be used if no other whitelist
On Wed, 2008-10-29 at 11:15 -0700, John Hardin wrote:
On Wed, 29 Oct 2008, Karsten Bräckelmann wrote:
The thing with noobs and whitelist_from (according to my experience on
this list) appears to be a lack of reading. I got the impression most of
them just blindly whitelist_from their own
On Wed, 2008-10-29 at 07:52 -0700, John Hardin wrote:
I'm going to suggest again that, given how much pain it causes noobs,
perhaps the use of whitelist_from should generate a lint _warning_ that it
should only be used if no other whitelist method will work...
On Wed, 29 Oct 2008, Karsten
Hi,
sendmail 8.13.7, Dan Nelson's spamss-milter 0.3.1, SA 3.1.5.
whitelist_from is ignored entirely, no matter if I put it into local.cf
or some other .cf. If I run SA in test mode (-t), SA honors
whitelist_from.
By digging into milter's source, I see this snipplet from line 911 on (I am not
a
Rainer Sokoll wrote:
Hi,
sendmail 8.13.7, Dan Nelson's spamss-milter 0.3.1, SA 3.1.5.
whitelist_from is ignored entirely, no matter if I put it into local.cf
or some other .cf. If I run SA in test mode (-t), SA honors
whitelist_from.
By digging into milter's source, I see this snipplet from
BTW, some versions of spamass-milter have had problems with recent versions
of SA. I don't know if that has been fixed or not, since I don't use it.
It it hasn't been fixed (at least in the version you have) it may be part of
your problem.
Loren
Greetings!
I have a file, local-names.cf, in the /etc/mail/spamassassin directory
which is a list of addresses I need to whitelist. It seems to work,
except for one sender. Here is the line from the .cf file:
whitelist_from LABONE.com
This never triggers when I receive mail with a
At 10:53 AM 11/10/2004, Michael Weber wrote:
I have a file, local-names.cf, in the /etc/mail/spamassassin directory
which is a list of addresses I need to whitelist. It seems to work,
except for one sender. Here is the line from the .cf file:
whitelist_from LABONE.com
This never
I use :
whitelist_from [EMAIL PROTECTED]
and it works good.
/Hitete
configuration file.
~Randy
* Don't read everything you believe.
-Original Message-
From: Marco van den Bovenkamp [mailto:[EMAIL PROTECTED]
Sent: Monday, October 04, 2004 11:00 AM
To: users@spamassassin.apache.org
Subject: Re: Global Whitelist_from not working
Randy Gibson wrote
rather than using --virtual-config-dir=.
N8
-Original Message-
From: Randy Gibson [mailto:[EMAIL PROTECTED]
Sent: Monday, October 04, 2004 4:31 PM
To: 'Marco van den Bovenkamp'; users@spamassassin.apache.org
Subject: RE: Global Whitelist_from not working
I really like ability to put global
Subject: FW: Global Whitelist_from not working
I think I found an answer to this on my own. It seems as though when spamd
hits the SQL database, it starts ignoring whitelist_from entries in
local.cf.
I noticed in the debug output that it also looks for @GLOBAL in the SQL
database, which I wasn't aware
Randy Gibson wrote:
I'm not using SQL so I don't have a place to put the @GLOBAL. Should I put
it in may local.cf?
If you're using user_pref files, try putting them in there; if the
problem is indeed 'whitelist entries are taken from the last place spamd
looks for them' (as it seems to be),
Since upgrading to SA3.0 user_prefs whitelist_from work
but not local.cf whitelist_from.
Help,
~Randy
* Don't read everything you believe.
At 01:29 PM 10/1/2004, Randy Gibson wrote:
Since upgrading to SA3.0 user_prefs whitelist_from work
but not local.cf whitelist_from.
1) check for syntax errors.. run spamassassin --lint. If SA's parser gets
sufficiently confused it can dump a whole config file.
2) You sure you have the right
PROTECTED]
Sent: Friday, October 01, 2004 11:35 AM
To: Randy Gibson; users@spamassassin.apache.org
Subject: Re: Global Whitelist_from not working
At 01:29 PM 10/1/2004, Randy Gibson wrote:
Since upgrading to SA3.0 user_prefs whitelist_from work
but not local.cf whitelist_from.
1) check for syntax
~Randy
* Don't read everything you believe.
-Original Message-
From: Matt Kettler [mailto:[EMAIL PROTECTED]
Sent: Friday, October 01, 2004 12:35 PM
To: Randy Gibson; users@spamassassin.apache.org
Subject: Re: Global Whitelist_from not working
At 01:29 PM 10/1/2004, Randy Gibson
: Global Whitelist_from not working
I have a similar problem with whitelist_from entries in local.cf. --lint shows
no issues.
What's happening with me is that whitelist_from works for the first few hits,
then it stops working entirely.
the line in local.cf says whitelist_from [EMAIL PROTECTED
28 matches
Mail list logo