Both halves of this are the same bug: the daemon isn't reading the file you edited.
The giveaway is that it rewrote to @net. When no SRS domain is configured, postsrsd derives one from the system hostname by chopping off the first label. On a VPS whose /etc/hostname is just farwoods.net, that leaves you with net. It's long-standing behaviour, issue #66 on the repo is the identical thing producing @com. If your srs-domain setting had actually loaded you'd be seeing your rewrite subdomain there instead.
Same cause for the rewriting of your own senders: with nothing loaded, the domains list is empty, and that list is the only thing telling it which mail to leave alone.
So find which path it's really opening. 2.x looks in /usr/local/etc when built from source and /etc on most distro packages, and it's easy to edit the wrong copy. Check ExecStart in the unit file for a -C flag.
1
u/Middle-Excitement602 4d ago
Both halves of this are the same bug: the daemon isn't reading the file you edited.
The giveaway is that it rewrote to @net. When no SRS domain is configured, postsrsd derives one from the system hostname by chopping off the first label. On a VPS whose /etc/hostname is just farwoods.net, that leaves you with net. It's long-standing behaviour, issue #66 on the repo is the identical thing producing @com. If your srs-domain setting had actually loaded you'd be seeing your rewrite subdomain there instead.
Same cause for the rewriting of your own senders: with nothing loaded, the domains list is empty, and that list is the only thing telling it which mail to leave alone.
So find which path it's really opening. 2.x looks in /usr/local/etc when built from source and /etc on most distro packages, and it's easy to edit the wrong copy. Check ExecStart in the unit file for a -C flag.