2014-11-25 13:52, Paul Gardiner wrote:
On 25/11/2014 12:39, Paul Gardiner wrote:
On 25/11/2014 12:13, Axb wrote:
On 11/25/2014 12:50 PM, Paul Gardiner wrote:
I'm using spampd as follows:
spampd --port=10025 --relayhost=127.0.0.1:25 --user=paul
--group=users
--homedir=/home/paul/.spamassassin --tagall --children=5
--maxsize=512
--log-rules-hit
This is hardly a SA issue...
Suggest you check the spampd docs...
http://www.worlddesign.com/Content/rd/mta/spampd/spampd.html
I'd bet you're missing options in your command line...
Ok thanks. I was thinking you guys produce spampd as well because
it was part of the same opensuse package, but I guess it's just
the packager put them together for convenience.
Thanks for your time. It helps a lot just to know that the change
of spampd version is the more likely cause of my problems. Probably
spampd has become more configurable and as you say I need another
option on the command line, although I didn't before.
Actually, just so that I'm sure of what you are saying: is that it
is spampd's responsibility to add X-Spam-Status that I'm now not
seeing or is it spamassassin's responsibility, but spampd is not
requesting it, or is maybe suppressing it in some way.
Glancing at its code, spampd pulls a rewritten message from
SpamAssassin, which should include the X-Spam-Status header field
by default. The X-Spam-Status in this setup is added by the rule:
add_header all Status "_YESNO_, score=_SCORE_ required=_REQD_
tests=_TESTS_ autolearn=_AUTOLEARN_ version=_VERSION_"
in a default SpamAssassin config file 10_default_prefs.cf.
The 'add_header' option can be overruled by your local configuration
(by a 'clear_headers') option. Missing 10_default_prefs.cf would
have the same effect (like being installed in a directory where
SpamAssassin/spampd isn't using), so make sure the spampd is
configuring SpamAssassin to use correct directories for rules.
Mark
