Not good form to answer my own posts, but the scenario I proposed at the
end works. I just tested it.

Reject globally and redirect a more general pattern per domain.

Neil


On 2016-06-21 7:18 PM, Neil Herber (nospam) wrote:
> For a project I need aliases of the form "xHIDDEN@ing@several.domains".
> To make them easy to redirect, my rule is:
>
> g_redirect was="x-HIDDEN@="one.real.address@real.domain"
>
> This means that users can be added by just having the correct "prefix".
>
> Now, however, dozens of these are being targeted by spammers.
>
> I tried to spamcatch them with rules like:
>
> g_redirect was="xHIDDEN@*" to="spamcatcher@eton.ca"
>
> But the original, more general rule above keeps forwarding them.
>
> Is there any way I can trap things like "x-user1" while still allowing
> "x-anything-else" to redirect as it always did?
>
> I do not want to have to create a rule for each good address, because
> they far outnumber the bad ones, and I don't have a record of them all.
>
> One solution that just sprung to mind is to use global redirects for the
> spamcatchers and domain specific redirects for the general rule. This
> assumes that the global redirect "wins" before the domain specific
> redirect sees the mail. Will that work?
>
> Thanks!
> Neil
>

-- 
Neil Herber