[Spambayes] expected behaviour in Outlook2k

[Mark Hammond]

> 1.  it worked in v0.3 and earlier . . . .

Yes - we added the feature <wink>

> 2.  I can understand it not having enough info to 
> automatically delete it (move it to 'SPAM_UNSURE'?), but what 
> I      don't understand is why 'No mail items are selected' 
> response after clicking on the 'Delete As Spam' button.

The problem was that the lack of clues *did* move them to "unsure" - or
worse, to "spam".  When these reports are not forged, this is clearly wrong.

The "No mail items are selected" message is misleading - I have changed it
to "No filterable mail items are selected" - but I am not sure that helps.

> P.S. I have saved several emails (in html)from a particular 
> 'spamhaus' that have no response when clicking on 'Delete As 
> Spam'; would these messages be of any interest for further research?

Yes please.  One will do :)  I have since fixed a related bug that did cause
some messages to be considered non-filterable when they should have been.  I
didn't see this with any NDRs, but I will be interested to see if this fixes
your problem.

The basic problem is that we want to exclude items that have not actually
been sent (ie, generated internally).  The fact they have not been sent is
why we do not filter them - if they have actually been sent and received by
an internet mail system, then they *should* be filtered as they would have
the clues.  However, all NDR's I have seen that do not filter are like this
- never actually been outside Outlook/Exchange, so therefore have limited
properties and therefore no reasonable clues.

Mark.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: winmail.dat
Type: application/ms-tnef
Size: 2468 bytes
Desc: not available
Url : http://mail.python.org/pipermail/spambayes/attachments/20030801/eb4bb2d3/winmail-0001.bin