Author Topic: Emails/Mails going in SPAM  (Read 8577 times)

0 Members and 1 Guest are viewing this topic.

Offline
*
Emails/Mails going in SPAM
« on: December 07, 2016, 07:48:27 AM »
Dear All,

Am new to Centos Web Panel as well as to VPS, I mean I have never uses VPS or Centos Web Panel before, I do have some knowledge of cpanel though.

SO recently i bought this vps with Centos Web panel.

Everything is fine except the emails part, No matter what i do my emails end up in spam.

As am not well worsed with cwp(Centos Web Panel) I have no idea what setting ot do so that my emails gets delivered to inbox and not spam

Below are my dns settings for my website.


ahmhao.com.      86400      IN      NS      ns1.ahmhao.com.
ahmhao.com.      86400      IN      NS      ns2.ahmhao.com.
ahmhao.com.      0      IN      A      216.107.149.108
localhost.ahmhao.com.      0      IN      A      127.0.0.1
ahmhao.com.      0      IN      MX      5      ahmhao.com.
mail      0      IN      CNAME      ahmhao.com.
www      0      IN      CNAME      ahmhao.com.
ftp      0      IN      CNAME      ahmhao.com.
;      Add      additional            below      this      line
default._domainkey      14400      IN      TXT      "v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDU+1uAkb5utSqF4zqIi44J0UhrUFTtVyIcLP2nglySOSGBVMUV8ksl19PaWQ3VZSstXtYBFBvx9tp6QHx3jJIOqaYt/ijdA4jmTWzuru4t3nR81Jee+tMK+rkPxvVoJSCitRTogJ8bfy0SkQYwcYWbk+4bT5FmUcRmQ9uSgG3h1wIDAQAB"
ns1.ahmhao.com.      86400      IN      A      216.107.149.108
ns2.ahmhao.com.      86400      IN      A      216.107.149.108
ahmhao.com.      86400      IN      TXT      "v=spf1 mx a ip4:216.107.149.108 mx:ahmhao.com"


Is the above right ? or do i need to make any changes so as to get my mails delivered to inbox, or do i have to do some additional configuration that am not aware of ? I contacted my vps provider but those guys are just delaying it since past 10 days.

Just because this email issue I had to deactivate the registration on my wordpress website which is hosted on this vps

Ps: before this vps i was on shared hosting, which delivered my emails to inbox and not spam, if that helps

Any help will be appreciated

Awaiting reply from anyone

Rajan Singh

Offline
***
Re: Emails/Mails going in SPAM
« Reply #1 on: December 07, 2016, 09:44:06 AM »
Dear Rajan,

Still not clear for me,
all email from *@ahmhao.com went to spam fordet at other side?
or all email from outside, deliverred  to span folder  at mailbox @ahmhao.com?

Offline
*
Re: Emails/Mails going in SPAM
« Reply #2 on: December 07, 2016, 10:18:37 AM »
Dear Jae,

Thanks for deciding to help me out

all email from *@ahmhao.com went to spam folder at other side

Regards

Offline
***
Re: Emails/Mails going in SPAM
« Reply #3 on: December 08, 2016, 09:09:25 AM »
Dear Rajan,

did try send email  both with webmail and email client?  like outlook
if you dont mind, pls send email to support@curemail.net, i will check log from my server side...


Offline
*
Re: Emails/Mails going in SPAM
« Reply #4 on: December 08, 2016, 09:46:08 AM »
I don't use any email client, But i do use webmail, I have made 3 email accounts, and tested it. Mail from all these email ids ends up in spam folder of receiver(tested on gmail and yahoo)

Also my website in running on wordpress so tried sending a test mail from WP SMTP MAIL plugin also and their test emails also ends up in spam :/

I have sent you a test email from noreply@ahmhao.com, please check.

PS : I still have 3 months package left on my shared hosting plan which i dont use as i have switched to this vps plan with a new hoster. So i tested my shared hosting and sent a test mail from them to gmail and yahoo and both ended up in inbox. That should clear that there is nothing wrong with my domain but some settings from cwp. Jus sharing this might help

Awaiting reply
Regards
Rajan
« Last Edit: December 08, 2016, 09:48:20 AM by rajanxsingh »

Offline
**
Re: Emails/Mails going in SPAM
« Reply #5 on: December 08, 2016, 08:24:58 PM »
Hi,

