Dear Mailcow community,
hope you had a successfull day so far!
I’m using Mailcow for quite a while now and it runs rock solid.
On Monday I’ve updated my instance from version 2023-11 to 2023-12a, after which my HP printer isn’t able to send scans via email anymore.
Due I’m using an application password, I’ve generated a new one without success. Even a whole reset of my printer didn’t fix the issue.
When testing my scan to mail configuration the printer throws a “System Failure” without further details. When changing the credentials from Mailcow to my Gmail account it works flawless - so it needs to be a problem with my mailcow server.
The Postifx logs contain the following entry when clicking the “Test” button in the printer UI (sensitive data was replaced by “xxx”):
E84465C0968: replace: header Received: from printer01-a (pxxxxxxxx.dip0.t-ipconnect.de [xxx.xxx.xxx.xxx])??(using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits))??(No client certificate requested)??(Authenticated send from pxxxxxxxx.dip0.t-ipconnect.de[xxx.xxx.xxx.xxx]; from=<noreply@my-domain.com> to=<me@my-domain.com> proto=ESMTP helo=<printer01-a>: Received: from [127.0.0.1] (localhost [127.0.0.1]) by localhost (Mailerdaemon) with ESMTPSA id E84465C0968??for <me@my-domain.com>; Wed, 10 Jan 2024 23:06:02 +0100 (CET)
After some investigation I’ve found out, that just the scan to mail function is broken. The printer can still send system messages, i.e. about missing paper or ink, with the same configuration as at “scan to mail” without any error.
Do you have any idea how I could further investigate this issue?
Some system facts:
VPS at Netcup
Ubuntu 20.04.6 LTS
firewalld instead of ufw
Mailcow 2023-12a
Looking forward to your reply and supprt.
Kind regards
Tom(trix)