Re: [Mailman-Users] public listname case? + system pass?

[Bob Weissman]

At 01:53 AM 9/2/02, Richard Barrett wrote:
>At 02:17 02/09/2002 -0400, Fuzzy wrote:
>
>>On Sun, 1 Sep 2002, Bob Weissman wrote:
>>
>>> >* Paul Reilly <[EMAIL PROTECTED]> [20020901 01:20]: wrote:
>>> >> 1) when i create a new list with 'newlist -q mylist [EMAIL PROTECTED] mypass'
>>> >>it creates the list fine, but it always changes the case of the
>>> >>listname to uppercase. ie "mylist" becomes "Mylist".
>>>
>>> Edit Mailman/MailList.py, changing the lines
>>> self.real_name = '%s%s' % (string.upper(self._internal_name[0]),
>>>self._internal_name[1:])
>>> to
>>> self.real_name = self._internal_name
>>>
>>> - Bob
>>
>>
>>would this do the same for mm 2.1b3?
>>
>>--- Mailman/MailList.py.origMon Sep  2 01:42:15 2002
>>+++ Mailman/MailList.py Mon Sep  2 02:14:47 2002
>>@@ -297,8 +297,7 @@
>> self.bounce_matching_headers = \
>> mm_cfg.DEFAULT_BOUNCE_MATCHING_HEADERS
>> self.anonymous_list = mm_cfg.DEFAULT_ANONYMOUS_LIST
>>-internalname = self.internal_name()
>>-self.real_name = internalname[0].upper() + internalname[1:]
>>+self.real_name = self.internal_name()
>> self.description = ''
>> self.info = ''
>> self.welcome_msg = ''
>
>A simpler way is to just change the first (real_name) and fourth (MM 2.0.x) or sixth 
>(MM 2.1b3) (subject_prefix) fields on the web admin GUI General Options page for the 
>list.

Simpler? Not in the case where the Mailman administrator wants all lists forever after 
to not have their first characters uppercased. Changing the code once accomplishes 
this once and for all.

- Bob



--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/

Re: [Mailman-Users] public listname case? + system pass?

[Bob Weissman]

>* Paul Reilly <[EMAIL PROTECTED]> [20020901 01:20]: wrote:
>> 1) when i create a new list with 'newlist -q mylist [EMAIL PROTECTED] mypass'
>>it creates the list fine, but it always changes the case of the
>>listname to uppercase. ie "mylist" becomes "Mylist".
>> 
>>This means I need to go in to the web interface to change it back to
>>lower case every time. How do I stop this from happening? What code
>>needs to be edited ? I'm using mailman 2.0.13


Edit Mailman/MailList.py, changing the lines
self.real_name = '%s%s' % (string.upper(self._internal_name[0]),
   self._internal_name[1:])
to
self.real_name = self._internal_name

- Bob


--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/

Re: [Mailman-Users] Archive time stamp weirdness

[Bob Weissman]

At 02:43 PM 8/13/02, Jon Carnes wrote:
>So what happens when you run "date"?  Does it display the proper timezone?

Yes. (My machine is using PST8PDT as the timezone, if that detail is important.)

The correct time is the earlier one, by the way. The archive's .mbox file shows in the 
last message
Date: Tue Aug 13 14:36:00 2002
X-Original-Date: Tue, 13 Aug 2002 14:35:22 -0700

But somehow an hour is getting added to the "last message date."

- Bob

>On Tuesday 13 August 2002 06:46 pm, Bob Weissman wrote:
>> My 2.0.11 archives are showing a strange symptom, namely that the last
>> message time stamp is exactly one hour later than the last archived
>> time. Looks like a timezone issue, maybe, but I didn't see anything
>> obvious in the pipermail sources.
>>
>> Last message date: Tue Aug 13 15:36:00 2002
>> Archived on: Tue Aug 13 14:36:00 2002
>>
>> Any ideas?


--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/

[Mailman-Users] Archive time stamp weirdness

[Bob Weissman]

