FYI, I'm not seeing a DKIM signature from the list server? (in gmail) Authentication-Results: mx.google.com; dkim=neutral (body hash did not verify) header.i=@toke.dk; spf=pass (google.com: best guess record for domain of bloat-bounces@lists.bufferbloat.net designates 2600:3c03::f03c:91ff:fe61:86ce as permitted sender) smtp.mailfrom= bloat-bounces@lists.bufferbloat.net; dmarc=fail (p=NONE dis=NONE) header.from=toke.dk Looks like lists.bufferbloat.net has an SPF record now though, yay :) On Sun, 30 Oct 2016 at 15:56 David Collier-Brown wrote: On 30/10/16 02:48 PM, Toke Høiland-Jørgensen wrote: > The mail server at lists.bufferbloat.net should now be DKIM-signing > outgoing email. This is a test of that; please ignore. :) > > -Toke > _______________________________________________ > Bloat mailing list > Bloat@lists.bufferbloat.net > https://lists.bufferbloat.net/listinfo/bloat I ran it through spamcop and it passed, so it's structurally OK. --dave A few lines make it look like you're experimenting (;-)) Received-SPF: none (domain of lists.bufferbloat.net does not designate permitted sender hosts) Received: from lists.bufferbloat.net (lists.bufferbloat.net [45.79.142.77]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by vmx5.spamcop.net (Postfix) with ESMTPS id 84FF3ED1CE for ; Sun, 30 Oct 2016 11:48:56 -0700 (PDT) X-Original-To: x Delivered-To: x -- David Collier-Brown, | Always do right. This will gratify System Programmer and Author | some people and astonish the rest davecb@spamcop.net | -- Mark Twain _______________________________________________ Bloat mailing list Bloat@lists.bufferbloat.net https://lists.bufferbloat.net/listinfo/bloat