Re: [Mailman-Developers] Headers in administrative messages

--On Friday, October 10, 2008 1:31 PM -0700 Mark Sapiro <[EMAIL PROTECTED]> wrote: Kenneth Porter wrote: It might be nice to get the List-id header in messages to the administrator. I have a spam white-listing rule for list messages and I'm finding some of my auto-discard notifi

[Mailman-Developers] Headers in administrative messages

It might be nice to get the List-id header in messages to the administrator. I have a spam white-listing rule for list messages and I'm finding some of my auto-discard notifications are ending up in my spam folder instead of my administrator folder because they lack the list id pattern I use to

Re: [Mailman-Developers] before next release: disable backscatter in default installation

On Saturday, April 12, 2008 12:44 PM -0400 Barry Warsaw <[EMAIL PROTECTED]> wrote: > Thanks! Capture here in the "best practices" section: > > http://wiki.list.org/display/DEV/Home Note that there's already backscatter prevention info here:

Re: [Mailman-Developers] mm-handler 2.1.10

--On Saturday, March 29, 2008 4:47 PM -0500 David Champion <[EMAIL PROTECTED]> wrote: > It's important NOT to have an "m" flag, but just in case you forget > that, mm-handler tries to handle multiple recipients a little. How about checking for multiple recipients, logging a line explaining to r

Re: [Mailman-Developers] mm-handler 2.1.10(was:beforenextrelease:disable backscatter in default installation)

--On Saturday, March 29, 2008 1:30 PM -0700 Mark Sapiro <[EMAIL PROTECTED]> wrote: > True, but Kenneth added additional logging beyond the debuging code. The additional stuff was just printf-debugging to figure out what was going wrong earlier. It can be excised or wrapped in if($Debug). > Als

Re: [Mailman-Developers] mm-handler2.1.10(was:beforenextrelease:disable backscatter in defaultinstallation)

--On Saturday, March 29, 2008 2:23 PM -0700 Mark Sapiro <[EMAIL PROTECTED]> wrote: > mm-handler parses its arguments from sendmail and builds a list of > recipients and then processes that list in a loop. If it is really the > case that a message addressed to, e.g., more than one list will be > p

Re: [Mailman-Developers] mm-handler 2.1.10 (was:beforenextrelease:disable backscatter in default installation)

New bug: The script is wrongly case-sensitive on the list name. A user just tried to send to "Tribes2-pickups" instead of "tribe2-pickups" and it dropped with a log message of "no such list". ___ Mailman-Developers mailing list Mailman-Developers@python

Re: [Mailman-Developers] mm-handler 2.1.10 (was:beforenextrelease:disable backscatter in default installation)

--On Saturday, March 29, 2008 9:37 AM -0700 Mark Sapiro <[EMAIL PROTECTED]> wrote: > I just checked, and my CentOS 5 system only has Sys::Syslog and not > Unix::Syslog. It might be worthwhile to provide your version plus a > patch to go back to the old DEBUG w/o logging. OTOH, Unix::Syslog is > a

Re: [Mailman-Developers] before next release: disable backscatterin default installation

--On Saturday, March 29, 2008 3:51 PM +0900 "Stephen J. Turnbull" <[EMAIL PROTECTED]> wrote: > If you equate self-defense with justice, you are wrong. Vigilantes go > beyond self-defense, and that's where they go wrong. We're quibbling over definitions. It's impossible to find agreement under

Re: [Mailman-Developers] mm-handler 2.1.10 (was: beforenextrelease:disable backscatter in default installation)

--On Friday, March 28, 2008 7:08 PM -0700 Mark Sapiro <[EMAIL PROTECTED]> wrote: > I would like to get this in the contrib directory for Mailman 2.1.10. I > can do this in several ways. One would just be to replace the existing > mm-handler and update the README.mm-handler as needed. That might b

Re: [Mailman-Developers] before next release: disable backscatterin default installation

--On Saturday, March 29, 2008 8:58 AM +0900 "Stephen J. Turnbull" <[EMAIL PROTECTED]> wrote: > > However you know that it's a mortal sin when you end up on several > > blacklists (and rightly so!) for having sent backscatter to > > innocent bystanders. > > Oh, brother! Look up "vigilante", an

Re: [Mailman-Developers] mm-handler 2.1.10 (was: before nextrelease:disable backscatter in default installation)