My 2.0.11 archives are showing a strange symptom, namely that the last message time 
stamp is exactly one hour later than the last archived time. Looks like a timezone 
issue, maybe, but I didn't see anything obvious in the pipermail sources.

Last message date: Tue Aug 13 15:36:00 2002
Archived on: Tue Aug 13 14:36:00 2002 

Any ideas?

Thanks,
- Bob


--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/

Re: [Mailman-Users] Digest Header modification ?

[Bob Weissman]

At 02:40 PM 8/2/02, Dan Mick wrote:
>> Every digest starts with these lines:
>
>> And these are the lines I would like to replace with something else.
>> They do not appear anywhere in the UI. In fact, the only place where I
>> could find them is in /etc/mailman/masthead.txt
>> However, editing the text there will, I'm fairly sure, edit it for ALL
>> mailing lists, which is not what I want to do.
>
>Yes, that's where those lines appear, and the only place.
>You can edit a list-specific copy in 2.1, but in
>2.0.x they are global.

Use the source, Luke! The great benefit of open source software is that you can make 
it do whatever you want. (grep is your best friend when trying to figure out what to 
change, where.) In this case, all you have to do is 

1. Create a new masthead for your list in the same directory as your existing 
masthead.txt. Call it my_masthead.txt, say.

2. Edit Handlers/ToDigest.py to check for your one specific list.

if self.__mlist.real_name == 'my_list_name':
masthead = Utils.maketext('my_masthead.txt', self.TemplateRefs())
else:
masthead = Utils.maketext('masthead.txt', self.TemplateRefs())
  
Sure, it's a hack. But who cares? If it offends you, there are obvious ways of making 
it more elegant.

- Bob


--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/

Re: [Mailman-Users] Public lists and archiving questions

[Bob Weissman]

At 09:00 AM 8/2/02, David Mir wrote:
>I have tried the first option it still does not show up when I go my listinfo 
>site.  Is there anything I should check to see if there are errors?

Here's a tip which should probably be added to the FAQ.

If you have lists which appear in the Admin index, but not in the Listinfo index, it 
is usually because of a domain mismatch, often due to the use of virtual hosts.

In your case, it appears to be due to an extra "www." I can see your lists at
http://soartech.com/mailman/listinfo/
but not at
http://www.soartech.com/mailman/listinfo/

Please look at the VIRTUAL_HOST_OVERVIEW option in Defaults.py and at the web_page_url 
attribute of your lists. You will need to change one of them.

- Bob


--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/

Re: [Mailman-Users] Re: individual moderation of users in mailman

[Bob Weissman]

At 11:36 AM 8/1/02, J C Lawrence wrote:
>On Thu, 1 Aug 2002 14:34:51 -0300 
>Marcelo Assis <[EMAIL PROTECTED]> wrote:

>> 1- can we set ONE indivual member into moderated mode, so we can >
>> approve/deny all his messages before they get to the list, instead
>> of putting the WHOLE list in moderated mode?
>
> Yes, but Mailman v2.0 is really not built for this

Yes, it is. Each list has a forbidden_posters variable.

forbidden_posters (privacy): Addresses whose postings are always held for 
approval. 
Email addresses whose posts should always be held for approval, no matter what 
other
options you have set. 

- Bob


--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/

[Mailman-Users] For the truly lazy! (You know who you are.)

[Bob Weissman]

If you're as lazy as I am, you know that it's worth 5 minutes of programming effort to 
save 1/2 second of user action repeated multiple times.

I got tired of having to manually focus on the password input box in my lists' 
administrative authentication pages. It was costing me one mouse click or two hits of 
the Tab key. So I decided to make the input box self-focusing.

If you're even lazier than I am, you don't even have to figure this out for yourself. 
Just apply the following 1-line patch in ~mailman/templates to patch admlogin.txt. It 
works in all the browsers I have access to. This is for Mailman 2.0.x. I haven't tried 
2.1 yet.

- Bob

--- admlogin.txt.ORIG   Tue Jul 30 10:38:31 2002
+++ admlogin.txtTue Jul 30 11:24:48 2002
@@ -2,7 +2,7 @@
 
   %(listname)s Administrative Authentication
 
