Errors don't seem to be logged correctly

[h4nsen]

Trying to debug why my parse-dmarc installation cannot connect to my IMAP server.

It seems only log-statements like log.Printf("Connecting to %s...", addr) actually make it to the logs.

Return-statements, like return fmt.Errorf("failed to connect: %w", err) cannot be found anywhere.

[meysam81]

@h4nsen

Apart from the log, how would I reproduce this?

can you share some steps? which imap provider are you using?

are you using docker or the pre-compiled binaries?

[h4nsen]

@meysam81

I'm trying to connect to my local mailcow instance. Both mailcow and parse-dmarc run in docker instances with internet access.

When using SSL/TLS I get some unknown error in parse-dmarc (can't see it due to missing logs)

When I connect using an openssl-client, I can connect just fine. So I suspect theres some problems with validating the certificate chain in parde-dmarc.

If I try to connect without TLS (which my mailcow instance is set to now allow) I'm able to connect to the server. But the error-message from mailcow that plaintext-authentication is not allowed is not logged anywhere.

I guess one way to reproduce the error, would simply be to provide incorrect credentials (username/password). That would log a succeeded connection but not invalid credentials.

[meysam81]

@h4nsen

can you try again with this docker image: meysam81/parse-dmarc:21908415451

built here:

https://github.com/meysam81/parse-dmarc/actions/runs/21908415451/job/63254978260

once ready, will ship it to the next release.

[h4nsen]

Perfect, error messages are clearly logged now.

Thanks! And sorry for the delay before I was able to test.