On 2022-08-02 2:16 PM, Justin Case wrote:
I run the mailserver put its basically a tightly baked postfix dovecot under Synology DSM UI. So I won’t manually change config files. But “Ignore authorization for LAN connections” sounds reasonable, I have activated that now. Lets see if that helps.
It has to know 172.x is a "LAN" connection... if they don't have a way to set $mynetworks, I think you might want to add a raspi to your home lab to run a proper postfix instance. ;)
This does, however, not solve the problem that the hostname is not an FQDN and that it cannot be overridden with bsmtp. So I am still 100% away from a working solution :(
It's common enough, half of them get "localhost" from the resolver anyway and happily stick it in the mail header. I tend to specify From: addresses like "win-acme-on-server-X@mydomain" to know where it came from -- and if anyone decides to reply, they can keep the bounce.
As far as mail delivery goes, FQDN is not needed for anything. It's only there for that UCE check which should be disabled for "LAN connections".
PS. if bsmtp gets its hostname from the resolver, you might be able to fool it by setting up a nameserver for docker ips. Or maybe get names from docker network -- but I never looked into that.
Dima _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