Can you check does your service like opendkim and spf works correctly, seems like your bind config looks fine but does it really signs them cos dkim must have open port to check its all legit.

I used this tools to check my mail server too:

https://www.port25.com/authentication-checker/

Regards

Offline
*
Re: Emails/Mails going in SPAM
« Reply #6 on: December 12, 2016, 02:18:16 PM »
Hi,

I did send the eamil and got below results, let me know if need to do anything. Thanks in advance



==================================================================================
Authentication Report
From    auth-results@verifier.port25.comAdd contact    Date    
<- <<- ->   []

This message is an automatic response from Port25's authentication verifier
service at verifier.port25.com.  The service allows email senders to perform
a simple check of various sender authentication mechanisms.  It is provided
free of charge, in the hope that it is useful to the email community.  While
it is not officially supported, we welcome any feedback you may have at
<verifier-feedback@port25.com>.

Thank you for using the verifier,

The Port25 Solutions, Inc. team

==========================================================
Summary of Results
==========================================================
SPF check:          pass
DomainKeys check:   neutral
DKIM check:         pass
SpamAssassin check: ham

==========================================================
Details:
==========================================================

HELO hostname:  server.ahmhao.com
Source IP:      216.107.149.108
mail-from:      noreply@ahmhao.com

----------------------------------------------------------
SPF check details:
----------------------------------------------------------
Result:         pass
ID(s) verified: smtp.mailfrom=noreply@ahmhao.com
DNS record(s):
    ahmhao.com. SPF (no records)
    ahmhao.com. 86400 IN TXT "v=spf1 mx a ip4:216.107.149.108 mx:ahmhao.com"
    ahmhao.com. 0 IN MX 5 ahmhao.com.
    ahmhao.com. 0 IN A 216.107.149.108

----------------------------------------------------------
DomainKeys check details:
----------------------------------------------------------
Result:         neutral (message not signed)
ID(s) verified: header.From=noreply@ahmhao.com
DNS record(s):

----------------------------------------------------------
DKIM check details:
----------------------------------------------------------
Result:         pass (matches From: noreply@ahmhao.com)
ID(s) verified: header.d=ahmhao.com
Canonicalized Headers:
    date:Mon,'20'12'20'Dec'20'2016'20'19:52:00'20'+0530'0D''0A'
    from:noreply@ahmhao.com'0D''0A'
    to:<check-auth2@verifier.port25.com>'0D''0A'
    subject:Test'0D''0A'
    dkim-signature:v=1;'20'a=rsa-sha256;'20'c=relaxed/simple;'20'd=ahmhao.com;'20's=default;'20't=1481552520;'20'bh=fdkeB/A0FkbVP2k4J4pNPoeWH6vqBm9+b0C3OY87Cw8=;'20'h=Date:From:To:Subject;'20'b=

Canonicalized Body:
    Test'0D''0A'
   

DNS record(s):
    default._domainkey.ahmhao.com. 14400 IN TXT "v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDU+1uAkb5utSqF4zqIi44J0UhrUFTtVyIcLP2nglySOSGBVMUV8ksl19PaWQ3VZSstXtYBFBvx9tp6QHx3jJIOqaYt/ijdA4jmTWzuru4t3nR81Jee+tMK+rkPxvVoJSCitRTogJ8bfy0SkQYwcYWbk+4bT5FmUcRmQ9uSgG3h1wIDAQAB"

Public key used for verification: default._domainkey.ahmhao.com (1024 bits)

NOTE: DKIM checking has been performed based on the latest DKIM specs
(RFC 4871 or draft-ietf-dkim-base-10) and verification may fail for
older versions.  If you are using Port25's PowerMTA, you need to use
version 3.2r11 or later to get a compatible version of DKIM.

----------------------------------------------------------
SpamAssassin check details:
----------------------------------------------------------
SpamAssassin v3.4.0 (2014-02-07)

Result:         ham  (-1.8 points, 5.0 required)

 pts rule name              description
---- ---------------------- --------------------------------------------------
-0.0 SPF_PASS               SPF: sender matches SPF record
 1.2 RCVD_NUMERIC_HELO      Received: contains an IP address used for HELO
-3.0 RP_MATCHES_RCVD        Envelope sender domain matches handover relay domain
-1.9 BAYES_00               BODY: Bayes spam probability is 0 to 1%
                            [score: 0.0000]
