Re: [Mailman-Users] Daily admin post -- can it be weekly? (for low traffic lists)

and ACLs and RBLs are already in place. Yet spam still gets through. Go figure :-) -- | Bretton Vine | 083 633 8475 | [EMAIL PROTECTED] | | GPG: http://bretton.hivemind.net/bretton_vine.asc | "It suddenly struck me that that tiny pea, pretty and blue, was the Earth. I put up my thumb an

[Mailman-Users] obscuring list addresses on the listinfo page

, send email to | . 1. How would one obscure ? 2. How could you do it for 300+ lists thanks -- | Bretton Vine | 083 633 8475 | [EMAIL PROTECTED] | | GPG: http://bretton.hivemind.net/bretton_vine.asc | "You can kill a man but you can't kill an idea."

[Mailman-Users] Daily admin post -- can it be weekly? (for low traffic lists)

l the available options, which means the same spammer keeps sending to the list * some flat out refuse to have to do constant admin work on a low volume list -- | Bretton Vine | 083 633 8475 | [EMAIL PROTECTED] | | GPG: http://bretton.hivemind.net/bretton_vine.asc | One day a mother comes home f

[Mailman-Users] extracting banned/rejected/discarded email addresses for exim blacklist

sis and just add new addresses to exim's blacklist) Part of the reason I'm looking into this is that despite all my pleading some list-owners just won't admin their lists properly (and yes I know I can set a limit on max days to hold - but some legitimate mail might get lost then)

Re: [Mailman-Users] MM lists on Gmane

now for some lists people have to be vetted and archives are completely banned. Online means of archiving lists are useful -- don't get me wrong -- but some sense of polite protocol must be observed to prevent abuse. Besides, doesn't the mailman list already have an web-accessible arc

Re: [Mailman-Users] MM lists on Gmane

Jason R. Mastaler said the following on 2006/09/17 08:10 AM: > If Gmane allows me and others to keep up with Barry's release > announcements for example in a convenient manner, I think that's a good thing. What's preventing you from just subscribing to the announce list?

Re: [Mailman-Users] MM lists on Gmane

red by some RFCs but list-etiquette is mostly a word of mouth exercise. It's best taught by example. -- | Bretton Vine | 083 633 8475 | [EMAIL PROTECTED] | | GPG: http://bretton.hivemind.net/bretton_vine.asc | "It is important to go through the st

