Open VVD opened 1 year ago
Part 1 here is indeed a bug, but I'm not so sure about the second proposal. It makes the query twice as big, just to add a special case to an otherwise unsupported scenario.
Consider any third party server which has no way of knowing that ALIAS1@my.domain
is an alias to USER1@my.domain
. That server would naturally reject any messages from USER1@my.domain
to any private group if only ALIAS1@my.domain
, but not USER1@my.domain
were a member of that group. We do exactly the same.
I say let's leave that second part as it is.
However, while looking at part 1, I noticed how stupid our queries in Exim config file are. I'm going to rewrite them to replace some WHERE
conditions with JOIN
clauses.
Query from example file
docs/debian-conf.d/router/250_vexim_virtual_domains
.If user added in any group, then he can send emails in any non-public group too - need
g.id = c.group_id
:If alias was added in non-public group, then sender from main login can't send emails to this group. This query fixed this:
Example: mailbox
USER1@my.domain
, aliasALIAS1@my.domain
=>USER1@my.domain
, non-public groupGROUP1@my.domain
with memberALIAS1@my.domain
. With old sql queryUSER1@my.domain
can't write in non-public groupGROUP1@my.domain
, onlyALIAS1@my.domain
can. With new sql queryUSER1@my.domain
can write in non-public groupGROUP1@my.domain
too.