> Let me get this straight -- we have ignorant and the willfully abusive > people in these countries creating or abetting spam for others to deal > with, and *we're* supposed to be concerned about public relations?
I don't think you're getting it. If North America (I'm from Canada) didn't have what I would consider a stranglehold on .com/net/org, we would be using .someserver.us, or .someserver.ca. And I'm also willing to bet that the .us TLD would not bother themselves about going after open relays in the .us TLD. Further to that, if someone were to put .us into this specific test I bet you'd be squaking about it not being right, since you have so many emails coming in and going out to .us TLDs. Don't get me wrong, I'd *love* for the TLDs to have the job of making sure that any servers with DNS MX records were not open relays (including the .com/net/org), but that is unfortunately a fairy-tale at this point in time. > Seriously -- are we now going to pitch the default rules against finding > Big5 encoding in the Subject line because it might trample the feelings > of some people? Maybe they'll figure out that their get-rich-quick Seriously -- are we now going to pitch the default rules against finding English words in the subject line because it might trample the feelings of some people? I'm not being an ass here -- just because *YOU* and *I* don't get a lot of BIG5-encoded email does not mean that the people for whom that encoding is necessary in order to get their language into email don't get a lot of legitimate email that way. If you really feel this strongly about it, I suggest forking off a "Latin-based language" ruleset instead of trying to force everyone on the planet to accept your language-biased rulesets. I agree strongly with Daniel here; while that specific test works well for people such as you and I, it's devastating for people who use a very different character encoding in their normal email, or happen to have email addresses an an unfortunate TLD. Actually I've been a victim of this same kind of problem; Benshaw happens to do a lot of business with Korean companies and a lot of the .kr email was coming in as spam until I nix'd the test myself. > schemes are unwelcome and stop sending them. It catches spam for me, > that's all I can say. The point of SpamAssassin is, to some degree, to > disseminate the collected experience of its contributors. And that > includes unpleasant and possibly politically incorrect experience. This is true, but are you absolutely sure that your experiences are the same as those for people using SA with very different email types? I'm all for political incorrectness, but not when it's obviously harming entire languages and there are literally hundreds of other tests which are correctly spamfile'ing the email. Regards, Andrew _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
