On Wednesday 12 May 2004 3:05 pm, James Treworgy wrote:
> I've got a third-party spam filter that is used as a pipe in users
> .qmail file. In migrating to vpopmail, I've been able to configure it
> to work fine, but if a user makes any changes via qmailadmin, anything
> I've added to their .qmail is lost. Also, for "standard" mail
> configuration, there is no user .qmail file (it deletes it).
>
> I'd like to be able to have a .qmail file *always* in a user directory
> which contains my custom pipe, and have qmailadmin always include this
> user-specific configuration at the top of any .qmail file it writes.
> I guess in an ideal world, the qmailadmin interface would have a
> setting where a user could add anything they wanted to be included in
> their .qmail file and maintain it with their profile.
>
> I'm relatively new to vpopmail/qmailadmin so I don't know if this is
> possible to configure either by hand or through qmailadmin. I've read
> everything I could and couldn't find an answer to my question; the
> instructions for handling mail filtering seems different. Any suggestions
> or existing hacks?

If you use the lastest devel version (we use 5.5.1 in production) you
can use the new spamassasin code. It integrates calling spamassassin
into the vdelivermail program using some flags in the gid field. Use
--enable-spamassassin=y on the configure line. Then you can use
regular .qmail files without the pipe command, hence qmailadmin
won't step on them. 

You can disable spamassassin per user or per domain.
For domains update the vlimits file. For users run
vmoduser -f [EMAIL PROTECTED]
         -f ( disable spamassassin)

You can also have vdelivermail automatically delete email
that is marked as spam (which is how I use it). By default
that is disabled. To enable per user run:
vmoduser -F [EMAIL PROTECTED]
         -F ( delete spam)

You can also put that in the vlimits setup. 

We also have a hack to qmailadmin to add support for enable/disable
spamassassin. But it steps on the enable-modify-spam feature, so it
wasn't rolled into the CVS versions.

Hope that helps
Ken Jones

Reply via email to