Eddy, > I'm using spamassassin 3.2.5 on my academic RHEL server and it works > well :-) > I'm also using Net::DNS version: 0.65, amavisd-new 2.6.4, postfix 2.5.6 > > I'm receiving an email which take too much time to process. > I have to remove it from my postfix's mail queue > > here is part of the spamassassin debug run: > ...cut... > 13:31:25.577 13.621 0.002 [28208] dbg: rules: running rawbody tests; > score so far=0.001 > 13:31:25.617 13.661 0.039 [28208] dbg: rules: compiled rawbody tests > 13:31:25.794 13.839 0.178 [28208] dbg: rules: ran rawbody rule > __SARE_HTML_SINGLET2 ======> got hit: ">o<" > 13:31:25.836 13.880 0.042 [28208] dbg: rules: ran rawbody rule > __SARE_BLACK_FG_COLOR ======> got hit: ""color: black" > 13:31:26.093 14.137 0.257 [28208] dbg: rules: ran rawbody rule > __TVD_BODY ======> got hit: "vers" > 13:31:26.129 14.173 0.036 [28208] dbg: rules: ran rawbody rule > __SARE_HAS_FG_COLOR ======> got hit: ""color:" > 13:51:46.568 1234.612 *1220.439* [28208] dbg: async: select found 17 > responses ready (t.o.=0.0) > 13:51:46.568 1234.612 0.000 [28208] dbg: async: completed in 1221.532 s: > URI-A, A:dns3.nettica.com.
> The async step takes 1220 seconds to complete !! > > It happend everytime I'm processing manually that specific message [...] > I do not understand how it can take 1220 seconds to complete when it > said timeout=15s It is not the DNS query that is a problem here. Most likely some regexp rules are taking that long. Async DNS queries are fired off at the beginning, then most other rules are evaluated, giving DNS resolver opportunity to do its job during that time. Only after most rules have been evaluated are the DNS responses collected. There is no point in enforcing a timeout on DNS responses when we have to wait for other computations anyway. Mark
