Scott, What if instead of a single wildcard character (that could mistake actual content as having a wildcard, with unexpected results), there was a multi character code? Web URLs, for example, use a system that starts with %:
http://www.w3.org/International/O-URL-code.html Whereby "san diego" looks like "San%20diego" So instead of drugstore*@yahoo.com, we put something like drugstore{*}@yahoo.com into our content filters. Such a system (instead of just a character) would also allow for flexibility like {#} for just a number and {##} for multiple numbers. A system unique enough that it doesn't preclude possible actual search string text, but simple enough to easily remember and type. My {#} cents. ;) Dan On Tuesday, December 31, 2002 13:17, Kami Razvan <[EMAIL PROTECTED]> wrote: >Message >Hi Scott: >Any chance of this ever be considered.� This would be for a wildcard in FROM field. >� >Another trend is: [EMAIL PROTECTED] >� >naturally anyone buying drug from someone with a yahoo account >should be questioned.� We get these type of eMails with the >numbers changing from free accounts. >� >Of course we don't want to block:� [EMAIL PROTECTED] (just an example). >� >But variations of drugstore*@yahoo.com or hotmail.com should be a flag. >� >I know we have talked about wildcards in the filters for the >body but I think in the FROM field it should not be as hard to >implement. >� >Regards, >Kami >� >� --- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)] --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type "unsubscribe Declude.JunkMail". The archives can be found at http://www.mail-archive.com.
