-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Joseph N., [JN] wrote:
JN> ... The problem is that the business-related MUA can filter only by JN> sender, recipient, or subject. So if I set SpamPal not to modify the JN> subject line, then my business app wouldn't be able to filter out JN> the spam. I now understand. JN> It seems like my only choices are to come up with a new business JN> e-mail address, which the spamsters may not detect and which would JN> allow me to modify how SpamPal operates, or simply live with the JN> munged subject line as the price of managing spam. Unless you see JN> another option...? Perhaps you could tune Spampal to not be so sensitive. It would be better in your case to get the occasional spam go through than the occasional legitimate mail have its subject header munged. You could adjust the Blacklists you use. I was told to avoid using the following Blacklists and this cut down dramatically on the number of false positives I got. SpamCop *.monkeys.com ABL Easynet Blackholes rfc-ignorant.org Use the country based ones as well especially if you don't expect mail from Eastern countries. I don't have many correspondents from that side of the globe so they're all whitelisted. Also, be sure that your whitelist is well tuned. - -- -= allie_M =- | List Moderator _ -----BEGIN PGP SIGNATURE----- Version: PGP SDK 3.0.2 iQA/AwUBPyXRDVfJ62ArBxfiEQI1iwCghkwmYiniLo+W2aLtoaUX/v++4m0Amwex Win9xS2/pMXZ4qWRZlV336C/ =O1Co -----END PGP SIGNATURE----- ________________________________________________ Current version is 1.62r | "Using TBUDL" information: http://www.silverstones.com/thebat/TBUDLInfo.html