-
+
 
 %(message)s
   


--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/

Re: [Mailman-Users] forwarded message from Woodie Sayles

[Bob Weissman]

At 08:54 AM 7/29/02, Woodie Sayles wrote:
>I have list members who have subscribed as [EMAIL PROTECTED], but when they
>send an email out, it goes out under the name [EMAIL PROTECTED] We
>can't subscribe every member under two emails, so I'm wondering if the Alias
>Names will work for this situation. If so, how? Or, if anyone has any other
>suggestions on this, I would appreciate hearing them.

Isn't this exactly what SMART_ADDRESS_MATCH is for?

# When true, Mailman will consider [EMAIL PROTECTED] to be the same address as
# user@domain.  If set to 0, Mailman will consider [EMAIL PROTECTED] to be the
# same address as [EMAIL PROTECTED], but different than user@domain.  Usernames
# will always be case preserved, and host parts of addresses will all be
# lowercased.
SMART_ADDRESS_MATCH = 1

- Bob


--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/

Re: [Mailman-Users] question

[Bob Weissman]

I just tried it on a test list, and the remove_members command did the trick, at least 
in version 2.0.11. Caeden should be able to do
remove_members qsep \"[EMAIL PROTECTED]

If that doesn't work, try upgrading to 2.0.11 or better.

- Bob

At 11:54 AM 7/27/02, Tim Miller wrote:
>I had a similar problem with a list several weeks back.  It wasn't the same 
>characters but the situation was the same.  No method I tried including removing it 
>from the command line and trying to rebuild the lists .db file worked.  I finally 
>started restoring the back-up .db files for the list until I found one where the 
>address was not corrupted.
>
>Tim
>
>
>At 02:41 PM 7/26/2002, Caeden Dempsey wrote:
>
>>I am having problems unsubscribing someone from my listserv.  Somehow the address 
>was listed as 
>"[EMAIL PROTECTED]
> (notice quotation mark at beginning).  This person is receiving mail.  When I try to 
>unsubscribe the address I get this message:
>>
>> 
>>
>>
>>Error Unsubscribing:
>>
>>* [EMAIL PROTECTED]>  
>>How can I remove this address from my list?
>>
>> 
>>
>>Caeden
>>
>> 
>>
>> 
>>
>>---
>>
>>Caeden Dempsey
>>
>>LGBT Student Empowerment Project 
>>
>>United States Student Association
>>
>>202.347.8772
>>
>>[EMAIL PROTECTED]
>>
>>www.usstudents.org


--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/

Re: [Mailman-Users] Setting the footer

[Bob Weissman]

At 10:51 AM 7/22/02, Shannon M. Anderson wrote:
>I have been using Mailman for a while now for different lists I run. I am having a 
>time getting mailman to set a footer at the end of the mails it sends out. I have in 
>both regular and digest member areas a simple footer set (using strait text) but when 
>I post to list No footers show up.
>Am I missing some thing that activates this option?

The only time I've seen this behavior is when someone posts a MIME message (in HTML or 
whatever) to a list. Then the footer gets dropped because it occurs after the final 
MIME boundary.

Try sending a message explicitly in plain text only and see whether the footer 
reappears. If it doesn't, something more serious is wrong.

- Bob



--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py

[Mailman-Users] "Members" vs. "Subscribers"

[Bob Weissman]

This is a linguistic subtlety in the English version of Mailman.

Maliman refers to list subscribers as "members," for example when rejecting a post 
from a "non-member" to a "members-only" list. This terminology is confusing in some 
circumstances. Here's why.

I run lists for a professional, non-profit, organization which has dues-paying 
members. Not all paying members subscribe to all lists, and not all subscribers are 
paying members. If a dues-paying member has a posting rejected to what Mailman calls a 
"members-only" list, he will promptly complain to me that he is, in fact, a "member." 
And he's right. He's just not a *subscriber* to the list in question.

In my own Mailman 2.0.11 installation, I've scoured the sources for user-visible 
strings and changed "member" to "subscriber" everywhere I thought it was important. I 
would like to suggest this become an official terminology change for future versions 
of Mailman.

