Forwarding failed

[l987845225]

Can I ask, is the project invalid? Or can it only be forwarded to Gmail? I tested with Hotmail and Foxmail, and in the end, the result only verified DKIM and did not perform any other operations. The email sent shows that it was sent successfully, but the forwarded email was not received, and it is not in the junk mailbox either. Here is the complete log.

>> Chdir to /app...
 ____  _                 _         __  __       _ _
/ ___|(_)_ __ ___  _ __ | | ___   |  \/  | __ _(_) |
\___ \| | '_ ` _ \| '_ \| |/ _ \  | |\/| |/ _` | | |
 ___) | | | | | | | |_) | |  __/  | |  | | (_| | | |
|____/|_|_| |_| |_| .__/|_|\___|  |_|  |_|\__,_|_|_|
                  |_|
  _____                                _
 |  ___|__  _ ____      ____ _ _ __ __| | ___ _ __
 | |_ / _ \| '__\ \ /\ / / _` | '__/ _` |/ _ \ '__|
 |  _| (_) | |   \ V  V / (_| | | | (_| |  __/ |
 |_|  \___/|_|    \_/\_/ \__,_|_|  \__,_|\___|_|

v1.4.7
Source#c2fe07d Wed Oct 13 12:11:40 2021 +0000 * master
Built on Wed Oct 13 12:11:55 UTC 2021 by buildkitsandbox

>> ENV SMF_DOMAIN not set.
>> ENV SMF_CONFIG found. value:[@xxxxxx.org:xxxxx@hotmail.com:test]
>> ARGV arguments found. value:[start]
Generating an EC private key
writing new private key to 'smtp.ec.key'
-----
>> SMF_CONFIG found in ENV. use this settings for forward maps.
>> Setting password[test] for user @xxxxxx.org ...
postmap: warning: /etc/postfix/virtual.db: duplicate entry: "@xxxxxx.org"
>> Set hostname to xxxxxx.org
Postfix logging configuration
Postfix will use the default logging configuration: /dev/stdout
OpenDKIM: Keys for xxxxxx.org not found, generating witk keysize 2048...
opendkim-genkey: generating private key
opendkim-genkey: private key written to default.private
opendkim-genkey: extracting public key
opendkim-genkey: DNS TXT record written to default.txt
Inserting xxmail.eu.org data to /etc/opendkim/{KeyTable, SigningTable, TrustedHosts}
OpenDKIM: this TXT record for xxxxxx.org should be present:
default._domainkey      IN      TXT     ( "v=DKIM1; k=rsa; "
          "p=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxKCAQEAoCthugCy3Nky5IzqVIFx2ZOIuZUTEva+DUdCz2kg7lptmU27fkFxex0Bfk0KK9rUjVI2abPIGfi5ZrBG0g5l7tY9peXWRaz/2+FuQEiiTy9T8KbsQfF1i8gLPwtPe14rPyXY09zyyPFtf1aI9mh2i9Ti0/P7AkQCR4ifw1u+T5axWm+19/3NnNWE+wEQlEmFtgU9wiK9iLoS6e"
          "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxB7RS37q/vH1j+9lv4c9Dp2vGdxH9xH+VvySzBSPk7BvHOWKxrXEPdv6ErS2NW+pagfL6fArMO3PGUNJqcHwVu94O87LPEwgMYVIzQIDAQAB" )  ; ----- DKIM key default for xxxxxx.org
Configuring DKIM key settings in /etc/opendkim/opendkim.conf
Postfix main.cf custom entries from SMF_POSTFIXMAIN_
Postfix master.cf custom entries from SMF_POSTFIXMASTER_
Editing /etc/postfix/master.cf, adding missing entry for postlog unix-domain datagram service
>> Start self-testing...
1..24
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 xxxxxx.org
# opendkim-testkey: using default configfile /etc/opendkim/opendkim.conf
# opendkim-testkey: checking key 'default._domainkey.xxxxxxorg'
# opendkim-testkey: 'default._domainkey.xxxxxx.org' record not found
ok 20 test custom main.cf entries
ok 21 test custom master.cf entries
ok 22 test default postfix logging configuration
ok 23 test custom postfix logging configuration with an error
ok 24 test custom postfix logging configuration
>> 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
[2023-10-05T02:45:51.532135] 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'
Oct  5 02:45:51 dcdba899fbb8 syslog-ng[895]: syslog-ng starting up; version='3.27.1'
Oct  5 02:45:51 dcdba899fbb8 syslog-ng[895]: 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().;
[services.d] done.
Oct  5 02:46:16 dcdba899fbb8 opendkim[902]: 6AEAC6FF1: DKIM verification successful

[resolS]

I'm having the same issue, but with gmail. I can't figure out what the problem is.

[VarunBatraIT]

I managed to do this, I did these four things in total:

forward all email add spf add dkim create filter in gmail to avoid going to spam.

Tutorial I wrote: https://webapplicationconsultant.com/docker/how-to-use-docker-to-forward-emails-sent-to-your-domain-to-your-email-works-for-gmail/

[huan]

Thanks for sharing this great article to the community!

I’d like to invite you to add your blog to the README so that it can help more users in the future.

Please feel free to send a Pull Request, thanks again.

[VarunBatraIT]

Hi @huan Thanks for the invitation, it meant a lot to me. I think your read me more than sufficient to get started and article will only be redundant as it is only subset of your settings only in docker-compose variation. I am not sure where should I place it in readme. Perhaps, you can add under a separate section "Useful articles" or just paste that docker-compose.yml from my blog. Whatever you think is best for the community.

[huan]

Hi @VarunBatraIT ,

More tutorials like yours to the README will be of great value to the community.

Adding under a separate section "Useful articles" is a good idea; please feel free to send a PR to add your blog link, and we can always revise it after the PR has been merged.

[VarunBatraIT]

Couldn't agree more. I have created #127

[huan]

Merged!