Orin,
My guess is that IMail replaced the first @ with a % and then Declude
read that from the Q file and caused the PERCENT test to be failed.
Declude, with only very specific and rare exceptions, processes the
whole outgoing message as one and not every individual recipient.
The PERCENT test is rarely or never failed depending on circumstances,
and IMail shouldn't be accepting such messages for local users if you
don't have catch-alls, and outgoing messages should only be able to be
sent by authentication in most systems, which should be legitimate.
Turning off or scoring the PERCENT test might be warranted.
Matt
Orin Wells wrote:
Interesting.
Buried in among the 87 email addresses was one with a typo that added
an extra @ in a bad place. [EMAIL PROTECTED]@aol.com for example. It was
32nd on the list but apparently this was enough to trip up Declude to
declare EVERY address to be sensed to include a Percent sign. What
the address resolved to was [EMAIL PROTECTED]
My guess is Declude is doing a scan on the WHOLE bcc set rather than
breaking it down for each address individually even though the message
later shows the specific address alleged to be getting tested.
---
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.
---
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.