- Bob



--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py

Re: [Mailman-Users] SMART_ADDRESS_MATCH isn't very

[Bob Weissman]

At 01:54 PM 7/15/02, Jerry Stratton wrote:
>>I have a user subscribed as [EMAIL PROTECTED] who just posted to a
>>members-only list as [EMAIL PROTECTED] (Because of Sun's email setup,
>>this is out of the user's control.) The posting failed to go through
>>even though SMART_ADDRESS_MATCH was set to 1.
>>
>>Has anyone else hit this problem and found a fix? It seems like it
>>must be a logic error in Utils.FindMatchingAddresses(), but it's not
>>obvious to me where the problem is.
>
>I think we have, and I think the solution was that mailman assumes it has the 
>canonical e-mail address and searches for that domain within the domain of incoming 
>mail. So, if your user was subscribed as [EMAIL PROTECTED], attempts to e-mail from 
>[EMAIL PROTECTED] would work, because eng.sun.com contains sun.com. But sun.com does 
>not contain eng.sun.com, so posting as sun.com when subscribed as eng.sun.com does 
>not work.
>
>There is probably some logic to this, as it is not unreasonable to posit a site where 
>multiple subdomains are unrelated. (i.e., [EMAIL PROTECTED] and name@[EMAIL PROTECTED] have 
>their own namespaces). Mailman appears to be assuming that the subscription address 
>is the most general possible, and only more specific addresses will match with 
>SMART_ADDRESS_MATCH turned on.
>
>Anyway, our solution was to resubscribe the user with their "real" address, and I 
>have not heard from that list manager since on that subject.

Yes, I believe your analysis is correct. You can see the logic (or lack thereof? :-) 
in Utils.GetPossibleMatchingAddrs().

Thanks. I've changed the user's address on the list and it should work now.

For the curious, engineering folks at Sun Microsystems appear at eng.sun.com when at 
the office, and at sun.com when working from home. So they can't really help it.

- Bob



--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py

Re: [Mailman-Users] mailman list of lists

[Bob Weissman]

At 07:55 AM 7/15/02, [EMAIL PROTECTED] wrote:
>I have a mailman list that contains the address of three other mailmain
>lists.  My hope is for this to allow me to reach all people by the main
>list, or certain groups of people by one of the sub-lists.  Here is an
>example:
>
>  |--members-faculty
>  |
>members-all---|--members-staff
>  |
>  |--members-students
>
>This would allow me to send mail to everyone, just faculty, just staff, or
>just students.  However, there are two problems with this approach.

Mailman 2.0.x is not particularly good at umbrella lists (especially if there's 
overlap among the sub-lists).

>1) I can send to each of these lists individually, but when I send to the
>members-all list, each sub-list holds the message for approval.  I have
>added my email address to the list of "Addresses of members accepted for
>posting", and member_posting_only is set to "yes".  My understanding is
>that even though I do not belong to either of these lists, I will be
>allowed to send to all of them.  And this is indeed the case, as long as I
>am not sending via members-all.  My guess is that mailman is the re-sender
>in such a case, and is not allowed to post without permission.  Is this
>the case?  And if so, how do I change it?

Have you got require_explicit_destination set on the Privacy Options page? If so, you 
need to add members-all@your\.domain to the acceptable_addresses field for each 
sub-list.

>2) Once I approve the messages to be sent to the sub-lists, the subject
>line lists both list names like this:
>
>[members-all][members-x] my subject
>
>where x is either faculty, staff, or student.  I would like each sub-list
>to show its name ONLY if it is mailed to directly, but not if it is mailed
>to from the main list.  I don't think this is possible, but if it is,
>please let me know.

Not possible without serious code-hacking. What I suggest is eliminating the tag from 
the "all" list. Then subscribers will see only the tag for the list they are on. In a 
similar vein, you probably want to remove any footer information pointing to the "all" 
list, since subscribers can't maintain their own data on that list anyway.

In fact, there may be no need to have members-all be a full-fledged list. Perhaps it 
can be a simple alias pointing to the sub-lists.

- Bob



