Am 17.09.2014 um 23:51 schrieb RW: > On Wed, 17 Sep 2014 17:24:10 +0200 > Reindl Harald wrote: >> please read my previous message >> >> what i asked is careful considered and exactly what i need >> even if you could reach something similar with other ways >> because the admin backend needs to be understood by other >> persons too and finaly what can be done even by non-tech >> people so they can give answers to endusers >> >> * a few rules with free chosen names and assigned scores >> * the possibility to assign them to senders or sender-domains >> * the possibility to assign them to rcpt or rcpt-domains > > As I told you before you can already do this if you are autogenerating > rules for global configuration - just generate ordinary SpamAssassin > rules
the *how* is the question and you talked about ~/.spamassassin which just don't exist in the environment, i know the same now as i started the thread "it is likely possible somehow" _______________________________________ so *how* create rules itself defining "to_trust_1", "to_trust_2" "to_trust_3", "from_trust_1", "from_trust_2" and assign them a score level? to_trust_1 imagina...@example.com to_trust_1 imagina...@example.com to_trust_2 imagina...@example.com to_trust_3 imagina...@example.com from_trust_1 send...@example.net from_trust_2 send...@example.net from_trust_3 send...@example.net from_trust_3 send...@example.net is it really that hard to understand that i seek for an example _______________________________________ >>> as usal the cronjob builds "local.cf" from a template and that >>> settings >> >> If you are going to autogenerate them into local.cf you can generate >> header rules just as easily. The chief advantage of what you are >> asking for would be for users to set in ~/.spamassassin.
signature.asc
Description: OpenPGP digital signature
