Mail goes in gmail spam

Hi, I tried several digital ocean droplet with nameserver directly on it, and each time my emails went in gmail spam folder. I don’t understand why :frowning:
My DKIM, SPF and DMarc are good and I’m getting a 10/10 on mail-tester.com.

Here’s the email i’m getting on GMAIL.

Delivered-To: receiver@gmail.com
Received: by 10.25.217.205 with SMTP id q196csp275006lfg;
        Thu, 20 Aug 2015 14:53:57 -0700 (PDT)
X-Received: by 10.180.103.132 with SMTP id fw4mr205433wib.52.1440107637864;
        Thu, 20 Aug 2015 14:53:57 -0700 (PDT)
Return-Path: <me@domainname.me>
Received: from domainname.me (domainname.me. [46.101.178.47])
        by mx.google.com with ESMTPS id s4si10888256wjx.53.2015.08.20.14.53.57
        for <receiver@gmail.com>
        (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
        Thu, 20 Aug 2015 14:53:57 -0700 (PDT)
Received-SPF: pass (google.com: domain of me@domainname.me designates 46.101.178.47 as permitted sender) client-ip=46.101.178.47;
Authentication-Results: mx.google.com;
       spf=pass (google.com: domain of me@domainname.me designates 46.101.178.47 as permitted sender) smtp.mailfrom=me@domainname.me;
       dkim=pass header.i=@domainname.me;
       dmarc=pass (p=QUARANTINE dis=NONE) header.from=domainname.me
Received: from authenticated-user (domainname.me [46.101.178.47])
	(using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by domainname.me (Postfix) with ESMTPSA id E9B0914393B
	for <receiver@gmail.com>; Thu, 20 Aug 2015 17:53:26 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=domainname.me;
	s=mail; t=1440107606;
	bh=VZRhXwaha5p5tg+FPjJOwO8l4B1thv2RYUFwB4TD+VE=;
	h=Date:From:To:Subject:From;
	b=ZjN800HXr0X8C9MzwfxC7217KCAh5W4w+LIKXnjLGwbGfKsTMgWI2MKmMKBBo59nr
	 hob/YgAuh1panXVSVFMTpvy6M58Akb8WCfUDK4m/sjW1pZvB2yrSGxQoAOZsDdSNtG
	 RAgkFw/a4qrBwsbSQiX/h38gF5gA6bOEu5ovEK0RQ70XRziAeCUzidYtGURPShrTtj
	 WemhFwbu5IkpZsi4NdAri6E8U/feZruaZ2SjBePjR9bPptcqlFVfsDGYcuZoY3rHE/
	 P87TFbZS74S0zW/7o0ACQ/ReWs/TJ0SvrnxcJVh8+3TL/9g+xngQ2qys8LmBdovllR
	 AqDn/oi4eeDpA==
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8;
 format=flowed
Content-Transfer-Encoding: 8bit
Date: Thu, 20 Aug 2015 23:53:26 +0200
From: Geoffrey <me@domainname.me>
To: receiver@gmail.com
Subject: Hi here's my sub
Message-ID: <e2554a325d2cdd54036c5c3acb516f04@domainname.me>
X-Sender: me@domainname.me

Hi guy tell me if it work.

-- 
Geoffrey

Thank you very much :slight_smile:

Do you have DKIM_SIGNED on the website (category SpamAssassin) you said ?

Hi,

yes my message is DKIM signed :

-0.1	DKIM_SIGNED	Message has a DKIM or DK signature, not necessarily valid
0.1	DKIM_VALID	Message has at least one valid DKIM or DK signature
0.1	DKIM_VALID_AU	Message has a valid DKIM or DK signature from author's domain
0.55	RP_MATCHES_RCVD	Envelope sender domain matches handover relay domain
0.001	SPF_HELO_PASS	SPF: HELO matches SPF record
0.001	SPF_PASS	SPF: sender matches SPF record

I use the Gmail Postmaster tools to monitor my domain to ensure there are no issues on the gmail service. Seems to work pretty well. Almost all the big mail providers have some version of this. The AOL one for example is nice as it will email me if anyone on AOL ever hits the spam button on an email from my domain. Check it out.

https://gmail.com/postmaster/

I use it too. But it doesn’t display me anything. :frowning:

However WTF ? Am I the only one having this problem using a Digital Ocean droplet + Mail in a Box ?
I use several domains + ip always the same problem…

Can someone help me ?..

Thank in advance :wink:

well I just did the same thing, I sent an email to my gmail address using the same subject and body as you did, thinking maybe google is using that word sequence to flag it, but it did not flag mine as spam. My headers look identical to yours, so that’s a weird one. Did you verify your PTR record?

I guess there is no PTR record for that IP, so that may be the issue:
http://mxtoolbox.com/SuperTool.aspx?action=ptr%3A46.101.178.47&run=toolpage

The issue here is that most of DigitalOcean IP’s are use for spam purposes.
Most of the time, you used a second hand IP that was use for spamming before.

I have the same issue also, and after switching to Vultr VPS problem solved.

Thank you very much for your help :slight_smile:
@RoldanLT certainly, I decided to change my host to gandi and now it works like a charm.

@usachris Thanks for your test ! In fact when you tried the PTR record I already had change my host (so my ip too).
Thank you !

Switching to Vultr won’t prevent the problem, both DO and VULTR have a high % of IPs blacklisted…
The trick is to check the IP they give you, and if it is blacklisted, create another instance before you purge the one you have (otherwise they will give you the same IP)

.
.
.

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.