Scott,
Thanks for the discovery. The reason I was wanting to use the IS, is due to
not wanting to step on email addresses that maybe valid. For example, if he had an
ex-employee that had the email address [EMAIL PROTECTED] , but has a valid user called
[EMAIL PROTECTED] If I use the CONTAINS, it would wipe out both of them. I guess I
can just make sure with him that there is no overlap of addressing and use the
CONTAINS. Thanks again for looking.
Keith
-----Original Message-----
From: R. Scott Perry [mailto:[EMAIL PROTECTED]
Sent: Sat 3/15/2003 4:30 PM
To: [EMAIL PROTECTED]
Cc:
Subject: RE: [Declude.JunkMail] ALLRECIPS Use Question
> >Are you using a "copyall" account? If so, ALLRECIPS would contain the
> >copyall account as well as the user that you were sending to, so "ALLRECIPS
> >0 IS [EMAIL PROTECTED]" would never match.
>
>Scott, I am not using the 'copyall' account. However, this is on a
>Store/Forward domain if that makes a difference. Any suggestions?
I've found out the problem. It turns out that the ALLRECIPS will include
both the intended recipient address and the actual recipient address. So
if you send the E-mail to "[EMAIL PROTECTED]", ALLRECIPS might be
"[EMAIL PROTECTED], [EMAIL PROTECTED]" (if no aliases were used), or
"[EMAIL PROTECTED], [EMAIL PROTECTED]" (if there was an alias pointing to
[EMAIL PROTECTED]).
-Scott
---
[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.
<<winmail.dat>>
