-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Run spamassassin with vmail user #200
Conversation
One thing I really dislike about Exim is how it's configuration files are anything but self-explanatory (unless perhaps you've graduated some Exim college or something). For the reference, Debian has a commented out block in it's default configuration, which specifies to run SA as Debian-exim, but then the comment above that block explicitly states that it's not a very good idea. |
Actually, I'd probably default to |
On the other hand, running as nobody (whose home directory does not exist, at least in Debian) prevents spamassassin from creating its settings file. It seems that in Debian, the |
docs/vexim-acl-check-content.conf
Outdated
@@ -31,14 +31,14 @@ | |||
# Reject mails with more than 15 spam-points. This is a system-wide setting and does not respect | |||
# individual user settings! | |||
#deny message = This message has been rejected due to spam. | |||
# spam = maildeliver:true | |||
# spam = vmail:true | |||
# condition = ${if >{$spam_score_int}{150}{true}{false}} | |||
|
|||
# Always add X-Spam-Score and X-Spam-Report headers, using SA system-wide settings | |||
# (user "nobody"), no matter if over threshold or not. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Interestingly, this line mentions 'nobody', this must be a mistake.
But we may want to use 'nobody' in non-packaged vexim versions.
The best is probably to use a dedicated user for this, like debian uses |
I don't think there's point in that. We don't really care about the settings, since we're using settings from the database. I think |
Only the points for each user are in the database. If you use your own rules, modify the points for some rules, add some features (more blacklists, whitelisting of know addresses, ...). All this is done in the spamassassin-folder of the system-user running spamassassin. Some of this could perhaps be moved into a database as well. |
This (rule and score modifications) sounds to me like somewhat more advanced usage. If someone's going this far, they probably know what they're doing and how to set up a new user for Spamassassin. At least IMO. |
And it is needed for the bayes-filter (which must be trained). the problem is more, that we haven't well documented the installation and configuration of spamassassin (compared to http://axel.sjostedt.no/misc/dev/vexim-customizations/). |
Our user name per the installation manual is |
5c81bbf
to
4860339
Compare
I rebased this PR and made some changes. You already added some more comments before. If you think this PR is not required any more, feel free to close this PR. |
Huh, maybe we should put that username in a macro? :) |
What do you mean with macro? |
I meant
in the master file and
here. Not sure how much sense this makes, considering that it is defined in a separate file. What do you think? |
There is only one appearance of it. One huge advantage would be that we can keep all settings at a small spot. This will make updates much easier to implement... |
done :D |
I always run my spamassassin with the
vexim
user. This way all the .spamassassin training files, special configuration, ... is within the home-folder of thevexim
-user.Does it make sense to take the exim-user?