From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26704 invoked by alias); 9 Feb 2005 21:35:01 -0000 Mailing-List: contact overseers-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: , Sender: overseers-owner@sources.redhat.com Received: (qmail 26680 invoked from network); 9 Feb 2005 21:34:54 -0000 Received: from unknown (205.217.158.180) by sourceware.org with QMTP; 9 Feb 2005 21:34:54 -0000 Received: (qmail 389 invoked by uid 10); 9 Feb 2005 21:34:53 -0000 Received: (qmail 10538 invoked by uid 500); 9 Feb 2005 21:34:44 -0000 Mail-Followup-To: overseers@sources.redhat.com, angela@wonderslug.com To: angela@wonderslug.com Cc: overseers@sources.redhat.com Subject: Re: user not receiving mail References: <20050209204948.779F5E3A7D@foam.wonderslug.com> From: Ian Lance Taylor Date: Thu, 10 Feb 2005 15:16:00 -0000 In-Reply-To: <20050209204948.779F5E3A7D@foam.wonderslug.com> Message-ID: User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2005-q1/txt/msg00201.txt.bz2 I've done a Bcc to the person with the problem. Angela Marie Thomas writes: > I can forward his originl mail, but I'd like to sanitize it from > potential spammers (his headers are decidedly anti-spam so I'd like > to respect that). Is there a blessed script for sanitizing mail > that I can use or do I have to spin my own? His messages are in the queue, and deliveries are consistently reporting deferral: Connected_to_213.239.196.208_but_connection_died._(#4.4.2)/ This means that when qmail was delivering e-mail to his system, it made a connection, but the system did not respond within the timeout period, which is configured to be 30 seconds. The timeout applies to the initial greeting, and to the response to any SMTP command. I just tried by hand, and I can confirm that his main MX responds very slowly. The initial greeting and MAIL FROM are fast, but the response to the RCPT TO is very slow. I'm sure it is consistently blowing out the 30 second timeout used by sourceware. I don't know why his system responds so slowly. The 30 second timeout is aggressive, and I could see it backing it off to 60 seconds. Not more than that, though. Ian