on 7/16/02 10:27 PM, Thomas Tempelmann wisely articulated: > I have 2 thoughts: > > 1. > If this information is not present in the header, the only way > to see for which account the mail was is by looking into the > log. This is awkward. Can't this be improved in some way? > Delivery was probably accomplished through a BCC.
> 2. > Since I see this happening only with SPAM mail, can't this be > used for another spam protection mechanism? > There are a lot of uses for BCC. A mail group in your address book that has the option of hiding recipient addresses is one. Some list servers use this mechanism as well. > Oh, and one more: Wouldn't it be possible (I mean easy) to > allow me to write code that would get executed when SIMS receives > a mail so that this code of mine could look at the mail text, > allowing me to delete certain mail that I consider spam right > away? I guess Communigate Pro can do this, though? Ooh, a server-side content filter. CGP can do this, I hear. One must be VERY careful when figuring out the logistics. There is a funny [and sad] article in Tidbits from last week: <http://www.tidbits.com/tb-issues/TidBITS-637.html> Jeff ############################################################# 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]>
