Daniel J McDonald wrote:
It would be a harmless confusion, but if you specified:
not_ok_locales se
ok_locales en
The ok_locales would do nothing at all. We'll have to document that
*very* carefully.
Maybe something like:
ok_locales !se all
Hmm, that's a bit confusing to me,
Stefan Jakobs wrote:
Let's assume you running a mailrelay for a university and your users are from
different countries. Lets assume further on you have no Swedish people at
your university (and you get a lot of spam from Sweden). Then it would be
nice to have a not_ok_locales option,
M or does he think
All we know is users don't think like we do. http://www.useit.com/alertbox/
M how will you benefit from contact with this broader spectrum if
M they're emailing you in a character set you can't read?
* Sternstone recalls: I was only 20 years old and had my name in Tamil
in my
On Friday 07 December 2007 04:42, Matt Kettler wrote:
[EMAIL PROTECTED] wrote:
MK I'll be happy to change my assumptions, but can you name any good
reason MK why they would want to do so?
The Matt theme: restrict oneself from getting mail from any but a few
safe people, languages, or
Matt Kettler wrote:
Stefan Jakobs wrote:
Let's assume you running a mailrelay for a university and your users are
from
different countries. Lets assume further on you have no Swedish people at
your university (and you get a lot of spam from Sweden). Then it would be
nice to have a
On Fri, 2007-12-07 at 08:38 -0500, Matt Kettler wrote:
Stefan Jakobs wrote:
Let's assume you running a mailrelay for a university and your users are
from
different countries. Lets assume further on you have no Swedish people at
your university (and you get a lot of spam from Sweden).
Karsten Bräckelmann wrote:
Maybe the devs can briefly explain how the charset is being determined.
Or at least, where exactly in the code one could find it...
Matt, also, I got a feeling, that logic is what the OP is actually
about. He does not want to leave out what he wants to be
[EMAIL PROTECTED] wrote:
M or does he think
All we know is users don't think like we do. http://www.useit.com/alertbox/
Fundamentally, SpamAssassin is a tool written by system administrators,
for system administrators and advanced users.
Like it or not, the project's primary goal has always
On Fri, 2007-12-07 at 23:36 +0100, Stefan Jakobs wrote:
On Friday 07 December 2007 20:42, Karsten Bräckelmann wrote:
Let's assume, one of them happens to be Swedish. And even though the
entire communication is English, that ignorant bastard dares to have his
real name at the bottom of his
On Friday 07 December 2007 20:42, Karsten Bräckelmann wrote:
On Fri, 2007-12-07 at 08:38 -0500, Matt Kettler wrote:
Stefan Jakobs wrote:
Let's assume you running a mailrelay for a university and your users
are from different countries. Lets assume further on you have no
Swedish people
On Sat, 2007-12-08 at 03:40 +0100, Karsten Bräckelmann wrote:
It's a rather twisted logic. You don't define what's good or bad (that
again would be a black/whitelist), you leave out what's bad...
Hmm, maybe not so twisted after all. ok_locales equals these are the
charset classes I probably can
On Sat, 2007-12-08 at 02:05 +0100, Stefan Jakobs wrote:
On Saturday 08 December 2007 01:15, Karsten Bräckelmann wrote:
Ok. My fault I mistook charsets with country codes. But replace se with
ru or ch or greek7. The result is the same. You want one charset to be
considered as not ham and
On Fri, 2007-12-07 at 08:38 -0500, Matt Kettler wrote:
Stefan Jakobs wrote:
Let's assume you running a mailrelay for a university and your users are
from
different countries. Lets assume further on you have no Swedish people at
your university (and you get a lot of spam from Sweden).
On Saturday 08 December 2007 01:15, Karsten Bräckelmann wrote:
snip
Ok. My fault I mistook charsets with country codes. But replace se with
ru or ch or greek7. The result is the same. You want one charset to be
considered as not ham and you have to give the whole list to the
parameter.
On Thu, 2007-12-06 at 22:42 -0500, Matt Kettler wrote:
[EMAIL PROTECTED] wrote:
And those who really want this effect can just list every locale except
the one they dislike, if that's really what they want.
Given the really small number of locales (character sets), this isn't
unreasonable to
On Fri, 2007-12-07 at 09:23 -0500, Matt Kettler wrote:
Also, keep in mind that it's perfectly valid to have multiple ok_locales
statements so:
No. :)
According to the documentation, if there are multiple ok_locales lines,
only the last one is used.
guenther
--
char *t=[EMAIL PROTECTED];
Jonathan Armitage wrote:
Provided it is possible with your MTA, you could consider rejecting
such email at that level, thus relieving SA of the burden of having to
scan it at all.
This is easy in Exim, but I don't know if other mailers can do the
same thing.
In postfix, a header or a body
Anyway, Mail::SpamAssassin::Conf should admit that it doesn't mention
What if I hate a specific language, people, culture. Is there e.g., a
not_ok_locales?
Don't put the answer here, put it on Mail::SpamAssassin::Conf, even if
the answer is that there is no answer. Thank you.
The basic user understands whitelist_from and blacklist_from. But when
he encounters the locales, he wonders why cannot there be
whitelist_locales and blacklist_locales. He does not want to learn the
superior logic of why his wish is not smart. He just wants to find the
commands for
[EMAIL PROTECTED] wrote:
MK Let's say you speak English and Chinese, and hate Russian because you
MK get lots of spam in that text format and don't speak it.
That's me, English and Chinese, and hate Russian.
MK In this situation, why would you want not_ok_localles ru instead of
MK
MK I'll be happy to change my assumptions, but can you name any good reason
MK why they would want to do so?
The Matt theme: restrict oneself from getting mail from any but a few
safe people, languages, or whatever. Life goes on in its familiar grey
days. But alas, the software knows best.
The
[EMAIL PROTECTED] wrote:
Anyway, Mail::SpamAssassin::Conf should admit that it doesn't mention
What if I hate a specific language, people, culture. Is there e.g., a
not_ok_locales?
Don't put the answer here, put it on Mail::SpamAssassin::Conf, even if
the answer is that there is no answer.
[EMAIL PROTECTED] wrote:
MK I'll be happy to change my assumptions, but can you name any good reason
MK why they would want to do so?
The Matt theme: restrict oneself from getting mail from any but a few
safe people, languages, or whatever. Life goes on in its familiar grey
days. But alas,
The jidanni theme: open up life to a rainbow of possibilities.
Y'know, at the risk of being rude, does the rainbow of possibilities include
the possibility of READING the expletive-deleted CONF FILE? Just asking.
But the basic user is not in the business of understanding things.
Then he
im looking for some opposit parameters of ok_locales to
make spamassassin mark all incoming mail of some specific charsets or
language settings (locales) to get marked by default.
for example: since i life in western europe i never expect mails from
eastern europe, asia, afrika or something
On Wed, 2007-12-05 at 17:00 +0100, Axel Werner wrote:
im looking for some opposit parameters of ok_locales to
make spamassassin mark all incoming mail of some specific charsets or
language settings (locales) to get marked by default.
for example: since i life in western europe i never
Karsten Bräckelmann wrote:
On Wed, 2007-12-05 at 17:00 +0100, Axel Werner wrote:
im looking for some opposit parameters of ok_locales to
make spamassassin mark all incoming mail of some specific charsets or
language settings (locales) to get marked by default.
Provided it is possible
Axel Werner wrote:
im looking for some opposit parameters of ok_locales to
make spamassassin mark all incoming mail of some specific charsets or
language settings (locales) to get marked by default.
for example: since i life in western europe i never expect mails from
eastern europe, asia
28 matches
Mail list logo
