* Django [BOfH] <dja...@nausch.org>:
> I've a very bad performace on one of my MX. MAils a scanned most while 3
> - 5 seconds. :(
> The system is:
> CentOS 7
> No database, all datas in filespace!
> Here's an example mail delivery on this system's maillog:
> Feb 2 21:57:59 mailbitch1 amavis: (17306-04) TIMING-SA total
> 3482 ms - parse: 0.88 (0.0%), extract_message_metadata: 1.71 (0.0%),
> get_uri_detail_list: 0.09 (0.0%), tests_pri_-1000: 4.6 (0.1%),
> tests_pri_-950: 0.61 (0.0%), tests_pri_-900: 0.61 (0.0%),
> tests_pri_-400: 0.47 (0.0%), tests_pri_0: 971 (27.9%), check_dkim_adsp:
> 2.9 (0.1%), check_spf: 3.8 (0.1%), poll_dns_idle: 2486 (71.4%),
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,
$ spamassassin -D timing,async -t <test.msg
[*] sys4 AG
https://sys4.de, +49 (89) 30 90 46 64
Schleißheimer Straße 26/MG,80333 München
Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263
Vorstand: Patrick Ben Koetter, Marc Schiffbauer, Wolfgang Stief
Aufsichtsratsvorsitzender: Florian Kirstein