RE: [vps-mail] spamd in a vps v2 gateway

["Christopher Mellor" <providertalk.lists@xxxxxxxx>]

I have also had problems with running spamd with virtual config.
I am fairly new to Spamassassin, and my attempts were on Server A not
VPS2.
Verio support then told me it [virtualconfig] does not work on Server A
with spamd.
However, I am about to upgrade to VPS2.
My question is does anyone have spamd running on VPS2 with user prefs
(or rather virtual config?)?

FYI my last test start Command was:
virtual /usr/local/bin/spamd -d -p 1783 -A <ipaddress> -x --user-config
--virtual-config-dir=/usr/local/etc/spamassassin_user/%d
Did I get that bit right?
Cheers
Chris
-----Original Message-----
From: owner-vps-mail@xxxxxxxxxxxx [mailto:owner-vps-mail@xxxxxxxxxxxx]
On Behalf Of Bennett Lanford
Sent: 27 February 2004 17:11
To: vps-mail@xxxxxxxxxxxx
Subject: Re: [vps-mail] spamd in a vps v2 gateway


ADNET Ghislain <gadnet@xxxxxxxx> said:

> Hi,
>
>  i am trying to build a gateway with spamd filtering and i got a
> problem that perhaps you have allready met :)
>
>   The problem is in the use of the virtual config dir:
>
> -x -virtual-config-dir=/etc/mail/ghmail/sites/%d  --max-children 50
> --auto-whitelist -D
>
> here is my config and all the bayesian and auto white list files just
> go into the default spamd user's directory instead of
> /etc/mail/ghmail/sites/%d :(
>
>   my sendmail config is:
>
> DOMAIN(generic)dnl
> FEATURE(`access_db')dnl
> FEATURE(`mailertable')dnl
> FEATURE(`enhdnsbl', `bl.spamcop.net', `"Spam blocked see:
> http://spamcop.net/bl.shtml?"$&{client_addr}', `t')dnl
> define(`confBIND_OPTS', `WorkAroundBrokenAAAA')dnl MAILER(smtp)dnl
> MAILER(local)dnl
>
>  i tried with procmail and now with milters

I don't see any mention of milters in your mc file. Did you forget an
INPUT_MAIL_FILTER (or the alternate MAIL_FILTER) line?

> but this does not want to
> work. Any idea ?
>
>   Nothing in the logs even with define(`confLOG_LEVEL', `51')dnl

Any log level above 15 is treated as log level 15 (last I checked, at
least).

If you really *are* doing milters--and add an INPUT_MAIL_FILTER line,
etc. --you can set the milter log level with something like

define(`confMILTER_LOG_LEVEL',`22')dnl

(I think 22 is the highest milter log level currently supported ...???)

--
Bennett Lanford
ben@xxxxxxxxxxxxx


======================================================================
This is <vps-mail@xxxxxxxxxxxx>       <http://www.perlcode.org/lists/>
Before posting a question, please search the archives (see above URL).


======================================================================
This is <vps-mail@xxxxxxxxxxxx>       <http://www.perlcode.org/lists/>
Before posting a question, please search the archives (see above URL).