2005/12/30, Adam Kosmin <akosmin@vtsystems.com>:
> Hello dspammer's,
>
> Does anyone here understand how to use this feature or have a working
> example?
>
> All the best,
>
> --
> Adam Kosmin
> GNU/Linux SA
> Visual Trading Systems, LLC
>
> Empire State Building
> 350 Fifth Avenue, Suite 6420
> New York, NY 10118, USA
>
> Email akosmin@vtsystems.com
> Phone 1 (212) 871-1747 ext. 340
In the source I see "_ds_read_attribute" and and "_ds_pref_val" for
parsing the dspam.conf file.
# from the documentation in the source;
_ds_pref_val: returns the value of an attribute within a preference set.
Which makes _ds_read_attribute parse the whole preference set.
So the _ds_pref_val only makes sense if _ds_read_attribute is used
first to read a preference set.
You can search for those two to see what can be parsed from the
dspam.conf file.
A quick look show for instance "makeCorpus on" which is documented in
the source, but only in the source. There is a reason for this I
think.. "makeCorpus" is
never parsed by "_ds_read_attribute".. so it doesn't make a difference
if included
in dspam.conf or being documented outside the source.
After having done a quick look I don't see any parsing for a "domain
based delivery hosts" option in dspam.conf.. Which implies that this
feature is not yet implemented.. I could be wrong..
Using Postfix this would be a nice option to use indeed. With
transport you will only route your relay (protected) domains through
dspam and have dspam deliver it directly to the smtp server(s) of your
client(s). All other mails will use the default smtp transport which
will just deliver the mail without calling dspam.
This is a nicer option than having two separate postfix instances to split the
inbound and outbound traffic.
Have a nice day
Received on Sun Jan 1 07:15:51 2006
This archive was generated by hypermail 2.1.8 : Mon Jan 02 2006 - 00:00:01 EST