At 12:53 PM 10/3/2001 , Paul Galati wrote: >I just had a kick in the head and had a revelation, it may be old to >some but I am excited about this feature that can now be exploited. Any I am >having a problem initially, and maybe there is some syntax I can do to get >this to work. > >Let's say I download some software and they want an email address but you are >not sure where this email address will end up. I have discovered a way to >track this efficiently. > ><*SPAM> = SPAM > >I have a local account named SPAM. Now when I go to Iomega to download their >software, I can give them an address of [EMAIL PROTECTED] and so on >for other sites. The router will route all mail that contains SPAM to the >local account. The RFC headers of the email do indicate the original >recipient so it can be traced to where that address went to. Pretty neat, but >hear is the problem.....
I have an entry in my router: <tod-*> = tod and when I am asked for an email address I give them, for example [EMAIL PROTECTED] Any mail so addressed goes to my normal, everyday account. But if I ever have a problem with them I can add an entry to the router (ahead of the <tod-*> entry): <tod-Iomega> = spamtrap and be done with them. ############################################################# 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]>