--On Friday, March 28, 2008 4:39 PM -0700 Kenneth Porter <[EMAIL PROTECTED]> wrote: > I'll put an updated copy on my website shortly. (Will also have fixed > comments.) Updated version: <http://matureasskickers.net/MISC/mm-handler.experimental> Changes fr

Re: [Mailman-Developers] mm-handler 2.1.10 (was: before nextrelease:disable backscatter in default installation)

--On Friday, March 28, 2008 4:29 PM -0700 Mark Sapiro <[EMAIL PROTECTED]> wrote: > In case you haven't got it already Thanks, just found it myself. ;) I'll put an updated copy on my website shortly. (Will also have fixed comments.) ___ Mailman-Deve

Re: [Mailman-Developers] mm-handler 2.1.10 (was: before next release:disable backscatter in default installation)

I should have read the error reply more closely. It gave me back this: Your mail for [EMAIL PROTECTED] could not be sent: no list named "tribes2-pickups-pickups" is known by lists.matureasskickers.net That should be easy to chase down. Since I patched the script to syslog I think I now

[Mailman-Developers] mm-handler 2.1.10 (was: before next release: disable backscatter in default installation)

--On Thursday, March 06, 2008 4:02 PM -0600 David Champion <[EMAIL PROTECTED]> wrote: > Here is an update to mm-handler which might address this adequately. I > no longer use mm-handler myself (despite having written it), so I can't > test this short of installing a new Mailman instance. Can so

Re: [Mailman-Developers] before next release: disable backscatter indefault installation

On Wednesday, March 26, 2008 8:18 PM -0400 CristóbalPalmer <[EMAIL PROTECTED]> wrote: > Jo, would you please be willing to take the lead in improving this > wiki page: > > http://wiki.list.org/display/SEC/Controlling+spam > > since it looks rather stubbish? Agreed. I grabbed text from Jo's ori

Re: [Mailman-Developers] anti-backscatter mm-handler (was before next release: disablebackscatter in default installation)

BTW, the experimental mm-handler isn't currently letting posts through, but I haven't had a chance to debug it. I'll try to look at it this weekend. It no longer reports an error, though, once I fixed the permissions. ___ Mailman-Developers mailing list

Re: [Mailman-Developers] before next release: disable backscatter in default installation

