Here is my DNS Record.

dkim._domainkey.legaljobsinusa.com  TXT 86400  k=rsa; 
p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQC/CvLQsXjX0+90gy6wLr5uzfmHR6Ot9ziBDlFkogWDkthCeli9NgBActwET2yTTYWAdY5ClBcpmAF+JquzTLaGksATYBov1U9xrt2UVSDBWiipCSawmxSUyJpUFC8xwB/Emcso5sBuD28hHJq0HhImiw9XqT5qv+uclKxor5+liwIDAQAB


Regards,
Linux Admin Team

  ----- Original Message ----- 
  From: PRAJITH 
  To: LinuxAdmin 
  Cc: [email protected] 
  Sent: Monday, July 13, 2015 5:43 PM
  Subject: Re: [exim] Exim4 vs Gmail - DKIM algorithms incompatibility


  Can you paste here your dkim txt record? 



  On 13 July 2015 at 17:17, LinuxAdmin <[email protected]> wrote:

    Hi Jon Gerdes,

    Pls find the complete header for my mail. At DNS level the Public key 
entered correcly rest of the Domains like Yahoo susccessfully verified it.

    
======================================================================================
    Delivered-To: [email protected]
    Received: by 10.202.174.140 with SMTP id x134csp1464346oie;
           Mon, 13 Jul 2015 04:36:29 -0700 (PDT)
    X-Received: by 10.140.234.142 with SMTP id 
f136mr53828725qhc.16.1436787389747;
           Mon, 13 Jul 2015 04:36:29 -0700 (PDT)
    Return-Path: <[email protected]>
    Received: from ovh2.vpsemailsrvr.com (ovh2.vpsemailsrvr.com. [192.95.30.44])
           by mx.google.com with ESMTPS id 
f19si20232787qhc.91.2015.07.13.04.36.28
           for <[email protected]>
           (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
           Mon, 13 Jul 2015 04:36:29 -0700 (PDT)
    Received-SPF: pass (google.com: domain of [email protected] 
designates 192.95.30.44 as permitted sender) client-ip=192.95.30.44;
    Authentication-Results: mx.google.com;
          spf=pass (google.com: domain of [email protected] designates 
192.95.30.44 as permitted sender) [email protected];
          dkim=fail [email protected];
          dmarc=pass (p=QUARANTINE dis=NONE) header.from=legaljobsinusa.com
    Message-ID: <[email protected]>
    X-Google-Original-Message-ID: <1436787387.<[email protected]>>
    DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; 
d=legaljobsinusa.com; s=dkim;
            h=Date:Message-ID:from:Subject:To; 
bh=hbHsegzs2riFX6atLQLOBj5njrfb8Jzzj1yEZQ8DixY=;
            
b=P0W3Cq9rKYM0fWsA+G8KSV9uV3BbOXA3F3C8IaP3iH7dNo1/TjXJWuRvB9vPLKEs/NQ8rWGX9WYdJ0wMk0ZYLSZ/cysjmgNgnEDwPy5ADKTSvwVYy9duRU9j30Fqf/9xLdS8Lai4k1cWU+DrCA8yPDn4AaRiejceq4Ks6gV3wfA=;
    Received: from root by ovh2.vpsemailsrvr.com with local (Exim 4.84)
            (envelope-from <[email protected]>)
            id 1ZEc27-0006UX-AJ
            for [email protected]; Mon, 13 Jul 2015 06:36:27 -0500
    To: [email protected]
    Subject:  Hi Ravi This is your info
    from: <[email protected]>
    X-virtual-MTA: virtualgroup1r
    Date: Mon, 13 Jul 2015 06:36:27 -0500

    Hi Ravi This is your 
info=========================================================================================================================Also
 pls find output of "exim -bV"# exim -bVExim version 4.84 #2 built 09-Oct-2014 
09:21:51Copyright (c) University of Cambridge, 1995 - 2014(c) The Exim 
Maintainers and contributors in ACKNOWLEDGMENTS file, 2007 - 2014Berkeley DB: 
Berkeley DB 4.7.25: (April  4, 2012)Support for: crypteq iconv() IPv6 PAM Perl 
Expand_dlfunc TCPwrappers OpenSSL Content_Scanning DKIM Old_Demime PRDR OCSP 
Experimental_SPF Experimental_SRS Experimental_DMARC Experimental_Proxy 
Experimental_TPDA Experimental_CertnamesLookups (built-in): lsearch wildlsearch 
nwildlsearch iplsearch cdb dbm dbmjz dbmnz dnsdb dsearch ldap ldapdn ldapm nis 
nis0 nisplus passwd sqliteLookups (as-module):Authenticators: cram_md5 
cyrus_sasl dovecot plaintext spaRouters: accept dnslookup ipliteral manualroute 
queryprogram redirectTransports: appendfile/maildir/mailstore/mbx autoreply 
lmtp pipe smtpFixed never_users: 0Size of off_t: 8Configuration file is 
/etc/exim/exim.conf======================================================================================================================

    Regards,
    Dilip Jadav

    ----- Original Message ----- From: "Jon Gerdes" <[email protected]>
    To: <[email protected]>
    Sent: Saturday, July 11, 2015 5:31 AM
    Subject: Re: [exim] Exim4 vs Gmail - DKIM algorithms incompatibility




      On Fri, 2015-07-10 at 16:39 +0200, Heiko Schlittermann wrote:

        LinuxAdmin <[email protected]> (Fr 10 Jul 2015 13:05:08 CEST):
        > I am facing problem in DKIM Signing for Gmail, rest all domins
        > verify its very vell.
        >


      ...


        If google can't resolve

            txt selector._domainkey.example.com

        they can't verify the domainkey signature.

        Please do not obfuscate. And, what does „exim -bV“ tell you?


      ...

      As Heiko said: Please don't obfuscate.  That makes it hard to diagnose
      your problem without having to spend quality time filling in the
      missing bits.

      You wont lose any security in leaving email headers unmolested, unless
      you are doing it as a courtesy when quoting information about someone
      else's email.  Even then, it is just a courtesy and not a security
      enhancement.

      However: we will probably need your selector (unless it really is
      s=selector) but never diclose your private key, for obvious reasons.

      Cheers
      Jon


      Blueloop Ltd
      01460 271055
      https://www.blueloop.net
      Blueloop House, Ilchester Road, YEOVIL, BA21 3AA Registered England & 
Wales - 3981322


      -- 
      ## List details at https://lists.exim.org/mailman/listinfo/exim-users
      ## Exim details at http://www.exim.org/
      ## Please use the Wiki with this list - http://wiki.exim.org/ 




    -- 
    ## List details at https://lists.exim.org/mailman/listinfo/exim-users
    ## Exim details at http://www.exim.org/
    ## Please use the Wiki with this list - http://wiki.exim.org/

-- 
## List details at https://lists.exim.org/mailman/listinfo/exim-users
## Exim details at http://www.exim.org/
## Please use the Wiki with this list - http://wiki.exim.org/

Reply via email to