Because since we use SPAMCHK there was also some bounced messages from
Exim indicating the casue of the error

        "forced faulure: SPAMCHK ..."

I'm sure Exim bounce our messages because there are the "X-RBL-Warning:
" lines in the header.
Talk about a "poor man's spam filter" -- relying on the mailserver the spammer uses to run the spam tests. :)

What can be wrong on this header lines? The only way to resolve this
issue fast and without discussion with the other ISP is to remove all
X-... Header lines for outgoing messages in our declude config file.
In this case, since they don't seem to care *which* spam tests fail (the fact that you use an X-RBL-Warning: header rather than blocking the E-mail typically indicates that the test doesn't justify blocking the E-mail), I would recommend using a trick to allow you to keep the X-RBL-Warning: headers while still getting this mail through.

To do this, you can create a per-domain configuration file for the domain that is running Exim. To do this, you can copy the \IMail\Declude\$default$.JunkMail file to \IMail\Declude\example.com\$default$.JunkMail, and use "IGNORE" as the action for all the tests.
-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.

Reply via email to