On 22/06/2016 11:18 a.m., surgemailHIDDEN@etwinsite.com wrote:
> For a project I need aliases of the form "xHIDDEN@email@example.com".
> To make them easy to redirect, my rule is:
> g_redirect was="x-HIDDEN@="firstname.lastname@example.org"
That's a little risky, as it applies to all domains, NOT just your own
domains so it also prevents you from sending to xHIDDEN@y.domain. The
safer way to do this is to put this rule in for each domain as a domain
level 'redirect' rather than global.
> This means that users can be added by just having the correct "prefix".
> Now, however, dozens of these are being targeted by spammers.
I would suspect they are hitting them by accident, but that's a guess.
> I tried to spamcatch them with rules like:
> g_redirect was="xHIDDEN@*" to="email@example.com"
> 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?
Yes I would expect that to work.
I think changing to domain level redirect rules is a very good idea
Last Message | Next Message
Site Map |
Contact Netwin |
POP3 Mail Server |
Linux Webmail |
UnInstall instructions for all products
Copyright © 2017 Netwin Ltd. All rights reserved.