DKIM-Patch 1.1.6 4


Es ist eine neue Version des DKIM-Patch für ISPConfig verfügbar.

Download: DKIM-Patch

Changes to 1.1.5:


allow the admin to change txt-records for dkim, dmarc and spf directly
fixed fr-language for the resync-tool
fixed regex for spf-includes


Kommentar erstellen

Deine E-Mail-Adresse wird nicht veröffentlicht. Erforderliche Felder sind markiert *

4 Gedanken zu “DKIM-Patch 1.1.6

  • Stephane

    Hi,
    Is there a way to increase the input in the TXT editing ?
    Cause when I try to copy / past the DKIM key that doesn’t fit.
    => Try to copy / past cause the server A is for DNS and server B for mail.

    DKIM strength is set to “strong”.

    Kind regards.

    • Florian Schaal Beitragsautor

      If 255 chars is too short for your needs, you can increase maxlength for data in interface/web/dns/form/dns_txt.tform.php

      If you manage both severs within one interface, you can insert the dns-record for dkim with the dkim-button.

  • Florian

    As far as I can see you integrated a suffix for the DKIM-Selector when generating a new private key under ISPConfig > E-Mail > E-Mail Domain. A possibly existing old / former key however doesn’t get cleaned up in DNS. Is that by intention? Furthermore using the “recreate DKIM Priovate-key” more than once leads to a very long selector like e.g. “default14228923981422893419”. So it seems that the suffix is not removed before appending a new one. Is that a bug?

    Independent from that: As you seem to be German native, any plans to develop a German translation for those really helpful patches?

    • Florian Schaal Beitragsautor

      If you create a new key-pair, you see two records in the dns. This is attended to make sure, that a receiver can verify a mail even if the mail is delivered for certain reasons a few days later. I don´t think that it is a problem if you have two dkim-records with different selectors in your dns-zone and that´s also the reason why a timestamp is added to the latest selector. If you dislike such selectors, you can change the value at any time.
      To disable an older key, you can (as admin) change the txt-record.
      Feel free to translate everything. 😉 You can register at my git, fork something, make your changes, submit them and create a merge-request. Or send me your translated lng-files by mail.