Re: [vchkpw] spamassassin patch ready ahead of schedule
On Fri, 30 Jan 2004, Rob Nelson wrote: > I for one am interested in looking at this. Is there a URL available to > download the plugin? Sure. http://spork.us/dotqmailedit-1.1.tgz There's a brief README, but I highly recommend reading through dotqmailedit.c for more information. In brief, this gives vacation/forward/spam-controls to users within squirrelmail. Thanks, C > Charles Sprickman wrote: > > >Sorry to be replying late... > > > >But, if anyone is interested, we have a squirrelmail plugin and a small C > >program to handle turning spam-filtering on/off and also for setting > >vacations and forwards from within SquirrelMail. It does not require > >running your webserver as the vpopmail user. Combined with the "sasql" > >plugin, it gives users the ability to set many vpopmail options without > >having to ever look at qmailadmin. > > > >Let me know if anyone has interest in this. The only thing I ask is that > >if you find it useful, that you contribute any cleanup back to me. > > > >Thanks, > > > >Charles > > > > > >
RE: [vchkpw] spamassassin patch ready ahead of schedule
-Original Message- From: Rob Nelson [mailto:[EMAIL PROTECTED] Sent: Friday, January 30, 2004 12:11 PM To: [EMAIL PROTECTED] Subject: Re: [vchkpw] spamassassin patch ready ahead of schedule I for one am interested in looking at this. Is there a URL available to download the plugin? Charles Sprickman wrote: >Sorry to be replying late... > >But, if anyone is interested, we have a squirrelmail plugin and a small >C program to handle turning spam-filtering on/off and also for setting >vacations and forwards from within SquirrelMail. It does not require >running your webserver as the vpopmail user. Combined with the "sasql" >plugin, it gives users the ability to set many vpopmail options without >having to ever look at qmailadmin. > >Let me know if anyone has interest in this. The only thing I ask is >that if you find it useful, that you contribute any cleanup back to me. > >Thanks, > >Charles > > I am interested as well! Jake S
Re: [vchkpw] spamassassin patch ready ahead of schedule
I for one am interested in looking at this. Is there a URL available to download the plugin? Charles Sprickman wrote: Sorry to be replying late... But, if anyone is interested, we have a squirrelmail plugin and a small C program to handle turning spam-filtering on/off and also for setting vacations and forwards from within SquirrelMail. It does not require running your webserver as the vpopmail user. Combined with the "sasql" plugin, it gives users the ability to set many vpopmail options without having to ever look at qmailadmin. Let me know if anyone has interest in this. The only thing I ask is that if you find it useful, that you contribute any cleanup back to me. Thanks, Charles
Re: [vchkpw] spamassassin patch ready ahead of schedule
Sorry to be replying late... But, if anyone is interested, we have a squirrelmail plugin and a small C program to handle turning spam-filtering on/off and also for setting vacations and forwards from within SquirrelMail. It does not require running your webserver as the vpopmail user. Combined with the "sasql" plugin, it gives users the ability to set many vpopmail options without having to ever look at qmailadmin. Let me know if anyone has interest in this. The only thing I ask is that if you find it useful, that you contribute any cleanup back to me. Thanks, Charles
Re: [vchkpw] spamassassin patch ready ahead of schedule
On Saturday 17 January 2004 6:03 pm, Raboo Treed wrote: > is this a feature that will be added to vpopmail permantly?? > > if not now it should be in contrib on the stable i think Yep, it will be added permanently. Ken Jones
Re: [vchkpw] spamassassin patch ready ahead of schedule
is this a feature that will be added to vpopmail permantly?? if not now it should be in contrib on the stable i think
Re: [vchkpw] spamassassin patch ready ahead of schedule
On Thursday 15 January 2004 11:51 am, Systems Administrator wrote:
> And the -c option doesn't seem to be creating .spamassassin dirs inside
> their homedirs
I found a problem with spamassassin version 2.61 and latest cvs 2.70
Here is a patch that should allow for auto creation of vpopmail
.spamassassin/user_prefs file. It should be applied to your
SpamAssassin.pm file, then restart spamd
--- SpamAssassin.pm.orig 2004-01-15 11:57:05.0 -0800
+++ SpamAssassin.pm 2004-01-15 12:00:17.0 -0800
@@ -1268,7 +1268,7 @@
}
sub get_and_create_userstate_dir {
- my ($self) = @_;
+ my ($self,$userdir) = @_;
# user state directory
my $fname = $self->{userstate_dir};
@@ -1276,8 +1276,8 @@
# If vpopmail is enabled then set fname to virtual homedir
#
- if (defined $self->{user_dir}) {
-$fname = File::Spec->catdir ($self->{user_dir}, ".spamassassin");
+ if ($userdir) {
+$fname = "$userdir/.spamassassin";
}
if (defined $fname && !$self->{dont_copy_prefs}) {
@@ -1309,8 +1309,8 @@
return(0);
}
- if ($userdir && $userdir ne $self->{user_dir}) {
-warn "Oops! user_dirs don't match! '$userdir' vs '$self->{user_dir}'\n";
+ if ($userdir) {
+$self->{user_dir} = $userdir;
}
if (!-f $fname)
Re: [vchkpw] spamassassin patch ready ahead of schedule
On Thursday 15 January 2004 11:51 am, Systems Administrator wrote:
> How can I NOT use spamassassin for certain users?
> And have user based preferences for spam assassin?
vmoduser -f [EMAIL PROTECTED] turns off spam assassin for [EMAIL PROTECTED]
I'm getting the same problem with user dir creation with
spamassasin version 2.61 (latest) but it is working fine with
version 2.44 redhat 9 rpm. Looks like some differences in
the code, specifically line 1295 in SpamAssassin.pm
$self->{user_dir} does not get set
and is later used to create the .spamassassin directory.
I'm trying out some modifications to SpamAssassin.pm
Ken
RE: [vchkpw] spamassassin patch ready ahead of schedule
How can I NOT use spamassassin for certain users? And have user based preferences for spam assassin? And the -c option doesn't seem to be creating .spamassassin dirs inside their homedirs -Original Message- From: Ken Jones [mailto:[EMAIL PROTECTED] Sent: Thursday, January 15, 2004 11:38 AM To: Systems Administrator; [EMAIL PROTECTED] Subject: Re: [vchkpw] spamassassin patch ready ahead of schedule On Thursday 15 January 2004 11:23 am, Systems Administrator wrote: > User preferences don't seem to be working, and it seems to be doing > spamassassin system wide after installing cvs vpopmail and the > spamassassin.patch > > Heres my config: > > /etc/mail/spamassassin/local.cf - > required_hits 10 > rewrite_subject 1 > subject_tag [SPAM] > report_safe 0 > use_dcc 0 > use_pyzor 0 > use_razor2 1 > skip_rbl_checks 1 > rbl_timeout 3 > use_bayes 1 > bayes_auto_learn 1 > allow_user_rules 1 > > /etc/sysconfig/spamassassin - > SPAMDOPTIONS="-x -d -c -v -u vpopmail -D" > (Your email said to use -uvpopmail but the default from spamassassin from > -u spamd, I changed it back and forth and I don't believe any difference) > > /home/vpopmail/domains/mydomain/.qmail-default - > > | /home/vpopmail/bin/vdelivermail '' bounce-no-mailbox > > What I use to call spamassassin per user in .qmail - > > | spamassassin | maildir ./Maildir/ > > In a home dir, I have a .spamassassin/user_prefs > > And in the users_prefs I have a blacklist_from [EMAIL PROTECTED] > > It did not block the email address.. > > > And basically..when I tail /var/log/maillog (notice the -D above) I see > spamc being called for every email.. Users that don't even have a .qmail > file.. Much less calling spamassassin with it. > > > What am I doing wrong?? > It might be the -x option to spamd -x, --nouser-configDisable user config files With this setup, no users will need a .qmail file to call spamassassin. vdelivermail envoked from .qmail-default will call it. For .qmail-user files in the domain's directory, you try calling spamassassin like so: | spamc -f [EMAIL PROTECTED] | whatever Ken
Re: [vchkpw] spamassassin patch ready ahead of schedule
On Thursday 15 January 2004 11:23 am, Systems Administrator wrote: > User preferences don't seem to be working, and it seems to be doing > spamassassin system wide after installing cvs vpopmail and the > spamassassin.patch > > Heres my config: > > /etc/mail/spamassassin/local.cf - > required_hits 10 > rewrite_subject 1 > subject_tag [SPAM] > report_safe 0 > use_dcc 0 > use_pyzor 0 > use_razor2 1 > skip_rbl_checks 1 > rbl_timeout 3 > use_bayes 1 > bayes_auto_learn 1 > allow_user_rules 1 > > /etc/sysconfig/spamassassin - > SPAMDOPTIONS="-x -d -c -v -u vpopmail -D" > (Your email said to use -uvpopmail but the default from spamassassin from > -u spamd, I changed it back and forth and I don't believe any difference) > > /home/vpopmail/domains/mydomain/.qmail-default - > > | /home/vpopmail/bin/vdelivermail '' bounce-no-mailbox > > What I use to call spamassassin per user in .qmail - > > | spamassassin | maildir ./Maildir/ > > In a home dir, I have a .spamassassin/user_prefs > > And in the users_prefs I have a blacklist_from [EMAIL PROTECTED] > > It did not block the email address.. > > > And basically..when I tail /var/log/maillog (notice the -D above) I see > spamc being called for every email.. Users that don't even have a .qmail > file.. Much less calling spamassassin with it. > > > What am I doing wrong?? > It might be the -x option to spamd -x, --nouser-configDisable user config files With this setup, no users will need a .qmail file to call spamassassin. vdelivermail envoked from .qmail-default will call it. For .qmail-user files in the domain's directory, you try calling spamassassin like so: | spamc -f [EMAIL PROTECTED] | whatever Ken
RE: [vchkpw] spamassassin patch ready ahead of schedule
User preferences don't seem to be working, and it seems to be doing spamassassin system wide after installing cvs vpopmail and the spamassassin.patch Heres my config: /etc/mail/spamassassin/local.cf - required_hits 10 rewrite_subject 1 subject_tag [SPAM] report_safe 0 use_dcc 0 use_pyzor 0 use_razor2 1 skip_rbl_checks 1 rbl_timeout 3 use_bayes 1 bayes_auto_learn 1 allow_user_rules 1 /etc/sysconfig/spamassassin - SPAMDOPTIONS="-x -d -c -v -u vpopmail -D" (Your email said to use -uvpopmail but the default from spamassassin from -u spamd, I changed it back and forth and I don't believe any difference) /home/vpopmail/domains/mydomain/.qmail-default - | /home/vpopmail/bin/vdelivermail '' bounce-no-mailbox What I use to call spamassassin per user in .qmail - | spamassassin | maildir ./Maildir/ In a home dir, I have a .spamassassin/user_prefs And in the users_prefs I have a blacklist_from [EMAIL PROTECTED] It did not block the email address.. And basically..when I tail /var/log/maillog (notice the -D above) I see spamc being called for every email.. Users that don't even have a .qmail file.. Much less calling spamassassin with it. What am I doing wrong?? -Original Message- From: Ken Jones [mailto:[EMAIL PROTECTED] Sent: Thursday, January 15, 2004 7:04 AM To: X-Istence Cc: [EMAIL PROTECTED] Subject: Re: [vchkpw] spamassassin patch ready ahead of schedule On Thursday 15 January 2004 5:43 am, X-Istence wrote: > Raboo Treed wrote: > > what does the patch do exactly?? > > > > calls spamc uppon mailcheck? > > Yes indeed, it forks, and calls spamc, gives it the message, and then > checks the score it returns from SPAMD to then if it is over a set limit > delete it, or otherwise it tags it and delivers it to the users maildir. Almost but not quite. Tha'ts what the FreeBSD port patch does. This is slightly different. What this does is what I posted as a proposal yesterday. Basicly: if spamassassin is enabled, and NO_SPAMASSASSIN bit is 0, then fork spamc, hands it the message, then puts the resulting email in the regular file. It does not reject the message if over a certain limit. All email goes through, just scanned using the users preferences if available, otherwise the system preferences. Ken
Re: [vchkpw] spamassassin patch ready ahead of schedule
On Thursday 15 January 2004 5:43 am, X-Istence wrote: > Raboo Treed wrote: > > what does the patch do exactly?? > > > > calls spamc uppon mailcheck? > > Yes indeed, it forks, and calls spamc, gives it the message, and then > checks the score it returns from SPAMD to then if it is over a set limit > delete it, or otherwise it tags it and delivers it to the users maildir. Almost but not quite. Tha'ts what the FreeBSD port patch does. This is slightly different. What this does is what I posted as a proposal yesterday. Basicly: if spamassassin is enabled, and NO_SPAMASSASSIN bit is 0, then fork spamc, hands it the message, then puts the resulting email in the regular file. It does not reject the message if over a certain limit. All email goes through, just scanned using the users preferences if available, otherwise the system preferences. Ken
Re: [vchkpw] spamassassin patch ready ahead of schedule
Raboo Treed wrote: what does the patch do exactly?? calls spamc uppon mailcheck? Yes indeed, it forks, and calls spamc, gives it the message, and then checks the score it returns from SPAMD to then if it is over a set limit delete it, or otherwise it tags it and delivers it to the users maildir. X-Istence
Re: [vchkpw] spamassassin patch ready ahead of schedule
what does the patch do exactly?? calls spamc uppon mailcheck?
Re: [vchkpw] spamassassin patch ready ahead of schedule
Ken Jones wrote: Tom Collins sent me the FreeBSD ports patch with code to enable spamassassin. It pretty much did the whole job except for the pw_gid flags, some configure.in changes and a new vmoduser option to disable spam assassin. So the patch is ready ahead of schedule, whoo hoo! Ken Jones I had posted that to the list a while ago hoping it could be added (I dont know how to use sourceforge cvs), anyways, im happy its being used. Soon i might send in a patch to use bogofilter with it, as bogofilter is written in C/C++ it should be faster than AS. X-Istence
Re: [vchkpw] spamassassin patch ready ahead of schedule
Good deal.. I would like to look at this. -John - Original Message - From: "Ken Jones" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, January 14, 2004 10:01 PM Subject: [vchkpw] spamassassin patch ready ahead of schedule > Tom Collins sent me the FreeBSD ports patch with code to enable spamassassin. > It pretty much did the whole job except for the pw_gid flags, some > configure.in changes and a new vmoduser option to disable spam assassin. > So the patch is ready ahead of schedule, whoo hoo! > > I'm running it on our mail server now and it seems to be working just fine. > > The patch is up on source forge > RequestID 877367 > Summary spamassassin patch against cvs > > One thing to note. If you start spamd with the -c option it should > automatically create the users .spamassassin directory where bayes > files can be kept. Be careful about allowing bayes, the files can get over 1M. > > I'm running spamd with these options "-d -c -v -uvpopmail" > Currently my .spamassassin directory has these files: > |bayes_journal bayes_seen bayes_toks user_prefs| > The user_prefs file is where we can have qmailadmin/vqadmin > support required_hits, safe_report and whitelists > > I'll try to write up a README.spamassassin tomorrow. > > Ken Jones >
[vchkpw] spamassassin patch ready ahead of schedule
Tom Collins sent me the FreeBSD ports patch with code to enable spamassassin. It pretty much did the whole job except for the pw_gid flags, some configure.in changes and a new vmoduser option to disable spam assassin. So the patch is ready ahead of schedule, whoo hoo! I'm running it on our mail server now and it seems to be working just fine. The patch is up on source forge RequestID 877367 Summary spamassassin patch against cvs One thing to note. If you start spamd with the -c option it should automatically create the users .spamassassin directory where bayes files can be kept. Be careful about allowing bayes, the files can get over 1M. I'm running spamd with these options "-d -c -v -uvpopmail" Currently my .spamassassin directory has these files: |bayes_journal bayes_seen bayes_toks user_prefs| The user_prefs file is where we can have qmailadmin/vqadmin support required_hits, safe_report and whitelists I'll try to write up a README.spamassassin tomorrow. Ken Jones