Re: [Mailman-Users] central location for /pythonlib/* for multipleinstallations

ngle source of the pythonlibs. Now just to make sure a future upgrade path isn't compromised by opting for this. -- | Bretton Vine | 083 633 8475 | [EMAIL PROTECTED] | | GPG: http://bretton.hivemind.net/bretton_vine.asc | "If I work incessantly to the last, nature owes me another fo

[Mailman-Users] central location for /pythonlib/* for multiple installations

ils.py are different sizes, some the same dates, others not Given that this affects 250+ lists it's an important issue I need clarification on before experimenting. thanks in advance. -- | Bretton Vine | 083 633 8475 | [EMAIL PROTECTED] | | GPG: http://bretton.hivemind.net/bretton_

Re: [Mailman-Users] RELEASED: Mailman 2.1.9

Bretton Vine said the following on 2006/09/13 06:15 PM: > Will the following patch apply to 2.1.9 source? > [ 1220144 ] allow specifying another list in accept_these_nonmembers > http://sourceforge.net/tracker/index.php?func=detail&aid=1220144&group_id=103&atid=300103 Con

Re: [Mailman-Users] RELEASED: Mailman 2.1.9

hp?func=detail&aid=1220144&group_id=103&atid=300103 regards -- | Bretton Vine | 083 633 8475 | [EMAIL PROTECTED] | | GPG: http://bretton.hivemind.net/bretton_vine.asc | NP: http://www.sylviemarks.de/mp3/radiox060906sylviemarks.mp3 --

Re: [Mailman-Users] Problems with digests

j, header): qrunner(18178): File "MMHOME/pythonlib/email/Message.py", line 563, in _get_params_preserve qrunner(18178): params = Utils.decode_params(params) qrunner(18178): File "MMHOME/pythonlib/email/Utils.py", line 337, in decode_params qrunner(18178): charset, language, val

Re: [Mailman-Users] odd error with archive(?) and processing of mail cc'd to list with PDF attachement

Bretton Vine said the following on 2006/09/13 09:28 AM: > Sep 03 13:52:25 2006 qrunner(7888): charset, language, value = > decode_rfc2231(EMPTYSTRING.join(value)) > Sep 03 13:52:25 2006 qrunner(7888): File "MMHOME/pythonlib/email/Utils.py", > line 284, in decode_rfc2231

[Mailman-Users] odd error with archive(?) and processing of mail cc'd to list with PDF attachement

in decode_params Sep 03 13:52:25 2006 qrunner(7888): charset, language, value = decode_rfc2231(EMPTYSTRING.join(value)) Sep 03 13:52:25 2006 qrunner(7888): File "MMHOME/pythonlib/email/Utils.py", line 284, in decode_rfc2231 Sep 03 13:52:25 2006 qrunner(7888): charset, language, s

Re: [Mailman-Users] GPL Issues (was Re: query re "message has implicit destination"(devils advocate!))

well technically only copyright holders can do so) -- | Bretton Vine | 083 633 8475 | [EMAIL PROTECTED] | | GPG: http://bretton.hivemind.net/bretton_vine.asc | "A new study shows that licking the sweat off a frog can cure depression. The down side is, the minute you st

Re: [Mailman-Users] query re "message has implicit destination"(devils advocate!)

;s probably a case of motivation. Developers would need to be motivated to chase one of the organisations mentioned and it would be time-consuming and require effort when they might prefer to be coding. Obviously a gap here for a champion from within the user base to pursue the

Re: [Mailman-Users] query re "message has implicit destination"(devils advocate!)

general -- things you only realise when you're actually implementing it on a box or run into trouble. I doubt anyone is to blame for this -- there are simply too many variables involved. I'd suggest to anyone looking at Mailman as a solution search the docs/FAQ/list-archives, *and* join th

Re: [Mailman-Users] query re "message has implicit destination"(devils advocate!)

g, I needed a simple answer. I couldn't find one myself, so I asked. In return I learned far more than I requested, and developed an immediate respect for those who understood where I was coming from. In time perhaps those who endured irritation will understand. :-) -- | Bretton Vine | 083 633 847

Re: [Mailman-Users] query re "message has implicit destination"(devils advocate!)

e communities. And community isn't about 'gifts' from the elders or sticking to sensible rules. It's about invigorating the elders so they feel like children in a toy-store again. (and no I'm not being ageist or condescending or merely rebellious here) -- | Bretton Vine | 083

Re: [Mailman-Users] query re "message has implicit destination"(devils advocate!)

t the restraint they have shown. The teacher learns more from the student than the student learns from the teacher. It would be wise not to forget that. -- | Bretton Vine | 083 633 8475 | [EMAIL PROTECTED] | | GPG: http://bretton.hivemind.net/bretton_vine.asc | "It is important that stude

Re: [Mailman-Users] query re "message has implicit destination"(devils advocate!)

so many which > are more important for such a thing. Perhaps a list of "you /really/ should set these settings to X" would be useful to people short on time :-) Of course you could just bundle the product that way in the first place but where's the fun in that? -- | Bretton Vine

Re: [Mailman-Users] query re "message has implicit destination" (devils advocate!)

stops working. I'm not about to embark on learning Python just to understand Mailman (although it would be a useful exercise in a broader sense) but I do wish documentation had the same level of diligence and peer-review that the code gets (not specifically mailman -- software in general) I can

Re: [Mailman-Users] query re "message has implicit destination" (devils advocate!)

s beyond the point of being able to fix them. The former end up as luddites. > You're asking me whether or not we should have all the software defaults > set to their safest mode > Excuse me? See Subject: (devils advocate) ;-) >> # Functionality = 1 > I don't see how t

Re: [Mailman-Users] query re "message has implicit destination"

nce. > Also, you've probably already set require_explicit_destination off for > the list so there won't be a next time. Pretty much > Hint - look at max_num_recipients before you get burned on that one too. Set to 5 (default) -- | Bretton Vine | 083 633 8475 | [EMAIL PROTECT

Re: [Mailman-Users] query re "message has implicit destination"

Fair enough. At least there is something to reference now instead of "I don't know, give me 5 mins with google and I'll get back to you" -- | Bretton Vine | 083 633 8475 | [EMAIL PROTECTED] | | GPG: http://bretton.hivemind.net/bretton_vine.asc | "For a smart material to

Re: [Mailman-Users] query re "message has implicit destination"

ber that matches that setup and still resulted in the error indicated. Odd? I think so. Does the error lie with the system, no, I'm pretty sure it doesn't going by the useful input I've had. Thanks again :-) -- | Bretton Vine | 083 633 8475 | [EMAIL PROTECTED] | | GPG: http://

Re: [Mailman-Users] query re "message has implicit destination" (devils advocate!)

conf files I've seen is something like the following: # Uncomment the following line to enable $functionality. This setting is # disabled by default because it is important you understand why it exists # and actually turn it on purposefully (which is what we suggest you do) # See http://.

Re: [Mailman-Users] query re "message has implicit destination"

r of "but you can turn it off" is seldom sufficient in satisfying their curiosity. Some people want options and flashing lights and a machine that goes "ping" while others actually want to know why the lights flash in the first place. I work for the latter Believe it or

Re: [Mailman-Users] query re "message has implicit destination"

ave the setting enabled. I don't quite agree, but it seems to be a point of view without a strong counter-argument. regards -- | Bretton Vine | 083 633 8475 | [EMAIL PROTECTED] | | GPG: http://bretton.hivemind.net/bretton_vine.asc | Every portrait that is painted with feeling is a portrait of the

Re: [Mailman-Users] How to create a list with an approved list of posters? (not answered by FAQ?)

tid=300103&aid=1220144&group_id=103 That and a combination of setting the moderator flag for a list for all users and unsetting of "mod" for specific addresses in Membership Management we want to allow to post which is probably what you want. regards -- | Bretton Vine | 083

[Mailman-Users] query re "message has implicit destination"

tion is highly tweaked to our environment based on online documentation relating to Mailman and Exim. Can anyone shed some light (and yes, I've googled and gone through numerous FAQ answers which have bought me some time but not a reason why the default installation behaviour is as it is for B

[Mailman-Users] follow-up to previous posts, exim + mailman + virtualhosts

nd the relevant documentation on to do it? Can the config be setup in mailman or is some magic required with regards DNS, Apache (rewrite, redirect, alias directives etc) and Exim. thanks -- | Bretton Vine | 083 633 8475 | [EMAIL PROTECTED] | | GPG: http://bretton.hivemind.net/bretton_vi

[Mailman-Users] vhost patchset for 2.1.7 (Debian, Exim)

Neil Blakey-Milner's patch working briefly but it wasn't sufficient for my needs. I know him so I contacted him directly but he's unable to assist with tweaking the 2.1.7 patches to my needs. (Neil's original patches) 1. http://mithrandr.moria.org/blog/139.html 2. http:

Re: [Mailman-Users] errors after applying virtualhost patches to 2.1.7

Bretton Vine said the following on 2006/03/20 07:19 PM: > After applying the following two patches to the mailman source, > compiling and installing on Debian unstable I get the attached errors in > my logfiles. Apologies, forgot to add which patches I applied: [1] http://nix.lauft.ne

[Mailman-Users] errors after applying virtualhost patches to 2.1.7

man/Archiver/HyperArch.py", line 379, in __setstate__ d['_mlist'] = self._open_list(listname) File "/var/lib/mailman/Mailman/Archiver/HyperArch.py", line 344, in _open_list except Errors.MMListError, e: NameError: global name 'Errors' is not defined --