Title: Message
The was definitely a change between Declude Version
3.0.5.23 and Version 3.0.5.26 in its handling of header processing. We had
to roll back to .23 because .26 was causing strange behavior with certain mime
encapsulated messages. I sent evidence to David Franco-Rocha off-line
Organization:Cypress Integrated Systems, Inc.
X-Priority: 3 (Normal)
Message-ID: [EMAIL PROTECTED]
To: Kevin Bilbee Declude.Virus@declude.com
Subject: Re[3]: [Declude.Virus] Running declude 4.x
In-Reply-To: [EMAIL PROTECTED]
References: [EMAIL PROTECTED] [EMAIL PROTECTED]
MIME-Version: 1.0
P.S. This time, I clipped out the Org setting completely.
Yeah, uh, _this_ time. . . . :)
Last test. I'd never use the list for tests, normally, but this time
it's the list that has the prob (that is, I'm not running 3+)
--Sandy
---
[This E-mail was scanned for viruses by Declude EVA
I am having trouble finding 3.0.5.23 on the website?
I would like to try that release.
Thanks,
John
- Original Message -
From: Scott Fisher [EMAIL PROTECTED]
To: Declude.Virus@declude.com
Sent: Sunday, February 19, 2006 1:29 PM
Subject: Re: [Declude.Virus] Running declude 4.x
If
Declude has a problem with non-standard headers. There is a whole
category of spam that has headers with this problem.
The other symptom we see is that Declude is unable to edit the headers
properly when this happens. That is, for us, Declude cannot alter the
Subject line (which we use in
