Mail to spam

leandersmeets · Post by **leandersmeets** » Fri Apr 04, 2014 10:05 am

Hello,

I have just installed Vesta on my DigitalOcean VPS. And now I’m configuring my hosting panel but my mail isn't working correctly. All my mail are received in the spam box. Below you see the SPF and DKIM are correct configured:

Code: Select all

Received-SPF: pass (google.com: domain of [email protected] designates 188.226.211.177 as permitted sender) client-ip=188.226.211.177;
To: <[email protected]>
Subject: reereg
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8;
 format=flowed
Content-Transfer-Encoding: 7bit
Date: Fri, 04 Apr 2014 11:40:06 +0200
From: [email protected]
Message-ID: <[email protected]>
User-Agent: Roundcube Webmail/0.7.2

rgergergeger

What is going wrong?

nightstryke · Post by **nightstryke** » Sat Apr 05, 2014 7:34 am

Send a mail to [email protected] and post the results.

leandersmeets · Post by **leandersmeets** » Mon Apr 07, 2014 11:05 am

This is what I get:

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
DomainKeys check:   neutral
DKIM check:         pass
Sender-ID check:    pass
SpamAssassin check: ham

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

HELO hostname:  server.leanderhosting.nl
Source IP:      188.226.211.177
mail-from:      [email protected]

----------------------------------------------------------
SPF check details:
----------------------------------------------------------
Result:         pass 
ID(s) verified: [email protected]
DNS record(s):
    flutkut.nl. SPF (no records)
    flutkut.nl. 14400 IN TXT "v=spf1 a mx ip4:188.226.211.177 ?all"
    flutkut.nl. 14400 IN A 188.226.211.177

----------------------------------------------------------
DomainKeys check details:
----------------------------------------------------------
Result:         neutral (message not signed)
ID(s) verified: [email protected]
DNS record(s):

----------------------------------------------------------
DKIM check details:
----------------------------------------------------------
Result:         pass (matches From: [email protected])
ID(s) verified: header.d=flutkut.nl
Canonicalized Headers:
    message-id:<[email protected]>'0D''0A'
    from:[email protected]'0D''0A'
    date:Mon,'20'07'20'Apr'20'2014'20'13:03:25'20'+0200'0D''0A'
    content-transfer-encoding:7bit'0D''0A'
    content-type:text/plain;'20'charset=UTF-8;'20'format=flowed'0D''0A'
    mime-version:1.0'0D''0A'
    subject:Test'20'e-mail'20'Vesta'20'cp'0D''0A'
    to:<[email protected]>'0D''0A'
    dkim-signature:v=1;'20'a=rsa-sha256;'20'q=dns/txt;'20'c=relaxed/relaxed;'20'd=flutkut.nl;'20's=mail;'20'h=Message-ID:From:Date:Content-Transfer-Encoding:Content-Type:MIME-Version:Subject:To;'20'bh=mBpN/G27rMMSa6h+4DPNmMnS56Y4kaBUz7Kc5Fjw3kU=;'20'b=;

Canonicalized Body:
    Test'20'e-mail'0D''0A'
    

DNS record(s):
    mail._domainkey.flutkut.nl. 14400 IN TXT "k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDaYMeDi+Q4Z5xHZ3aKAWYO1dLPOtm6BHpdSEs7e5ewBQbhfj0guVbiqvQ8x9U4H3Kcg9PV+HapaNkskn6DylxWvaFa/CjqYJP6VT2rG9fVhwI/PVGEkkJBlb9NDlAaPJtjSipasH+mbo3sWurEKVUaNO1LRnuF7tyIi5sfDLBhOwIDAQAB"

