Scott: So - how will we debug this?
>> The "WHITELIST" line only works in \IMail\Declude\global.cfg. << That's where it is - the ONLY place. >> Also note that failures will appear in the log, but any actions should not be taken on the E-mail << I only noticed it, because the Q* and D* file appeared in my HOLD folder. So the action DID take place, as I had mentioned. >> with the "IPBYPASS 63.107.174.32", it would be the server that connected to 63.106.174.32. << Doesn't apply. The .32 is our backup SMTP server. As you were able to determine from the SMTP header that I had included - the .32 machine was NOT even involved!? So - I ask again, why was it "HELD" when the originating mail server was White-Listed? As a reminder, here once again the mail header: Received: from maywood-is-0001.webhost.hm-software.com [63.107.174.1] by mail.webhost.hm-software.com with ESMTP (SMTPD32-7.04) id A8824660392; Tue, 06 Nov 2001 10:57:54 -0500 Received: from localhost ([127.0.0.1]) by maywood-is-0001.webhost.hm-software.com with Microsoft SMTPSVC(5.5.1877.197.19); Tue, 6 Nov 2001 10:27:23 -0500 To: [EMAIL PROTECTED] From: [EMAIL PROTECTED] X-Mailer: Perl Sendmail Version 1.21 Christian Mallwitz Germany X-URL: http://www.hotelazenberg.de/anfrage/default.htm Subject: Anfrage Return-Path: [EMAIL PROTECTED] Message-ID: <[EMAIL PROTECTED]> Date: 6 Nov 2001 10:27:23 -0500 X-Declude-Sender: [EMAIL PROTECTED] [63.107.174.1] X-Declude-Spoolname: D0882392.SMD X-Declude-Note: Processed by Declude 1.28; remote host maywood-is-0001.webhost.hm-software.com. Best Regards Andy Schmidt Phone: +1 201 934-3414 x20 (Business) Fax: +1 201 934-9206 -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of R. Scott Perry Sent: Tuesday, November 06, 2001 03:33 PM To: [EMAIL PROTECTED] Subject: Re: [Declude.JunkMail] 1.28 - WhiteList not working >the following mail failed despite the IP being WHITELISTED globally as well >as individually. This is causing QUITE a problem. Note that in Declude JunkMail, you can only whitelist on a global basis. The "WHITELIST" line only works in \IMail\Declude\global.cfg. Also note that failures will appear in the log, but any actions should not be taken on the E-mail (IE HOLD, DELETE, SUBJECT, WARN...). A final thought: The IP whitelist will only check what Declude thinks the IP address of the remote server is, not any intermediate ones. Since you have "HOP 0", that would normally the mail server that connects to the IMail server, but with the "IPBYPASS 63.107.174.32", it would be the server that connected to 63.106.174.32. If you also have "IPBYPASS IP 63.107.174.1", then Declude would not whitelist the E-mail (it would see the IP address as 127.0.0.1, the address that connected to 63.107.174.1.). >WHITELIST IP 63.107.174. >WHITELIST IP 63.107.174.1 >WHITELIST IP 63.107.174.14 >WHITELIST IP 63.107.174.78 Also, only the first entry is needed here. The "WHITELIST IP 63.107.174." should whitelist E-mail from 63.107.174.xxx. Having the multiple entries will not cause a problem, though. -Scott --- 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". You can E-mail [EMAIL PROTECTED] for assistance. You can visit our web site at 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". You can E-mail [EMAIL PROTECTED] for assistance. You can visit our web site at http://www.declude.com .
