Author Topic: EMAIL SENT FROM CWP GOING TO SPAM  (Read 15447 times)

0 Members and 1 Guest are viewing this topic.

Offline
*
EMAIL SENT FROM CWP GOING TO SPAM
« on: July 08, 2019, 07:37:49 AM »
Hi,

I have configured my CWP on an AWS EC2 Instance,I have configured my rPTR records as well,Also DKIM and SPF records are enabled on server,
Still The emails i m sending from my cwp server are going to spam on gmail,yahoo and other big email clients,
Can anyone please recommend what should be done?

Re: EMAIL SENT FROM CWP GOING TO SPAM
« Reply #1 on: July 08, 2019, 09:38:15 AM »
Have you checked the message source? Are SPF & DKIM actually being transmitted? If they are then you're doing better than me!
I have an open thread on the subject.

Offline
*
Re: EMAIL SENT FROM CWP GOING TO SPAM
« Reply #2 on: July 08, 2019, 11:37:55 AM »
Hi,

I have configured my CWP on an AWS EC2 Instance,I have configured my rPTR records as well,Also DKIM and SPF records are enabled on server,
Still The emails i m sending from my cwp server are going to spam on gmail,yahoo and other big email clients,
Can anyone please recommend what should be done?

Try this https://www.mail-tester.com/ and get back to me with the results.

Offline
***
Re: EMAIL SENT FROM CWP GOING TO SPAM
« Reply #3 on: July 08, 2019, 01:02:57 PM »
Use mxtollbox to generate and test spf, ptr , and _DMARC (use these too). I don't worry about dkim personally but the more the merrier.

I find if mxtollbox is used to generate and test and it says all ok, then I don't have too many deliverability problems.

Offline
*
Re: EMAIL SENT FROM CWP GOING TO SPAM
« Reply #4 on: July 08, 2019, 02:07:54 PM »
Your message is not signed with DKIM
This is the only error i m getting,
However i have enabled DKIM for my domain
Alos my score is 8.3

Hi,

I have configured my CWP on an AWS EC2 Instance,I have configured my rPTR records as well,Also DKIM and SPF records are enabled on server,
Still The emails i m sending from my cwp server are going to spam on gmail,yahoo and other big email clients,
Can anyone please recommend what should be done?

Try this https://www.mail-tester.com/ and get back to me with the results.

Offline
*
Re: EMAIL SENT FROM CWP GOING TO SPAM
« Reply #5 on: July 08, 2019, 02:18:11 PM »
This is a message source recieved on gmail id,


Delivered-To: noman.iqbal2092@gmail.com
Received: by 2002:adf:df07:0:0:0:0:0 with SMTP id y7csp2563338wrl;
        Mon, 8 Jul 2019 07:14:34 -0700 (PDT)
X-Google-Smtp-Source: APXvYqxbrS+PLF4WAUto85odafEpkQN3Tt93w15PzTD1D4jXOo835238KoR2RJ9AaZ1/YzV77cxI
X-Received: by 2002:a63:db4b:: with SMTP id x11mr23913765pgi.254.1562595274790;
        Mon, 08 Jul 2019 07:14:34 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; t=1562595274; cv=none;
        d=google.com; s=arc-20160816;
        b=P/3TTIVcXovT1/bH/LmQkJbx5PLJMimT3Kj+MhGFfRuNh1Uh0Zup4YTdW5iPq5pcTg
         hThgUnco1QVYwRie/sJSyAU0delfXnITG8bDt5rVGo0m0QOM0JQRd02i0SrTo7QAuGt0
         czBo8/ZU3wgdBfsNL1wQiPLqAR0T37s/BR8AU6mpR6OZul/3UA2Qfmti1j1LaWXok5Go
         cXMenjOhQRN+CpgGHTZjhconoeo9LZPIxCFjW+FL82rfKAFVvYKAqp5CiO1jVQU1oeZc
         f9Dfre0J6c7uts+Qlo33lm/JdT3TrKN3GerCavpNlmuE5/hEOoW+qXa6UxTCtP18NlVp
         JDJQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816;
        h=user-agent:message-id:subject:to:from:date
         :content-transfer-encoding:mime-version:dkim-signature;
        bh=3SBkjLY5an7S44WY5KF9I1KAOxG9ZX5VEVfj7GT8rwk=;
        b=iOBh2ANiB7Cfg1ogh7HPTpPcfjXAZp5gYQrcTyPXLRqnjgGb3A9j0xmIAEnkxYIqWS
         zZ9rHzyD1jYYAXdauLJ4BmOpCjhMsbaGUBmekw+Ga4PkJoVGZ7d0dwLA61QhRosO+UpF
         FLc7fy8McBcFMG0hm+yk1btHagUfT7QrpK9YREDnM8H6X3mDEmO0YiDmVd46y1DV4aSK
         rd5K7++dbzgPQ/IrNxOpAodJ2noHL9VHKjmNaVkUZcOTpo1/KuQEk9u1bbGCBEPMzLpT
         HdPwlpVfws+WJGpkP/nGGgoGJr7PRC7MRW5p6LpkzkmNXXkFlRytrzex5QtTO9e6qJ2L
         SsvA==