Public key used for verification: mail._domainkey.flutkut.nl (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.

----------------------------------------------------------
Sender-ID check details:
----------------------------------------------------------
Result:         pass 
ID(s) verified: [email protected]
DNS record(s):
    flutkut.nl. SPF (no records)
    flutkut.nl. 14400 IN TXT "v=spf1 a mx ip4:188.226.211.177 ?all"
    flutkut.nl. 14400 IN A 188.226.211.177

----------------------------------------------------------
SpamAssassin check details:
----------------------------------------------------------
SpamAssassin v3.3.1 (2010-03-16)

Result:         ham  (-2.0 points, 5.0 required)

 pts rule name              description
---- ---------------------- --------------------------------------------------
-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

==========================================================
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: <[email protected]>
Received: from server.leanderhosting.nl (188.226.211.177) by verifier.port25.com id h8a30211u9c9 for <[email protected]>; Mon, 7 Apr 2014 07:03:29 -0400 (envelope-from <[email protected]>)
Authentication-Results: verifier.port25.com; spf=pass [email protected]
Authentication-Results: verifier.port25.com; domainkeys=neutral (message not signed) [email protected]
Authentication-Results: verifier.port25.com; dkim=pass (matches From: [email protected]) header.d=flutkut.nl
Authentication-Results: verifier.port25.com; sender-id=pass [email protected]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=flutkut.nl; s=mail;
	h=Message-ID:From:Date:Content-Transfer-Encoding:Content-Type:MIME-Version:Subject:To; bh=mBpN/G27rMMSa6h+4DPNmMnS56Y4kaBUz7Kc5Fjw3kU=;
	b=TfYdj/pqMyZio4py1EFzf7Tcn6lQIPxZkAF8PLIzH7Xv21Z/mIOQbKZACs5/xU0vMmnaci3+DBa049qhIMKqcCSpjnt/AZvj5ooOj9Y7rgpo1Au1wIiJ1Hjglp+IBiChARS292sgf2mD5v2OrC4x1oUlzy5s3KHSF6f9QXPt25U=;
Received: from admin by server.leanderhosting.nl with local (Exim 4.80)
	(envelope-from <[email protected]>)
	id 1WX7Kn-0002zv-1f
	for [email protected]; Mon, 07 Apr 2014 11:03:25 +0000
To: <[email protected]>
Subject: Test e-mail Vesta cp
X-PHP-Originating-Script: 0:main.inc
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8;
 format=flowed
Content-Transfer-Encoding: 7bit
Date: Mon, 07 Apr 2014 13:03:25 +0200
From: [email protected]
Message-ID: <[email protected]>
X-Sender: [email protected]
User-Agent: Roundcube Webmail/0.7.2

Test e-mail

n1kko · Post by **n1kko** » Mon Apr 07, 2014 12:42 pm

Use this http://www.mail-tester.com/ will give you clear details of what your issue is

MyKEcz · Post by **MyKEcz** » Mon Apr 07, 2014 6:06 pm

Does DigitalOcean support custom PTR (Reverse DNS) records? Try to check them.
I would only recommend http://mxtoolbox.com/diagnostic.aspx (Also server can be BlackListed).

Problem can be also on SMTP TLS side. In default is that function disabled, so servers can't communicate encrypted. Enable it in /etc/exim4/exim4.conf.template, uncomment lines:

tls_advertise_hosts = *
tls_certificate = /usr/local/vesta/ssl/certificate.crt
tls_privatekey = /usr/local/vesta/ssl/certificate.key

service exim4 restart

nightstryke · Post by **nightstryke** » Mon Apr 07, 2014 11:04 pm

MyKEcz wrote:Does DigitalOcean support custom PTR (Reverse DNS) records? Try to check them.
I would only recommend http://mxtoolbox.com/diagnostic.aspx (Also server can be BlackListed).

Problem can be also on SMTP TLS side. In default is that function disabled, so servers can't communicate encrypted. Enable it in /etc/exim4/exim4.conf.template, uncomment lines:

tls_advertise_hosts = *
tls_certificate = /usr/local/vesta/ssl/certificate.crt
tls_privatekey = /usr/local/vesta/ssl/certificate.key

service exim4 restart

That fixed my issue with DKIM Check but no DomainKeys check which is still Neutral.

leandersmeets · Post by **leandersmeets** » Tue Apr 08, 2014 7:12 am

This is what I get from mail-tester:

http://www.mail-tester.com/web-2jJVIU&reloaded=1

I also changed my exim4.conf.template and will test it in the afternoon and let you guys know.

leandersmeets · Post by **leandersmeets** » Fri Apr 11, 2014 9:32 am

Hi guys,

I checked my mail again and this is what I get:

DomainKeys Identified Mail ( DKIM ) is a method for associating a domain name with an e - mail message , which a person, organization, function or any kind of responsibility for the message can claim .
The DKIM signature of your message :

v = 1 ;
a = rsa - sha256 ;
q = dns / txt ;
c = relaxed / relaxed ;
d = sleutelpaar.nl ;
s = mail ;
h = Message- ID : From : Date : Content- Transfer-Encoding : Content- Type : MIME -Version : Subject : To;
bh = rQ4GfaKEN9BW9uNtO4NWVNcAPOEsjzsH6whh8rrg2o4 = ;

We could not figure out the public key .
Make sure you have added to your domain sleutelpaar.nl to use the selector mail . 's DKIM DNS TXT record
If you've recently updated DNS be patient and test your newsletter again in 12 hours , it may take some time before your DNS change is propagated everywhere

Probaly the public key isn't correct.
Does any one know how to solve this problem?

Below a picture of my DNS settings

nightstryke · Post by **nightstryke** » Fri Apr 11, 2014 2:46 pm

Doesn't look like all your dkim info is in there.
Try running this in ssh as root.

Code: Select all

# v-delete-mail-domain-dkim vestacpusername domainname
# v-add-mail-domain-dkim vestacpusername domainname 1024

Note: The 1024 is the standard encryption that should be used.

To make sure the changes took effect run this in ssh as root.

Code: Select all

# v-list-mail-domain-dkim vestacpusername domainname

Try that.

leandersmeets · Post by **leandersmeets** » Tue Apr 15, 2014 8:12 am

Hi,

I tried to set:

Code: Select all

# v-delete-mail-domain-dkim vestacpusername domainname
# v-add-mail-domain-dkim vestacpusername domainname 1024

But it doesn't work right?
Below you see the screenshot of it:

Vesta Control Panel - Forum

Mail to spam

Mail to spam

Re: Mail to spam

Re: Mail to spam

Re: Mail to spam

Re: Mail to spam

Re: Mail to spam

Re: Mail to spam

Re: Mail to spam

Re: Mail to spam

Re: Mail to spam

Login • Register