Re: [vchkpw] SpamAssassin/vmodinfo changes

[Tom Collins]

I have a sizable patch from Jeff Hedlund scheduled for the 
qmailadmin-1.0.21 release that adds very flexible, per-user 
spamassassin support.

I'll (hopefully) announce the release later today, along with 
information on how it works.

--
Tom Collins
[EMAIL PROTECTED]

Re: [vchkpw] SpamAssassin/vmodinfo changes

[Bill Shupp]

On Saturday, March 8, 2003, at 01:28  AM, Gabriel Ambuehl wrote:

Hi,

I just added my SpamAssassin changes to vpopmail-5.3.19 which is now
vpopmail-5.3.20.
Where's the patch to 5.3.19?  No need to increment the version number,
as I'll do that when coordinating with other patches that come in.
I couldn't verify Bill's problem of vdelivermail crashing when spamd
wasn't running on FreeBSD 4.7 myself but I'd like to hear from others.
Well, did you actually implement FALLBACK support?

Regards,

Bill Shupp

Re: [vchkpw] SpamAssassin/vmodinfo changes

[Bill Shupp]

On Friday, March 7, 2003, at 06:33  AM, Gabriel Ambuehl wrote:

Hello,
I've added support for SpamAssassin into vdelivermail (basically, it
will just add the SpamAssassin score of the mail if activated and
NEVER delete mail on the server).
Further, I added the -w switch to vmodinfo which has it display all
users in a domain, handy if you want to just know about them or feed
them to some scripts to do something with them (in my case, I wanted
the feature so I can set quotas for them all with xargs ;-).
Anyway, find the tarball at http://buz.ch/software.

I'd very like to hear comments and bug reports about SpamAssassin
integration (-w switch was simple enough ;-). From all I can tell,
there shouldn't be any licensing issues as the spamassassin client
stuff seems to be under the BSDL or alike license and thus can be
incorporated into GPL projects just fine.
Gabriel,

Thanks for sharing your changes.  However, did you address the problems 
I pointed out with the last version of these changes?  Your email does 
dot indicate either way. 
(http://www.mail-archive.com/[EMAIL PROTECTED]/msg11282.html).  Also, 
can you provide a patch to the current development release, 5.3.19?

Regards,

Bill Shupp