On Sunday 24 October 2010 14:34:04 escalera wrote: > Fol all messages, spamassassin takes 14++ seconds. Version: 3.3.1 > Debuging it, the times are: > Oct 24 14:03:20 email spamd[22477]: timing: total 14237 ms - > read_scoreonly_config: 4 (0.0%), > signal_user_changed: 6 (0.0%), > parse: 6 (0.0%), > extract_message_metadata: 80 (0.6%), > get_uri_detail_list: 6 (0.0%), > tests_pri_-1000: 5 (0.0%), > tests_pri_-950: 2 (0.0%), > tests_pri_-900: 2 (0.0%), > tests_pri_-400: 2 (0.0%), > tests_pri_0: 327 (2.3%), > check_dkim_signature: 2 (0.0%), > check_dkim_adsp: 52 (0.4%), > check_spf: 52 (0.4%), > poll_dns_idle: 13355 (93.8%), > check_dcc: 1.14 (0.0%), > [...] > > As you can see, the most time is on poll_dns_idle and tests_pri_500 tests. > Any idea that what appends? > How to dissable those tests?
The poll_dns_idle is just a state where SpamAssassin is waiting for DNS replies to come in or a timeout to expire. Apparently at least some (if not all) of your DNS queries are not being answered. Typically these are RBS or URIDNSBL tests, so perhaps one of the queried black/white-lists is down, or some perhaps there is a DNS resolver problem at your site. The 14+ (15) seconds timeout comes from your 'rbl_timeout' setting. You may decrease this value, perhaps down to 6 seconds, if your DNS resolving is otherwise reasonably fast. Nevertheless, you should investigate which DNS query is stalled by adding a '--debug=async' debug area to you spamd or spamassassin, e.g.: $ spamassassin -D timing,async -t <test.msg Mark
