Loren Wilton wrote:
Well, I didn't get any responses on the MDF mailing list,
so I was wondering if SA was the better angle to be coming
at this with.
I think we can help you, but it will depend on exactly what you want to do.
SA normally is used to filter to mail for recipients. You seem to be
talking about mail FROM a list, but then seem to be talking about filtering
mail TO the list. So I'm a little confused on just what you want to do.
No, it's to a list. At the list exploder, we want to be able to apply
certain per-list policies. For instance, for most lists (but not all),
the following would be applicable:
languages_ok en
score SUBJ_FARAWAY 6.0
score SUBJ_ILLEGAL_CHARS 6.0
score UNWANTED_LANGUAGE_BODY 6.0
etc.
For some lists, we might have:
score MIME_HTML_ONLY 6.0
and for everyone, we would want:
score ILLEGAL_DATE 6.0
score DATE_IN_FUTURE_96_XX 6.0
score DATE_IN_FUTURE_48_96 6.0
score DATE_IN_PAST_96_XX 6.0
score DATE_IN_PAST_48_96 6.0
as examples.
I was wondering... Since MdF can be used to invoke SA, and it can
extract information from the headers such as a the envelope recipient
information... I was wondering about a lot of the ML's on
lists.sourceforge.net.
They get a lot of spam. Especially open forums like alsa-devel that you
don't have to be subscribed to in order to post to.
Of course, this is something that the owner of the ML should fix in their
configuration. The sounds like a free spammer tool to me, configured as it
is.
Well, it's a common thing. Many "devel" lists require open postings so
that users can tell developers about bugs without having to join the list.
So I was wondering if MdF could be used to have a clever hack
where one could see if the message was going to a single recipient
(in this case, the local recipient would be a list name) and try to have
SA apply additional rules for that list.
Sure. Write a rule that checks for a specific To or envelope sender or
List-Id:
header __ML_LIST_1 List-Id =~ /ALSA Devel/
Unfortunately, the List-Id isn't yet present at this point. Sendmail
receives the message from the original poster, invokes SA and/or
MDF, and then when everything checks out, uses "mailman" as
the delivery agent (who then inserts the List-Id).
You might have multiple recipients, but only one of them should
be local, unless the message is being cross-posted to several lists
and more than one of them are on this host.
I.e. you might have a site-wide policy, that says you can't post if:
INVALID_DATE
DATE_IN_PAST_96_XX
DATE_IN_FUTURE_96_XX
meta BOGUS_SENDER __ML_LIST_1 & INVALID_DATE && (__DATE_IN_PAST ||
__DATE_IN_FUTURE)
score BOGUS_SENDER 10
(You will have to build the metas for __DATE_IN_PAST, etc)
are fired... And you might have a specific set of rules for a list like
alsa-devel (the 'L' in ALSA is for Linux, so it might be reasonable
to assume that no one will be posting with charset='windows-1252'...
it's also an English language list, so having 'ok_languages en' would
be reasonable as well).
This would be a pretty bad idea. I develop Linux stuff and on linux, but my
mail system is either OE or Outlook on Windows boxen. I can't be the only
one.
Loren
Well, I don't know.
The RFC's are pretty clear that western European languages are encoded
as USASCII => ISO-8859-1 => UTF-8 in that order, no exceptions.
Any UA breaking this (even, or perhaps especially if it's MS, since they're
big enough to have adequate personnel and resources to know better) should
be spanked.
Otherwise, it won't get fixed.
As I remember, setting the default codepage in Windows to be ISO-8859-1
system-wide isn't that hard.
-Philip
