I'm running ISPconfig 2.2.16 on a Debian 3.1 server. The spam filter is working fine for local delivery, but when I use the forward option and keep a copy on the server, the copy on the server gets a spam subject, but the forwarded message doesn't. Is there a way to use the spam filter on forwarded messages? thanks.
Spam scanning can not be enabled in 2.2.16 for forwarded messages, because the forwarding is done before procmail (and the mail scanning scripts) are invoked in the receiving process.
It can be implemented if the mails were forwarded by a procmail recipe and not in the forwrad file as it is done in the ISPConfig development branch (2.3.2).
For 2 months now I'm testing ISPconfig on a Mandriva system with a lot of problems. A few days ago I switched to Debian and finally setup a working system. Do I really have to look for another control panel?
Do you mean that it will be possible with ISPConfig 2.3.2? If so, when will there be a stable release? I'm installing VHCS on a new Debian system. Maybe that will solve my problem but I like to stay with ISPConfig.
IT IS possible with ISPConfig 2.3.2, There are no known bugs in 2.3.2. Maybe it will solve problems or it will create new problems. VHCS seems not to be under active development anymore. The last update on sourceforge.net is from january 2006.
I've been doing some quick tests on a live server with 2.3.2 It's buggy, but after all, it's not a stable version. Spam mails still don't get forwarded. Maybe in a next release. I can always setup a local testserver if you like.
Sure, but in this release you can simply enable this by changing the file /root/ispconfig/isp/conf/procmailrc.master from: Code: {MAILDIR_COMMENT}MAILDIR=$HOME/Maildir/ {MAILDIR_COMMENT}DEFAULT=$MAILDIR {MAILDIR_COMMENT}ORGMAIL=$MAILDIR {QUOTA} INCLUDERC={PMDIR}/.mailsize.rc {FORWARD_NO_SCAN} {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 {FORWARD} {AUTORESPONDER_COMMENT}INCLUDERC={PMDIR}/.autoresponder.rc to: 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 {FORWARD_NO_SCAN} {FORWARD} {AUTORESPONDER_COMMENT}INCLUDERC={PMDIR}/.autoresponder.rc Every new or updated email account will now scan forwarded emails for spam.
Thanks for your reply. I can see this option on my testserver too so I guess this is going to work. On my liveserver however I prefer a stable version. Soon I hope.
I was able to install VHCS Pro 2.4.7.1 and do some quick tests. This software is nothing for me. But what a nice interface! I sure like to have such interface on a ISPConfig system.
Indeed this way all forward mails that are spam have a rewritten subject. But all mails go first to [email protected]ldomain. Is this normal? With a lot of mails what about overhead?
The emails are not send to admispconfig@localhost, the emails to the admispconfig account are statistic emails and contain just the size of the original email in bytes.
I see. Thanks. Since I need this option I'm about to use 2.3.2-dev in a production system but I don't feel good about it.
I would also like to see the actual dev branch released, but actually I persoally think it has not been enough tested. It's Sad but it's seem that very few people use it. So please if you found a bug please report it.
I will only use 2.3.2-dev to forward mails. I can report bugs but have no idea where. I can't post on the Developers' Forum.