Cuttlefish should scream when DKIM signing can't be done
Or at least logging.
When domain mismatch (from and dkim), sending unsingned mail, silently, is just a treason.
@athoune that doesn't sound good :frowning:
To make this easy to fix can you clearly describe what it does now and what it should do instead?
Hum, it should an error. The mail is not sent, SMTP scream. If you wont to use strange domain, just use an "app" without DKIM.
So you expect Cuttlefish to reject the message if DKIM signing can't be done :+1:
yes.
It's intentional that it falls back to not signing mails if the domains don't match. This way at least emails will go out even if they're sent from the wrong domain and cuttlefish will do its best to deliver them.
However, I agree that it is absolutely wrong that it does this completely silently. It should log warnings/errors. This could use #307.