Webmail filters, working as they should?

1

Hi

I receive lots of email and I like using filters. However, with Axigen I find it very difficult and rules end up working in ways I don’t expect.

I expect to create a set of filters that are executed in order, if conditions are matched, the actions executed.

I also expect to be able to “stop processing” the rest of filters if a more important rule wants other not to be processed.

With axigen all rules seem to be executed no matter what. and Move may actually duplicate emails if several rules want to move the message to a folder.

Adding to this is also the fact that SPAM seems to be managed by rules. That means that I can get SPAM emails in the SPAM folder but also copied to another folder if there was a filter triggered along the way.

Honestly this does not work as it should: if I have to single out the 2 major issues:

  • Move should never result in multiple emails been created. Perhaps 2 moves in a row make the email end up where you don’t expect. But there is always one email.

  • I need to be able to stop the rest of the filters from processing. For example, if the email is SPAM move to SPAM folder, and stop processing any other filter.

I am getting something wrong? Is anybody else having problem with filters?

2

Hello Rafael,

Please take into consideration that all filters (at server level / domain level / user level) implies a “stop” action at the end and you could not overpass this setup.

$ cat /mnt/axifuse/domains/test.domain.tld/accounts/test.account/wmFilter.sieve 
##Filter id=9 name="forward-to-gmail-com" enabled=1
if allof (
        header :contains  ["Subject"] ["important"]
) {
        redirect :copy  "xxx@gmail.com";
        stop;
}

Thus you should consider to promote your SPAM rule as the first one.

Regarding your second report (having multiple location where the message is delivered) this is usually the result of “move” operations requested at different levels. For example the message is delivered to Spam folder due to a server level filter but delivered also to Inbox due to a whitelist filter set at account level

You could follow the decision path looking to Processing service logs (you may consider to set the log level to Protocol Communication) for an incoming message.

HTH,
Ioan

3

@indreias, ok, let me review what is going on…