On 6/27/25 00:23, BetaRays wrote:
Basically, lmtp-delivery on my system is just a special user that is given rights to access the LMTP socket: if your socket is accessible to everyone, you can use nobody.
/var/cyrus/socket/lmtp is accessible with 777 root:cyrus privileges on my system.
/var/cyrus/socket/lmtpunix-0.lock is 600 cyrus:cyrus though. I have appended my virtual table with the 'uolys cyrus' link:
uo...@on.lt vla...@on.lt uo...@sala.online.lt vla...@on.lt vla...@online.lt vla...@on.lt vla...@on.lt uolys uolys cyrus
Unfortunately, no effect, the same rooting after 'smtpctl update table virtuals'.
cyrus:cyrus is a bot user (Cyrus mail server UID 60) on my system. I cannot put it in my group GID uolys, because Cyrus should stay isolated, private process. And I doubt that this would be the ultimate solution: other users (a...@on.lt, g...@on.lt) now receive mail via their own routes (user=ab, user=gm) instead of mine user=uolys.
At this point I would suggest enabling tracing and/or debug logs with smtpctl, I think there is a tracing category that logs alias lookups step by step.
I kept a few of 'smtpctl trace smtp, transfer, expand aliases' enabled, now I have enabled all of them (smtpctl trace all), I will monitor more closely. Also FairEmail on my phone is capable to show mail delivery traces (alogside mail headers). Thank you for the help!