--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py

[Mailman-Users] SMART_ADDRESS_MATCH isn't very

[Bob Weissman]

Defaults.py says:

# When true, Mailman will consider [EMAIL PROTECTED] to be the same address as
# user@domain.  If set to 0, Mailman will consider [EMAIL PROTECTED] to be the
# same address as [EMAIL PROTECTED], but different than user@domain.  Usernames
# will always be case preserved, and host parts of addresses will all be
# lowercased.
SMART_ADDRESS_MATCH = 1

but this really doesn't work.

I have a user subscribed as [EMAIL PROTECTED] who just posted to a members-only list as 
[EMAIL PROTECTED] (Because of Sun's email setup, this is out of the user's control.) The 
posting failed to go through even though SMART_ADDRESS_MATCH was set to 1.

Has anyone else hit this problem and found a fix? It seems like it must be a logic 
error in Utils.FindMatchingAddresses(), but it's not obvious to me where the problem 
is.

Thanks,
- Bob



--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py

RE: [Mailman-Users] Customization of "main" Mailman pages

[Bob Weissman]

At 12:28 PM 6/26/02, Tim Mektrakarn wrote:
>NO! the question is how do you edit the MAIN listserv page where the lists are 
>populated not the main page of a specific list. 
>
>for example
>http://mail.python.org/mailman/listinfo
>
>THAT PAGE
>
>not 
>
>http://mail.python.org/mailman/listinfo/c++-sig
>
>i think we all know how to edit a page like that.

Edit Cgi/listinfo.py.

- Bob



--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py

[Mailman-Users] Help me with a trivial withlist script

[Bob Weissman]

There are times when I want to set an attribute on a whole bunch of mailing lists en 
masse. I tried to write a withlist script to do this, but it only works when the 
attribute value is a string. It doesn't work if the value is an integer. I'm no Python 
expert, but I thought from reading the docs that eval(`value`) would result in an 
expression of the correct type. No such luck.

To keep things simple, the script does only one list at a time, and I run it from a 
shell "for" loop.
def set_attr(mlist, attr, value): 
setattr(mlist, attr, eval(`value`)) 
mlist.Save()

What am I missing?

Thanks,
- Bob



--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py

RE: [Mailman-Users] remove email address from Mailman-Footer?

[Bob Weissman]

At 03:08 PM 5/31/02, steven wrote:
>I'm trying to find out how to edit the text which is created by the use
>of 
>
>I.E., where do I edit/define  ?

You will have to modify the function HTMLFormatter.GetMailmanFooter()

- Bob



--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py

Re: [Mailman-Users] Redundant headers in digests

[Bob Weissman]

At 11:56 AM 5/29/02, J C Lawrence wrote:
>On Wed, 29 May 2002 08:01:56 -0700 
>Bob Weissman <[EMAIL PROTECTED]> wrote:
>
>> I subscribe to the "SA Talk" list for SpamAssassin discussions in
>> digest mode. When I receive a digest, it shows all the headers in
>> every digested message. So I get loads of List-*, Resent-*,
>> Content-Type, etc., etc. headers in each and every digested message.
>> IMHO, Mailman should remove these from outgoing digests. Any takers?
>
>A MIME digest should contain unedited versions of the constituent
>messages.  Why?  That way it can be burst back into the discrete
>messages just as if the subscriber had received them that way in the
>first place (and is the way digests are and were intended to be used).

Thanks for the explanation. I guess Eudora isn't handling these properly, then. I'll 
switch to a text digest.

- Bob



--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py

[Mailman-Users] Redundant headers in digests

[Bob Weissman]

I subscribe to the "SA Talk" list for SpamAssassin discussions in digest mode. When I 
receive a digest, it shows all the headers in every digested message. So I get loads 
of List-*, Resent-*, Content-Type, etc., etc. headers in each and every digested 
message.

IMHO, Mailman should remove these from outgoing digests. Any takers?

- Bob



--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py

Re: [Mailman-Users] Not creating users?? (new install question)

[Bob Weissman]

