I turned on the iMail Calendar for a client and they responded with an odd
problem. If someone uses the calendar to invite someone else, there is
evidently a javascript popup window that can come from the request email.
This javascript then allows the user to click to respond. It's this
response that Declude is catching as spam.
Emails sent normally from the users machine do not fail spam tests, only
when this javascript method is used.
The header reports the failure of c8200204, or no From address, and
therefore reports both SPAMHEADERS and BADHEADERS, which then hit my WEIGHT.
Actually, there are a number of problems given that code -- no From: header
and no Date: header (either or which will trigger the BADHEADERS test), and
no Message-ID: header.
Anyway, looking the header I have here, there is a From: line.
After delivery, you will see a From: header (as IMail will fix up headers a
bit just before delivery). However, you'll notice that the From: header
appears after the Declude headers, which means they were not there when
Declude scanned the E-mail.
But looking at the raw email on the server, the from line is this:
From [EMAIL PROTECTED] Fri Feb 28 10:21:17 2003
It seems the timestamp is appended to the From line for some reason. This
is probably being seen as a corruption in the header.
Actually, that's the format that IMail uses for the .mbx files, and is
normal (the line won't be included in the E-mail when it is downloaded).
In this case, Ipswitch needs to make sure that the E-mail that is sent
includes both a From: and Date: header when it is sent (the Message-ID:
header would be nice, but isn't required if they have a good reason not to
include it).
-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. The archives can be found
at http://www.mail-archive.com.
