RE: [spambayes-dev] 1.0 Build Testing (please!)
Well, the option is there and people are using it so I thought we should at least make it work correctly. <wink> I never cared for it, either, because it plays havoc with the ability to reply to the message if it was in fact legitimate, and I would have no reservations about simplifying the configuration and eliminating this option.
There is no good solution here, because OE is so limited. IIRC, you can filter on From:, To:, Subject: and the body, so we have to use one of those or the notation is useless. To: and From: are arguably less intrusive than Subject:, so I like that we offer two options. I doubt many people notate ham, so as long as there are no false positives (a reasonable assumption), and few unsure hams (likely for many people I think), then changing the To: doesn't hurt. I wouldn't have a problem with changing it so that it matched whatever the RFC says (maybe classification@spambayes or something like that which is an invalid address, but valid formatting?). =Tony Meyer
From: Tony Meyer [mailto:tameyer@ihug.co.nz] Sent: Tuesday, September 28, 2004 11:28 PM
<...>
There is no good solution here, because OE is so limited. IIRC, you can filter on From:, To:, Subject: and the body, so we have to use one of those or the notation is useless. To: and From: are arguably less intrusive than Subject:, so I like that we offer two options. I doubt many people notate ham, so as long as there are no false positives (a reasonable assumption), and few unsure hams (likely for many people I think), then changing the To: doesn't hurt.
Looking at OE6, the filter conditions are: From: To: cc: To: or cc: Subject: body priority size attachment secure The filter actions are similarly anemic: delete highlight w/color flag mark as read mark as watched or ignored mark for download
I wouldn't have a problem with changing it so that it matched whatever the RFC says (maybe classification@spambayes or something like that which is an invalid address, but valid formatting?).
If you want that, the .invalid TLD is reserved in the RFC's as, well, invalid. I'm not sure exactly what it buys you, but classification@spambayes.invalid is by definition not resolvable. If you created an address book entry for each classification 'address', I think OE would display the name instead of the address. That might be a reasonable workaround for people stuck with OE. -- Seth Goodman
participants (2)
-
Seth Goodman -
Tony Meyer