At 02:24 PM 5/23/02, Mark Rauterkus wrote:
>How do you easily patch the contents of the output file (-o) into the
>aliases file? The cut and paste is a drag with pico, and the word wrap is a
>pain.

Why not just say
newlist -o /etc/mail/aliases

- Bob



--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py

Re: [Mailman-Users] Read-Only Mailing Lists

[Bob Weissman]

At 06:01 PM 5/21/02, you wrote:
>At 05:45 PM 5/21/2002 -0700, you wrote:
>>That's it. If you would spend half the amount of time learning Python and
>>HTML as you do complaining, you would have figured all of this out by now.
>
>I know HTML just fine thank you but I am not a Python programmer.  Even if I were the 
>spaghetti code that this is makes it difficult to patch into logical useable code.

I'm not a Python programmer, either. But it's trivially easy to understand. Give it a 
try. It took me 30 minutes to derive this patch.

>>And I was an Aerosmith fan before you were. They played at a giant beer bash
>>at my college circa 1973 (they had one album out). Dozens of kegs and "cups"
>>the size of large popcorn vats at the movies. People were passed out
>>everywhere. It was a good time.
>
>I doubt you were and if your idea of a good time is having everyone passed out from 
>being drunk that could explain a lot about your code.

I'm not a liar. What I told you is true. The venue was Rockwell Cage at MIT, where I 
earned a degree in computer science and engineering. And now you've just lost your 
chance at getting any help from me. What an idiot.

- Bob



--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py

Re: [Mailman-Users] Read-Only Mailing Lists

[Bob Weissman]

This is eminently doable, but you have to be willing and able to patch Mailman.

1. Patch Mailman to be able to turn off the List-* headers on a per-list basis so you 
don't confuse your subscribers with instructions that don't work. I can send this 
patch to anyone who wants it. I haven't figured out how to contribute it to 
SourceForge.

2. Edit listinfo.html for each list you want to have non-standard instructions on its 
listinfo page.

3. Restrict posting by setting "member_posting_only" to "no" and "posters" to the 
address(es) of people allowed to post. These are both on the "privacy" admin page.

That's it. If you would spend half the amount of time learning Python and HTML as you 
do complaining, you would have figured all of this out by now. And I was an Aerosmith 
fan before you were. They played at a giant beer bash at my college circa 1973 (they 
had one album out). Dozens of kegs and "cups" the size of large popcorn vats at the 
movies. People were passed out everywhere. It was a good time.

- Bob

At 05:15 PM 5/21/02, AerosmithFanClub.com List Admin wrote:
>LOTS OF LUCK!   I asked how to do this and only got rude answers that said I am 
>trying to force the software to do things it was not intended to do.  If you figure 
>it out let me know.  BTW the actual restricting of posts to just you is the easy 
>part.  The numerous referneces to web pages, posting instructions, etc that do not 
>apply to a news list will be a PITA.
>
>
>At 07:37 PM 5/20/2002 -0700, Benjamin Young wrote:
>>Hi all,
>>
>>I am new to Mailman and have searched the archives without finding a solution to my 
>problem but could not find an answer. I would like to create a list where only the 
>admin has permission to post (e.g. an announcements list).
>>
>>I could find no way to do this but this is OK if there is a way to customize the 
>welcome and help messages. I already customized the List-specific text prepended to 
>new-subscriber welcome message but this only adds the message to the beginning of the 
>pre-written message. I could not find any folders related to the list software in my 
>site's files but can I modify the entire welcome message for each of my lists?
>>
>>Thanks!
>>Benjamin



--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py

Re: Rel: [Mailman-Users] feature - multiple web views for adminlists

[Bob Weissman]

At 09:55 AM 5/21/02, Ashley M. Kirchner wrote:
>Terry Davis wrote:
>> Thank you for your reply.  Where can I read up on how to 'recompile' for
>> that directory?  What config files much I change, etc.
>
>When that's done, recompile, and reinstall.  Do this for each individual vhost.

You don't need to do this. One installation of Mailman is sufficient for multiple 
vhosts. I have this running just fine on my site. You have to be willing to patch 
Mailman/Cgi/admin.py, but this is much cleaner than having multiple copies of Mailman.

