First when you say "next release", does that mean that there will be no more interims?

No -- it means that whenever a new version (release, beta, or interim) is online, it will contain the fix. Interims aren't released quite as quickly now, but they will continue.


Secondly, regarding one of the points that I made in my note, Declude is picking the wrong IP out of the headers in certain circumstances. Declude is very unforgiving of any IP listed in the headers that is not surrounded by brackets, but if there are two such entries in one received header, Declude is picking the first entry for the DNSBL's and for the REMOTEIP variable, and might also be affecting the HELO. For instance, with the following header which was created by an RFC compliant Netscape Mail 7.2, Declude is reading the first bracketed IP instead of the second:
Received: from [192.168.100.100] [24.195.119.188] by mailpure.com with ESMTP


(SMTPD32-8.13) id A518CF400DA; Thu, 14 Oct 2004 00:48:24 -0400
This is generally a minor issue, but there can definitely be cases where this can affect filtering or whitelisting and it would be nice to see this handled differently at some point in the future.

I'll take a look at this to see why this is happening.

-Scott
---
Declude JunkMail: The advanced anti-spam solution for IMail mailservers since 2000.
Declude Virus: Ultra reliable virus detection and the leader in mailserver vulnerability detection.
Find out what you've been missing: Ask for a free 30-day evaluation.


---
[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