You should be able to solve that part by using Attributes / Originates from a non-local source / Move message to another user (instead of Always triggers).

/Rolf 

I've started using Mercury to collect my mail but have continued to use my old system for actual mail distribution.

So Mercury currently collects mail and puts it all into a single Domain mailbox.  My system then collects from there by POP3 and does the distribution to the real users - with spam going to a spam folder..

As I no longer have the benefit of my ISP filtering the mail, I am getting nearly 1000 spams per day.  While SpamHalter does a good job I still have to go through it all to check for false positives.

We have here only 4 users but run about 50 aliases.  I would like to do the following:

- Accept mail for a defined list of aliases

- Reject all other mail

- Put all accepted mail into a single mailbox.

 Can this be done?

Thanks.

Aliases are considered valid local users so you simply need to make sure that "Accept mail for invalid local addresses" isn't checked in MercuryS configuration.

To move all accepted mail to one mailbox you can create a global rule that always triggers and moves the message to a named mailbox.

/Rolf 

THank you.  I have the Aliases in place.  Please could you advise on the rule to set up.

 I tried a Global rule and that moved even outgoing messages to the local user!