1. Create your virtual hosts, if you haven't already. Make sure your vhosts are 
pointing to Mailman for cgi, icons, and pipermail. For Apache, this is (depending on 
where ~mailman lives):

ScriptAlias /mailman /usr/home/mailman/cgi-bin

  AllowOverride None
  Options None
  Order allow,deny
  Allow from all

Alias /icons /usr/home/mailman/icons
Alias /pipermail /usr/home/mailman/archives/private

This goes inside your  sections of vhosts.conf for each vhost.

2. In your Mailman/mm_config.py file, make sure that VIRTUAL_HOST_OVERVIEW is set to 
1. (I use 2, which is nonstandard, to get an exact vhost match rather than the 
standard substring match. See patch below. If you have vhost names which are 
substrings of each other, you will need to use 2 and you will also need to change 
listinfo.py similarly to admin.py.)

3. Apply the patch below to admin.py. This copies some vhost-discrimination code from 
listinfo.py to admin.py. It works for 2.0.9 and above (I haven't tried it on older 
versions.)

4. For each list, change the web_page_url to point to the virtual host. This is the 
bottom-most parameter on the main admin page for each list. You may need to wait some 
time for the DNS records of the new vhosts to propagate before people can access the 
pages.

- Bob

Patch follows

*** admin.py.ORIG   Thu May  9 12:24:58 2002
--- admin.pyThu May  9 12:32:06 2002
***
*** 25,30 
--- 25,31 
  import types
  import rfc822
  import signal
+ from urlparse import urlparse

  from Mailman import Utils
  from Mailman import MailList
***
*** 200,205 
--- 201,229 
  for n in names:
l = MailList.MailList(n, lock=0)
  if l.advertised:
+ # Following cloned from listinfo.py - BW 5/9/02
+   # XXX We need a portable way to determine the host by which we are being
+   # visited!  An absolute URL would do...
+   http_host = os.environ.get('HTTP_HOST', os.environ.get('SERVER_NAME'))
+   port = os.environ.get('SERVER_PORT')
+   # strip off the port if there is one
+   if port and http_host[-len(port)-1:] == ':'+port:
+   http_host = http_host[:-len(port)-1]
+   if mm_cfg.VIRTUAL_HOST_OVERVIEW:
+ if mm_cfg.VIRTUAL_HOST_OVERVIEW == 2: # Want an exact match
+ # extract the host part of the url
+ host_part = urlparse(l.web_page_url)[1]
+ # remove the port, if any
+ host_part = string.split(host_part, ":")[0]
+ if http_host and host_part != http_host:
+ # List is for different vhost - skip it.
+ continue
+ else: # Want a simple containment match
+ if http_host and \
+ string.find(http_host, l.web_page_url) == -1 and \
+ string.find(l.web_page_url, http_host) == -1:
+   # List is for different identity of this host - skip it.
+   continue
  advertised.append(l)

  if error:



--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py

Re: [Mailman-Users] Mailman question

[Bob Weissman]

At 10:16 AM 5/18/02, Jon Heath wrote:
>I am a little confused on how to set up a read only mailing list.
>I would like my subscribe page to look like the options on this one:
>http://mail.python.org/mailman/listinfo/mailman-announce
>but currently it looks like this one:
>http://www.nutmegged.net/mailman/listinfo/nutmegged_nutmegged.net
>
>How do I get rid of the option "To post a message to all the list members,
>send email to Nutmegged@nutmegged. " in admin?...

You will have to hand-edit the list's copy of listinfo.html. You can do this from the 
web interface ("Edit the HTML for the public list pages") or from the shell using your 
favorite editor.

Warning: the indentation in this file is not always indicative of the actual HTML 
structure. Kind of strange, coming from a Python programmer. :-) Does anyone know of a 
pretty-printer which can reformat the indentation of an HTML file?

- Bob



--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py

Patch to suppress List-* headers on a per-list basis (was Re: [Mailman-Users] Help )

[Bob Weissman]

