Hi Guys,
Firstly, many thanks for all your replies.
I've now made some changes to my spamd conf file (/etc/conf.d/spamd) based
on the replies given.
This is what it looks like now:
==
SPAMD_OPTS=-m 6 -H -u mail -D --timeout-child=60
# spamd stores its pid in this file. If you use the
On Thu, 1 Apr 2010, Keith De Souza wrote:
I've now made some changes to my spamd conf file (/etc/conf.d/spamd) based
on the replies given.
This is what it looks like now:
==
SPAMD_OPTS=-m 6 -H -u mail -D --timeout-child=60
You don't need -D (debugging output) unless you're actively
On Thu, 1 Apr 2010, Phill Edwards wrote:
actually posting to the right place! Is this the official spamassassin
mailing list?
Your own spam filter might be eating a lot of the messages?
Try setting a rule to score -100 on mail received from apache.org...
- C
I'm trying to create a RPM for my Fedora 10 system and have encountered a
problem.
I run the command: rpmbuild -tb Mail-SpamAssassin-3.2.5.tar.gz
It seems to run OK until this point ...
--
Requires(post): /bin/sh
Requires(preun): /bin/sh
Requires(postun): /bin/sh
Requires: /bin/sh
Greetings, again.
spamassassin --lint runs clean.
I re-entered the line by hand and deleted the original so that shouldn't be an
issue.
I also reviewed the configuration file location list and there are no other
local.cf files or user_prefs files in the list of directories.
Thanx!
-Michael
Since upgrading to the new spamassassin, I'm seeing the following two
log entries related to cleanup of child PIDs:
1. Apr 1 08:26:38 spamd2 spamd[396]: spamd: handled cleanup of child
pid [31720] due to SIGCHLD: INTERRUPTED, signal 2 (0002)
2. Mar 28 18:00:15 spamd2 spamd[17562]: spamd:
On Thu, 2010-04-01 at 11:52 -0400, Micah Anderson wrote:
Since upgrading to the new spamassassin, I'm seeing the following two
log entries related to cleanup of child PIDs:
1. Apr 1 08:26:38 spamd2 spamd[396]: spamd: handled cleanup of child
pid [31720] due to SIGCHLD: INTERRUPTED, signal 2
I installed postfix, amavisd, spamassassin and clamav
I don't understand when I must comment/uncomment the line SAUPDATE=YES in
the file /etc/sysconfig/sa-update.
Can you help me?
Thanks
Andrea
On 2010-03-30 01:29, Brent Kennedy wrote:
Graylisting does work.
Jonas Eckerman wrote:
I know it works. That's why I said I like it because it stops spam.
Been using my own implementation for years.
For what it's worth, I reconfigured my greylisting relay from a
blanket delay to delaying
Adam Katz wrote:
matching p0f's results with the (perl-compatible) regular expression
/Windows (?:XP|2000(?!SP4)|Vista)/
will safely block only desktops.
Oops, that lost a space after the 2000 part. That should read:
/Windows (?:XP|2000 (?!SP4)|Vista)/
Also note that p0f is currently
Adam Katz wrote:
For what it's worth, I reconfigured my greylisting relay from a
blanket delay to delaying only spamcop neighbors, anything that hits a
DNSBL, and any Windows *desktop* (using p0f).
The move reduced the fatal delay of 80-90% of my incoming mail down to
64%, which is pretty
On 2010/04/01 11:38 AM, Michael Weber wrote:
spamassassin --lint runs clean.
I re-entered the line by hand and deleted the original so that shouldn't be an
issue.
I also reviewed the configuration file location list and there are no other
local.cf files or user_prefs files in the list of
For what it's worth, I reconfigured my greylisting relay from a
blanket delay to delaying only spamcop neighbors, anything that hits a
DNSBL, and any Windows *desktop* (using p0f).
The move reduced the fatal delay of 80-90% of my incoming mail down to
64%, which is pretty reasonable given
Ned Slider wrote:
Some implementations, postgrey for example, keep a whitelist of
servers known to retry, so once a small number of mails (3 by
default iirc) have been successfully delivered from a given server
(or servers in the same /24 subnet), it is auto-whitelisted on the
basis that
I tried all the things that were mentioned without any luck.
So, I got out my sledgehammer.
I removed SA from my system and deleted every SA directory, reinstalled 3.3.1
from the RPM's I had just created, ran sa-update, and copied over the old
local.cf file.
It now works.
I'm not sure where
Matt wrote:
I wrote a perl script that whitelists any servers from greylisting for
6 months that send a message that scores less then 1 by spamassassin.
If it later sends a message that scores greater then 5 it is removed
from the whitelist. Works great. After having a few months to learn
On 4/1/2010 11:38 AM, Michael Weber wrote:
eetings, again.
spamassassin --lint runs clean.
I re-entered the line by hand and deleted the original so that shouldn't be
an issue.
I also reviewed the configuration file location list and there are no other
local.cf files or user_prefs files
17 matches
Mail list logo
