[Bug 1936] RFE: specify multiple hosts for "spamc -d"

[bu...@bugzilla.spamassassin.org]

https://issues.apache.org/SpamAssassin/show_bug.cgi?id=1936





--- Comment #6 from Ty! Boyack <ty...@nrel.colostate.edu>  2008-04-02 15:11:30 PST ---
Specifying multiple hosts can work, however, it seems that only the first host
will be used unless 1) that host is down, or 2) you also specify '-H' or
'--randomize' on the command line.  With that flag set it does spool spam to
more than one spamd server.

I think this might be a common misunderstanding of the use.  I'm wondering if
it makes sense to change the default behavior to normally enable '--randomize'
and maybe add a new option of something like '--spamd-hosts-in-order' for the
cases where someone really wants to specify an order to their spamd servers. 
But most people I have talked with are thinking along the lines of spamd farms
that they would like load balanced.



(In reply to comment #5)
> The man page for spamc(1) (v 3.0.0 and 3.2.3) suggests that this is already
> implemented:  [ from http://linux.die.net/man/1/spamc ]
> 
>    -d host[,host2], --dest=host[,host2]
>        In TCP/IP mode, connect to spamd server on given host (default:
>        localhost).  Several hosts can be specified if separated by commas.
> 
> This suggests that this feature request has been implemented
> and the RFE for this feature has been completed.
> This bug should have been closed when that happened.
> 
> However, the implementation does not work.
> Enter bug 4971, which was marked as a duplicate of this bug,
> mostly due to the fact that bug 1936 was never closed.
> 
> I can confirm the fact that this feature does not work:
> the command "spamc -d host,host2 <test.eml" will never try host2.
> (Debian Etch, package spamassassin 3.2.3-0.volatile1)
> 
> If nobody is working on this, the documentation should be changed to reflect the
> fact that the -d flag does NOT accept a comma-delimited list.
> 
> If somebody is actually working on this, this bug should be closed and bug 4971
> should be re-opened to take over where this bug left off.


-- 
Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.