When some user send email to user1, only user2 receives message, as expected.
When mail is sent to user1 and user2, no one receives mail.
When mail is sent to user2 and user1, both accounts receive mail.
The results may vary, but in general rule does not work as expected in every situation. I’ve been in contact with Axigen support for past couple of days, but it got me nowhere closer to solution, nor they want to confirm the bug.
On my test server I could not replicate the reported behavior (when sending from an external email address), meaning all messages where delivered to user2, with no messages delivered to user1.
Because the way “incoming message rules” are evaluated it is very difficult to explain what is happening in your particular case.
This is why I may suggest to create a fresh new domain with 2 users (beside postmaster), create the redirect rule (via WebMail > Settings > Filters) for user1. In such way we’ll be sure that only the server level filter may interact with the message flow.
Before checking if the problem still replicate please increase the log level to Protocol Communication for SMTP Receiving and Processing services and test again. If the problem still exists than please share the log file (usually everything.txt, if needed please archive it) with some hints to what to look for.
Please also mention the Axigen version you are using so I could redo my tests with a similar version (if not exactly the same).
One possible explanation is that you may have created the match-redirect rule at domain level (via WebAdmin).
Could you please delete the rule from domain level and re-create it (via WebAdmin) at account level (which is somehow similar with my tests - I’ve defined the rule via WebMail interface of user1)?
I’m not suggesting to bypass but I’m trying to explain that the redirect rule you like to implement (if one account is into TO or CC of a message redirect the message to another account without keeping the message) should be added at account level (via WebAdmin or WebMail).
At domain level it will produce abnormal results as you already observed.
Nevertheless we’ll try to reproduce on our side and if successful bring into our dev team attention in order to have a final confirmation if this is a bug or not.