ARC-Authentication-Results: i=1; mx.google.com;
       dkim=pass header.i=@quickhire.io header.s=default header.b="feQ4L/ia";
       spf=pass (google.com: domain of test@quickhire.io designates 34.210.49.236 as permitted sender) smtp.mailfrom=test@quickhire.io;
       dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=quickhire.io
Return-Path: <test@quickhire.io>
Received: from webpanel.golpik.com (webpanel.golpik.com. [34.210.49.236])
        by mx.google.com with ESMTPS id y15si1117515pfe.199.2019.07.08.07.14.34
        for <noman.iqbal2092@gmail.com>
        (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
        Mon, 08 Jul 2019 07:14:34 -0700 (PDT)
Received-SPF: pass (google.com: domain of test@quickhire.io designates 34.210.49.236 as permitted sender) client-ip=34.210.49.236;
Authentication-Results: mx.google.com;
       dkim=pass header.i=@quickhire.io header.s=default header.b="feQ4L/ia";
       spf=pass (google.com: domain of test@quickhire.io designates 34.210.49.236 as permitted sender) smtp.mailfrom=test@quickhire.io;
       dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=quickhire.io
Received: from localhost (localhost [127.0.0.1]) by webpanel.golpik.com (Postfix) with ESMTPA id 067F052898C for <noman.iqbal2092@gmail.com>; Mon,
  8 Jul 2019 19:14:34 +0500 (PKT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=quickhire.io; s=default; t=1562595274; bh=3SBkjLY5an7S44WY5KF9I1KAOxG9ZX5VEVfj7GT8rwk=; h=Date:From:To:Subject; b=feQ4L/iaY2WXPQjyu7XEu0kzfejoVE1sItaIpsUCTbr/CVle/r3XkDdTHjwgaxRVV
    Mwj1hsCha+FkQ4IcpHlOQIeP83UBBxWz4ZaYqsKMpze1s0R6WKOBEUmke6on11DVwf
    WhgRvYIIJyxkQChY8fCzJ7arbzpBDTSQXjgPGQUY=
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
Content-Transfer-Encoding: 7bit
Date: Mon, 08 Jul 2019 19:14:34 +0500
From: test@quickhire.io
To: noman.iqbal2092@gmail.com
Subject: Testing
Message-ID: <a6b6bc82d094d193c73b0d8945b2ffd0@quickhire.io>
X-Sender: test@quickhire.io
User-Agent: Roundcube Webmail/1.2.3

gholpi

Offline
*
Re: EMAIL SENT FROM CWP GOING TO SPAM
« Reply #6 on: July 08, 2019, 02:19:42 PM »
I had previously DKIM turned off,

Now i have turned it on and still am getting score of 8.2
Emails are still going to spam,
can you please check source message i posted above

Hi,

I have configured my CWP on an AWS EC2 Instance,I have configured my rPTR records as well,Also DKIM and SPF records are enabled on server,
Still The emails i m sending from my cwp server are going to spam on gmail,yahoo and other big email clients,
Can anyone please recommend what should be done?

Try this https://www.mail-tester.com/ and get back to me with the results.

Offline
*
Re: EMAIL SENT FROM CWP GOING TO SPAM
« Reply #7 on: July 08, 2019, 03:00:17 PM »
Your email source is showing your dkim, spf & dmarc are passing, so that should not be an issue, have you check whether your ip is clean & clear from all rbls?, this is not really a cwp issue, it takes time to build ip reputation, took me months before i got 98% delivery straight to inbox rate for thousands of my users.

Offline
*
Re: EMAIL SENT FROM CWP GOING TO SPAM
« Reply #8 on: July 09, 2019, 10:31:36 AM »
I donot have any client shifted on cwp due to spam issue,so there is no emails generating right now,,would i need to move some clients here?so that emails start going then spam ratio will be decreased?
also my IP is clean on all Sites

Offline
*
Re: EMAIL SENT FROM CWP GOING TO SPAM
« Reply #9 on: July 09, 2019, 12:57:04 PM »
Spam Score depends on the language of the subject line and the text content too. If those are found spammy by google your emails will end up in spam.
Check the spamscore of your email here at https://spamscorechecker.com/

Offline
*
Re: EMAIL SENT FROM CWP GOING TO SPAM
« Reply #10 on: August 05, 2021, 09:37:09 AM »
I am having same problem.

My SPF and iprev and DKIM check all are okay

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
"iprev" check:      pass
DKIM check:         pass

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

HELO hostname:  server1.hostiko.in
Source IP:      139.59.43.122
mail-from:      info@quickwebworks.com

----------------------------------------------------------
SPF check details:
----------------------------------------------------------
Result:         pass
ID(s) verified: smtp.mailfrom=info@quickwebworks.com

DNS record(s):
    quickwebworks.com. 300 IN TXT "google-site-verification=jWjr_biMGrWjebqh4hDExUjcReP7d0UYGKs6UFQx3Zo"
    quickwebworks.com. 300 IN TXT "v-spf1 mx a"
    quickwebworks.com. 300 IN TXT "v=spf1 +a +mx +ip4:139.59.43.122 ~all"
    quickwebworks.com. 300 IN A 104.21.42.140
    quickwebworks.com. 300 IN A 172.67.162.127
    quickwebworks.com. 300 IN MX 0 server1.hostiko.in.
    server1.hostiko.in. 300 IN A 139.59.43.122


----------------------------------------------------------
"iprev" check details:
----------------------------------------------------------
Result:         pass (matches server1.hostiko.in)
ID(s) verified: policy.iprev=139.59.43.122

DNS record(s):
    122.43.59.139.in-addr.arpa. 300 IN PTR server1.hostiko.in.
    server1.hostiko.in. 300 IN A 139.59.43.122


----------------------------------------------------------
DKIM check details:
----------------------------------------------------------
Result:         pass (matches From: info@quickwebworks.com)
ID(s) verified: header.d=quickwebworks.com

Canonicalized Headers:
    to:check-auth@verifier.port25.com'0D''0A'
    from:Quick'20'Web'20'Works'20'<info@quickwebworks.com>'0D''0A'
    date:Thu,'20'5'20'Aug'20'2021'20'14:55:40'20'+0530'0D''0A'
    dkim-signature:v=1;'20'a=rsa-sha256;'20'c=relaxed/simple;'20'd=quickwebworks.com;'20's=default;'20't=1628155544;'20'bh=frcCV1k9oG9oKj3dpUqdJg1PxRT2RSN/XKdLCPjaYaY=;'20'h=To:From:Date;'20'b=

Canonicalized Body:
    '0D''0A'
   

DNS record(s):
    default._domainkey.quickwebworks.com. 300 IN TXT "v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQC9nDfJgnpcXuBEjs8BuvM6JjkhKNsdbWmbPB6dTfZqCbkGIMDtNeNKTo9aFp6vO5pH9QidRLH4WekTb1iJHUy5zhBmglivI/9M/obdBcVBxW6TRPidRB7U4eIS/kwsjMcv7+NvtwHJA6W+3eMNiqRX4FInH706IcvOPcqUoKlF5QIDAQAB"

Public key used for verification: default._domainkey.quickwebworks.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.

==============================================================
Explanation of the possible results (based on RFCs 7601, 7208)
==============================================================


DKIM Results
============

none:  The message was not signed.

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

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

policy:  The message was signed, but some aspect of the signature or
    signatures was not acceptable to the ADMD.

neutral:  The message was signed, but the signature or signatures
    contained syntax errors or were not otherwise able to be
    processed.  This result is also 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.


SPF Results
===========

none:  Either (a) no syntactically valid DNS domain name was extracted from
    the SMTP session that could be used as the one to be authorized, or
    (b) no SPF records were retrieved from the DNS.

neutral:  The ADMD has explicitly stated that it is not asserting whether
    the IP address is authorized.

pass:  An explicit statement that the client is authorized to inject mail
    with the given identity.

fail:  An explicit statement that the client is not authorized to use the
    domain in the given identity.

softfail:  A weak statement by the publishing ADMD that the host is probably
    not authorized.  It has not published a stronger, more definitive policy
    that results in a "fail".

temperror:  The SPF verifier encountered a transient (generally DNS) error
    while performing the check.  A later retry may succeed without further
    DNS operator action.

permerror: The domain's published records could not be correctly interpreted.
    This signals an error condition that definitely requires DNS operator
    intervention to be resolved.


"iprev" Results
===============

pass:  The DNS evaluation succeeded, i.e., the "reverse" and
    "forward" lookup results were returned and were in agreement.

fail:  The DNS evaluation failed.  In particular, the "reverse" and
    "forward" lookups each produced results, but they were not in
    agreement, or the "forward" query completed but produced no
    result, e.g., a DNS RCODE of 3, commonly known as NXDOMAIN, or an
    RCODE of 0 (NOERROR) in a reply containing no answers, was
    returned.

temperror:  The DNS evaluation could not be completed due to some
    error that is likely transient in nature, such as a temporary DNS
    error, e.g., a DNS RCODE of 2, commonly known as SERVFAIL, or
    other error condition resulted.  A later attempt may produce a
    final result.

permerror:  The DNS evaluation could not be completed because no PTR
    data are published for the connecting IP address, e.g., a DNS
    RCODE of 3, commonly known as NXDOMAIN, or an RCODE of 0 (NOERROR)
    in a reply containing no answers, was returned.  This prevented
    completion of the evaluation.  A later attempt is unlikely to
    produce a final result.




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

Return-Path: <info@quickwebworks.com>
Received: from server1.hostiko.in (139.59.43.122) by verifier.port25.com id h1en9m2p2toa for <check-auth@verifier.port25.com>; Thu, 5 Aug 2021 09:25:47 +0000 (envelope-from <info@quickwebworks.com>)
Authentication-Results: verifier.port25.com; spf=pass  smtp.mailfrom=info@quickwebworks.com;
 iprev=pass (matches server1.hostiko.in)  policy.iprev=139.59.43.122;
 dkim=pass (matches From: info@quickwebworks.com)  header.d=quickwebworks.com
Received: from [192.168.1.74] (unknown [180.188.232.207])
   (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
   (No client certificate requested)
   by server1.hostiko.in (Postfix) with ESMTPSA id 87E6046971C;
   Thu,  5 Aug 2021 14:55:44 +0530 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=quickwebworks.com;
   s=default; t=1628155544;
   bh=frcCV1k9oG9oKj3dpUqdJg1PxRT2RSN/XKdLCPjaYaY=; h=To:From:Date;
   b=CbCs/49nQqu2z8ySVooNgMl/ZYIkcLAkJJeNAAYB13CWsOulbrEk8NxVyD0+Ne8yk
    3houjXJO7JVOUbjFATTx/9QRNzrnWla6zH0VC3LmpX4eCyIcqh9KL0K7eMzd2xPIzb
    syybhx4laDwcUDfC4KW3AYycWdcjEMSDYf7l0RXE=
To: check-auth@verifier.port25.com
From: Quick Web Works <info@quickwebworks.com>
Organization: Quick Web Works
Message-ID: <69ae235b-bc42-e0a3-6335-badd318cbbfc@quickwebworks.com>
Disposition-Notification-To: Quick Web Works <info@quickwebworks.com>
Date: Thu, 5 Aug 2021 14:55:40 +0530
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101
 Thunderbird/78.12.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US


IP Reputation is Good


DMARC is okay


After that its going to spam in Gmail, Hotmail and some other domains. I don't have any solutions to this.

I know that its not a CWP problem. CWP support is really good. But they can help us to reach our goal.

or I can buy there support if the solution is paid.


« Last Edit: August 05, 2021, 09:42:15 AM by quickwebworks »