Question

Why the emails are going to spam? Exim VestaCP CentOS 7.3.1611 Bangalore [BLR1]

EMAILS ARE GOING TO SPAM.

I have setup VestaCP on our CentOS droplet. Exim is the running mail server. BANGALORE, INDIA

10/10 on mail-tester.com

  • SPF RECORD - PASS
  • DKIM - PASS
  • A RECORDS - PASS
  • MX RECORD - PASS
  • Reverse DNS - PTR RECORD - PASS
  • DMARC - OK

STILL, EMAILS ARE GOING TO RECEIVER SPAM.

What are we missing? Here is the head of the mail: " Received: by mail-tester.com (Postfix, from userid 500) id D34C99FD23; Thu, 15 Jun 2017 17:25:40 +0200 (CEST) Authentication-Results: mail-tester.com; dkim=temperror (0-bit key; unprotected) header.d=fitbox.io header.i=@fitbox.io header.b=fvomWH/g; dkim-atps=neutral X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mail-tester.com X-Spam-Level: X-Spam-Status: No/-0.1/5.0 X-Spam-Test-Scores: DKIM_SIGNED=0.1,DKIM_VALID=-0.1,DKIM_VALID_AU=-0.1, SPF_PASS=-0.001,T_RP_MATCHES_RCVD=-0.01 X-Spam-Last-External-IP: 139.59.32.41 X-Spam-Last-External-HELO: server.fitbox.io X-Spam-Last-External-rDNS: server.fitbox.io X-Spam-Date-of-Scan: Thu, 15 Jun 2017 17:25:40 +0200 X-Spam-Report: * -0.0 SPF_PASS SPF: sender matches SPF record * -0.0 T_RP_MATCHES_RCVD Envelope sender domain matches handover relay *
domain * -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.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily * valid Received-SPF: Pass (sender SPF authorized) identity=mailfrom; client-ip=139.59.32.41; helo=server.fitbox.io; envelope-from=test@fitbox.io; receiver=web-eq1wh@mail-tester.com DMARC-Filter: OpenDMARC Filter v1.3.1 mail-tester.com 292BF9F747 Authentication-Results: mail-tester.com; dmarc=pass header.from=fitbox.io Authentication-Results: mail-tester.com; dkim=temperror (0-bit key; unprotected) header.d=fitbox.io header.i=@fitbox.io header.b=fvomWH/g; dkim-atps=neutral Received: from server.fitbox.io (server.fitbox.io [139.59.32.41]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail-tester.com (Postfix) with ESMTPS id 292BF9F747 for web-eq1wh@mail-tester.com; Thu, 15 Jun 2017 17:25:38 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=fitbox.io; s=mail; h=Message-ID:From:Date:Content-Transfer-Encoding:Content-Type: MIME-Version:Subject:To:Sender:Reply-To:Cc:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID : In-Reply-To:References:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=1Ub7OfiWvh6z5PFWvqGZs2WIkpHP+/FbenAvXIbIBIk=; b=fvomWH/gXhDo2R/gVp+zvtCCma n/vlzOnTQAH8lXwT88IK23iZo3ZxWE/ZRF1P9rnWe9MqpFV0LdjHJxWt74b8I9xhNt+NgTLFkSe 73 EI0u4BrQeobsHqemJiT4rcOqifFD5Q/SDUlHs1IGOJr+zYpTQMh/1nqwK7iOjGD51hWQ=; Received: from admin by server.fitbox.io with local (Exim 4.89) (envelope-from test@fitbox.io) id 1dLWeO-0003y1-OA for web-eq1wh@mail-tester.com; Thu, 15 Jun 2017 20:55:36 +0530 To: web-eq1wh@mail-tester.com Subject: Helllo 1245 Welcome to FitBox X-PHP-Originating-Script: 0:rcube.php MIME-Version: 1.0 Date: Thu, 15 Jun 2017 20:55:36 +0530 From: test@fitbox.io Message-ID: 6ee77c5a7ace86baaad58d363f08ce24@fitbox.io X-Sender: test@fitbox.io User-Agent: Roundcube Webmail/1.2.5 Return-Path: test@fitbox.io Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit "

Thanks in Advance for the help…

Subscribe
Share

Submit an answer
You can type!ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

@hybridboy11

Do you have the headers from the recipient that we can take a look at so we can see what’s being flagged on their end?

Checking your domain, everything looks to be order and when testing the IP against blacklists, you’re clear so that shouldn’t be an issue either. Overall everything looks good, though having the headers form the recipient would allow us to take a closer look at what may actually be going on since you’re showing a perfect score on the mail test.

**Here is the head: ** Delivered-To: prasham.bhuta@gmail.com Received: by 10.37.173.70 with SMTP id l6csp1232491ybe; Thu, 15 Jun 2017 23:36:14 -0700 (PDT) X-Received: by 10.84.217.152 with SMTP id p24mr10761686pli.206.1497594974532; Thu, 15 Jun 2017 23:36:14 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1497594974; cv=none; d=google.com; s=arc-20160816; b=ruidIHxNyxw/wO6e+amAp43FNeKUx6oy8jo+jSGA+pTNxf13VtL+RYM3bshAdV29Yz gyAVnx25TntbBVtNKZVPHYl/vLthAojHHLoohqLVjHTUstIZQXut5fzWeXwuPUkRIf0s D6vggHiM+I+85r1JClhYYY9SrVXHzD8mNmoXD7YHrk8AtsoRysLm8DsZJCiRiYkf3Btu E0YJFsBv4F8iDNocFa7qKeGC14ElaXUwRBS7+4uDcP66PgW5z2GvZqE1FZLcfRkcQXTB b0xUnzIJ/jhuyrymPmNLg3sagHVprqRUs8cSlyl5lxYdClZCUm4HYJToQUc1Bhq4zdVL jwow== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=user-agent:message-id:from:date:content-transfer-encoding :mime-version:subject:to:dkim-signature:arc-authentication-results; bh=o+KZo+UU7YRtVmP+WPz6LPhjsSegQ2JUGef5uOkbxRM=; b=LosUU7Lf04uqn8vvw1GCF3kGFxitYI7FWyTVMcPl8QAdOXD/lDSKRKlLLg68u4OjEe OXyoXT5Gp5CK1J2JHwVjYeFxrCOjcuyifqL3xqeRbtH0MzJPZqYyhFhyYzH1uryvi3Wp 8Z71pHQWS+vPtB21s3432XIg4zcpYhsWpbzp+h5Q9aYqeA7KuV0ipXu1RJFxIqikhC5d jz8uAHHMaDs/lZe57icUVYP3pjQ6dbnAqc92hoOUvatccRRUabPD7B78+D+Ahf/wwYwD j/yD3xglANGKCWF5zAQkuQTY5tBPhfjaNHitZsjql21Xra+8YamnLUxghnrQEO2k9GfC CUwg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@fitbox.io header.b=hdj/dTFN; spf=pass (google.com: domain of test@fitbox.io designates 139.59.32.41 as permitted sender) smtp.mailfrom=test@fitbox.io; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=fitbox.io Return-Path: test@fitbox.io Received: from server.fitbox.io (server.fitbox.io. [139.59.32.41]) by mx.google.com with ESMTPS id m28si1174722pli.427.2017.06.15.23.36.13 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 15 Jun 2017 23:36:14 -0700 (PDT) Received-SPF: pass (google.com: domain of test@fitbox.io designates 139.59.32.41 as permitted sender) client-ip=139.59.32.41; Authentication-Results: mx.google.com; dkim=pass header.i=@fitbox.io header.b=hdj/dTFN; spf=pass (google.com: domain of test@fitbox.io designates 139.59.32.41 as permitted sender) smtp.mailfrom=test@fitbox.io; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=fitbox.io DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=fitbox.io; s=mail; h=Message-ID:From:Date:Content-Transfer-Encoding:Content-Type: MIME-Version:Subject:To:Sender:Reply-To:Cc:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: In-Reply-To:References:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=o+KZo+UU7YRtVmP+WPz6LPhjsSegQ2JUGef5uOkbxRM=; b=hdj/dTFNMtPQfn33z4oxDI4A2I 3hOV4JpxFKt6Nag0rLomDiMygXGF9y6F44m1t0NbzmULUEWQgOenNhgzBUBgKqKXPbWAF0WfTfGjZ a9M32zD/RfQTqGYYYkLvlkK3Ynr3liIcw0cXU/XFKuqmc2yf1yWjqOWnU0CzmmiUGaZo=; Received: from admin by server.fitbox.io with local (Exim 4.89) (envelope-from test@fitbox.io) id 1dLkrb-0005V7-Dg; Fri, 16 Jun 2017 12:06:11 +0530 To: prasham.bhuta@gmail.com, hybridboy11@gmail.com, web-weolu@mail-tester.com Subject: Mail Testing 123212 X-PHP-Originating-Script: 0:rcube.php MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Fri, 16 Jun 2017 12:06:11 +0530 From: test@fitbox.io Message-ID: ebcefa4e8ac86a3f067eee2d3cc9f529@fitbox.io X-Sender: test@fitbox.io User-Agent: Roundcube Webmail/1.2.5

Heety Guj