We are happy to announce that Vesta is back under active development as of 25 February 2024. We are working on v1 candidate and expect to engage more with the community over the coming months. We are committed to open source, and we encourage contributors to help us build the future of Vesta.
Emails go to spam folder Topic is solved
-
- Posts: 2
- Joined: Wed Nov 21, 2018 9:30 am
- Os: CentOS 6x
- Web: apache + nginx
Emails go to spam folder
I have changed the hostname and PTR and all other things which required but still emails go to spam folder in gmail, yahoo & outlook.. Here the result of port25 check:
And in mail tester it gets 7.5 score
Can anybody tell me what is wrong the vesta?
Thanks
Code: Select all
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
<[email protected]>.
Thank you for using the verifier,
The Port25 Solutions, Inc. team
==========================================================
Summary of Results
==========================================================
SPF check: pass
"iprev" check: pass
DKIM check: pass
SpamAssassin check: ham
==========================================================
Details:
==========================================================
HELO hostname: mail.janocode.com
Source IP: 45.77.99.66
mail-from: [email protected]
----------------------------------------------------------
SPF check details:
----------------------------------------------------------
Result: pass
ID(s) verified: [email protected]
DNS record(s):
janocode.com. 60 IN TXT "v=spf1 a mx ip4:45.77.99.66 ~all"
janocode.com. 60 IN A 45.77.99.66
----------------------------------------------------------
"iprev" check details:
----------------------------------------------------------
Result: pass (matches mail.janocode.com)
ID(s) verified: policy.iprev=45.77.99.66
DNS record(s):
66.99.77.45.in-addr.arpa. 60 IN PTR mail.janocode.com.
mail.janocode.com. 60 IN A 45.77.99.66
----------------------------------------------------------
DKIM check details:
----------------------------------------------------------
Result: pass (matches From: [email protected])
ID(s) verified: header.d=janocode.com
Canonicalized Headers:
message-id:<[email protected]>'0D''0A'
subject:e'0D''0A'
to:[email protected]'0D''0A'
from:[email protected]'0D''0A'
date:Wed,'20'21'20'Nov'20'2018'20'04:35:13'20'+0300'0D''0A'
content-transfer-encoding:7bit'0D''0A'
content-type:text/plain;'20'charset=US-ASCII;'20'format=flowed'0D''0A'
mime-version:1.0'0D''0A'
dkim-signature:v=1;'20'a=rsa-sha256;'20'q=dns/txt;'20'c=relaxed/relaxed;'20'd=janocode.com;'20's=mail;'20'h=Message-ID:Subject:To:From:Date:'20'Content-Transfer-Encoding:Content-Type:MIME-Version:Sender:Reply-To:Cc:'20'Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender:'20'Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id:'20'List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive;'20'bh=eAtZDoIzaPBP9ngu7k5Qa9X1BEYM95fAIYC0VppkzQM=;'20'b=;
Canonicalized Body:
e'0D''0A'
DNS record(s):
mail._domainkey.janocode.com. 60 IN TXT "v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCyTFTwAHE3vZ5lkAqeOjmiE2DUQIJZ0dB9awC1p+/wt8fjOHnktIqZC3XzTigbq6hLG8l9gRbJP+U5F2kgiSuTigTDyBAdC5sVdx1Q1m3dIPilt3phIn7A5OwOmKynhY70xoSr0B4Fnflqn43W9dtQ8AjuGHKoO5ECRmEQpFM26wIDAQAB"
Public key used for verification: mail._domainkey.janocode.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 (0.4 points, 5.0 required)
pts rule name description
---- ---------------------- --------------------------------------------------
-1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1%
[score: 0.0000]
-0.0 SPF_PASS SPF: sender matches SPF record
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's
domain
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid
2.4 BODY_SINGLE_WORD Message body is only one word (no spaces)
==============================================================
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: <[email protected]>
Received: from mail.janocode.com (45.77.99.66) by verifier.port25.com id huir542e8s4r for <[email protected]>; Wed, 21 Nov 2018 01:35:14 +0000 (envelope-from <[email protected]>)
Authentication-Results: verifier.port25.com; spf=pass [email protected];
iprev=pass (matches mail.janocode.com) policy.iprev=45.77.99.66;
dkim=pass (matches From: [email protected]) header.d=janocode.com
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed;
d=janocode.com; s=mail; h=Message-ID:Subject:To:From:Date:
Content-Transfer-Encoding:Content-Type:MIME-Version: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=eAtZDoIzaPBP9ngu7k5Qa9X1BEYM95fAIYC0VppkzQM=; b=Qf3WT/o+EIFSMkUpyl4BY0XFP
w9ngp08ZN+vCDmAjhv/G6kLsyMaVosBfuXdvv3VQ9Sux/PlVsW+hSCxrgB3ztAsj+SQwbEiLax82A
7zVbcBqdcYUs6dqViygONsqcAKme5qgus0Rb7XpihkxDz0BdD9Cel+bbmqX9EAPGFObdk=;
Received: from localhost ([127.0.0.1] helo=janocode.com)
by mail.janocode.com with esmtp (Exim 4.89)
(envelope-from <[email protected]>)
id 1gPHQ9-0007wn-M0
for [email protected]; Wed, 21 Nov 2018 04:35:13 +0300
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII;
format=flowed
Content-Transfer-Encoding: 7bit
Date: Wed, 21 Nov 2018 04:35:13 +0300
From: [email protected]
To: [email protected]
Subject: e
Message-ID: <[email protected]>
X-Sender: [email protected]
User-Agent: Roundcube Webmail/1.3.4
e
Can anybody tell me what is wrong the vesta?
Thanks