Problem with outgoing emails getting spam

[ngelG]

Hi, I have a hard problem with my VPS.

I have postfix as mail server on plesk 12 under ubuntu 12.

I dont know why the outgoing mails of all my domains in my servers are getting spam in servers like gmail, yahoo, hotmail...

I'm using mxtoolbox to fix errors and warnings and finally fixed all of them, but my mails are still outgoing to spam.

In mxtoolbox actually I have no mail server errors / warning, u can see it with, for example, this one of my domains: http://goo.gl/iNqTma

I need really help!

Headers:

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

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

HELO hostname: mail.genetikasystems.com
Source IP: 85.214.122.217
mail-from: [email protected]

----------------------------------------------------------
SPF check details:
----------------------------------------------------------
Result: pass
ID(s) verified: [email protected]
DNS record(s):
grupoges.com.es. SPF (no records)
grupoges.com.es. 3600 IN TXT "1|www.grupoges.com.es"
grupoges.com.es. 3600 IN TXT "v=spf1 +a +mx -all"
grupoges.com.es. 3600 IN A 85.214.122.217

----------------------------------------------------------
DomainKeys check details:
----------------------------------------------------------
Result: permerror (DK_STAT_NOKEY: No public key available (permanent failure)
ID(s) verified: )
DNS record(s):
default._domainkey.grupoges.com.es. 600 IN TXT "v=spf1 +a +mx -all"

----------------------------------------------------------
DKIM check details:
----------------------------------------------------------
Result: neutral (message not signed)
ID(s) verified:

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):
grupoges.com.es. SPF (no records)
grupoges.com.es. 3600 IN TXT "1|www.grupoges.com.es"
grupoges.com.es. 3600 IN TXT "v=spf1 +a +mx -all"
grupoges.com.es. 3600 IN A 85.214.122.217

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

Result: ham (-1.8 points, 5.0 required)

pts rule name description
---- ---------------------- --------------------------------------------------
0.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was blocked.
See
http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block
for more information.
[URIs: grupoges.com.es]
-1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1%
[score: 0.0000]
0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid
0.0 TVD_SPACE_RATIO TVD_SPACE_RATIO

==========================================================
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 mail.genetikasystems.com (85.214.122.217) by verifier.port25.com id h8rmgk11u9cb for <[email protected]>; Tue, 21 Oct 2014 19:32:26 -0400 (envelope-from <[email protected]>)
Authentication-Results: verifier.port25.com; spf=pass [email protected]
Authentication-Results: verifier.port25.com; domainkeys=permerror (DK_STAT_NOKEY: No public key available (permanent failure)) [email protected]
Authentication-Results: verifier.port25.com; dkim=neutral (message not signed)
Authentication-Results: verifier.port25.com; sender-id=pass [email protected]
Received: from [192.168.0.102] (unknown [154.48.156.113])
by mail.genetikasystems.com (Postfix) with ESMTPSA id 7A13D46E60B4
for <[email protected].>; Wed, 22 Oct 2014 01:32:20 +0200 (CEST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
s=default; d=grupoges.com.es;
b=CcxzStnaKkL2gPAEtpa3edcAA8PaZErzFqEIokBMUDDzYJgsqC5N2k53XfLAtnDR86lCk97FVY6TbaMWPN1R5Q43k9wRbPo3UXGe/mw21NL31wq3K7ZO6NMaSAiOORogvzdbYylDL205UjZOrMlT3N5mrRGlQhKGr2SiccN0ySY=;
h=Message-IDate:From:User-Agent:MIME-Version:To:Subject:Content-Type:Content-Transfer-Encoding;
Message-ID: <[email protected]>
Date: Wed, 22 Oct 2014 01:32:18 +0200
From: GKS <[email protected]>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0
MIME-Version: 1.0
To: [email protected].
Subject: sample
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

 

[UFHH01]

...
Result: permerror (DK_STAT_NOKEY: No public key available (permanent failure)
...

There is no private key, which may verify the default domainkey for your domain - either generate a new one manually, or let Plesk do it, by switching domainkeys OFF and ON again, in the global mail-server settings and in the domain - mail - server settings.

DomainKeys Protection ( Plesk 12 Online documentation )​