From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 65989 invoked by alias); 1 Feb 2017 17:44:53 -0000 Mailing-List: contact overseers-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: , Sender: overseers-owner@sourceware.org Received: (qmail 65858 invoked by uid 89); 1 Feb 2017 17:44:40 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-HELO: cgf.cx Received: from external.cgf.cx (HELO cgf.cx) (107.170.62.102) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 01 Feb 2017 17:44:40 +0000 Received: by cgf.cx (sSMTP sendmail emulation); Wed, 01 Feb 2017 12:44:38 -0500 DKIM-Filter: OpenDKIM Filter v2.11.0 cgf.cx 4CFBC406C0 Date: Wed, 01 Feb 2017 17:44:00 -0000 From: Christopher Faylor To: "overseers@sourceware.org" , octoploid Subject: Re: mails from markus@trippesldorf.de don't make it to libc-alpha@sourceware.org Message-ID: <20170201174438.GA4640@ednor.casa.cgf.cx> Mail-Followup-To: "overseers@sourceware.org" , octoploid References: <132141485967441@web5g.yandex.ru> <191531485969302@web9h.yandex.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <191531485969302@web9h.yandex.ru> User-Agent: Mutt/1.5.20 (2009-06-14) X-SW-Source: 2017-q1/txt/msg00056.txt.bz2 On Wed, Feb 01, 2017 at 06:15:02PM +0100, octoploid wrote: >01.02.2017, 17:44, "octoploid" : >> I cannot post messages to libc-alpha@sourceware.org with my >> markus@trippesldorf.de account anymore. >> (Posting to gcc-patches@gcc.gnu.org however works fine). >> >> All mails are just silently rejected after 24h. >> >> Could you please remove my email address from the black list? > >Here is an example: > >Hi. This is the qmail-send program at mail.ud10.udmedia.de. >I'm afraid I wasn't able to deliver your message to the following addresses. >This is a permanent error; I've given up. Sorry it didn't work out. > >: >recipient did not talk proper QMTP (#4.3.0) >I'm not going to try again; this message has been in the queue too long. For the record, this bounce message is not a "silently rejected" scenario. You got a clear bounce message which should have been reported as your first communication. It is a sign that I had a port misconfigured on sourceware and that is now fixed.