Hi, Ok i have modified the user file .spamassassin.rc Ispconfig changing automatically this file by the master file ?
.spamassassin.rc will be overwritten by ISPConfig. Please copy the template /root/ispconfig/isp/conf/spamassassin.rc.master to the /root/ispconfig/isp/conf/customized_templates directory and modify /root/ispconfig/isp/conf/customized_templates/spamassassin.rc.master instead.
Sure, you can set this in the user settings. You dont have to modify the spamassassin.rc for that as this is a normal buildin function of ispconfig that can be configured per user. Have a look at the spam and antivirus details of the user form and select "Discard" as spam strategy.
Might be a bit late to react on this thread... ;-) But wouldn't it be an idea to add a line to /root/ispconfig/isp/conf/customized_templates/procmailrc.master that says: Code: INCLUDERC={PMDIR}/.myprocmail.rc So every user can adjust his/her .myprocmail.rc to add special filtering rules, e.g. putting spam into a particular folder, etc.
The problem is that the order of the recipes in .procmailrc matters. So the question is in which position do we add this line? Before all others? After all others? Somewhere in between?
If we talk about a user-specific file for handling mails tagged as spam by spamassassin it has to be anywhere after calling .spamassassin.rc, right? IMHO it makes sense to put the call before the autoresponder. What about this: Code: {MAILDIR_COMMENT}MAILDIR=$HOME/Maildir/ {MAILDIR_COMMENT}DEFAULT=$MAILDIR {MAILDIR_COMMENT}ORGMAIL=$MAILDIR {QUOTA} INCLUDERC={PMDIR}/.mailsize.rc {QUOTA_COMMENT}INCLUDERC={PMDIR}/.quota.rc {ANTIVIRUS_COMMENT}INCLUDERC={PMDIR}/.antivirus.rc {MAILSCAN_COMMENT}INCLUDERC={PMDIR}/.local-rules.rc {MAILSCAN_COMMENT}INCLUDERC={PMDIR}/.html-trap.rc {SPAMASSASSIN_COMMENT}INCLUDERC={PMDIR}/.spamassassin.rc INCLUDERC={PMDIR}/.myprocmail.rc {AUTORESPONDER_COMMENT}INCLUDERC={PMDIR}/.autoresponder.rc What would keep us from putting .myprocmail.rc there? Even for filtering rules other than spam-related?