Hi Eric,

Thanks for sharing the link for domainkey.
I have already installed domainkey from older qmailtoaster with domainkeys
folder under /var/qmail/control/domainkeys.
Do i need to reinstall as per your guidance?
http://www.qmailtoaster.com/dkim.html
Is it suit for centos 6.7 32 and 64 bit.


On Fri, Sep 27, 2019 at 2:53 PM Eric's mail <ebr...@whitehorsetc.com> wrote:

> http://www.qmailtoaster.com/dkim.html
>
> Get Outlook for Android <https://aka.ms/ghei36>
>
>
>
>
> On Thu, Sep 26, 2019 at 10:41 PM -0600, "ChandranManikandan" <
> kand...@gmail.com> wrote:
>
> Hi Andy,
>>
>> I have installed DKIM in our server and there is private and public key
>> on our server.
>> I have added the public like below in our dns hosting provider (Godaddy)
>> control panel
>>
>> TXT
>> Host: rhc._domainkey.domainname
>> TXT value:  k=rsa; p=private key
>> TTL 1 hour
>>
>> But it's not signed in the email.
>>
>> I have configured MX,SPF,DMARC and DKIM in DNS server settings.
>>
>> Did i made a mistake in DNS settings?
>>
>> Could you help me
>>
>> On Fri, Sep 27, 2019 at 11:50 AM Andrew Swartz <awswa...@acsalaska.net>
>> wrote:
>>
>>> Your email does not contain a DKIM signature.
>>>
>>> The ARC* headers are signatures added by gmail after receipt.
>>>
>>> If you had a DKIM signature, it would be below this part of the header
>>> chain:
>>>
>>> Received: from mail.pan-asia.in ([49.128.33.86])
>>>         by mx.google.com with ESMTPS id 
>>> t6si1129421pgt.557.2019.09.25.21.12.54
>>>         for <kand...@gmail.com>
>>>         (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
>>>         Wed, 25 Sep 2019 21:12:55 -0700 (PDT)
>>> Received-SPF: pass (google.com: domain of m...@reliancehrconsulting.com 
>>> designates 49.128.33.86 as permitted sender) client-ip=49.128.33.86;
>>> Authentication-Results: mx.google.com;
>>>        spf=pass (google.com: domain of m...@reliancehrconsulting.com 
>>> designates 49.128.33.86 as permitted sender) 
>>> smtp.mailfrom=m...@reliancehrconsulting.com;
>>>        dmarc=pass (p=NONE sp=NONE dis=NONE) 
>>> header.from=reliancehrconsulting.com
>>>
>>>
>>> That and everything above it was added by gmail.
>>>
>>> You may have set up the DNS part of DKIM, but your server does not seem
>>> to be signing the emails.
>>>
>>> When you get it working, you can test by sending an email to a
>>> reflector, like this:
>>>
>>> sa-t...@sendmail.net
>>>
>>> It will analyze the smtp session and the email and then email the
>>> results back to you.
>>>
>>> There are several other reflectors listed at the bottom of this page:
>>>
>>>
>>> https://www.cisco.com/c/en/us/support/docs/security/email-security-appliance/118571-technote-esa-00.html
>>>
>>>
>>> Hope this helps,
>>>
>>> -Andy
>>>
>>>
>>>
>>> On 9/25/2019 8:39 PM, ChandranManikandan wrote:
>>>
>>> Hi Friends,
>>>
>>> I have tried to send an test email from my domain to gmail.
>>> It is going the gmail spam folder and i have configured SPF and DMARC in
>>> dns.
>>>
>>> Could you look at the below message header in gmail and help me to solve
>>> this problem.
>>>
>>> Delivered-To: kand...@gmail.com
>>> Received: by 2002:ac0:bf91:0:0:0:0:0 with SMTP id o17csp1656435imk;
>>>         Wed, 25 Sep 2019 21:12:55 -0700 (PDT)
>>> X-Google-Smtp-Source: 
>>> APXvYqxiLedyv3u6JDrnZQHvyrvIcmrH9n2kSrdj3NOCigD3cs53Rm6tgsJPdMbI9UBNqbqOc1Hz
>>> X-Received: by 2002:a63:1720:: with SMTP id 
>>> x32mr1332168pgl.289.1569471175444;
>>>         Wed, 25 Sep 2019 21:12:55 -0700 (PDT)
>>> ARC-Seal: i=1; a=rsa-sha256; t=1569471175; cv=none;
>>>         d=google.com; s=arc-20160816;
>>>         b=JGxA7PMxFt1qrwUPb9SXj40SHUhyOOPo+pENSvAaYhLkzdijEWpCgu5KWAW3yEfvWA
>>>          
>>> a2+Q9sPT9qJQZlwFvFmH4ZRi20KCLo9RMvbkRSW3L/L8Lzztic/OCfj2+o1HKmCKl4gk
>>>          
>>> bPWD4Tv9a/0Zg+EqIFUgJD0QhpFnSXMHmw59RoD3EurAA7zex+55NNRdnS2o7aluru0U
>>>          
>>> dYI9xixpZd276FwfDDy+FLSh5EYuYTmjkXEMEgmbNCMhGQ5WQ9AASzwVyDbXhFt9ixSN
>>>          
>>> JB8MKPw3P8cDyX/+Db1WoflU82H2KbVV+ON4GFhrvDVYkpQiWHbASNVipQfPj2YSItPP
>>>          g6Ng==
>>> ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; 
>>> s=arc-20160816;
>>>         h=importance:content-transfer-encoding:mime-version:user-agent:cc:to
>>>          :from:subject:date:message-id;
>>>         bh=g3zLYH4xKxcPrHOD18z9YfpQcnk/GaJedfustWU5uGs=;
>>>         b=XDv2dnoYR6tpeltyJ8tD82IKUIGCs0888LAX5xt4MqpL8IPAcUqA8xYLJvNx+heJH/
>>>          
>>> 5xT0tBciuRolqjCA7jRI2BSSTGmO7wKoEuuL8uvaYfpxM+7eGTNpnIV0mLH3V9z7SUr0
>>>          
>>> /Wcr/O3KstHzBxoYgAc71UguXyLG6LarOFgjcxvpVh4k3FbMKXJy+7wDDJC5zCfAcSQr
>>>          
>>> VrmJqYWJsc4VcgFrs0+O024BqMmlrLn5WycmtpLAZ0LP/tflbx4OzMMoL+K3AvpIdccB
>>>          
>>> hHtkCIyNislpUv6EqxxZLvumM2ysFL4Dd7M06ZpBxm5gIA3HVOL33E7JY2YQefIHv/io
>>>          vIpg==
>>> ARC-Authentication-Results: i=1; mx.google.com;
>>>        spf=pass (google.com: domain of m...@reliancehrconsulting.com 
>>> designates 49.128.33.86 as permitted sender) 
>>> smtp.mailfrom=m...@reliancehrconsulting.com;
>>>        dmarc=pass (p=NONE sp=NONE dis=NONE) 
>>> header.from=reliancehrconsulting.com
>>> Return-Path: <m...@reliancehrconsulting.com>
>>> Received: from mail.pan-asia.in ([49.128.33.86])
>>>         by mx.google.com with ESMTPS id 
>>> t6si1129421pgt.557.2019.09.25.21.12.54
>>>         for <kand...@gmail.com>
>>>         (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
>>>         Wed, 25 Sep 2019 21:12:55 -0700 (PDT)
>>> Received-SPF: pass (google.com: domain of m...@reliancehrconsulting.com 
>>> designates 49.128.33.86 as permitted sender) client-ip=49.128.33.86;
>>> Authentication-Results: mx.google.com;
>>>        spf=pass (google.com: domain of m...@reliancehrconsulting.com 
>>> designates 49.128.33.86 as permitted sender) 
>>> smtp.mailfrom=m...@reliancehrconsulting.com;
>>>        dmarc=pass (p=NONE sp=NONE dis=NONE) 
>>> header.from=reliancehrconsulting.com
>>> Received: (qmail 11583 invoked by uid 89); 26 Sep 2019 04:12:53 -0000
>>> Received: from unknown (HELO mail.reliancehrconsulting.com) 
>>> (m...@reliancehrconsulting.com@127.0.0.1)
>>>   by mail.pan-asia.in with ESMTPA; 26 Sep 2019 04:12:53 -0000
>>> Received: from 129.126.169.22
>>>         (SquirrelMail authenticated user m...@reliancehrconsulting.com)
>>>         by mail.reliancehrconsulting.com with HTTP;
>>>         Thu, 26 Sep 2019 12:12:53 +0800
>>> Message-ID: 
>>> <afd61f84dae4a2d7454e332d9f725c75.squir...@mail.reliancehrconsulting.com>
>>> Date: Thu, 26 Sep 2019 12:12:53 +0800
>>> Subject: test
>>> From: m...@reliancehrconsulting.com
>>> To: kand...@gmail.com
>>> Cc: m...@reliancehrconsulting.com
>>> User-Agent: SquirrelMail/1.4.22-0.qt.el6
>>> MIME-Version: 1.0
>>> Content-Type: text/plain;charset=iso-8859-1
>>> Content-Transfer-Encoding: 8bit
>>> X-Priority: 3 (Normal)
>>> Importance: Normal
>>>
>>> test
>>>
>>>
>>>
>>>
>>> --
>>>
>>>
>>> *Regards, Manikandan.C *
>>>
>>>
>>
>> --
>>
>>
>> *Regards,Manikandan.C*
>>
>

-- 


*Regards,Manikandan.C*

Reply via email to