Google doesn't recognize dkim

Discussion in 'General' started by buhler, Feb 6, 2024.

  1. buhler

    buhler Member

    Google doesn't recognize dkim
    I sent an email to my google account with a copy to my hotmail and yahoo accounts.
    Hotmail and yahoo recognize dkim, but gmail doesn't.
    Look at the headers:

    Hotmail:
    Authentication-Results: spf=pass (sender IP is xxxxxxxxxxxx) smtp.mailfrom=simaoebuhler.com.br; dkim=pass (signature was verified) header.d=simaoebuhler.com.br;dmarc=pass action=none header.from=simaoebuhler.com.br;compauth=pass reason=100

    yahoo
    Authentication-Results: atlas-production.v2-mail-prod1-gq1.omega.yahoo.com; dkim=pass [email protected] header.s=default; spf=pass smtp.mailfrom=simaoebuhler.com.br; dmarc=pass(p=NONE) header.from=simaoebuhler.com.br;

    gmail
    Authentication-Results: mx.google.com; dkim=fail [email protected] header.s=default header.b=xxxxxx; spf=pass (google.com: domain of [email protected] designates xxxxxxxxxxxx as permitted sender) [email protected]; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=simaoebuhler.com.br

    Has something changed in gmail so that ISPConfig isn't prepared? Because it's the same email that was sent with a copy. my ISPCONFIG version 3.2.11p1
     
    Last edited: Feb 6, 2024
  2. till

    till Super Moderator Staff Member ISPConfig Developer

    I don't think so, and I have not recognized any issues sending it to Gmail. Besides that, ISPConfig is not involved in signing emails with DKIM; It is just a control panel for hosting systems. The DKIM signing is done by either Rspamd or Amavis on your system, depending on which you have installed.
     
  3. buhler

    buhler Member

    DEbian 10 installed following the tutorial:
    The Perfect Server - Debian 10 (Buster) with Apache, BIND, Dovecot, PureFTPD and ISPConfig 3.2 (howtoforge.com)
    I've had this ISPConfig installed for a long time and now this has started to happen
     
  4. Taleman

    Taleman Well-Known Member HowtoForge Supporter

  5. pyte

    pyte Well-Known Member HowtoForge Supporter

    The records are fine for me. All 4 of your NS servers report the same record. Did you by any chance change the DKIM Key recently and made the test shortly afterwards?

    And your DMARC records seems to contain a syntax error, you may want to have a look into it.
     
  6. buhler

    buhler Member

    I discovered that if I leave dmarc with policy none it doesn't pass the google check. If I leave it as reject it works as expected.
     
  7. pyte

    pyte Well-Known Member HowtoForge Supporter

    The issue i mentioned with your DMARC record is the reporting format. Your records says
    Code:
    rf=afrf:iodef;
    I guess it can either be afrf or iodef so rf=afrf; for example. Otherwise it results in a syntax error.
     
  8. buhler

    buhler Member

    I've just sent an email and the dmarc result looks like this:

    ARC-Authentication-Results: i=1; mx.google.com; dkim=pass [email protected] header.s=default header.b=Q6GwHoBf; spf=pass (google.com: domain of [email protected] designates xxxxxxxxxxx as permitted sender) [email protected]; dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=simaoebuhler.com.br

    I'll change the dmarc policy from reject to none and test it in about 1 hour
     
    Last edited: Feb 7, 2024
  9. buhler

    buhler Member

    Now it seems to be working.
    It must have been a problem with google itself.
    Because I haven't changed anything in the configuration

    ARC-Authentication-Results: i=1; mx.google.com; dkim=pass [email protected] header.s=default header.b=jqQhiuBs; spf=pass (google.com: domain of [email protected] designates 172.98.193.91 as permitted sender) [email protected]; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=simaoebuhler.com.br
     
    pyte likes this.

Share This Page