>Here is the header. You'll notice - the mail came from the 10.x.x.x private
>address block. So THAT one should not count at all - it's their local LAN.
Declude does check for that...
> >From there it went to their virus firewall at 194.127.224.201, which is a
>European Address Block - which happens to be EXACTLY where the sending
>domain "mainova.de" is located (last time I checked my American globe).
>
>So... why does SPAMROUTING fail?
It's a bug, that will be fixed in the next release. I'll show you what
happened:
>Received: from 10.129.1.101 by viruswall1 (InterScan E-Mail VirusWall
>NT);
This header type is only used by InterScan ("From IP.IP.IP.IP", which
doesn't appear to be a valid header). We added support for the Interscan
header, but Declude was looking at it starting at the space after from, so
it was looking at " 10.129.1.101" instead of "10.129.1.101". The check for
internal IPs (such as 10.x.x.x) saw the space instead of the "10", and
didn't treat it as an internal IP. So while Declude is correctly
recognizing IPs in Interscan's headers, it isn't recognizing the internal
IPs in their headers.
The next release will properly handle internal IPs in the headers that
Interscan adds.
-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". You can E-mail
[EMAIL PROTECTED] for assistance. You can visit our web
site at http://www.declude.com .
