>> Are you sure you matched this up correctly? <<
Declude Version 1.68i5.
Here is "the chain of evidence" I followed:
You did good. :)
It turns out this is a bug in Declude JunkMail, where it would stop
processing headers if it encountered a header continuation line that
consisted of a single
>> Are you sure you matched this up correctly? <<
Declude Version 1.68i5.
Here is "the chain of evidence" I followed:
A) The snippet of our own, highly informative, bounce message showing the
DECLUDE variables:
... (verbose text omitted) ...
Mail Server: 161.225.2.41 for target.com [targe
This one returned code 802c (This E-mail has a bogus Date: header.) -
however, the Date: header does look just fine?
Are you sure you matched this up correctly? When I run it through here, it
only triggers the SPAMHEADERS test (due to the string of spaces that
appear in the subject), but n
Hi Scott:
This one returned code 802c (This E-mail has a bogus Date: header.) -
however, the Date: header does look just fine?
May be the problem is the "Subject" header - as it appears to "wrap" around
into a second line? But, then again, multi-line headers appear to be quite
normal, becaus
