Question about dspam/dspamc
Raphaël Halimi <[email protected]> Sat, 06 Dec 2014 02:32:25 +0100
| Newsgroups | gmane.mail.spam.dspam.user |
|---|---|
| Message-ID | <[email protected]> |
Hi,
I use DSPAM in server mode for some years now and relied on LMTP between
Postfix/DSPAM/Cyrus to communicate with each other, so I didn't really
look into the different modes of operation of the dspam binary itself;
but recently it occurred to me that I was calling dspam in
self-contained mode for retraining, whereas I could just call it as a
thin client which would communicate with the already-running server
instance.
So I have a question about the difference between dspam and dspamc
because the README isn't quite clear on this: it gives two contradicting
affirmations.
Between lines 1771 and 1784 we have:
> The DSPAM agent can then be called the same as if you were running in
> standard (non-client/server) mode and adding --client to the set of
> parameters. Running dspam without --client specified will cause DSPAM to
> revert to its normal non-daemon behavior and establish database connections
> on its own. The client settings will be loaded from dspam.conf, and the
> agent will act as a thin client instead. For example:
>
> dspam --client --user dick jane --deliver=innocent -d %u
>
> Alternatively, if you'd like to use a thinner client, dspamc is identical
> to the dspam binary in behavior, but has been stripped down to only include
> the lightweight client.
>
> dspamc --user dick jane --deliver=innocent -d %u
...which seems to imply that "dspamc" is equivalent to "dspam --client".
But later, between lines 1892 and 1895, we can read:
> "dspam" mode notes.
> In dspam mode, only the dspam client will be connecting to your LMTP server.
> This can be dspamc (a thin-client) or the dspam binary. In either case,
> you'll need to specify --client to tell DSPAM to act as a client. DLMTP
...which says that dspamc still needs the "--client" option.
The logic would dictate that the first affirmation is true, and the
second one is false; if that's the case, then the README should be
fixed, as well as dspamc man page (if it can work only as a thin client,
the man page shouldn't mention the --server option, and stress out that
the --client option is useless).
To be clear, in main.cf (Postfix), I had:
> dspam-retrain unix - n n - 10 pipe
> flags=Ru user=dspam argv=/usr/bin/dspam --user ${sender} --class=${nexthop} --source=error
If I replace /usr/bin/dspam with /usr/bin/dspamc, do I have to use the
--client option ? I don't think so, but could someone familiar with the
source code confirm ?
Thanks :)
--
Raphaël Halimi
------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk
_______________________________________________
Dspam-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspam-user
signature.asc
(application/pgp-signature, 949 B)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQJ8BAEBCgBmBQJUglyqXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ2RkE5NEVDNUQyOEM4RDY4QkU3OTJBRUY0 RDk5RjY2NjBBNTk4MjdCAAoJEE2Z9mYKWYJ7lxEQAIEgJrvz+EUdpbvFpaWYSSBd 1b45uqfFyBb5E6jS6PN6UBNWisbcu0kL7txK8a/DTxvmb5iroD5nBVbXBOX57555 YvKXpq9HGDgP2F6lK5L6UIp1iFNry5/op7B3go7C23Pfc+Onh+pSY3YoEHS/hZOI mwp9oqsQAYbEUL8its/GVX3JQ3YgRRQYyOcuCOqQCDNfn9wwdOujGySIZZqZi9xj rg8ESTJtAevkMO27THjfD+R2WuGYTi5l+fy7/v2yMlfVLA/Z+keAtYKX5rEX5QwO X6a2dHijOF71O4xiBExR4Wpu+9pSr4/Ach1gYh18O9NrolwAPFEmakuErlAhlqtd 0Dwysj1idqg8TyJNuheY+vs5CWnaxa1dXqbxylRVD31d3F6EHL4HcqNKTQ9rVCae 5lqhe9nWq98bL3rRMw7/SoSkJwWjxN6PWWrHACUBya48Vr69hoWLdcUIsPW6Kgsj 3+jJPEJLbZvma2S9kHQWELMsQhF1kVULeytDtHsctA7+1YtUfmxobkvsiLW9K/7i 4xGtQ3ZGUKWwYqa2Rxgbz90McS73nqTvPftjipvl59gebzYspu7AXHjRKp0A6Xq2 jZqTz+jDIayoWvLuA7cjHzph+c6KKN2GUjjS6YMOVLpD6cbeDNYSPPNNpuAUHk9T Ma2O2tMyDO+PHGN42PYL =TTEm -----END PGP SIGNATURE-----