Sorry if I'm stating the obvious here -- or even more so if I'm dead wrong -- but your ColdFusion mailing application(s) is/are generated malformed e-mail headers, i.e., not RFC-2821-compliant (please see http://www.isi.edu/in-notes/rfc2821.txt.) This is likely why they are caught and flagged by Declude.
The part where you state: > We prefer not to have the private IP exposed and it is misleading anyway. is rather baffling to me. I assumed that what you mean by "private IP" is one of those covered in RFC 1918 (Cf. http://www.isi.edu/in-notes/rfc1918.txt) and these addresses are non routable. There are *many* servers using them behind a firewall for NAT'ing and yours is/are very likely to be also used by many other networks. "Exposing" it in e-mail headers should not be cause for concern as no-one outside your firewall will be able to send anything directly to your "private" IP(s). If I am in error with any of the above, someone else on this list will quickly rectify the facts (and set me straight!), Guy ----- Original Message ----- From: "Ben Lee Schneider" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, July 21, 2003 17:07 Subject: [IMail Forum] Changing Sender > Hi, > We are currently using Cold Fusion to generate a lot of e-mail that is > forwarded to our I-mail server. Both are behind a firewall with local IPs > and we set the Imail server to accept relayed mail from the local IP of the > CF server. We've also recently implemented Declude and our ColdFusion-based > e-mails are encountering some issues. All e-mail generated from the CF > server fails the badheaders, and often the spamhearders tests. We're only > using weight20 to add to the subject so most legit CF mail still does not > get tagged but every one fails the badheaders test and I would like to > correct this. The other thing I noticed is that the x-declude sender header > the local IP address of the web server. I figure I can probably add > corrected header info to my ColdFusion e-mails to correct this but I don't > know what I need to add. I also don't know how to go about getting the > private IP replaced with the public. We prefer not to have the private IP > exposed and it is misleading anyway. I've enclosed a sample header. Any > help is much appreciated! > Ben > > Date: Mon, 21 Jul 2003 12:35:28 -0500 > From: [EMAIL PROTECTED] > Mailer: Affiniscape Members 24.7 Mail System > Subject: A new Support email has been received > To: [EMAIL PROTECTED] > X-RBL-Warning: BADHEADERS: This E-mail was sent from a broken mail client > [c004020e]. > X-RBL-Warning: SPAMHEADERS: This E-mail has headers consistent with spam > [c004020e]. > X-RBL-Warning: WEIGHT10: Weight of 11 reaches or exceeds the limit of 10. > X-Declude-Sender: [EMAIL PROTECTED] [x.x.x.x] > X-Note: This E-mail was scanned by Declude JunkMail (www.declude.com) for > spam. > X-Spam-Tests-Failed: BADHEADERS, IPNOTINMX, SPAMHEADERS, WEIGHT10 [11] > X-Spam-Prob: 0.714377 > Sender: [EMAIL PROTECTED] > Reply-To: [EMAIL PROTECTED] > > To Unsubscribe: http://www.ipswitch.com/support/mailing-lists.html List Archive: http://www.mail-archive.com/imail_forum%40list.ipswitch.com/ Knowledge Base/FAQ: http://www.ipswitch.com/support/IMail/