At 12:08 AM 5/14/02, J C Lawrence wrote:
>> There should be options in the admin interface to handle all of this.
>
>Thankyou for your excellent analysis.  When can we expect your patch to
>add these features?
>
>> The 'fix' you offer me for this question is not a fix at all.
>
>Ahh.  When can we expect your patch to do it properly?

I have a patch for 2.0.10 which allows list owners to set, on a per-list basis, 
whether the List-* headers are added to each posting. I need this for the same reason 
as the Aerosmith guy, namely because I have several outgoing-only "newsletter" lists 
which I don't want users trying to self-administer.

(It took me all of a half hour to figure out how to write this patch, by the way, and 
I didn't even know Python when I started. I congratulate the Mailman authors on making 
the software flexible enough to add a new attribute to mlists, generate the adin GUI 
for same automagically, and make retrofitting existing lists a simple matter of using 
withlist.)

Anyway, the FAQ says this particular modification is frowned upon, so I didn't submit 
it. If people want it, I can package it up and document it. I imagine that others have 
also implemented this, as it's a pretty obvious change to CookHeaders.py and 
MailList.py. Should I submit mine? If so, where should I send it?

- Bob



--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py

Re: [Mailman-Users] New user question

[Bob Weissman]

At 09:55 AM 5/13/02, Bob Weissman wrote:
>At 09:42 PM 5/12/02, Marc MERLIN wrote:
>>On Sun, May 12, 2002 at 09:50:44AM -0700, Bob Weissman wrote:
>>> I hope  I'm reading  this right; may  I infer that  these headers  will be
>>> supressable on a per-list basis?
>> 
>>Nope, site-wide only.
>>Barry already  knows that mailman  3 will  probably need a  toggle redesign,
>>where  most options  will  be  sitewide, listwide  and  even per-user  where
>>possible
>
>Too bad. If I wanted to implement this myself in 2.0.10, by adding a new attribute to 
>mailing lists, is there any way to cause the new attribute to be added to existing 
>mailing lists? Or must I rmlist/newlist all of my existing lists to cause them to 
>contain the new attribute?

Never mind. I figured out how to do it with withlist.

- Bob



--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py

Re: [Mailman-Users] New user question

[Bob Weissman]

At 09:42 PM 5/12/02, Marc MERLIN wrote:
>On Sun, May 12, 2002 at 09:50:44AM -0700, Bob Weissman wrote:
>> I hope  I'm reading  this right; may  I infer that  these headers  will be
>> supressable on a per-list basis?
> 
>Nope, site-wide only.
>Barry already  knows that mailman  3 will  probably need a  toggle redesign,
>where  most options  will  be  sitewide, listwide  and  even per-user  where
>possible

Too bad. If I wanted to implement this myself in 2.0.10, by adding a new attribute to 
mailing lists, is there any way to cause the new attribute to be added to existing 
mailing lists? Or must I rmlist/newlist all of my existing lists to cause them to 
contain the new attribute?

Thanks,
- Bob



--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py

Re: [Mailman-Users] New user question

[Bob Weissman]

At 07:35 PM 5/11/02, Barry A. Warsaw wrote:
>   AcLA> On top of that all those damn extra headers that
>AcLA> are added to each email are a total pain.  If you (whoever
>AcLA> you are) would make it so that each list could be configured
>AcLA> the way he list master wants rather than force certain
>AcLA> methodologies on us would greatly be appreciated.
>
>I guess I'm now "whoever you are". :)  Some people hate the headers,
>others see them as the standards-compliant way to improve the user's
>experience.  But with your site admin's approval, you will be able to
>suppress these headers in MM2.1.
>
>-Barry

I hope I'm reading this right; may I infer that these headers will be supressable on a 
per-list basis?

I run a number of lists for a non-profit professional organization with over 1000 
members. Most of the lists are standard Mailman lists, meaning subscribers can 
self-administer them; the List-* headers are fine for these.

But some of the lists are regenerated monthly from the membership database (I do 
sync_members manually every month on these). Subscribers cannot self-administer these 
lists, and I would just as soon not give them pointers to features which will not work.

Thanks,
- Bob



--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py