Test FAILED!
861 opened this issue · 2 comments
issue with running tests. Does anyone knew how to fix this? Where can I find the guide to set up the domain for this.
Thanks.
Start self-testing...
1..21
ok 1 SMF_CONFIG exist
ok 2 SMF_DOMAIN exist
ok 3 virtual maping source is set
ok 4 virtual maping data is set
ok 5 virtual maping db is set
ok 6 system hostname FQDN resolvable
ok 7 postfix myhostname FQDN & resolvable
ok 8 check other hostname setting
ok 9 confirm postfix is running
ok 10 confirm port 25 is open
ok 11 crond is running # skip skip this for 0.3.0 -> 0.4.0
ok 12 ESMTP STATTLS supported
ok 13 ESMTP AUTH supported
ok 14 ESMTP STARTTLS connect ok
ok 15 create user testi@testo.com by password test
ok 16 ESMTP AUTH by testi@testo.com/test
ok 17 ESMTP TLS AUTH by testi@testo.com/test
ok 18 deleting test user testi@testo.com
not ok 19 test DKIM keys
(in test file test/simple-mail-forwarder.bats, line 182)
`opendkim-testkey -d ${domain:13:-1} -s default -vvv' failed with status 69
Validating DKIM for jttj.org
opendkim-testkey: using default configfile /etc/opendkim/opendkim.conf
opendkim-testkey: checking key 'default._domainkey.jttj.org'
opendkim-testkey: 'default._domainkey.jttj.org' record not found
ok 20 test custom main.cf entries
ok 21 test custom master.cf entries
Test FAILED!
!!!!!!!!!!!!!!!!!!!! SYSTEM ERROR !!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!! SYSTEM ERROR !!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!! SYSTEM ERROR !!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!! SYSTEM ERROR !!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!! SYSTEM ERROR !!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!! SYSTEM ERROR !!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!! SYSTEM ERROR !!!!!!!!!!!!!!!!!!!!
But I'll pretend to run... good luck! :P
CONGRATULATIONS! System is UP and You are SET!
Powered by SMF - a Simple Mail Forwarder
View in DockerHub: https://hub.docker.com/r/zixia/simple-mail-forwarder
Init System for Servicing...
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[2021-03-14T22:03:41.388232] WARNING: Configuration file format is too old, syslog-ng is running in compatibility mode. Please update it to use the syslog-ng 3.27 format at your time of convenience. To upgrade the configuration, please review the warnings about incompatible changes printed by syslog-ng, and once completed change the @Version header at the top of the configuration file; config-version='3.9'
Mar 14 22:03:41 b8047d2210b5 syslog-ng[673]: syslog-ng starting up; version='3.27.1'
Mar 14 22:03:41 b8047d2210b5 syslog-ng[673]: WARNING: log-fifo-size() works differently starting with syslog-ng 3.22 to avoid dropping flow-controlled messages when log-fifo-size() is misconfigured. From now on, log-fifo-size() only affects messages that are not flow-controlled. (Flow-controlled log paths have the flags(flow-control) option set.) To enable the new behaviour, update the @Version string in your configuration and consider lowering the value of log-fifo-size().;
Mar 14 22:03:42 b8047d2210b5 postfix/master[768]: daemon started -- version 3.5.9, configuration /etc/postfix
i tried both ubuntu 20.04 and centos 8， they have the same issue as above
@861 do you have custom main.cf and/or master.cf entries? If yes, disable them temporarily and run the tests again. I am asking based on your output. It is likely that your custom configs break the default tests and nothing bad is actually going on.