Re: [vchkpw] Spamassin configuration
On Saturday 26 February 2005 10:36 am, Tom Collins wrote: On Feb 25, 2005, at 8:48 PM, Ken Jones wrote: I wrote the code since we needed to support per user spamassasin preferences. At Tom's request I put it in the 5.5 development version. We run a 5.5.1 version production with no problems. I think it's about time we merged this feature into the 5.4 release. Any objections? I plan on rolling it in to 5.4 after my updated vdelivermail has been released and tested further. Since most of the code for the per-user spamassassin filtering is in vdelivermail, I'd rather re-integrate it into my new code. I'd like to get the spamassassin feature in a bit sooner. How about you put the new vdelivermail into cvs for testing. Then we can review and help test the new code while we integrate in the spamassasin code and the variable size increase to fix the quota problem. No need for you to do the extra work when we have available time. Cheers, Ken Jones
Re: [vchkpw] Spamassin configuration
On Saturday 26 February 2005 1:19 pm, Tom wrote: Will this also allow the user to sort spam to a user specified folder as well? Would be nice to cut out a procmail process too. Sounds like a good idea. We just need a place to store that information. Perhaps an optional new file that could specify the users spam folder. I think a relative directory path might be best for migration reasons. Ken Jones
Re: [vchkpw] Spamassin configuration
On Sunday 27 February 2005 2:42 am, Kurt Bigler wrote: on 2/25/05 3:43 PM, Jason S [EMAIL PROTECTED] wrote: On Fri, 25 Feb 2005 16:47:36 -0500 (EST), Ron Dyck [EMAIL PROTECTED] wrote: I'm currently upgrading my mail server and am installing simscan. Simscan claims that there is an option to configure vpopmail with spamassassin option: --enable-spamassassin (http://www.qmailwiki.org/Simscan/Guide) The allows vpopmail user options so individual users can set their own perferences. I can't find this configure option anywhere, but would like to consider it. Does anyone have any information on this? The document you reference tells you what you need to know as far as simscan is concerned. If you want more info about per-user config in spamassassin using sql, check here: http://wiki.apache.org/spamassassin/UsingSQL Excuse the newbie questions, but I've been reading for two solid days now, and I need to start asking some questions before I fall over dead... Does the per-user config require that I switch my qmail+vpopmail authorization from cdb to sql, or is this a separate issue? Separate issue. The spamassassin code is only in the development branch. We are talking about integrating it into the stable branch along with Tom's re-written vdelivermail. The vdelivermail code sure could use a clean re-write. Thanks for taking that on Tom! How are you planning on making per-user options available to individual users for editing? I thought I had read something about using SqWebmail for this but I can not find the message now and can find no other confirmation, and the SqWebmail info does not seem to mention any support for spamassasin. We are almost ready to release a new php web interface that talks to the vpopmail daemon where we planned on adding support for this spamassassin stuff. Hopefully we can release the new code tomorrow. Looking forward to having this feature rolled into 5.4. Me too. And we have time over here to work on it. Ken Jones
[vchkpw] VPopmail Quotas in chkuser
Hello, I've recently installed chkuser and I'm happy with what it does. I'm just wondering if it's possible to get chkuser to check the users quota before accepting the message or not? I see there is an environment variable to set the desired quota (CHKUSER_MBXQUOTA) but what I'd like it to do is to check the quota already set in vpopmail? This is mainly because different accounts on the same domain have different quotas. Any ideas? -- Regards, Scott Clark This email has been sent to you by Scott Clark mail at scottclark dot me dot uk. Visit me @ http://www.scottclark.me.uk/ The views and opinions expressed in this email are the author's own. This email is intended for the exclusive use of the addressee only. If you are not the intended recipient, you should not use the contents nor disclose them to any other person and you should immediately notify the sender and delete the email.
Re: [vchkpw] VPopmail Quotas in chkuser
Scott Clark wrote: Hello, I've recently installed chkuser and I'm happy with what it does. I'm just wondering if it's possible to get chkuser to check the users quota before accepting the message or not? I see there is an environment variable to set the desired quota (CHKUSER_MBXQUOTA) but what I'd like it to do is to check the quota already set in vpopmail? This is mainly because different accounts on the same domain have different quotas. Any ideas? Hi, I could be wrong but my experience shows me that CHKUSER_MBXQUOTA is a percentage of the users total quota. I use CHKUSER_MBXQUOTA=98 here and it works as I expect it too, ie rejecting mail when the users quota is 98% used. Regards, Rick
Re: [vchkpw] Spamassin configuration
On Saturday 26 February 2005 1:19 pm, Tom wrote: Will this also allow the user to sort spam to a user specified folder as well? Would be nice to cut out a procmail process too. Sounds like a good idea. We just need a place to store that information. Perhaps an optional new file that could specify the users spam folder. I think a relative directory path might be best for migration reasons. Ken Jones Suggestion: Maybe even a site-wite compile-time directive? Probably the most common would be something like SPAM under the INBOX for the filtered messages. Having it in SQL would be nice (allow users to configure it if they call the SPAM dir something else in their own hierarchy), although I'm not familiar enough with the innards of the code to know if that would work well... Sounds like a great feature though. We've been wanting to offer something like this to our users for a while, but haven't had the time to develop and interface for it. -Bill * Waveform Technology UNIX Systems Administrator
[vchkpw] Purpose of uid/gid fields in MySQL tables
Hello List, a search of archives didn't turn up anything so ... I was just checking my database and the uid and gid fields are always '0' for users. I checked in vpopuser source and in the function vadduser() from vpopmail.c it seems these are not set during account creation, and are only used in a chown(). following another function vauth_adduser() which updates the db. it doesn't seem to do anything with uid and gid here either when it builds the query string, so are these fields depreciated now and were used in some older version of vpopmail or something? (using 5.4.9) btw everything works fine I'm just curious if what I am seeing is correct or is all my stuff running as root and I'm a dummy. I don't think so though: vpopmail 5.4.9 Current settings --- vpopmail directory = /home/vpopmail uid = 89 gid = 89 [snip] Thank you, brian
Re: [vchkpw] Spamassin configuration
At 12:06 28/2/2005, you wrote: ..snip... How are you planning on making per-user options available to individual users for editing? I thought I had read something about using SqWebmail for this but I can not find the message now and can find no other confirmation, and the SqWebmail info does not seem to mention any support for spamassasin. We are almost ready to release a new php web interface that talks to the vpopmail daemon where we planned on adding support for this spamassassin stuff. Hopefully we can release the new code tomorrow. I don't know the PHP Web Interface written by Ken to change the per-user Spamassassin options but we are using here a Squirrelmail plugin that works smoothly in a Vpopmail system. It uses a C wrapper to write the User Prefs to .spamassassin dirs solving the permissions issue this way. Obviously this could be a useful solution only if you use this Webmail interface. William. -- Esta mensagem foi verificada por Ultralink-Scanner e nenhum virus foi encontrado. Web Server Ultralink: http://www.ultralink.com.br --
Re: [vchkpw] Spamassin configuration
On Fri, 25 Feb 2005, Ken Jones wrote: I wrote the code since we needed to support per user spamassasin preferences. At Tom's request I put it in the 5.5 development version. We run a 5.5.1 version production with no problems. I think it's about time we merged this feature into the 5.4 release. Any objections? How does this impact the current spam assassin option in qmailadmin? We currently use that (it just calls a default maildrop recipe) and use a squirrelmail plugin to set spamass prefs. We have another in-house plugin that can toggle the filtering on/off from within squirrelmail which I'm currently rewriting to use vpopmaild for .qmail manipulation. Is there a blurb somewhere that outlines how this new system works? Thanks, Charles Ken Jones inter7.com
Re: [vchkpw] Spamassin configuration
On Feb 28, 2005, at 2:36 PM, Bill Wichers wrote: Maybe even a site-wite compile-time directive? Probably the most common would be something like SPAM under the INBOX for the filtered messages. Having it in SQL would be nice (allow users to configure it if they call the SPAM dir something else in their own hierarchy), although I'm not familiar enough with the innards of the code to know if that would work well... How about if a mailbox called SPAM exists, put it there, otherwise just drop it in the INBOX? -- Tom Collins - [EMAIL PROTECTED] QmailAdmin: http://qmailadmin.sf.net/ Vpopmail: http://vpopmail.sf.net/ You don't need a laptop to troubleshoot high-speed Internet: sniffter.com
Re: [vchkpw] Spamassin configuration
on 2/28/05 7:06 AM, Ken Jones [EMAIL PROTECTED] wrote: On Sunday 27 February 2005 2:42 am, Kurt Bigler wrote: How are you planning on making per-user options available to individual users for editing? I thought I had read something about using SqWebmail for this but I can not find the message now and can find no other confirmation, and the SqWebmail info does not seem to mention any support for spamassasin. We are almost ready to release a new php web interface that talks to the vpopmail daemon where we planned on adding support for this spamassassin stuff. You mention vpopmail daemon. The only vpopmail daemon I have running is vchkpw, used with qmail-pop3d. I was thinking that vpopmail would only be used to provide the domain/user organization, and a hierarchy in which preferences could be stored. It is my hope that these per-user settings would (if desired) influence rejection by qmail-smtpd (i.e. via $QMAILQUEUE patch) rather than being limited to filtering that can be set up in .qmail files. I'm not sure if that's what you're referring to since I don't yet understand exactly at what levels this functionality interfaces with vpopmail. I'm also wondering about redundancy between this and chkuser, in terms of the need for qmail-smtpd to have access to vpopmail info at the domain/user level. I also haven't installed chkuser yet and don't know how it interfaces with vpopmail. Lacking intimate familiarity it's very hard work to assimilate all this information and so it is vastly helpful to be able to ask these questions. Thanks in advance. Hopefully we can release the new code tomorrow. Wow. Is what you are working on general enough to be used for per-user preferences that outside the spamassassin realm? In other words, if you are solving the problem of authenticating to gain access to per-user preferences, and putting up an interface for that, can you use hooks up front that are general enough to allow extension for other purposes? In my case, I'd like individual users to be able to enable any of several other other custom filtering rules having nothing to do with spamassassin. I don't want users to have to go in more than once place, especially more than one login to achieve this. In other words, I'm looking at a set of simple checkboxes for this purpose, not a general-purpose rule-entry paradigm. I'm sure there will be many others besides me that will want this, sooner or later. Looking forward to having this feature rolled into 5.4. Me too. And we have time over here to work on it. That's great. I can possibly help test. I would serve well as a dummy tester, as long as things are not too rough. -Kurt
Re: [vchkpw] Purpose of uid/gid fields in MySQL tables
On Feb 28, 2005, at 2:39 PM, [EMAIL PROTECTED] wrote: I was just checking my database and the uid and gid fields are always '0' for users. I checked in vpopuser source and in the function vadduser() from vpopmail.c it seems these are not set during account creation, and are only used in a chown(). following another function vauth_adduser() which updates the db. it doesn't seem to do anything with uid and gid here either when it builds the query string, so are these fields depreciated now and were used in some older version of vpopmail or something? (using 5.4.9) As far as I can tell, pw_uid is not used. pw_gid stores the permissions/limits for the user. If you use vmoduser to alter the user's permissions, you'll see the gid change. The newer pw_flags field represents the user's overall limits, taking domain-wide limits into account. Interestingly, it would appear that vauth_user() in vpopmail.c actually sets those field incorrectly. I've fixed the code in cvs, and it will be in the next release. Luckily, none of the vpopmail or qmailadmin code relied on the pw_gid being set correctly after calling vauth_user(). -- Tom Collins - [EMAIL PROTECTED] QmailAdmin: http://qmailadmin.sf.net/ Vpopmail: http://vpopmail.sf.net/ You don't need a laptop to troubleshoot high-speed Internet: sniffter.com
Re: [vchkpw] Spamassin configuration
Tom Collins wrote: On Feb 28, 2005, at 2:36 PM, Bill Wichers wrote: Maybe even a site-wite compile-time directive? Probably the most common would be something like SPAM under the INBOX for the filtered messages. Having it in SQL would be nice (allow users to configure it if they call the SPAM dir something else in their own hierarchy), although I'm not familiar enough with the innards of the code to know if that would work well... How about if a mailbox called SPAM exists, put it there, otherwise just drop it in the INBOX? That would be my choice, a lot of the systems I've looked at used the IMAP folder Spam to hold the messages tagged by spamc. That is how I had been planning to do it. Alternatively couldn't a env var be used? Change the var, change the delivery path relative to the users home dir. DAve -- Dave Goodrich Systems Administrator http://www.tls.net Get rid of Unwanted Emails...get TLS Spam Blocker!
Re: [vchkpw] Spamassin configuration
How about if a mailbox called SPAM exists, put it there, otherwise just drop it in the INBOX? That would be my choice, a lot of the systems I've looked at used the IMAP folder Spam to hold the messages tagged by spamc. That is how I had been planning to do it. Alternatively couldn't a env var be used? Change the var, change the delivery path relative to the users home dir. Sounds good to me, although better make sure the spam directory was case-insensitive. In just this thread we've seen SPAM, spam, and Spam :-) Env var seems like a neat idea too... I could see something doing a below this score, message-inbox, below this score AND above that score message-spam, and above someother score message-trash kind of sorting. Any plans to have vdelivermail absorb some maildrop functionality too? -Bill * Waveform Technology UNIX Systems Administrator
