Have you tried my suggestion? :)I can't follow: The default- and per Domain configuration is used to process incoming mail for this specific domain. But the Exim Mail server bounce our messages with the outgoing X-RBL-Warnings from declude. As I know only the pro version handle the outgoing actions set in the global.cfgSo I'm neither able to disable only outgoing warnings.
Declude JunkMail Standard allows for per-domain configurations. The per-domain (and per-user) configurations work based on who the E-mail is addressed to. Declude JunkMail will let you set up per-user/per-domain configurations for any recipient, regardless of whether they are local or not.
The X-RBL-Warning: header is a de-facto standard header (it isn't listed in the RFCs, but has been used by a number of different anti-spam programs for many years now). It basically means "This E-mail failed a spam test". I'm sure that Exim doesn't have anything against those headers; most likely, the ISP running Exim decided (without thinking about it) that they would bounce all E-mail with X-RBL-Warning: headers, no matter what spam test(s) they failed. That's a really dumb thing to do, but there are a lot of dumb people out there. :)The question is: Why Exim can have something against X-RBL-Warnings? Are this warnings a standard or a declude specific message? How can I prevent adding any header to outgoing messages? (if this solves the problem)
-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.
