Mark Martinec wrote: > Luis Daniel, > > >> I was debugging amavisd and I found this: >> brandmauer amavis[6320]: (06320-02-3) TIMING [total 45329 ms] - SMTP >> pre-DATA-flush: 403 (1%)1, SMTP DATA: 62 (0%)1, check_init: 126 (0%)1, >> digest_hdr: 2 (0%)1, digest_body: 9 (0%)1, gen_mail_id: 8 (0%)1, >> mime_decode: 205 (0%)2, get-file-type1: 363 (1%)3, decompose_part: 107 >> (0%)3, >> parts_decode: 0 (0%)3, check_header: 91 (0%)3, AV-scan-1: 1290 (3%)6, >> spam-wb-list: 2435 (5%)11, SA parse: 26 (0%)11, SA check: 4243 (9%)21, >> update_cache: 32 (0%)21, decide_mail_destiny: 35 (0%)21, fwd-connect: 362 >> (1%)22, fwd-xforward: 69 (0%)22, fwd-mail-pip: 179 (0%)22, fwd-rcpt-pip: 32 >> (0%)22, fwd-data-chkpnt: 46 (0%)22, write-header: 11 (0%)22, >> fwd-data-contents: 0 (0%)22, fwd-end-chkpnt: 34549 (76%)99, prepare-dsn: 91 >> (0%)99, main_log_entry: 86 (0%)99, update_snmp: 280 (1%)100, SMTP >> pre-response: 22 (0%)100, SMTP response: 69 (0%)100, unlink-1-files: 94 >> (0%) 100, rundown: 1 (0%)100 >> >> lok at this: fwd-end-chkpnt: 34549 (76%)99 >> to high value, what should I do then? >> > > Yes, it is pretty high, Postfix is taking 34 seconds to respond > to end-of-message. Perhaps you have not disabled header of body > checks in MTA on the re-entry path (port 10025) and you have > complex or poorly written regexp-based header/body checks there. > Or it could be some disk I/O problem. >
note that his amavisd-new is listening on 10025 (see his telnet transcript). not sure where he forwards mail (10026?) and what is done there... ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ AMaViS-user mailing list AMaViS-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amavis-user AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3 AMaViS-HowTos:http://www.amavis.org/howto/
