Apparently, it remains a secret...
On Fri, Jul 15, 2016 at 9:58 AM, Alan Bourke alanpbourke@fastmail.fm wrote:
Any Windows 10 users might find this useful:
-- Alan Bourke alanpbourke (at) fastmail (dot) fm
I poked around at your messages headers to figure out if you forgot to paste the link (which I do frustratingly often) or if some evil entity along the way snipped it out, and came across these curious headers:
Received-SPF: pass (google.com: domain of profoxtech-bounces@leafe.com designates 104.236.203.188 as permitted sender) client-ip=104.236.203.188; Authentication-Results: mx.google.com; dkim=neutral (body hash did not verify) header.i=@fastmail.fm; dkim=neutral (body hash did not verify) header.i=@messagingengine.com; spf=pass (google.com: domain of profoxtech-bounces@leafe.com designates 104.236.203.188 as permitted sender) smtp.mailfrom=profoxtech-bounces@leafe.com Received: from mail.leafe.com (localhost [127.0.0.1])
by mail.leafe.com (Postfix) with ESMTP id 9114D1204C9;
Fri, 15 Jul 2016 08:59:02 -0500 (CDT) Authentication-Results: mail.leafe.com; dkim=fail reason="verification failed; unprotected key" header.d=fastmail.fm header.i=@fastmail.fm header.b=jtCPR0aI; dkim-adsp=unknown (unprotected policy); dkim-atps=neutral X-Original-To: profoxxtproxynn7@leafe.com
That's new.