--On Tuesday, March 04, 2008 12:30 PM -0800 Jo Rhett <[EMAIL PROTECTED]> wrote: > 1. Don't create backscatter aliases for subscribe/unsubscribe/etc by > default. Nearly everyone uses web based signup. Here's the list of valid actions from mm-handler: @ValidActions = qw(admin bounces confirm jo

Re: [Mailman-Developers] before nextrelease: disable backscatter indefault installation

--On Monday, March 10, 2008 10:02 PM -0700 Mark Sapiro <[EMAIL PROTECTED]> wrote: > Maybe you can come up with some good text to add to the wiki page. Thanks for the details. Wiki updated. ___ Mailman-Developers mailing list Mailman-Developers@python

Re: [Mailman-Developers] anti-backscatter mm-handler (was before next release: disablebackscatter in default installation)

--On Monday, March 10, 2008 6:18 PM -0700 Mark Sapiro <[EMAIL PROTECTED]> wrote: > In any case, my guess would be a permissions issue or a group mismatch > from the mailman wrapper, but if everything is the same as with the > previous mm-handler, then that should not be the case. That looks like

[Mailman-Developers] anti-backscatter mm-handler (was before next release: disable backscatter in default installation)

--On Friday, March 07, 2008 4:31 PM -0800 Mark Sapiro <[EMAIL PROTECTED]> wrote: > Also, if you're happy with the way the new mm_handler is working, let > me know, and I'll get it in the contrib directory for 2.1.10. I'm seeing lines like the following in maillog. How do I trace the source of t

Re: [Mailman-Developers] before nextrelease: disable backscatter in default installation

--On Friday, March 07, 2008 4:31 PM -0800 Mark Sapiro <[EMAIL PROTECTED]> wrote: > I changed the last part. Take a look. Note that sitelist.cfg is > irrelevant. It is intended to be used as input to bin/config_list to > configure the site list ('mailman' list) more appropriately than the > defaul

Re: [Mailman-Developers] before next release: disable backscatter indefault installation

--On Monday, March 10, 2008 10:19 AM + Ian Eiloart <[EMAIL PROTECTED]> wrote: > Yep, it would be the easiest way to integrate acceptance testing with > Exim. It's common for sites to put Exim installations in front of > Exchange servers (for security reasons), and do SMTP call forwards to >

Re: [Mailman-Developers] before next release: disable backscatter indefault installation

On Wednesday, March 05, 2008 5:54 PM -0500 Barry Warsaw <[EMAIL PROTECTED]> wrote: > Mark's the release manager for 2.1, but FWIW I completely agree with > Stephen about this. What I would suggest though is that this > information be put in a prominent place on the wiki. We have a > security sp

Re: [Mailman-Developers] Confluence via Seamonkey

--On Friday, March 07, 2008 9:16 AM -0500 Barry Warsaw <[EMAIL PROTECTED]> wrote: > I haven't tried Seamonkey, but just be sure you have JavaScript enabled. > You probably already do, but I think that'll make a difference. Aha! That was it. I'd allowed it on FF yesterday at the office, but not

Re: [Mailman-Developers] SEC wiki space, Confluence via Seamonkey

--On Thursday, March 06, 2008 9:03 PM -0500 Barry Warsaw <[EMAIL PROTECTED]> wrote: > Try it now. At one point I thought the entire space should be write > restricted to just the core developers, but I think that's misguided. > I've opened up the permissions and we can lock specific pages if/whe

Re: [Mailman-Developers] before next release: disable backscatter in default installation

On Thursday, March 06, 2008 4:02 PM -0600 David Champion <[EMAIL PROTECTED]> wrote: > Here is an update to mm-handler which might address this adequately. I > no longer use mm-handler myself (despite having written it), so I can't > test this short of installing a new Mailman instance. Can some

Re: [Mailman-Developers] SEC wiki space (was: before next release:disable backscatter indefault installation)

On Thursday, March 06, 2008 12:47 PM -0800 Mark Sapiro <[EMAIL PROTECTED]> wrote: >>> http://wiki.list.org/display/SEC/Home >> >> This appears to be a read-only space. The add page link on the dashboard >> is grey and there's no Edit tab on the main page. > > > Did you 'Sign Up' and/or 'Log In'?

[Mailman-Developers] Per-user subject prefix setting

A frequent request on mailing lists without a subject prefix is to add one. This often leads to long debate threads about the utility of the prefix. There seems to be two different styles of processing mail that leads to this conflict. One style (which I use) is to filter mail into many folders,

Re: [Mailman-Developers] before next release: disable backscatter in default installation

On Tuesday, March 04, 2008 12:30 PM -0800 Jo Rhett <[EMAIL PROTECTED]> wrote: > 1. Don't create backscatter aliases for subscribe/unsubscribe/etc by > default. Nearly everyone uses web based signup. > > 2. Discard or hold messages from non-subscribers by default. How, exactly, does one do these

[Mailman-Developers] SEC wiki space (was: before next release: disable backscatter indefault installation)

On Wednesday, March 05, 2008 5:54 PM -0500 Barry Warsaw <[EMAIL PROTECTED]> wrote: > Mark's the release manager for 2.1, but FWIW I completely agree with > Stephen about this. What I would suggest though is that this > information be put in a prominent place on the wiki. We have a > security sp

Re: [Mailman-Developers] Dates again

--On Wednesday, November 24, 2004 3:25 PM -0500 Terri Oda <[EMAIL PROTECTED]> wrote: 3. Helping users sort the email in their inboxes. This can be important to some people, since I know when we had one user posting from 1980, many other list members weren't noticing her posts because their mail

Re: [Mailman-Developers] Dates again

--On Saturday, November 20, 2004 6:22 AM -0500 Steven Kuck <[EMAIL PROTECTED]> wrote: As I said, I can guarantee messages from the future are wrong. Disagree? Perhaps messages from more than a day (or N days) in the past could be bounced saying: "Either your system clock is wrong or your message

[Mailman-Developers] Plussed addresses

I'd like to use a "plussed" address in mailing lists (eg. [EMAIL PROTECTED]) and I'm wondering if anyone has proposed changing the mailman filtering to match a plussed member name with the unplussed equivalent? In other words, I'd like to subscribe to a list using the plussed address, but post wit