|Summary:||spamc shouldn't use the -t parameter as connection timeout|
|Product:||Spamassassin||Reporter:||David Schweikert <dws>|
|Component:||spamc/spamd||Assignee:||SpamAssassin Developer Mailing List <dev>|
Description David Schweikert 2006-05-17 18:21:50 UTC
When a host is down, spamc does try three times to contact one of the hosts given with -d and fails after the third failure. Everytime, the value given with -t is used before the next host is tried. If, for example, -t 300 is used and the spamd server(s) is down, it is going to take 15 minutes until spamc exits, which is 3 times the timeout that I am expecting. If you combine this for example with Postfix's killing of the delivery process after another timeout value (which you might intuitively choose a little bit higher than what is set for spamc), then the system starts to send bounces back. I think that using the '-t'-specified value as connect-timeout is not necessary and doesn't do what the user expects. Setting the connect-timeout to a fixed value like 5 or 10 seconds should be ok in any case. If necessary, a separate parameter for the connect-timeout could be used...