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 05:47 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 45A881B3821 for <xmpp@ietfa.amsl.com>; Fri, 20 Nov 2015 21:47:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.302
X-Spam-Level:
X-Spam-Status: No, score=-1.302 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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 0xiDOG-YWAgK for <xmpp@ietfa.amsl.com>; Fri, 20 Nov 2015 21:47:09 -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 01A221B381F for <xmpp@ietf.org>; Fri, 20 Nov 2015 21:47:09 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mail1.trendhosting.net (Postfix) with ESMTP id B085E150C1; Sat, 21 Nov 2015 05:47:07 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=pocock.pro; s=mail; t=1448084827; bh=dP2/pF1upOfhviE7FjQVmA7Zylh7kaBzZ9vwLIqIMcg=; h=Date:From:To:CC:Subject:References:In-Reply-To:From; b=NhdcCdvEMasff1NW7bHSK61+Qvydb7as4qVvTyq4fo5vmWglEEvMKHuDWlpxvwkBw zgkvusfHbfSE8n7P1xfNwW6LM47BQ9+7Dw6Kr7shU6UqR3gvJpyazTHmvvzS5kI3y/ FEnRHCzfDEDifxc4oFTgabV2/ZWSeHvbQjA9A1+4=
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 VcWIcAczzeyE; Sat, 21 Nov 2015 05:47:05 +0000 (GMT)
Message-ID: <56500558.3030805@pocock.pro>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=pocock.pro; s=mail; t=1448084825; bh=dP2/pF1upOfhviE7FjQVmA7Zylh7kaBzZ9vwLIqIMcg=; h=Date:From:To:CC:Subject:References:In-Reply-To:From; b=uGdQtvhorgDgINGhnenxEQlPvLaw/s3+5VmlgCYzfwR4GQYz6ZF1rhGVbXGkSy/L3 w78xWvxEeaZB2OdhZIuyXuB9snG8vnv+ODDMQB7v111czn68lWfta/XaRXOZsKpQpO 6LHaZmUnsjBOPhfgcpyLIZUg9c250W/Ob01Sgu34=
Date: Sat, 21 Nov 2015 06:47:04 +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: XMPP Summit <summit@xmpp.org>, Ralph Meijer <ralphm@ik.nu>
References: <20151030201307.2F2AB321F8@daniel1.office.readytechnology.co.uk> <564F8311.5010709@ik.nu> <CAKHUCzzRDsTYaW9a4+pABVsA7wKBuAMyp+pCHD6Y8Evjgd_vHA@mail.gmail.com>
In-Reply-To: <CAKHUCzzRDsTYaW9a4+pABVsA7wKBuAMyp+pCHD6Y8Evjgd_vHA@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/xmpp/Gh5-OFoXZULtzab-6nnCtrNihv4>
Cc: XMPP Working Group <xmpp@ietf.org>, Jabber/XMPP software development list <jdev@jabber.org>, XMPP Standards <standards@xmpp.org>, XSF Members <members@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 05:47:10 -0000


On 20/11/15 23:32, Dave Cridland wrote:
> The original went straight into my Google spam folder.
> 
> Conspiracy theories welcome.
> 


I don't use gmail myself.  Could you contact the support team and ask
why this message was marked as spam and let me know so I can be more
careful writing messages like that in future?

Could you look at the message headers to see if there is any clue there
from the spam classifier?

May not be an anti-XMPP conspiracy though, it is a known problem for a
long time now that Google's spam filter is quite bad and they expect you
to spend a little bit of time working for them every day training their
spam filter:
http://danielpocock.com/unpaid-work-training-googles-spam-filters

Regards,

Daniel

v2.23.0 | Report a Bug | By Email