Die verwendeten DNS-Server müssen bei einer Key-Stärke > 1024b einen TXT-Record mit der Länge > 255 Zeichen unterstützten. Ansonsten liefert amavis beim Testen der Keys
public key: OpenSSL error: bad base64 decode
.
Werden eigene DNS (bind) mit ISPConfig genutzt, reicht es, wenn die Datenbank dbispconfig auch auf den DNS-Server angepasst wird:
ALTER TABLE `dns_rr` CHANGE `data` `data` TEXT NOT NULL DEFAULT '';
Hi Florian,
I installed your DKIM patch and followed your tutorial : http://blog.schaal-24.de/ispconfig/ispconfig-dkim-patch/?lang=en
The patch installed fine I think but I have the “invalid (public key: OpenSSL error: bad base64 decode)” message when testing the domain key.
I applied the following fix : http://blog.schaal-24.de/ispconfig/dkim-patch-public-key-openssl-error-bad-base64-decode/?lang=en
I changed the data field format in the dbispconfig database and even tried to delete the DKIM record, regenerate a new key, restart amavis but still the same result to “amavis-new testkeys”.
I’m running debian 8 with ISPConfig 3.0.5.4p8
Thanks for your help,
David
public key: OpenSSL error: bad base64 decode is usually related to a wrong key in the dns.
Hello,
could I pleased for update of new version? 🙂
ISPConfig 3.0.5.4p6
Download: http://www.ispconfig.org/files/file/2-ispconfig/
Changelog: http://bugtracker.ispconfig.org/index.php?do=index&tasks=&project=3&due=84&status%5B%5D=
Thank you
??? You can use the latest version with ISPConfig 3.0.5.4p6
CAUTITION:
This script is for ISPConfig >= 3.0.5.4p2 – You are using 3.0.5.4p6
Aborting setup – please update ISPCOnfig installation first.
See INSTALL.TXT for manual-setup or get an older version from this plugin
Please update the patch from the git or download the latest version again. I just forgot to merge the new installer into the master-branch. 😉
thanks 🙂