So what you are saying is that they can have custom settings thru their personal .mailfilter file but not thru their own user_prefs dir thru SA. Correct?
> -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of > Dallas Engelken > Sent: Friday, March 29, 2002 3:04 PM > To: 'Gawain'; [EMAIL PROTECTED] > Subject: RE: [SAtalk] Maildrop/vpopmail with Spamassassin > > > > -----Original Message----- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED]]On Behalf Of > > Gawain > > Sent: Friday, March 29, 2002 12:15 PM > > To: [EMAIL PROTECTED] > > Subject: [SAtalk] Maildrop/vpopmail with Spamassassin > > > > > > I've just configured Spamassassin on a Yellow Dog Linux machine and > > it's working well. However, I'm not sure how to implement per-user > > prefs on this setup. > > > > We're using vpopmail and thus a given user doesn't have a standard > > login account and home directory for user_prefs. The structure for a > > given virtual user is something like: > > > > [$path_to_vpopmail]/domains/mysite.com/myuser/Maildir/ > > > > I'm pretty new at this so I hope I'm not missing something too > > obvious. How do I tell Spamassasin where to look for user-specific > > prefs? > > > > first you have to apply the seekable patch to vpopmail > (http://www.thesafebox.com) > > after you have the seekable patch applied, you can filter through maildrop > by changing your domain/.qmail-default file to > | maildrop mailfilter > > the mailfilter file must be owned by vpopmail:vckpw and have 0600 > permissions. otherwise maildrop will not process it. the contents of > mailfilter should be something like this. > > #################################################### > VPOP="| /var/vpopmail/pop/bin/vdelivermail '' bounce-no-mailbox" > VHOME=`/var/vpopmail/pop/bin/vuserinfo -d $EXT@$HOST` > > if ( $SIZE < 262144 ) > { > exception { > xfilter "/usr/bin/spamc -f -u $EXT@$HOST" > } > } > > if (/^X-Spam-Flag: *YES/) > { > exception { > include $VHOME/Maildir/.mailfilter > } > ## IF YOU WANT TO GATHER ALL SPAM INTO 1 MAILDRIR > exception { > to /home/pop/spam/ > } > ## OR IF YOU WANT TO DELIVER SPAM TO THE USERS MAILDIR > exception { > to "$VPOP" > } > } > else > { > exception { > include $VHOME/Maildir/.mailfilter > } > exception { > to "$VPOP" > } > } > #################################################### > > Running through this mailfilter you have.. > -VPOP set to vdelivermail.. which is what .qmail-default usually contains. > - VHOME set to users virtual home directory by calling vuserinfo > - If size of message is less than 256KB, run through Spam check > - If message contains spam header set to YES, check to see if the user has > their own > .mailfilter file. If they do, then it processes based on their rules. > If they dont have that file, you can either deliver the message to a > global spam maildir, or you can deliver the message tagged as > spam to their > maildir. You could also deliver to say $VPOP/Maildir/.Spam > maildir, so each > user you have their own filtered spam maildir. This maildir would only be > accessible through IMAP or SQWebmail, and they would not download the > messages via Pop3. > - If the message doen not contain spam header set to YES, then it checks > first for .mailfilter presence, and if it's not there, it delivers the > message normally through vdelivermail. > > If you need to set a catchall, then you'd edit $VPOP. > NOTE: Editing the catchall through QmailAdmin will screw up your > .qmail-default file. You would need to patch QmailAdmin to edit the new > .qmail-default file... or just set .qmail-default to 0400 so QmailAdmin > cannot write to it. > > Thats how I like to do it... hopefully that gives you ideas! > > Dallas > > > _______________________________________________ > Spamassassin-talk mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/spamassassin-talk > _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
