Sender Verification causing issues (printer)

zyrex

A user is trying to setup a printer to scan to email, however he get’s denied even though he is authenticated.
I’ve disabled sender verification on his mailbox, but he still gets the same error as before I did:

NOQUEUE: reject: RCPT from xx.xx.xx-.customer.lyse.net[109.247.xx.xx]: 504 5.5.2 <SEC001599EBA575>: Helo command rejected: need fully-qualified hostname; from=<post@zo**.org> to=<post@zo*.org> proto=ESMTP helo=<SEC001599EBA575>

So it claims to be because how a non-fqdn hostname, however there’s no place in the printer’s settings to adjust this any further.

Shouldn’t this be a non-issue when I’ve set “Allow send as: *” and it says Sender check disabled in red?

Or is this a different problem?
Thanks!

diekuh

The problem is using port 25 and not 587 or 465 🙂 and not authenticating (there is no auth. on port 25).

zyrex

Aah, yes - that makes sense, then - thanks!

So the reason for trying port 25, and now understand why it worked… This is the trouble the printer gives with port 587:

lost connection after STARTTLS from xxxxxx.customer.lyse.net[109.247..]
warning: TLS library problem: error:14209102:SSL routines:tls_early_post_process_client_hello:unsupported protocol:../ssl/statem/statem_srvr.c:1661:
info SSL_accept error from xxxxxx.customer.lyse.net[109.247..]: -1

I haven’t tried this yet, but this is probably because the printer doesn’t support TLS 1.2.. I am not really interested in enabling 1.0/1.1.

So in this case, I guess I’m SOL.
Samsung CLX-6260 just out there, giving me grief.

AllgaeuerBraunvie

I have Brother MFC printers and I’m facing the same issue that these don’t support TLS 1.2 yet. In general I don’t want to enable TLS 1.0/TLS 1.1 for general use. Anyway for sending FAXes via email2fax gateway i’d accept the risk.

Is it possible to have beside STARTTLS with port 587 a second port , e.g., 588, that is also using STARTTLS but also allowing the unsecure TLS 1.0/1.1. ?

A second option would be to put a separate smtp gateway docker container somewhere to your LAN for this printer only. That container would take the emails locally with the insecure protocol and forward it with the recent secure protocol to the mailcow.