-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
-0.1 DKIM_VALID             Message has at least one valid DKIM or DK signature
 1.1 FSL_HELO_BARE_IP_2     No description available.
 1.0 BODY_SINGLE_WORD       Message body is only one word (no spaces)

==========================================================
Explanation of the possible results (from RFC 5451)
==========================================================

SPF and Sender-ID Results
=========================

"none"
      No policy records were published at the sender's DNS domain.

"neutral"
      The sender's ADMD has asserted that it cannot or does not
      want to assert whether or not the sending IP address is authorized
      to send mail using the sender's DNS domain.

"pass"
      The client is authorized by the sender's ADMD to inject or
      relay mail on behalf of the sender's DNS domain.

"policy"
     The client is authorized to inject or relay mail on behalf
      of the sender's DNS domain according to the authentication
      method's algorithm, but local policy dictates that the result is
      unacceptable.

"fail"
      This client is explicitly not authorized to inject or
      relay mail using the sender's DNS domain.

"softfail"
      The sender's ADMD believes the client was not authorized
      to inject or relay mail using the sender's DNS domain, but is
      unwilling to make a strong assertion to that effect.

"temperror"
      The message could not be verified due to some error that
      is likely transient in nature, such as a temporary inability to
      retrieve a policy record from DNS.  A later attempt may produce a
      final result.

"permerror"
      The message could not be verified due to some error that
      is unrecoverable, such as a required header field being absent or
      a syntax error in a retrieved DNS TXT record.  A later attempt is
      unlikely to produce a final result.


DKIM and DomainKeys Results
===========================

"none"
      The message was not signed.

"pass"
      The message was signed, the signature or signatures were
      acceptable to the verifier, and the signature(s) passed
      verification tests.

"fail"
      The message was signed and the signature or signatures were
      acceptable to the verifier, but they failed the verification
      test(s).

"policy"
      The message was signed but the signature or signatures were
      not acceptable to the verifier.

"neutral"
      The message was signed but the signature or signatures
      contained syntax errors or were not otherwise able to be
      processed.  This result SHOULD also be used for other
      failures not covered elsewhere in this list.

"temperror"
      The message could not be verified due to some error that
      is likely transient in nature, such as a temporary inability
      to retrieve a public key.  A later attempt may produce a
      final result.

"permerror"
      The message could not be verified due to some error that
      is unrecoverable, such as a required header field being
      absent. A later attempt is unlikely to produce a final result.


==========================================================
Original Email
==========================================================

Return-Path: <noreply@ahmhao.com>
Received: from server.ahmhao.com (216.107.149.108) by verifier.port25.com id h9qo2220i3gp for <check-auth2@verifier.port25.com>; Mon, 12 Dec 2016 09:11:45 -0500 (envelope-from <noreply@ahmhao.com>)
Authentication-Results: verifier.port25.com; spf=pass smtp.mailfrom=noreply@ahmhao.com
Authentication-Results: verifier.port25.com; domainkeys=neutral (message not signed) header.From=noreply@ahmhao.com
Authentication-Results: verifier.port25.com; dkim=pass (matches From: noreply@ahmhao.com) header.d=ahmhao.com
Received: from 216.107.149.108 (localhost [127.0.0.1])
   by server.ahmhao.com (Postfix) with ESMTPA id C35186475
   for <check-auth2@verifier.port25.com>; Mon, 12 Dec 2016 14:22:00 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ahmhao.com;
   s=default; t=1481552520;
   bh=fdkeB/A0FkbVP2k4J4pNPoeWH6vqBm9+b0C3OY87Cw8=;
   h=Date:From:To:Subject;
   b=VJ8wfOwOrdp7s/T6Zi5YpgFJk7FyHB2Cn6mA4tCjlMboXEAEpXK8188yttejoBi2M
    BhHbQ9vOkD9GhWMD3P+GIiSFbaZqYVkxXp8bAyuWv4DQs0q3I9D24csarS81l1/Ift
    etnxtzvNCT+WkPpV+6gI5SgY9D7G0fbiGJPyEjUY=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8;
 format=flowed
Content-Transfer-Encoding: 7bit
Date: Mon, 12 Dec 2016 19:52:00 +0530
From: noreply@ahmhao.com
To: <check-auth2@verifier.port25.com>
Subject: Test
Message-ID: <75702794b527e73152aca54afae82f25@ahmhao.com>
X-Sender: noreply@ahmhao.com
User-Agent: Roundcube Webmail/0.8.5

Test
===================================================================================