Re: [101attendees] Jabber is inaccessible to me
Jared Mauch <jared@puck.nether.net> Thu, 22 March 2018 13:27 UTC
Return-Path: <jared@puck.nether.net>
X-Original-To: 101attendees@ietfa.amsl.com
Delivered-To: 101attendees@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DF8761272E1 for <101attendees@ietfa.amsl.com>; Thu, 22 Mar 2018 06:27:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level:
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
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 nKazb6mpvBQ0 for <101attendees@ietfa.amsl.com>; Thu, 22 Mar 2018 06:27:25 -0700 (PDT)
Received: from puck.nether.net (puck.nether.net [204.42.254.5]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4B96E1200C5 for <101attendees@ietf.org>; Thu, 22 Mar 2018 06:27:25 -0700 (PDT)
Received: from [IPv6:2001:67c:370:128:6d1e:7107:1fb3:74f7] (unknown [IPv6:2001:67c:370:128:6d1e:7107:1fb3:74f7]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by puck.nether.net (Postfix) with ESMTPSA id B33F4540D66; Thu, 22 Mar 2018 09:27:14 -0400 (EDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (1.0)
From: Jared Mauch <jared@puck.nether.net>
X-Mailer: iPhone Mail (15D100)
In-Reply-To: <6ab84231-3cc4-ccde-1685-245be0139722@isc.org>
Date: Thu, 22 Mar 2018 13:27:13 +0000
Cc: 101attendees@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <1F199F31-99BB-4A92-9F31-37D1DAEE22EE@puck.nether.net>
References: <20180321115545.GA12766@jurassic> <20180321115828.GB12766@jurassic> <20180322131911.GA14995@laperouse.bortzmeyer.org> <6ab84231-3cc4-ccde-1685-245be0139722@isc.org>
To: Ray Bellis <ray@isc.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/101attendees/uGDc0f76Vxu7ieXAu8DUIOCWm1Y>
Subject: Re: [101attendees] Jabber is inaccessible to me
X-BeenThere: 101attendees@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Mailing list of IETF 101 attendees that have opted in on this list <101attendees.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/101attendees>, <mailto:101attendees-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/101attendees/>
List-Post: <mailto:101attendees@ietf.org>
List-Help: <mailto:101attendees-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/101attendees>, <mailto:101attendees-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Mar 2018 13:27:27 -0000
Due to XMPP spam I had to whitelist my own s2s communications. Your server operator may have done the same. Jared Mauch > On Mar 22, 2018, at 1:25 PM, Ray Bellis <ray@isc.org> wrote: > >> On 22/03/2018 13:19, Stephane Bortzmeyer wrote: >> >> Was the problem solved? I have the same issue (and I promised to be >> Jabber scribe this afternoon). > > We're pretty sure it's the fault of our corporate jabber server, not the > IETF one. > > Ray > > _______________________________________________ > 101attendees mailing list > 101attendees@ietf.org > https://www.ietf.org/mailman/listinfo/101attendees
- [101attendees] Jabber is inaccessible to me Mukund Sivaraman
- Re: [101attendees] Jabber is inaccessible to me Mukund Sivaraman
- Re: [101attendees] Jabber is inaccessible to me Stephane Bortzmeyer
- Re: [101attendees] Jabber is inaccessible to me Ray Bellis
- Re: [101attendees] Jabber is inaccessible to me Jared Mauch