From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <95d2e7ed6bedce278c2a29ca32d77412@lsub.org> From: "Fco. J. Ballesteros" Date: Thu, 18 Apr 2013 16:51:07 +0200 To: 9fans@9fans.net In-Reply-To: <2e14c2fbb566df6d129d01cc4d835243@kw.quanstro.net> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="upas-owgbbitgyiiwepziruklrqwfrb" Subject: Re: [9fans] upas locking Topicbox-Message-UUID: 43e37f5a-ead8-11e9-9d60-3106f5b1d025 This is a multi-part message in MIME format. --upas-owgbbitgyiiwepziruklrqwfrb Content-Disposition: inline Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Yes, perhaps we should stop using that. Nevertheless, the problem I was trying to address is that everyone is sharing /mail/tmp (see the scripts in /mail/lib, although I'm sure you know them from memory :) ), and thus if one has one problem, it can lock everyone else using /mail/tmp. I'll take a look now to the countermeasures you suggest. I think we are applying a few other measures, including validatesender, but I'll take a look. --upas-owgbbitgyiiwepziruklrqwfrb Content-Type: message/rfc822 Content-Disposition: inline Received: from mail-lb0-f176.google.com ([209.85.217.176]) by lsub.org; Thu Apr 18 16:45:10 CES 2013 Received: by mail-lb0-f176.google.com with SMTP id y8so2730544lbh.7 for ; Thu, 18 Apr 2013 07:44:45 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:x-forwarded-to:x-forwarded-for:delivered-to:x-received :received-spf:x-virus-scanned:x-spam-flag:x-spam-score:x-spam-level :x-spam-status:from:date:to:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding:subject :x-beenthere:x-mailman-version:precedence:reply-to:list-id :list-unsubscribe:list-archive:list-post:list-help:list-subscribe :sender:errors-to; bh=DqD0cicp+8V89IfrD3SxuGXyHPmVLTIJprG0KcQ+RWM=; b=VrBjGZk3jfonx6cmEWQ/KK8TXWM0Xziwl0nePS39zOCj3u9lBWDNpe7VLz+vk+6r1+ JKlUKDOJ01dQu08pLpQQyyVaF2HLSr23k8teH1aX6RzA4WP6nnPzDo6M0A7UnuaIXb7b QRgCHs9c0W7wdzom+0+/Q2oa9jqEnYYtHGewGNHyMoeDkHGnhkl5W5Y1BA24IH8v5tH7 OCy6SSnVYeiy2MXsC6FneVNomQj4dvLxWfENfCpvY8X0ikQRmRbvxAzavjZcTg1Q+9xk 5aUzN0c8pxVIrlOszkWIM/LIYvDxGfErTur+NUL8i/V4R4ESwP4QW5ab+1vBVYoNBtth S71w== X-Received: by 10.112.164.65 with SMTP id yo1mr6049220lbb.107.1366296284890; Thu, 18 Apr 2013 07:44:44 -0700 (PDT) X-Forwarded-To: nemo@lsub.org X-Forwarded-For: nemo.mbox@gmail.com nemo@lsub.org Delivered-To: nemo.mbox@gmail.com Received: by 10.112.128.168 with SMTP id np8csp147741lbb; Thu, 18 Apr 2013 07:44:43 -0700 (PDT) X-Received: by 10.220.65.1 with SMTP id g1mr8460605vci.63.1366296282450; Thu, 18 Apr 2013 07:44:42 -0700 (PDT) Return-Path: <9fans-bounces@9fans.net> Received: from mail.9fans.net (mail.9fans.net. [67.207.142.3]) by mx.google.com with ESMTPS id oy17si6749359vcb.56.2013.04.18.07.44.40 (version=TLSv1 cipher=RC4-SHA bits=128/128); Thu, 18 Apr 2013 07:44:42 -0700 (PDT) Received-SPF: pass (google.com: domain of 9fans-bounces@9fans.net designates 67.207.142.3 as permitted sender) client-ip=67.207.142.3; Authentication-Results: mx.google.com; spf=pass (google.com: domain of 9fans-bounces@9fans.net designates 67.207.142.3 as permitted sender) smtp.mail=9fans-bounces@9fans.net Received: from localhost ([127.0.0.1] helo=[67.207.142.3]) by mail.9fans.net with esmtp (Exim 4.71) (envelope-from <9fans-bounces@9fans.net>) id 1USqCs-0001Pu-RT; Thu, 18 Apr 2013 14:53:02 +0000 Received: from lax-gw15.mailroute.net ([199.89.0.115] helo=gw15.lax01.mailroute.net) by mail.9fans.net with esmtp (Exim 4.71) (envelope-from ) id 1USqCr-0001Pp-Cp for 9fans@9fans.net; Thu, 18 Apr 2013 14:53:01 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by gw15.lax01.mailroute.net (Postfix) with ESMTP id 3Zs32h24CKz2BM9v for <9fans@9fans.net>; Thu, 18 Apr 2013 14:43:08 +0000 (GMT) X-Virus-Scanned: by MailRoute X-X-Spam-Flag: NO X-X-Spam-Score: -0.501 X-X-Spam-Level: X-X-Spam-Status: No, score=-0.501 tagged_above=-9999 tests=[KHOP_THREADED=-0.5, SPF_PASS=-0.001] autolearn=disabled Received: from gw15.lax01.mailroute.net ([199.89.0.115]) by localhost (gw15.lax01.mailroute.net.mailroute.net [127.0.0.1]) (mroute_mailscanner, port 10024) with LMTP id sy6FcjZbUvyU for <9fans@9fans.net>; Thu, 18 Apr 2013 14:43:06 +0000 (GMT) Received: from ladd.quanstro.net (ladd.quanstro.net [69.55.170.73]) by gw15.lax01.mailroute.net (Postfix) with ESMTP id 3Zs32d2Z9vz2BLcK for <9fans@9fans.net>; Thu, 18 Apr 2013 14:43:05 +0000 (GMT) From: erik quanstrom Date: Thu, 18 Apr 2013 10:42:56 -0400 To: 9fans@9fans.net Message-ID: <2e14c2fbb566df6d129d01cc4d835243@kw.quanstro.net> In-Reply-To: <1A70F044-4B17-4D0F-AE80-2BA28F0D28D1@lsub.org> References: <7C2F640A-2A94-4AA1-9CE9-4E4845F0860F@lsub.org> <96ac8463d3e63c152de3bf159eb53fb6@kw.quanstro.net> <1A70F044-4B17-4D0F-AE80-2BA28F0D28D1@lsub.org> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Subject: Re: [9fans] upas locking X-BeenThere: 9fans@9fans.net X-Mailman-Version: 2.1.13 Precedence: list Reply-To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> List-Id: Fans of the OS Plan 9 from Bell Labs <9fans.9fans.net> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: 9fans-bounces@9fans.net Errors-To: 9fans-bounces@9fans.net > The problem was that we had quite a number of upas/fs's and scanmails > running and it was because one of them had a problem and kept a > /mail/tmp/L.mbox file locked. All other ones kept waiting for that > (although all of them were using different "mboxes" created by the > piped script at /mail/tmp/$pid.blah.blah > i'm confused. doesn't this just make the problem smaller rather than fixing it? i would think if scanmail has the same issue, then mail will still go undelivered, right? we don't run scanmail. since scanmail relies on building rules, it needs constant maintence. and i didn't want to be on the hook for that. instead, i use mechanical defensive measures in smtpd and validatesender. the most effective measure is enforcing the rfc2821 rule that the ehlo string must look up in dns. to appease imap4 clients, there's a flag to force auth for clients ehlo'ing incorrectly. spamhaus does a good job cleaning up what remains. - erik http://www.quanstro.net/magic/man2html/8/smtp (yes, that's ugly!) --upas-owgbbitgyiiwepziruklrqwfrb--