IETF Logo Mail Archive

Re: [xmpp] [Summit] Fwd: [jdev] [CFP] FOSDEM 2016, RTC devroom, speakers, volunteers neeeded

Daniel Pocock <daniel@pocock.pro> Sat, 21 November 2015 07:38 UTC

Return-Path: <daniel@pocock.pro>
X-Original-To: xmpp@ietfa.amsl.com
Delivered-To: xmpp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 03E481B4143 for <xmpp@ietfa.amsl.com>; Fri, 20 Nov 2015 23:38:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.701
X-Spam-Level:
X-Spam-Status: No, score=-4.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, GB_I_LETTER=-2, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 2U6-fmzjB0CP for <xmpp@ietfa.amsl.com>; Fri, 20 Nov 2015 23:38:56 -0800 (PST)
Received: from mail1.trendhosting.net (mail1.trendhosting.net [195.8.117.5]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D0BF41B40B9 for <xmpp@ietf.org>; Fri, 20 Nov 2015 23:38:55 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mail1.trendhosting.net (Postfix) with ESMTP id BA8FF150AC; Sat, 21 Nov 2015 07:38:53 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=pocock.pro; s=mail; t=1448091533; bh=5X89FrVjNYi/Ve5mer0Fn8nuthNy7NbcNb2JeVLD1BU=; h=Date:From:To:CC:Subject:References:In-Reply-To:From; b=WRdNWYhsNZkBsiP3eggF54QNOzxEVtuk+c/POmDngvR4Pq7NC/Q54pibR4oSc3k6w 6OJ9e5R18950vXtPt++fUo2tQXU8z8Dw9vjapGmg6IQDwtLkpCpH7YmaIGlBN1dRMa q/TVcNn7crijt7MB5rwVsLkqVvFD2S0r/jLQGfF0=
Received: from mail1.trendhosting.net ([127.0.0.1]) by localhost (thp003.trendhosting.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id lRIsroaT2OPm; Sat, 21 Nov 2015 07:38:50 +0000 (GMT)
Message-ID: <56501F88.6090707@pocock.pro>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=pocock.pro; s=mail; t=1448091530; bh=5X89FrVjNYi/Ve5mer0Fn8nuthNy7NbcNb2JeVLD1BU=; h=Date:From:To:CC:Subject:References:In-Reply-To:From; b=a82bMloHKcFBdwuF+Z4FHri6gumrJx5EriILIEL1jajqcgT9Y2ofcvsWV7Bp4hQjN 9roUbC1rFAvQ9CmK83NHjwE73/r2vV6vJHqMQ9XiQdsYJq4XUDoRU6oPznainWFeTH /5loIZ7Vox8LSawjOcsGtSo1Ae5B7WXhXQHL+HPw=
Date: Sat, 21 Nov 2015 08:38:48 +0100
From: Daniel Pocock <daniel@pocock.pro>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Icedove/31.8.0
MIME-Version: 1.0
To: Arc Riley <arcriley@gmail.com>
References: <20151030201307.2F2AB321F8@daniel1.office.readytechnology.co.uk> <564F8311.5010709@ik.nu> <CAKHUCzzRDsTYaW9a4+pABVsA7wKBuAMyp+pCHD6Y8Evjgd_vHA@mail.gmail.com> <56500558.3030805@pocock.pro> <CAHhipD9siAa02=ae=Au=xwn7-jx0Q+Ong2TYsePeOgpUKp4n1g@mail.gmail.com>
In-Reply-To: <CAHhipD9siAa02=ae=Au=xwn7-jx0Q+Ong2TYsePeOgpUKp4n1g@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------020200090407040108090807"
Archived-At: <http://mailarchive.ietf.org/arch/msg/xmpp/rZA9Qy8dva3GnFFPXwuOBZ-qgVg>
Cc: XMPP Standards <standards@xmpp.org>, Jabber/XMPP software development list <jdev@jabber.org>, XMPP Working Group <xmpp@ietf.org>, XSF Members <members@xmpp.org>, Ralph Meijer <ralphm@ik.nu>, XMPP Summit <summit@xmpp.org>
Subject: Re: [xmpp] [Summit] Fwd: [jdev] [CFP] FOSDEM 2016, RTC devroom, speakers, volunteers neeeded
X-BeenThere: xmpp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: XMPP Working Group <xmpp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xmpp>, <mailto:xmpp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xmpp/>
List-Post: <mailto:xmpp@ietf.org>
List-Help: <mailto:xmpp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xmpp>, <mailto:xmpp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 21 Nov 2015 07:38:58 -0000

On 21/11/15 07:02, Arc Riley wrote:
> I'm on email, it did not go to spam.

Can anybody else comment on whether they got it or not?

Does anybody who did or did not receive it see any headers indicating
how Google's spam filters are classifying the message?

I'm hearing far too many reports of these problems these days.  Somebody
suggested it may be triggered by 4 of the letters in my surname,
although I feel lucky not be in the same situation as these people:

http://www.theguardian.com/technology/2015/nov/18/facebook-thinks-im-a-terrorist-woman-named-isis-has-account-disabled

v2.23.0 | Report a Bug | By Email