On Fri, 2006-03-17 at 15:37, Martin Hejl wrote:
> > Most of our lists aren't moderated. Only leaf-announce,
> > leaf-cvs-commits, and leaf-auto are. I did setup our lists so very
> > little spam gets through. I even wrote a FAQ for mailman on the subject.
> > I clear our mailman held posts periodically (I used to do this daily,
> > I'm lucky to remember to do it weekly now.). Most of the held posts I
> > end up discarding, as they're spam.
>
> so what would "taking over our mailing list management duties?" include?
> I'm not saying I won't do it, I just don't tend to say "yes" before I
> know what I'm getting into.
Martin,
Not much, unless you want to change the list configuration.
Approximately, 30min each time you decide to clean the held messages.
Occasionally modify (new project member adds) the accepted user posting
list on a couple of our lists.
Knowledge of email headers, and Mailman list management is
essential. You already have knowledge of rfc 1855.
http://staff.imsa.edu/~ckolar/mailman/mailman-administration-v2.html
SF will eventually move to a newer version of mailman (2.1 probably),
and that will require quite a bit of work.
> > http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq03.010.htp
> I'm not sure why you're sending that link - as far as I can tell, my
> message was "plain text" just fine, it simply was "multipart/mixed due
> to the attachment
Exactly. It was held for that reason. The mime type wasn't one of the
two that pass through the filter automatically.
> - I don't send forwards inline if I can avoid it,
> because doing so usually tends to hide the fact that it was a forward.
> Blocking "multipart/mixed" may be a little over-eager (since many mail
> clients use that by default, sending text+html) but I don't know how
> much spam this list gets, so I can't judge what kind of measures are
> needed to keep spam under control.
A lot of them get caught due to not being subscribed to the mailing
list. The remainder would get through, and that is significant. Just ask
Tom Eastep. He moved shorewall lists off SF for that reason and others.
Of course Tom's solution requires even more work on the admin side.
> > Our general list information page for each of our eight lists have
> > information on posting policies.
> >
> > e.g. "Using leaf-devel"
> > http://lists.sourceforge.net/lists/listinfo/leaf-devel
>
> ok, so I guess "multipart/mixed" is not "acceptable" on our lists.
> That's good to know. Not that I know of a way to "properly" forward a
> message to this list that way,
You can forward in-line. Multipart/mixed means you forwarded as an
attachment.
> but it doesn't really matter, since I
> plan on always remembering of hitting "reply all" when responding to
> this list.
I usually use reply-to-list, unless the desired recipient has issues
receiving mail posted to our lists.
> And if I don't, I'll hopefully remember to not forward the
> mail, but simply pretend I sent it that way to the list (not quite
> according to the hardcore version of the Netiquette as I understand it,
> but since it doesn't harm anybody, I guess it's no big deal).
It's been a while since I read RFC 1855. I doubt most people have ever
read it. :-(
ftp://ftp.rfc-editor.org/in-notes/rfc1855.txt
--
Mike Noyes <mhnoyes at users.sourceforge.net>
http://sourceforge.net/users/mhnoyes/
SF.net Projects: leaf, phpwebsite, phpwebsite-comm, sitedocs
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
leaf-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/leaf-devel
