MRatWork Forum by Mustafa Ramadhan
Sawo Project - Kloxo-MR Discussions => Kloxo-MR Technical Helps => Topic started by: kuldeep verma on 2013-09-04, 02:03:55
-
Dear Friends,
I know i am not alone facing this problem. After trying and following all possible guides to fix this issue, i am unable to find any working solution to get mails sent by kloxo in inbox...
Have checked and MY IP is not blacklisted anywhere and having valid PTR records..
Here are my settings:
My Website: www.mydomain.com
My Ip: 192.168.1.1
Hostname of my VPS: server.mydomain.com (having proper A entry to resolve 192.168.1.1)
RDNS: server.mydomain.com (192.168.1.1 resolving to server.mydomain.com)
Had a fresh install of kloxo mr..
Inside Kloxo
1) Server Mail Settings : Enable Domainkey is Checked.
2) mydomain.com {Email Auth} : Enable SPF is Checked.
3) MX Record value is: server.mydomain.com
Kloxo Email Accounts
1) Having an email account for abuse@mydomain.com (as guided by google)
2) Having an email account for postmaster@mydomain.com
3) Having an email account for admin@mydomain.com
My mails are still going to spam folder :(
Here is a complete message with headers
Delivered-To: xxxx@gmail.com
Received: by 10.216.172.134 with SMTP id t6csp254358wel;
Tue, 3 Sep 2013 12:27:31 -0700 (PDT)
X-Received: by 10.180.171.7 with SMTP id aq7mr14672980wic.28.1378236451515;
Tue, 03 Sep 2013 12:27:31 -0700 (PDT)
Return-Path: <admin@[color=#FF0000]mydomain.com[/color]>
Received: from server.mydomain.com (server.[color=#FF0000]mydomain.com[/color]. [192.168.1.1])
by mx.google.com with ESMTPS id pc4si7685730wic.24.1969.12.31.16.00.00
(version=TLSv1 cipher=RC4-SHA bits=128/128);
Tue, 03 Sep 2013 12:27:31 -0700 (PDT)
Received-SPF: pass (google.com: domain of admin@[color=#FF0000]mydomain.com[/color] designates 192.168.1.1 as permitted sender) client-ip=192.168.1.1;
Authentication-Results: mx.google.com;
spf=pass (google.com: domain of admin@[color=#FF0000]mydomain.com[/color] designates 192.168.1.1 as permitted sender) smtp.mail=admin@mydomain.com
Date: Tue, 03 Sep 2013 12:27:31 -0700 (PDT)
Message-Id: <52263823.04dab40a.523c.4a18SMTPIN_ADDED_MISSING@mx.google.com>
Received: (qmail 5275 invoked from network); 3 Sep 2013 19:27:20 -0000
Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
s=private; d=mydomain.com;
b=rdlog0ng9ExrzJ12UVl/eFWPdi45oFPHNO+Vp5pDsauvXLMFddPFnsviIlHcU09xBVba4op87oJnogOIKbiESYxyQVVX1T8GQpz3MLckasyfO9Zipeo/o3glnSNEoy52b5Vb4Lafq04jTIp1UPsHGkrBVZpRU4xqjLqjtgYCErY=;
Received: from unknown (HELO localhost) (admin@[color=#FF0000]mydomain.com[/color]@192.168.1.1)
by server.yeskullu.com with ESMTPA; 3 Sep 2013 19:27:20 -0000
Return-path: postmaster@[color=#FF0000]mydomain.com[/color]
From: Kuldeep <admin@[color=#FF0000]mydomain.com[/color]>
To: xxxx@gmail.com
Subject: Hello Dear!
MIME-Version: 1.0
Reply-To: admin@[color=#FF0000]mydomain.com[/color]
Content-Type: text/html;charset=UTF-8
Content-Transfer-Encoding: 7bit
<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<meta name="viewport" content="width=device-width, initial-scale=1.0"/>
<title>How Are You ?</title>
</head>
<body>
<p>Hi,<br />Kaha ho yar itne dino se ?</p>
</body>
</html>
Please help me in fixing this issue.. Thanks a lot for the help in advance..
-
Please ignore the BBcode in message..
-
gmail policy ? any email recieved client can resolved to not spam ?
yahoo ok ?
-
neither gmail not yahoo.. i am getting all mails sent by kloxo in spam folder.. However at same VPS if i install Cpanel it sends the mails in inbox at both yahoo as well as gmail :(
i think that there is some issue with kloxo mail.. its not sending proper DKIM or something missing..
Can anyone confirm and post his working settings ?
-
Did you read viewtopic.php?f=15&t=19344 (http://forum.mratwork.com/viewtopic.php?f=15&t=19344)
-
(http://oi42.tinypic.com/2ywejhx.jpg)
is everything fine according to this screenshot ?
-
Yes.
If you still see your message as spam in google and then set as 'no spam'.
-
Mustafa,
How to change DKIM from 384 to 1024 on Kloxo-MR-6.5.0.f-2013031828
-
However i change
lxshell_return("openssl", "genrsa", "-out", "private", 384);
to
lxshell_return("openssl", "genrsa", "-out", "private", 1024);
Delete all folders in /var/qmail/control/domainkeys
Then run sh /script/fixdomainkeys and now everything is okay :)
-
Latest Kloxo-MR already use 1024. So, read viewtopic.php?f=15&t=19344 (http://forum.mratwork.com/viewtopic.php?f=15&t=19344) about it.
-
I'm not use latest kloxo, because there is so much thing that not work properly... And honestly i'm afraid to update because i don't know what will stop working. Thats why i ask you.. Is that the right way to change from 384 to 1024 or not?
-
What Kloxo-MR latest update you know?.
-
Same here , all mails sent from all domains are going to SPAM to any mail address destination . Please Mustafa tell as how to fix that, all my sites have KEY LENGTH (BITS):1024.
-
Check again:
1. Have reverse-dns for every IP -> ask provider to set rdns for IPs
2. Enable domainkeys --> enable via 'server mail settings'
3. Enable SPF --> must set for every domains
-
Everything is set as you said but mails still go to SPAM.
The problem is this: I have one IP and 5 websites, the main site which is hostname on hosts file and rdsn (mail.default.com) works just fine, all emails are sent to Inbox, while all other domains mails are going to SPAM. Should I use the same MX record for all domains as the main domain (mail.default.com) ?
-
Is the same name hostname (inform from 'hostname -f') with information inside /etc/hosts?.
Let say. inform from 'hostname -f' is 'server.domain.com' and your ip is '123.123.123.123'. And then you set inside /etc/hosts as '123.123.123.123 server.domain.com server'?.
-
[root@trader ~]# hostname -f
trader.mysite.com
[root@trader ~]# nano /etc/hosts
GNU nano 2.0.9 File: /etc/hosts
127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4
::1 localhost localhost.localdomain localhost6 localhost6.localdomain6
188.211.51.92 trader.mysite.com trader
-
Try change to:
127.0.0.1 localhost.localdomain localhost localhost4.localdomain4 localhost4
::1 localhost.localdomain localhost localhost6.localdomain6 localhost6
188.211.51.92 trader.mysite.com trader
-
Same result :roll:
-
Because related to network applications, need reboot.
-
I have made the modifications you said , reboot the server but the same, main site send mails to inbox and others domains emails sends to SPAM :(
-
http://forum.mratwork.com/viewtopic.php?f=15&t=19412
DKIM signing is NOT available in KloxoMR because of qmail-toaster. I have posted the solution in the above tips and tricks forum.
This should help with the gmail problem. :) Enjoy
-
Thank you chrisf. I managed to fix it, I didn't try it your tutorial yet. What I did is to change MX for all domains with main domain mx entry (ex. mail.mysite.com) than reboot. It worked like charm, all mails from all domains are sent inbox. The only problem was that I have to access all mails from all domains using the same browser address webmail.mysite.com. My old shared hosting plan was the same using Cpanel - I had to access the same webmail.mysite.com to access 5 sites emails. Now the big surprise : After that I remove it the new MX entry and is still working perfect even after server reboot ! And I can access webmail using each domain name (i.e. webmail.mysite1.com, webmail.mysite2.com). I don't know why it works I just hope it will stay that way for good. What do you think ?
-
Strange.. only on one tested gmail account mails are received inbox, any other gmail address receive mails in SPAM, even main domain mail account is sending to SPAM :( It looks like I have to try your solution chrisf.
-
I followed all advices here but my mails are still going to gmail SPAM folder. Inside 'show original' I can see only one problem :
Received: from unknown (HELO tradePC) (suport@mysite.com@85.105.94.5)
Could this trigger gmail to make my message as SPAM ? If so, how to fix it ?
-
YES that is a spf problem. Send a message to this email address and report the response:
check-auth@verifier.port25.com
Be sure to include a subject and a small text in body.
You will get a response back. Report it here.
-
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: neutral
DomainKeys check: pass
DKIM check: pass
Sender-ID check: neutral
SpamAssassin check: ham
==========================================================
Details:
==========================================================
HELO hostname: trader.adresemail.com
Source IP: 188.215.51.97
mail-from: suport@adresemail.com
----------------------------------------------------------
SPF check details:
----------------------------------------------------------
Result: neutral (SPF-Result: None)
ID(s) verified: smtp.mailfrom=suport@adresemail.com
DNS record(s):
adresemail.com. SPF (no records)
adresemail.com. TXT (no records)
----------------------------------------------------------
DomainKeys check details:
----------------------------------------------------------
Result: pass
ID(s) verified: header.From=suport@adresemail.com
DNS record(s):
private._domainkey.adresemail.com. 300 IN TXT "v=DKIM1; g=*; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDXxyGgqk/RaBv6HO/DwMZzohjY7x+aOOXNl80EQSCNkU+nr7JdyMyKu+WnRZPZgrvbCrGo6Nz4TzG4aha4XYsEObqt+HJ3qovcVQE4FaawMyCZxqsCD51unOf851HIDCLcMJo6LCevKb0MLJmY3VRShZPNWKQ1SNYWt34gIvJIMQIDAAAB"
----------------------------------------------------------
DKIM check details:
----------------------------------------------------------
Result: pass (matches From: suport@adresemail.com)
ID(s) verified: header.d=adresemail.com
Canonicalized Headers:
message-id:<D293ED61BA66437EB69CBBD080A0B80A@traderPC>'0D''0A'
from:"AdreseMail"'20'<suport@adresemail.com>'0D''0A'
to:<check-auth@verifier.port25.com>'0D''0A'
subject:testing'0D''0A'
date:Mon,'20'9'20'Sep'20'2013'20'22:35:24'20'+0300'0D''0A'
mime-version:1.0'0D''0A'
content-type:multipart/alternative;'20'boundary="----=_NextPart_000_0017_01CEADAC.DFFD6970"'0D''0A'
dkim-signature:v=1;'20'a=rsa-sha1;'20'c=relaxed;'20'd=adresemail.com;'20'h='20'message-id:from:to:subject:date:mime-version:content-type;'20's='20'private;'20'bh=VHqE41t3jzZrKlY8owYiRdVz4gI=;'20'b=
Canonicalized Body:
Acesta'20'este'20'un'20'mesaj'20'cu'20'mai'20'multe'20'par?i'20''EE'n'20'format'20'MIME.'0D''0A'
'0D''0A'
------=_NextPart_000_0017_01CEADAC.DFFD6970'0D''0A'
Content-Type:'20'text/plain;'0D''0A'
'09'charset="iso-8859-1"'0D''0A'
Content-Transfer-Encoding:'20'quoted-printable'0D''0A'
'0D''0A'
Hello,'0D''0A'
'0D''0A'
Just'20'a'20'test'20'message.'0D''0A'
'0D''0A'
------=_NextPart_000_0017_01CEADAC.DFFD6970'0D''0A'
Content-Type:'20'text/html;'0D''0A'
'09'charset="iso-8859-1"'0D''0A'
Content-Transfer-Encoding:'20'quoted-printable'0D''0A'
'0D''0A'
<HTML><HEAD></HEAD>'0D''0A'
<BODY'20'dir=3Dltr>'0D''0A'
<DIV'20'dir=3Dltr>'0D''0A'
<DIV'20'style=3D"FONT-SIZE:'20'12pt;'20'FONT-FAMILY:'20''27'Calibri'27';'20'COLOR:'20'#000000">'0D''0A'
<DIV>Hello,</DIV>'0D''0A'
<DIV> </DIV>'0D''0A'
<DIV>Just'20'a'20'test'20'message.</DIV>'0D''0A'
<DIV> </DIV></DIV></DIV></BODY></HTML>'0D''0A'
'0D''0A'
------=_NextPart_000_0017_01CEADAC.DFFD6970--'0D''0A'
DNS record(s):
private._domainkey.adresemail.com. 300 IN TXT "v=DKIM1; g=*; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDXxyGgqk/RaBv6HO/DwMZzohjY7x+aOOXNl80EQSCNkU+nr7JdyMyKu+WnRZPZgrvbCrGo6Nz4TzG4aha4XYsEObqt+HJ3qovcVQE4FaawMyCZxqsCD51unOf851HIDCLcMJo6LCevKb0MLJmY3VRShZPNWKQ1SNYWt33gICJIkQIDAQAB"
Public key used for verification: private._domainkey.adresemail.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.
----------------------------------------------------------
Sender-ID check details:
----------------------------------------------------------
Result: neutral (SPF-Result: None)
ID(s) verified: header.From=suport@adresemail.com
DNS record(s):
adresemail.com. SPF (no records)
adresemail.com. TXT (no records)
----------------------------------------------------------
SpamAssassin check details:
----------------------------------------------------------
SpamAssassin v3.3.1 (2010-03-16)
Result: ham (-4.4 points, 5.0 required)
pts rule name description
---- ---------------------- --------------------------------------------------
-2.4 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain
-1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1%
[score: 0.0020]
0.0 HTML_MESSAGE BODY: HTML included in message
-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: <suport@adresemail.com>
Received: from trader.adresemail.com (188.215.51.97) by verifier.port25.com id h5ohfo11u9ch for <check-auth@verifier.port25.com>; Mon, 9 Sep 2013 15:35:24 -0400 (envelope-from <suport@adresemail.com>)
Authentication-Results: verifier.port25.com; spf=neutral (SPF-Result: None) smtp.mailfrom=suport@adresemail.com
Authentication-Results: verifier.port25.com; domainkeys=pass header.From=suport@adresemail.com
Authentication-Results: verifier.port25.com; dkim=pass (matches From: suport@adresemail.com) header.d=adresemail.com
Authentication-Results: verifier.port25.com; sender-id=neutral (SPF-Result: None) header.From=suport@adresemail.com
Comment: DomainKeys? See http://domainkeys.sourceforge.net/
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
s=private; d=adresemail.com;
b=j8RSCZXmzPjkDS8ZSK68hbgtoiop7P3rAC90KDeWscpEFargrvJcGjPWYF/K3iEM9LWZoMvoMYs96qM4+o1rTzdG9fTN37Ht942oRmLxqog+fO/vrswcfcW8t4dWNtT7LGVAbtjL7qCMwluoKIbEdVHLNJYAjYQXWBRaNr42OSw=;
h=Received:Received:Message-ID:From:To:Subject:Date:MIME-Version:Content-Type:X-Priority:X-MSMail-Priority:Importance:X-Mailer:X-MimeOLE;
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=adresemail.com; h=
message-id:from:to:subject:date:mime-version:content-type; s=
private; bh=VHqE41t3jzZrKlY8owYiRdVz4gI=; b=ofZjBMlVh5r0aLbZk6Ue
MjZuqZyIr8HVNAUa+Z1KjUUDx7wpPuxDEskIJ7N/Gc7elna2Y1wZKcUnWJvCGP0h
rp7JFLqtS1oSfqi3q+0D3rAWlrGfDJWC88+zN+j9F98tTwBYh1M1LbHrLAs3Yx7p
ua8y/8MJy5jvgiNnS4wwhOM=
Received: (qmail 31908 invoked from network); 9 Sep 2013 19:34:02 -0000
Received: from unknown (HELO traderPC) (suport@adresemail.com@86.105.94.7)
by trader.adresemail.com with ESMTPA; 9 Sep 2013 19:34:02 -0000
Message-ID: <D293ED61BA66437EB69CBBD080A0B80A@traderPC>
From: "AdreseMail" <suport@adresemail.com>
To: <check-auth@verifier.port25.com>
Subject: testing
Date: Mon, 9 Sep 2013 22:35:24 +0300
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="----=_NextPart_000_0017_01CEADAC.DFFD6970"
X-Priority: 3
X-MSMail-Priority: Normal
Importance: Normal
X-Mailer: Microsoft Windows Live Mail 16.4.3508.205
X-MimeOLE: Produced By Microsoft MimeOLE V16.4.3508.205
Acesta este un mesaj cu mai multe par?i în format MIME.
------=_NextPart_000_0017_01CEADAC.DFFD6970
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Hello,
Just a test message.
------=_NextPart_000_0017_01CEADAC.DFFD6970
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<HTML><HEAD></HEAD>
<BODY dir=3Dltr>
<DIV dir=3Dltr>
<DIV style=3D"FONT-SIZE: 12pt; FONT-FAMILY: 'Calibri'; COLOR: #000000">
<DIV>Hello,</DIV>
<DIV> </DIV>
<DIV>Just a test message.</DIV>
<DIV> </DIV></DIV></DIV></BODY></HTML>
------=_NextPart_000_0017_01CEADAC.DFFD6970--
-
And this is my Cloudflare and Kloxo-MR settings.
-
Under the domain name in KloxoMR click Email Auth - enable SPF.
Your cloud settings show a SPF record, but check-auth is not finding one. This has to be your problem - all major email now requires both a SPF TXT and a SPF RR. KloxoMR currently only supports SPF TXT - but it will get you into an inbox.
Enable the SPF under Email Auth after clicking on the domain.
After you enable it wait for a few hours and resend a message to verifier.port25 - you MUST get SPF to pass.
I will help :)
-
Read http://en.wikipedia.org/wiki/List_of_DNS_record_types (http://en.wikipedia.org/wiki/List_of_DNS_record_types), especially for SPF?. Is it as 'and as of August 2013 it’s considered for obsolescence.'?
-
It does appear that it is going to be obsolete - hmmm... Interesting. I will investigate more.
-
SPF TXT is still a must.
-
It was already enable it since I installed Kloxo-MR with no effect.
-
I just checked again with check-auth@verifier.port25.com and all seems fine :
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: pass
DKIM check: pass
Sender-ID check: pass
SpamAssassin check: ham
==========================================================
Details:
==========================================================
HELO hostname: trader.adresemail.com
Source IP: 188.215.51.97
mail-from: suport@adresemail.com
----------------------------------------------------------
SPF check details:
----------------------------------------------------------
Result: pass
ID(s) verified: smtp.mailfrom=suport@adresemail.com
DNS record(s):
adresemail.com. 300 IN SPF "v=spf1 a mx ~all"
adresemail.com. 300 IN A 188.215.51.97
----------------------------------------------------------
DomainKeys check details:
----------------------------------------------------------
Result: pass
ID(s) verified: header.From=suport@adresemail.com
DNS record(s):
private._domainkey.adresemail.com. 300 IN TXT "v=DKIM1; g=*; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDXxyGgqk/RaBv6HO/DwMZzohjY7x+aOOXNl80EQSCNkU+nr7JdyMyKu+WnRZPZgrvbCrGo6Nz4TzG4aha4XYsEObqt+HJfqovcVQ94FaawMyCZxqsCD51unOf851HIDCLcMJo6LCevKb0MLJmY3VRShZPNWKQ1SNYWt33gIvJIMQIDAQAB"
----------------------------------------------------------
DKIM check details:
----------------------------------------------------------
Result: pass (matches From: suport@adresemail.com)
ID(s) verified: header.d=adresemail.com
Canonicalized Headers:
message-id:<344A85AFB4444980A868799D66540940@traderPC>'0D''0A'
from:"AdreseMail"'20'<suport@adresemail.com>'0D''0A'
to:<check-auth@verifier.port25.com>'0D''0A'
subject:spf'20'rec'0D''0A'
date:Tue,'20'10'20'Sep'20'2013'20'09:29:23'20'+0300'0D''0A'
mime-version:1.0'0D''0A'
content-type:multipart/alternative;'20'boundary="----=_NextPart_000_0003_01CEAE08.3C1280A0"'0D''0A'
dkim-signature:v=1;'20'a=rsa-sha1;'20'c=relaxed;'20'd=adresemail.com;'20'h='20'message-id:from:to:subject:date:mime-version:content-type;'20's='20'private;'20'bh=m7B3VGaAVYBbSyQegRRvB/O8NaI=;'20'b=
Canonicalized Body:
Acesta'20'este'20'un'20'mesaj'20'cu'20'mai'20'multe'20'par?i'20''EE'n'20'format'20'MIME.'0D''0A'
'0D''0A'
------=_NextPart_000_0003_01CEAE08.3C1280A0'0D''0A'
Content-Type:'20'text/plain;'0D''0A'
'09'charset="iso-8859-1"'0D''0A'
Content-Transfer-Encoding:'20'quoted-printable'0D''0A'
'0D''0A'
spf'20'record'20'?'0D''0A'
'0D''0A'
'0D''0A'
------=_NextPart_000_0003_01CEAE08.3C1280A0'0D''0A'
Content-Type:'20'text/html;'0D''0A'
'09'charset="iso-8859-1"'0D''0A'
Content-Transfer-Encoding:'20'quoted-printable'0D''0A'
'0D''0A'
<HTML><HEAD></HEAD>'0D''0A'
<BODY'20'dir=3Dltr>'0D''0A'
<DIV'20'dir=3Dltr>'0D''0A'
<DIV'20'style=3D"FONT-SIZE:'20'12pt;'20'FONT-FAMILY:'20''27'Calibri'27';'20'COLOR:'20'#000000">'0D''0A'
<DIV>spf'20'record'20'?</DIV>'0D''0A'
<DIV> </DIV>'0D''0A'
<DIV> </DIV></DIV></DIV></BODY></HTML>'0D''0A'
'0D''0A'
------=_NextPart_000_0003_01CEAE08.3C1280A0--'0D''0A'
DNS record(s):
private._domainkey.adresemail.com. 300 IN TXT "v=DKIM1; g=*; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDXxyGgqk/RaBv6HO/DwMZzohjY7x+aOOXNl80EQSCNkU+nr7JdyMyKu+WnRZPZgrvbCrGo6Nz4TzG4aha4XYsEObqt+HJ3qov87VQE4FaawMyCZxqsCD51unOfhu51HIDCLcMJo6LievKb0MLJmY3VRShZPNWKQ1SNYWt33gIvJIMQIDAQAB"
Public key used for verification: private._domainkey.adresemail.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.
----------------------------------------------------------
Sender-ID check details:
----------------------------------------------------------
Result: pass
ID(s) verified: header.From=suport@adresemail.com
DNS record(s):
adresemail.com. 300 IN SPF "v=spf1 a mx ~all"
adresemail.com. 300 IN A 188.215.51.97
----------------------------------------------------------
SpamAssassin check details:
----------------------------------------------------------
SpamAssassin v3.3.1 (2010-03-16)
Result: ham (-4.4 points, 5.0 required)
pts rule name description
---- ---------------------- --------------------------------------------------
-2.4 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.0 HTML_MESSAGE BODY: HTML included in message
-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: <suport@adresemail.com>
Received: from trader.adresemail.com (188.215.51.97) by verifier.port25.com id h5qu3s11u9ck for <check-auth@verifier.port25.com>; Tue, 10 Sep 2013 02:29:18 -0400 (envelope-from <suport@adresemail.com>)
Authentication-Results: verifier.port25.com; spf=pass smtp.mailfrom=suport@adresemail.com
Authentication-Results: verifier.port25.com; domainkeys=pass header.From=suport@adresemail.com
Authentication-Results: verifier.port25.com; dkim=pass (matches From: suport@adresemail.com) header.d=adresemail.com
Authentication-Results: verifier.port25.com; sender-id=pass header.From=suport@adresemail.com
Comment: DomainKeys? See http://domainkeys.sourceforge.net/
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
s=private; d=adresemail.com;
b=wHzBgkQjzwqMa02TXYJtNitsqKf5OL5Ug2eCEAI6br7TvsgZnxiPFuDhzCMPqe+xkWWiQdsfLn6IW2faKyCKHVDSa1jOSI9VBLCQc9dcBkEGgcS5mjHl5nkaZFLUYP47wNCstn/b6dHGwtPQE1abq+UkrtfnLiQyjUa9X/0gz4k=;
h=Received:Received:Message-ID:From:To:Subject:Date:MIME-Version:Content-Type:X-Priority:X-MSMail-Priority:Importance:X-Mailer:X-MimeOLE;
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=adresemail.com; h=
message-id:from:to:subject:date:mime-version:content-type; s=
private; bh=m7B3VGaAVYBbSyQegRRvB/O8NaI=; b=zWa2zcNMcfnU94KzCcoO
UMzzzoBuHulojDkVyB6A5mNKUGwJf2LJk8TAlQBjslF5B2+bUvXBhJzY3x+Ur5VU
ByG/kb9YqukHbK0lI71P8T9GXNkhXyUr00OZfDREhIMItY4gXY6pxl4rOtuerGdv
5T0H8H7jnJXYtuw4ZAuekRU=
Received: (qmail 17528 invoked from network); 10 Sep 2013 06:28:00 -0000
Received: from unknown (HELO traderPC) (suport@adresemail.com@86.105.94.7)
by trader.adresemail.com with ESMTPA; 10 Sep 2013 06:28:00 -0000
Message-ID: <344A85AFB4444980A868799D66540940@traderPC>
From: "AdreseMail" <suport@adresemail.com>
To: <check-auth@verifier.port25.com>
Subject: spf rec
Date: Tue, 10 Sep 2013 09:29:23 +0300
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="----=_NextPart_000_0003_01CEAE08.3C1280A0"
X-Priority: 3
X-MSMail-Priority: Normal
Importance: Normal
X-Mailer: Microsoft Windows Live Mail 16.4.3508.205
X-MimeOLE: Produced By Microsoft MimeOLE V16.4.3508.205
Acesta este un mesaj cu mai multe par?i în format MIME.
------=_NextPart_000_0003_01CEAE08.3C1280A0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
spf record ?
------=_NextPart_000_0003_01CEAE08.3C1280A0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<HTML><HEAD></HEAD>
<BODY dir=3Dltr>
<DIV dir=3Dltr>
<DIV style=3D"FONT-SIZE: 12pt; FONT-FAMILY: 'Calibri'; COLOR: #000000">
<DIV>spf record ?</DIV>
<DIV> </DIV>
<DIV> </DIV></DIV></DIV></BODY></HTML>
------=_NextPart_000_0003_01CEAE08.3C1280A0--
But the mail are still going to Gmail SPAM folder and the same problem on header :
Received: from unknown (HELO traderPC) (suport@adresemail.com@86.105.94.7)
-
Under server setting in KloxoMR - goto Mail settings and for the mailserver name put the FQDN of the i.p. (reverse dns).
Example. If your main i.p. resolves back to server1.myserver.com - use that as your mail server name.
You have the HELO name set and it is not resolving back to that name.
-
If the mail server is set correctly (over looked your check-auth again) then check the reverse dns for your i.p.
If it resolves back to TraderPC - that is the problem. It has to resolve back to the FQDN.
-
86.105.94.7 resolves to
"ppp94105867.ambra.ro"
Top Level Domain: "ambra.ro"
Country IP Address: ROMANIA
This is your HELO problem. Your i.p. does not resolve back to your mail server name. This is a MUST.
You must have your provider set a PTR record for your i.p. - it needs to be trader.adresmail.com to have a correct HELO check (reverse dns to i.p.)
:)
-
But its already there http://www.intodns.com/adresemail.com (http://www.intodns.com/adresemail.com)
Also Server Mail Settings have correct 'My Name' :
-
Into DNS did you not see the BIG red block under MX concerning reverse dns PTR records?
You have none. So public email hosts try to verify your SPF and your HELO name and it comes back wrong.
You must have your provider put in a reverse dns record (PTR).
Look again at intodns.
-
I don't see any red but only green, I don't know where you sow that :( First thing I did when mail went to SPAM was to ask ISP to put PTR http://postimg.org/image/74481yd0f/ (http://postimg.org/image/74481yd0f/)
-
yes the PTR is now showing. At this point you should NOT be going to spam. Unless you have sent so much mail testing gmail has flagged the i.p.
I would mark mail as not spam. send mail to gmail and make sure it goes to inbox. then open a new gmail account and test.
it appears that some mail providers (hotmail and yahoo) will flag as junk/spam when a new ip starts sending mail to thier servers. if after time your mail is marked as not spam your server will start sending mail directly to inbox.
Has it started going to inbox?
-
Think about this.
Say it, we did to set wrong domain settings (without SPF and or domainkeys). And then we sent email to gmail.com. Yes, our message as 'spam'.
And then we corected domain settings and but why still as 'spam'?.
1. The answer is not every message check by qmail.com one-by-one. Gmail look up to their 'spam' database. If our email as 'spammer' in database so gmail think our message as 'spam'.
2. If someone set our message as 'not spam' in gmail panel, then gmail remove out email as 'spammer' in gmail database.
3. If no action like step 2 (set as 'no spam'), gmail will be evaluate periodically (say it every month) for 'spam' status in their database.
-
Well, the problem its still there , all mails are sent to gmail SPAM folder. Some friend used his own server to test my domain and mails are sent ok to inbox. I even changed PTR on ISP and accordinly hostname, mailname, mx, a and cname records. The exact same result. I asked hosting provider about IP and they told me I'am the first one using it. any spam test are fine . This problem is killing me.
-
Even when I send from webmail I get on gmail header 'Received: from unknown (HELO mx.zumzi.eu) (marius@zumzi.eu@127.0.0.1)'
Delivered-To: senuke22@gmail.com
Received: by 10.70.69.161 with SMTP id f1csp21771pdu;
Thu, 12 Sep 2013 06:45:34 -0700 (PDT)
X-Received: by 10.14.183.130 with SMTP id q2mr10764547eem.5.1378993534232;
Thu, 12 Sep 2013 06:45:34 -0700 (PDT)
Return-Path: <marius@zumzi.eu>
Received: from mx.zumzi.eu (mx.zumzi.eu. [188.215.51.97])
by mx.google.com with ESMTPS id p9si3192288eeu.204.1969.12.31.16.00.00
(version=TLSv1 cipher=RC4-SHA bits=128/128);
Thu, 12 Sep 2013 06:45:33 -0700 (PDT)
Received-SPF: pass (google.com: best guess record for domain of marius@zumzi.eu designates 188.215.51.97 as permitted sender) client-ip=188.215.51.97;
Authentication-Results: mx.google.com;
spf=pass (google.com: best guess record for domain of marius@zumzi.eu designates 188.215.51.97 as permitted sender) smtp.mail=marius@zumzi.eu;
dkim=pass header.i=@zumzi.eu
Comment: DomainKeys? See http://domainkeys.sourceforge.net/
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
s=private; d=zumzi.eu;
b=IELt3c1NpTXyVyrG6qE+Lpo2LW/QtiIz2eWQWP5eYAwWcmpw/Ww1yzqALDPuoIKzHZXyjYuSaBffXBUI6R+aYBSDgpr5jXOh10iqBk9qbSJoR8Slt7S4I8KuxLmo5DfRtr8U0j9DJvQOLwCrH6jyfj/lpGuxGFumfObuV8FUgr4=;
h=Received:Received:Mime-Version:X-Mailer:Message-ID:Date:Content-Type:From:Subject:To:X-Priority;
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=zumzi.eu; h=mime-version
:message-id:date:content-type:from:subject:to; s=private; bh=WkB
6nGuVC2SQoEad87298nOztas=; b=s4zNWgDOfXNjG5Rt+KSPkXkn1utYHvSgqNo
3lwovRT2sdEeVp9FvK3nO/OPAWaduysRr4zsR0P+D5IpIy3C5pStHEL44AXh3wlt
R+UGE7ZW6/y9Mm4OGChRPDRlm3xppSuWfAClpFrVbO0jKKqrtpWKbZ/eUkLsd9P+
qWsKN4lc=
Received: (qmail 7359 invoked from network); 12 Sep 2013 13:44:11 -0000
Received: from unknown (HELO mx.zumzi.eu) (marius@zumzi.eu@127.0.0.1)
by mx.zumzi.eu with ESMTPA; 12 Sep 2013 13:44:11 -0000
Mime-Version: 1.0
X-Mailer: AfterLogic WebMail PHP
Message-ID: <b9d50d40cd17dfdb688609f71249cafc@webmail.zumzi.eu>
Date: Thu, 12 Sep 2013 13:44:11 +0000
Content-Type: multipart/alternative;
boundary="----=_Part_918_628832272.1378993451"
From: marius@zumzi.eu
Subject: right
To: senuke22@gmail.com
X-Priority: 3 (Normal)
------=_Part_918_628832272.1378993451
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: Quoted-Printable
wrong
------=_Part_918_628832272.1378993451
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: Quoted-Printable
<!DOCTYPE html><html dir=3D"ltr"><head><meta http-equiv=3D"Content-Type" =
content=3D"text/html; charset=3Dutf-8" /><head><body><div><div>wrong</div=
></div></body></html>
------=_Part_918_628832272.1378993451--
-
I do not understand how every time you post your HELO name changes. Why is google not able to resolve where the mail is coming from?
I am not familiar with cloudflare.
-
I do not understand how every time you post your HELO name changes
I changed PTR and host name to be sure its not related to domain name.
I solved the problem, actually I have found what was it. I resotred backup to another server and mails are delivered inbox.
-
Have you set any SPF records? I usually use the SPF generator at http://www.royhochstenbach.com/projects/spfgenerator/ to resolve this for my clients.
-
Also, http://multirbl.valli.org/lookup/188.215.51.97.html shows your MX IP is on a few BLs. It would be worth checking into, as that would cause your mail to drop into people's spam folders.
-
thanks, hosting company told me those blacklists should not interfer with gmail as they're not important. Anyway ,using relay server works fine..