Re: Mailing list membership.

willi uebelherr <willi.uebelherr@riseup.net> Mon, 27 February 2017 17:11 UTC

Return-Path: <willi.uebelherr@riseup.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B6E512A23A for <ietf@ietfa.amsl.com>; Mon, 27 Feb 2017 09:11:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.722
X-Spam-Level:
X-Spam-Status: No, score=-2.722 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=riseup.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xw0WyQ3U7ZPL for <ietf@ietfa.amsl.com>; Mon, 27 Feb 2017 09:11:06 -0800 (PST)
Received: from mx1.riseup.net (mx1.riseup.net [198.252.153.129]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EFB3112A24A for <ietf@ietf.org>; Mon, 27 Feb 2017 09:11:05 -0800 (PST)
Received: from cotinga.riseup.net (unknown [10.0.1.164]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.riseup.net", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.riseup.net (Postfix) with ESMTPS id 30C3C1A292F; Mon, 27 Feb 2017 17:11:04 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak; t=1488215464; bh=ZL9kxGyobsrxfTHOw6bUqPIbPn4t6o+WnQ7QfDU52Z4=; h=Subject:References:Cc:To:From:Date:In-Reply-To:From; b=QzYBDYlrgFYO3cQu68X/HBuWelKd2XnsTYhwrOfTH07iunWMq2JSqD2Ka3k8PtZTu bV1KJ9avjzwaqC4kOjVP6pnZfKPbXOOiJ2Rc8kFufyDGHARerkCeubaCQIVRG3Z9Gv PQ0T01aympJ5ggpA43rZW7cfWaPmD6xxwIgnLtm8=
Received: from [127.0.0.1] (localhost [127.0.0.1]) (Authenticated sender: willi.uebelherr) with ESMTPSA id 745ED400EE
Subject: Re: Mailing list membership.
References: <HE1PR04MB1449F89BC245494298906D06BD540@HE1PR04MB1449.eurprd04.prod.outlook.com> <6.2.5.6.2.20170226124145.0b7b38c0@elandnews.com> <20f0d769-1937-3256-e37b-9583399c11d3@riseup.net> <20170227011852.GA5403@mx4.yitter.info> <5850e685-2f97-2bdb-87e2-0c11830e1d1c@riseup.net> <HE1PR04MB14490315646CDD5CC7DC2DBCBD570@HE1PR04MB1449.eurprd04.prod.outlook.com>
To: IETF discussion <ietf@ietf.org>
From: willi uebelherr <willi.uebelherr@riseup.net>
Message-ID: <ae531393-b622-a8b3-2cdd-65a4e99c6e9f@riseup.net>
Date: Mon, 27 Feb 2017 14:10:51 -0300
MIME-Version: 1.0
In-Reply-To: <HE1PR04MB14490315646CDD5CC7DC2DBCBD570@HE1PR04MB1449.eurprd04.prod.outlook.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/eYtQ_49Ab2bSIdvWX-sjF-vMV0s>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Feb 2017 17:11:07 -0000

Dear Khaled,

there are many speculations like that from Andrew Sullivan. The core is, 
they don't understand the real situation and create big clouds about 
nothing.

Independent, what e-mail service you use, the MTA of the maillist server 
installation have to distribute the emails. And if he can't do it, the 
people with access to the log-files have to look for, why the MTA is not 
able to distribute.

I am not sure, but i think, you are a subscriber in the list and have no 
access to the systemfiles. Therefore, the admin group have to do it. It 
is her job. Not yours.

many greetings, willi
Asuncion, Paraguay


On 27/02/2017 11:37, Khaled Omar wrote:
>> For Khalid it will be immpossible to analyse, what is going on with some emails in some specific situation. Only in the log file of the MTA you can see it. But this is not possible for Khalid, or?
>
> I think so, because I'm using a free e-mail service and don't have on-premise server, so I have to keep re-enabling my subscription for this sensitive situation.
>
> Khaled
>
> -----Original Message-----
> From: ietf [mailto:ietf-bounces@ietf.org] On Behalf Of willi uebelherr
> Sent: Monday, February 27, 2017 7:12 AM
> To: IETF discussion
> Subject: Re: Mailing list membership.
>
>
> Dear Andrew,
>
> John Levine told us another story. And i know it from some other maillist.
>
> For Khalid it will be immpossible to analyse, what is going on with some emails in some specific situation. Only in the log file of the MTA you can see it. But this is not possible for Khalid, or?
>
> I don't know, if you are member in the admin group. And i don't know, if John is member in the admin group. Independent, this group have to start the process of analyse.
>
> But John wrote, they work long time for that. And it is absolutly true, "It's a pain, it stinks,...". I wish you to find the real bug.
>
> many greetings, willi
>
>
> On 27/02/2017 01:38, John Levine wrote:
>  >
>  > This is the DMARC problem that has been discussed at length here.
>  > It's a pain, it stinks, we're working on it.
>  > R's,
>  > John
>
> On 26/02/2017 22:18, Andrew Sullivan wrote:
>> On Sun, Feb 26, 2017 at 07:19:13PM -0300, willi uebelherr wrote:
>>>
>>> the first action have to come from the ietf-discuss admin group and
>>> not from Khalid. The admin group have to analyse the bounce-counter
>>> for all list members.
>>
>> No.  Khalid's mail bounced something that came from the ietf mail
>> list, and it came to his mail because he was subscribed to that mail
>> list.  And therefore, the question is why his configuration is
>> bouncing things from the ietf mail server.  And that determination can
>> only be made at his end.
>>
>> A
>>
>
>