><bill.*@blacklisted> = bill.* ><bill.dice> = spamtrap ><bill.techies> = spamtrap ><bill.*> = bill > >The last line allows me to invent 'bill.whatever' addresses ad hoc, >and have them all funnel into 'bill'. The first line makes it so >that if a blacklisted host happens to try mailing one of them, it is >rewritten as if it is not blacklisted.
Why do you do this (the rewriting as if it is not blacklisted)? I understand the concept behind the last 3, but not the first. I would think you would not want to receive any mail from a blacklisted domain - after all, that's the purpose of blacklisting to begin with... ? >One at a time. What I do with my postmaster account is this: > ><postmaster%*@blacklisted> = postmaster-blocked > >That makes postmaster for any domain I host route to >'postmaster-blocked' if the mail comes from a blacklisted IP. The >'postmaster-blocked' account autoresponds with a message about the >blocking and dumps the mail into a folder that I occasionally peek >at. You could be simpler about it of course, and just route > >user%domain@blacklisted = user I admit that I am still confused about the % wildcard and exactly how it works, even though I use it in my router (I can follow a formula :-). It's not documented on Stalker's Router Settings page. % seems to be an �ber-@ that has to be distinguished from the other @ that is already used in this line. Stefan Jeglinski ############################################################# 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]>
