At 6:16 PM +0100 4/30/02, Ron Hahn imposed structure on a stream of electrons, yielding: >On 4/30/02 6:03 PM, "Bill Cole" <[EMAIL PROTECTED]> wrote: > >> At 4:37 PM +0100 4/30/02, Ron Hahn imposed structure on a stream of >> electrons, yielding: >>> Hi, >>> >>> I've quite an extensive ruleset and would like to know if: >>> >>> <james> = james-abc >>> <j*> = error >>> >>> Will bar all email addresses starting with "j" except "james".. I.e. Does >>> the rule parser bail out when it satisfies a rule or not? >> >> No, the router restarts from the top every time a rule is satisfied. >> An address is re-run until it makes it through unchanged. > >OK, so is there another way to accomplish this? What I would like to do is: > >A) at the top of the rule file have all the routing for good addresses >B) at the bottom of the rule file have explicit rejects for bad addresses > >Is this possible or am I misunderstanding the documentation?
The reverse may work better, but one possible strategy would be to route good addresses to prefixed addresses and route the rest to oblivion: <james> = real-james <j*> = error I do things a little differently. I use a lot of patterned tagged addresses, and route them all to my real address. Any that start getting spammed get entries above the patterned routing making them spamtraps. here's a snippet of my router <bill-techies2> = spamtrap <bill-pjm> = spamtrap <bill-*> = bill -- Bill Cole [EMAIL PROTECTED] ############################################################# This message is sent to you because you are subscribed to the mailing list <[EMAIL PROTECTED]>. To unsubscribe, E-mail to: <[EMAIL PROTECTED]> To switch to the DIGEST mode, E-mail to <[EMAIL PROTECTED]> To switch to the INDEX mode, E-mail to <[EMAIL PROTECTED]> Send administrative queries to <[EMAIL PROTECTED]>
