https://issues.apache.org/SpamAssassin/show_bug.cgi?id=7063
--- Comment #44 from Philip Prindeville ---
(In reply to Steadramon from comment #43)
> Seen https://issues.apache.org/SpamAssassin/show_bug.cgi?id=7068
Yeah, 7068 should catch this.
I run it with a threshold of 0.05 (5%).
--
You are
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=7063
--- Comment #43 from Steadramon ---
Seen https://issues.apache.org/SpamAssassin/show_bug.cgi?id=7068
--
You are receiving this mail because:
You are the assignee for the bug.
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=7063
paul.st...@gmail.com changed:
What|Removed |Added
CC||paul.st...@gmail.com
---
On 21. jul. 2014 17.10.49 CEST, "Kevin A. McGrail" wrote:
>a call with a umask of 0700:
>
> mkdir( $tmphome, 0700 ) or die "spamd: cannot create $tmphome: $!";
> mkdir( $tmpsadir, 0700 ) or die "spamd: cannot create $tmpsadir: $!";
>
>I would start looking at things like that to change the uma
On 7/21/2014 5:09 AM, Jan Hejl wrote:
That's what I plan to do, but i'd like to ask where to start? By
modifying spamd you mean source code modifications?
I don't know what temp files you are referring to but spamd clearly has
a call with a umask of 0700:
mkdir( $tmphome, 0700 ) or die "spa
On Mon, 21 Jul 2014, Jan Hejl wrote:
The other daemon is the biggest evil ever. Proprietary software which cannot
run under different user because it's hardcoded :(
The user name may be hardcoded but the user ID can't be. You could
potentially edit /etc/passwd and set the user ID for the prop
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6797
Michael Orlitzky changed:
What|Removed |Added
CC||mich...@orlitzky.com
--- Com
The other daemon is the biggest evil ever. Proprietary software which
cannot run under different user because it's hardcoded :(
Dne 21.7.2014 11:18, Matthias Leisi napsal(a):
The lesser evil is to start the other daemon as the same user as spamd
(assuming that the other daemon does not need yet
The lesser evil is to start the other daemon as the same user as spamd
(assuming that the other daemon does not need yet another set of
permissions which can not be solved through eg simple group
memberships).
-- Matthias
On Mon, Jul 21, 2014 at 11:09 AM, Jan Hejl wrote:
> That's what I plan to
That's what I plan to do, but i'd like to ask where to start? By
modifying spamd you mean source code modifications?
Thanks
Jan
Dne 19.7.2014 15:21, Kevin A. McGrail napsal(a):
You will need to modify spamd to us 440 and put both users in the same
group is my best guess.
Regards,
KAM
Jan Hej
SpamAssassin version 3.3.0 has not had a rule update since 2014-07-13.
SpamAssassin version 3.3.1 has not had a rule update since 2014-07-13.
SpamAssassin version 3.3.2 has not had a rule update since 2014-07-13.
20140720: Spam or ham is below threshold of 150,000:
http://ruleqa.spamassassin.or
11 matches
Mail list logo
