Any filter must be setup correctly by the sysadmin. Setting up any filter incorrectly or too restrictively will cause problems for customers like those you describe.
Ken A.
Alan Brown wrote:
On Mon, 15 Sep 2003, Ken Anderson wrote:
There's a proxy server that supports pop3 called prometo on sourceforge that recently added SA support. I've tested it with qpopper, and it works good with SA, but there's no way to do per user rules. Pretty cool to do this on the pop3 side tho.
All of these are still automated forms of JHD (Just Hit Delete)
There is a _LOT_ of collateral damage from the practice of JHD.
Genuine messages ("False positives") rejected by spam filters at MTA level result in reject messages arriving back at the original (non-forged) sender address, so they at least know something went wrong.
Any form of delete filtering after the message hits a user's inbox means that False Positives are silently dumped.
I've just been through this problem at $orkplace with a vendor's support mailbox silently trashing our mail, resulting in near-cancellation of a $100,000 contract. If their spam filters had been rejecting our messages we'd at least have known to phone them, instead of assuming we were being ignored.
Anyone doing MUA-level or POP3/IMAP-server-level filtering-by-deletion does so at their own peril. This is something which is best done in the SMTP handshake (it's trivial to reject messages after DATA and before the end-of-conversation.)
