Re: [vchkpw] Spamassassin: i wish..
Cristiano Deana wrote: Now spam threshold is hardcoded with --enable-spam-threshold=15 shouldn't be better to put it in vlimits.default? I think this should be made an option, if it is not set, look for vlimits.default, if it is set, then use it hard coded, i prefer that as i dont want vdelivermail to open files each time it runs, which can be a lot of times, as i get a lot of mail, id rather have it hard coded. X-Istence
Re: [vchkpw] Spamassassin: i wish..
Il giorno Friday 12 March 2004 12:53, X-Istence mi scriveva: Now spam threshold is hardcoded with --enable-spam-threshold=15 shouldn't be better to put it in vlimits.default? I think this should be made an option, if it is not set, look for vlimits.default, if it is set, then use it hard coded, Yes, better. Very well. -- Cristiano Deana - FreeCRIS Ho iniziato a usare FreeBSD perche' m$ usava me. ed e' spiacevole pgp public key: http://freecris.bmm.it/cris.asc in irc su: irc.azzurra.org #freebsd-it
Re: [vchkpw] Spamassassin: i wish..
Is it possible not to hard code the header? CRM114 just like SA can add a header like X-CRM114-Status: SPAM for identified spam emails. If the header is not hard coded, then vpopmail can work with both SA and CRM114 or other spam filters. Thanks, Shouguan Lin - Original Message - From: Ken Jones [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, March 12, 2004 8:26 AM Subject: Re: [vchkpw] Spamassassin: i wish.. On Friday 12 March 2004 6:35 am, Cristiano Deana wrote: Il giorno Friday 12 March 2004 12:53, X-Istence mi scriveva: Now spam threshold is hardcoded with --enable-spam-threshold=15 shouldn't be better to put it in vlimits.default? I think this should be made an option, if it is not set, look for vlimits.default, if it is set, then use it hard coded, Yes, better. Very well. In the patch I have based on the BSD patch, it uses the required_hits in the system global setting, normally in /etc/mail/spamassassin/local.cf and can be overriden by a users .spamassassin/users_pref file. So there is no need for an --enable-spam-threshold option. Spamassassin adds a header X-Spam-Flag: YES if the email goes over the required_hit count. I'm going to try and add the code to the cvs version over the weekend. Ken Jones
Re: [vchkpw] Spamassassin: i wish..
On Fri, 2004-03-12 at 13:01, Shouguan Lin wrote: Is it possible not to hard code the header? CRM114 just like SA can add a header like X-CRM114-Status: SPAM for identified spam emails. If the header is not hard coded, then vpopmail can work with both SA and CRM114 or other spam filters. then this would more likely be a system-wide difference in header. Perhaps being able to set this in config.h or similar would be handy. Unless individual users can change their header setting, then I'm not sure how one would do it, without parsing the spamassassin config file, which would be horribly time consuming and prone to bugs. -Jeremy -- Jeremy Kitchen Systems Administrator [EMAIL PROTECTED] Kitchen @ #qmail on EFNet - Join the party! . Inter7 Internet Technologies, Inc. www.inter7.com 866.528.3530 toll free 847.492.0470 int'l 847.492.0632 fax GNUPG key ID: 93BDD6CE
Re: [vchkpw] Spamassassin: i wish..
Ken Jones wrote: On Friday 12 March 2004 6:35 am, Cristiano Deana wrote: Il giorno Friday 12 March 2004 12:53, X-Istence mi scriveva: Now spam threshold is hardcoded with --enable-spam-threshold=15 shouldn't be better to put it in vlimits.default? I think this should be made an option, if it is not set, look for vlimits.default, if it is set, then use it hard coded, Yes, better. Very well. In the patch I have based on the BSD patch, it uses the required_hits in the system global setting, normally in /etc/mail/spamassassin/local.cf and can be overriden by a users .spamassassin/users_pref file. So there is no need for an --enable-spam-threshold option. Spamassassin adds a header X-Spam-Flag: YES if the email goes over the required_hit count. I'm going to try and add the code to the cvs version over the weekend. Ken Jones The BSD code had a hard set limit, with the --enable-spam-threshold=15, which means that anything over 15 would get DELETED, and not just tagged, which is what SA does normally. See, i like to have anything over 4 points tagged, then if for some reason, it is really spam, it will reach the 10 points i set with the enable flag, and vldelivermail will delete it instead of writing it to disk. Its one way i have kept my mail box clean of a lot of crud, as really, i dont want it to be saved if it is just spam. X-Istence
Re: [vchkpw] Spamassassin: i wish..
On Fri, 2004-03-12 at 14:35, X-Istence wrote: Ken Jones wrote: On Friday 12 March 2004 6:35 am, Cristiano Deana wrote: Il giorno Friday 12 March 2004 12:53, X-Istence mi scriveva: Now spam threshold is hardcoded with --enable-spam-threshold=15 shouldn't be better to put it in vlimits.default? I think this should be made an option, if it is not set, look for vlimits.default, if it is set, then use it hard coded, Yes, better. Very well. In the patch I have based on the BSD patch, it uses the required_hits in the system global setting, normally in /etc/mail/spamassassin/local.cf and can be overriden by a users .spamassassin/users_pref file. So there is no need for an --enable-spam-threshold option. Spamassassin adds a header X-Spam-Flag: YES if the email goes over the required_hit count. I'm going to try and add the code to the cvs version over the weekend. Ken Jones The BSD code had a hard set limit, with the --enable-spam-threshold=15, which means that anything over 15 would get DELETED, and not just tagged, which is what SA does normally. does normally? SA is only used for tagging mail. You can send me a GTUBE email and it won't get deleted, even with a score of 1000. See, i like to have anything over 4 points tagged, then if for some reason, it is really spam, it will reach the 10 points i set with the enable flag, and vldelivermail will delete it instead of writing it to disk. Its one way i have kept my mail box clean of a lot of crud, as really, i dont want it to be saved if it is just spam. yea, I like that sort of dual threshold setup as well. Perhaps spamassassin could be made to have dual thresholds and have like a X-REALLY-SPAM: header. I prefer not trying to compare values, but check for 'flags' personally. -Jeremy -- Jeremy Kitchen Systems Administrator [EMAIL PROTECTED] Kitchen @ #qmail on EFNet - Join the party! . Inter7 Internet Technologies, Inc. www.inter7.com 866.528.3530 toll free 847.492.0470 int'l 847.492.0632 fax GNUPG key ID: 93BDD6CE
Re: [vchkpw] Spamassassin: i wish..
Jeremy Kitchen wrote: On Fri, 2004-03-12 at 14:35, X-Istence wrote: Ken Jones wrote: On Friday 12 March 2004 6:35 am, Cristiano Deana wrote: Il giorno Friday 12 March 2004 12:53, X-Istence mi scriveva: Now spam threshold is hardcoded with --enable-spam-threshold=15 shouldn't be better to put it in vlimits.default? I think this should be made an option, if it is not set, look for vlimits.default, if it is set, then use it hard coded, Yes, better. Very well. In the patch I have based on the BSD patch, it uses the required_hits in the system global setting, normally in /etc/mail/spamassassin/local.cf and can be overriden by a users .spamassassin/users_pref file. So there is no need for an --enable-spam-threshold option. Spamassassin adds a header X-Spam-Flag: YES if the email goes over the required_hit count. I'm going to try and add the code to the cvs version over the weekend. Ken Jones The BSD code had a hard set limit, with the --enable-spam-threshold=15, which means that anything over 15 would get DELETED, and not just tagged, which is what SA does normally. does normally? SA is only used for tagging mail. You can send me a GTUBE email and it won't get deleted, even with a score of 1000. See, i like to have anything over 4 points tagged, then if for some reason, it is really spam, it will reach the 10 points i set with the enable flag, and vldelivermail will delete it instead of writing it to disk. Its one way i have kept my mail box clean of a lot of crud, as really, i dont want it to be saved if it is just spam. yea, I like that sort of dual threshold setup as well. Perhaps spamassassin could be made to have dual thresholds and have like a X-REALLY-SPAM: header. I prefer not trying to compare values, but check for 'flags' personally. -Jeremy Well, spamc somehow returns the amount of points it got some how, and that is how it gets deleted. X-Istence
Re: [vchkpw] Spamassassin: i wish..
On Fri, 2004-03-12 at 14:53, X-Istence wrote: The BSD code had a hard set limit, with the --enable-spam-threshold=15, which means that anything over 15 would get DELETED, and not just tagged, which is what SA does normally. does normally? SA is only used for tagging mail. You can send me a GTUBE email and it won't get deleted, even with a score of 1000. Well, spamc somehow returns the amount of points it got some how, and that is how it gets deleted. usually via message header, which can be parsed by a MDA such as maildrop or mailfront. I prefer the on/off switch type of headers though for filtering :) -Jeremy -- Jeremy Kitchen Systems Administrator [EMAIL PROTECTED] Kitchen @ #qmail on EFNet - Join the party! . Inter7 Internet Technologies, Inc. www.inter7.com 866.528.3530 toll free 847.492.0470 int'l 847.492.0632 fax GNUPG key ID: 93BDD6CE
