From: "Steven Levine" Received: from [192.168.100.201] (HELO mail.2rosenthals.com) by 2rosenthals.com (CommuniGate Pro SMTP 5.4.10) with ESMTPS id 8670425 for ecs-isp@2rosenthals.com; Sat, 02 Dec 2023 12:26:31 -0500 Received: from [192.168.200.201] (port=56971 helo=mail2.2rosenthals.com) by mail.2rosenthals.com with esmtp (Exim 4.96) (envelope-from ) id 1r9Tky-0006CE-1w for ecs-isp@2rosenthals.com; Sat, 02 Dec 2023 12:26:20 -0500 Received: from mta-201b.earthlink-vadesecure.net ([51.81.229.181]:47881 helo=mta-201a.earthlink-vadesecure.net) by mail2.2rosenthals.com with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1r9Tkr-0002FF-37 for ecs-isp@2rosenthals.com; Sat, 02 Dec 2023 12:26:14 -0500 DKIM-Signature: v=1; a=rsa-sha256; bh=dOT7Wi/ZoF8+w/zRPtGaF6WoZ5pZDzCb2x/KeM ap8R0=; c=relaxed/relaxed; d=earthlink.net; h=from:reply-to:subject: date:to:cc:resent-date:resent-from:resent-to:resent-cc:in-reply-to: references:list-id:list-help:list-unsubscribe:list-subscribe:list-post: list-owner:list-archive; q=dns/txt; s=dk12062016; t=1701537972; x=1702142772; b=OE+eTXP/zo2aA82E7905jITVluwodyOdkv01cfVR6i+sJySgHACaSkT U33pB+iA5HBuVAI1zQ4zXebUfOFYnAi2CrDxLfDWI2oJTJk3CuVMuUzG0k58nnYL61mY3P0 jPhk00oc6VyaxwI1FL9OyeBRg5j4t8rhyJQHXpLPWcc48bsGDWg28E425taQasmpeSECgAF OpXy9xy4GR1ESAr8x5h7gA4koVLbJe59Kw8iEn7AQlQ440Poq7KHAb8NKysUIakJBmxhGL1 esMAebVymIFSOAOm7ksQLcccEaU23vZvBI5vSd7n10rB8Spq7sK/mWTZdTmsVMBDuYZsHNB mLA== Received: from slamain ([108.193.255.92]) by vsel2nmtao01p.internal.vadesecure.com with ngmta id 615a7c3e-179d13c557342e0e; Sat, 02 Dec 2023 17:26:12 +0000 Message-ID: <656b65ca.4.mr2ice.fgrirsq@earthlink.net> Date: Sat, 02 Dec 2023 09:13:46 -0800 To: "eCS ISP Mailing List" In-Reply-To: Subject: Re: [eCS-ISP] clamscan issue X-Mailer: MR/2 Internet Cruiser Edition for OS/2 v3.00.11.24/60 In , on 12/02/23 at 10:20 AM, "Massimo S." said: Hi Massimo, >on the 2nd MTA i've VAL to 3072 and clamscan don't give issues but it's >true also that it scan only 7 mail domains I suspect there are several issues here. One is the number files to be scanned and the other is the size of the files to be scanned. The third is memory fragmentation which may be the most important factor for us. The change we made to how clam handled memory reduced the fragmentation significantly, but I don't think it fully eliminated it. The only current solution we have for fragmentation is to reduce the number files processed by a clamscan run. >i already have some exclusions e.g. for msglist.dat, domain.tni, etc. Have you tried scanning by user rather than by domain? >in my experience VAL 3072 gives issues in some setups This is true, but for you the only systems that matter are yours. >is there another suggested value? >(more than 2560 and before 3072) Unfortunately, no. VAL rounds values to 512MB multiples because of how paging works. Steven -- ---------------------------------------------------------------------- "Steven Levine" Warp/DIY/BlueLion etc. www.scoug.com www.arcanoae.com www.warpcave.com ----------------------------------------------------------------------