Emails are being delivered as spam to Gmail?

Reece asked:

for the last 6 weeks (yes, that long) I’ve been struggling to successfully deliver emails to Gmail accounts.

For some reason, every single email that is sent from our domain is flagged as spam by Gmail – it started happening when we moved from a shared host to a dedicated host.

I’ve configured SPF Records, Domain Keys and even DMARC records- however emails are still being delivered as spam, no matter the contents.

I’ve included my latest email headers below and any help would be greatly appreciated.

Delivered-To: evolutionvapingtest@gmail.com
Received: by 10.13.222.196 with SMTP id h187csp2343299ywe;
        Mon, 7 Dec 2015 06:05:44 -0800 (PST)
X-Received: by 10.112.39.5 with SMTP id l5mr13509340lbk.101.1449497143867;
        Mon, 07 Dec 2015 06:05:43 -0800 (PST)
Return-Path: <sales@evolutionvaping.co.uk>
Received: from evolutionvaping.co.uk (blue1095.server-cp.com. [212.48.74.96])
        by mx.google.com with ESMTPS id p62si16227395lfb.210.2015.12.07.06.05.43
        for <evolutionvapingtest@gmail.com>
        (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
        Mon, 07 Dec 2015 06:05:43 -0800 (PST)
Received-SPF: pass (google.com: domain of sales@evolutionvaping.co.uk designates 212.48.74.96 as permitted sender) client-ip=212.48.74.96;
Authentication-Results: mx.google.com;
       spf=pass (google.com: domain of sales@evolutionvaping.co.uk designates 212.48.74.96 as permitted sender) smtp.mailfrom=sales@evolutionvaping.co.uk;
       dkim=pass header.i=@evolutionvaping.co.uk;
       dmarc=pass (p=NONE dis=NONE) header.from=evolutionvaping.co.uk
Received: from localhost (evolutionvaping.co.uk [212.48.74.96])
    by blue1095.server-cp.com (Postfix) with ESMTPA id D7828A214F9
    for <evolutionvapingtest@gmail.com>; Mon,  7 Dec 2015 14:05:42 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.10.3 blue1095.server-cp.com D7828A214F9
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;
    d=evolutionvaping.co.uk; s=default; t=1449497142;
    bh=6aPl9HaCmvT9+lTZm8pj9mvVc2xOkR7awn27DmjT4p4=;
    h=To:Subject:From:Date:From;
    b=aMRtPVCRmk39ezowrn2Zh2qaQHJO9OJPdaIKC/cXs1/lUAoFzXnyMN53Pd+hJNMea
     FzoKt4V6mDovCwUXzJuGJQBxxwmyWNM0euoTzvg76SwvgtIM8bHS0zgzG+5WIvvVtW
     hHw1bak4UrNSKNuwaqWgJxpAJeJphr1v51J6NkjY=
To: =?utf-8?B?UmVlY2UgTSBWYXVnaGFu?= <evolutionvapingtest@gmail.com>
Subject: =?utf-8?B?RXZvbHV0aW9uIFZhcGluZzogTmV3IE9yZGVyICMgMTAwMDE4NzI2?=
From: Evolution Vaping <sales@evolutionvaping.co.uk>
Date: Mon, 07 Dec 2015 14:05:42 +0000
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
MIME-Version: 1.0
Message-Id: <20151207140542.D7828A214F9@blue1095.server-cp.com>

I’ve hidden our IP’s and domain name for contingency, if you believe it is required please let me know and I can provide it

Regards

Edit: I’ve already followed every step on the linked question and my problem still exists – I feel like there’s a fault with the way our emails are configured, however I cannot pinpoint where we’re going wrong 🙁

My answer:


With the caveat that you have obfuscated some things in your email, and have not posted the complete message:

The only serious problem I see with what you have posted is that some of your headers have been RFC 2047-encoded.

To: =?utf-8?B?UmVlY2UgTSBWYXVnaGFu?= <evolutionvapingtest@gmail.com>
Subject: =?utf-8?B?RXZvbHV0aW9uIFZhcGluZyB8IFlvcmtzaGlyZSBWYXBlciB8IEZsYXZvdXIgb2YgdGhlIFdlZWs=?=

This is done when a header needs to contain non-ASCII characters. However, on decoding them, we see that there aren’t any non-ASCII characters, so there was no reason to encode them to begin with.

To: Reece M Vaughan <evolutionvapingtest@gmail.com>
Subject: Evolution Vaping | Yorkshire Vaper | Flavour of the Week

I’ve seen a couple of other messages where unnecessary encoding was used, also considered spam at Gmail. I recommend that you figure out what is doing this, and reconfigure it to encode headers only when absolutely necessary. To that end you may wish to visit our sister site Magento.


View the full question and answer on Server Fault.

Creative Commons License
This work is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License.