Mailman 3 February 2000 - Mailman-Users

Re: [Mailman-Users] Rejects no longer email
by J C Lawrence 12 Feb '00

12 Feb '00

On Sat, 12 Feb 2000 17:24:16 -0800 Marc Merlin <marc_news(a)valinux.com> wrote: > On sam, fév 12, 2000 at 05:19:42 -0800, J C Lawrence wrote: >> The list functions perfectly as far as I can tell, with one >> exception: When I reject a message from the moderation interface >> nothing gets emailed to the poster. > I've also seen that on mailman 1.0rcsomething Of course, each time > I tried to reproduce it, I got the reject just fine. I recall on account of this problem previously on the list. It is repproduceable for me for the one list. All the other lists on the system handle rejects just fine. Its just the one list that goofs on rejects. >> Does anybody have a script hacked up to migrate the membership of >> one list to another along with their configs? > Mmmh, do you want to rename the list or move it to another mailman > install? If #1, rename the fields you can through the web form as > well as the file and directory names, and then use move_list from > mm1.2 cvs If you move the list to another mailman install, if the > pathnames are the same, you're in business, otherwise you have to > run move_list for mailman to fix the pathnames in config.db No. I suspect that something in <listname/config.db is corrupt, so I'd like to migrate all the contents of the current list's config.db to another list (membership and customisations), delete the current list and then rename the new list to the old name. Or something like that -- an attempt to get a correct config.db. -- J C Lawrence Home: claw(a)kanga.nu ----------(*) Other: coder(a)kanga.nu --=| A man is as sane as he is dangerous to his environment |=--

2 1

Rejects no longer email
by J C Lawrence 12 Feb '00

12 Feb '00

I've hit a most curious case: The list functions perfectly as far as I can tell, with one exception: When I reject a message from the moderation interface nothing gets emailed to the poster. No entries are made in any of the MailMan logs, no connections are made to the local MTA, and check_perms reports that everything ist just fine. Quite anooying. Does anybody have a script hacked up to migrate the membership of one list to another along with their configs? -- J C Lawrence Home: claw(a)kanga.nu ----------(*) Other: coder(a)kanga.nu --=| A man is as sane as he is dangerous to his environment |=--

2 1

Re: [Mailman-Users] DEFAULT_HOST_NAME change
by berto＠gsbrgo.uchicago.edu 11 Feb '00

11 Feb '00

Date: Fri, 11 Feb 2000 14:36:13 -0800 From: Marc Merlin <marc_news(a)valinux.com> On ven, fév 11, 2000 at 09:19:00 -0600, berto(a)gsbrgo.uchicago.edu wrote: > > We have a working Mailman 1.0 installation on a machine named > > xyz.uppity.edu > > We want to move our installation to a machine named > > xyzpop.uppity.edu > > ... > > As an experiment, I wrote a simple Perl filter. All it does is substitute > the string > > xyzpop.uppity.edu > > for the string > > xyz.uppity.edu > > in the test list's config.db file. You can't do that. If you binary patch, you need to replace with a string of the exact same length. If you don't, it renders the file unusable. The hostname has to be changed through the web interface, or with the help of the config_list script that is in mailman cvs (pre-1.2) If you rename a list, you need to use move_list, which also is in cvs Marc: Operating under the principle that "If It Ain't Broke, Don't Fix It," also time constraints that forbid us from doing everything we'd like, we remain using Mailman 1.0. (We'll upgrade eventually.) Is the config_list script simple enough, and have the underlying data structures remained unchanged, so that we could apply the config_list script to a 1.0 installation? Also, is the CVS repository open to public access? How would I do a checkout? Bob ------------------------------------------------------------------------------- Robert Osterlund, Unix Systems Manager berto(a)gsbrgo.uchicago.edu Grad School of Business, U of Chicago phone: 773/702-8898 1101 E. 58th Street, #309, Chicago, IL 60637, USA fax: 773/702-0233

2 1

Using mailman with https
by Marc Merlin 11 Feb '00

11 Feb '00

In order to have internal lists and archives available to a certain class of users, I am now running mailman under apache-ssl. I thought for a while that everything was fine, until I realized that all the post forms are broken because they reference http://server/ instead of https://server/ Changing DEFAULT_URL in mm_cfg.py doesn't help since it's apparently only used for the default value during new list creations. Where do I patch mailman to go to https intead of http? Thanks, Marc -- Microsoft is to software what McDonalds is to gourmet cooking Home page: http://marc.merlins.org/ (friendly to non IE browsers) Finger marc_f(a)merlins.org for PGP key and other contact information

2 2

Admin functions only
by Andre Giordano 11 Feb '00

11 Feb '00

Is there a way to make mailman not make a public listing where people can add themselves to a mailing list. I went the mailing list to be administered by one person. Anybody tried this ? -- Sincerely, André Giordano Bell Nexxia Inc. Email: giordano(a)on.aibn.com

1 0

DEFAULT_HOST_NAME change
by berto＠gsbrgo.uchicago.edu 11 Feb '00

11 Feb '00

Folks: We have a working Mailman 1.0 installation on a machine named xyz.uppity.edu We want to move our installation to a machine named xyzpop.uppity.edu (Actually, the system's hostname is 'xyzpop'. 'xyz' is an alias for 'xyzpop'. We have to set up a new machine with hostname 'xyz' that will be our new Web server. By means of mx records, we will be redirecting mail traffic from the new 'xyz' to 'xyzpop'.) As an experiment, I wrote a simple Perl filter. All it does is substitute the string xyzpop.uppity.edu for the string xyz.uppity.edu in the test list's config.db file. Now, when I try to access the list, Mailman gives the complaint raceback (innermost last): File "/opt/mailman/scripts/driver", line 112, in run_main main() File "/opt/mailman/Mailman/Cgi/admin.py", line 65, in main lst = MailList.MailList(list_name) File "/opt/mailman/Mailman/MailList.py", line 61, in __init__ self.Load() File "/opt/mailman/Mailman/MailList.py", line 809, in Load raise Errors.MMBadListError, ('Failed to unmarshal config info: ' TypeError: __add__ nor __radd__ defined for these operands The code in MailList.py reads: try: dict = marshal.load(file) if type(dict) <> DictType: raise Errors.MMBadListError, \ 'Unmarshaled config info is not a dictionary' except (EOFError, ValueError, TypeError), e: raise Errors.MMBadListError, ('Failed to unmarshal config info: ' I seem to be experiencing some sort of EOF error. I verified (through a 'wc -c' and 'ls -l') that the replacement config.db is exactly 9 bytes longer than the original config.db: the added 'pop' times three, for the three times that 'xyz.uppity.edu' appears in the source config.db. So I don't think the Perl filter added any extraneous characters, or subtracted anything, beyond the desired substitution. As an experiment, I tried editing the original config.db with Emacs. Same result. So, is my naive strategy for doing this translation doomed? Will we be forced to set up an entirely new installation as 'xyzpop.uppity.edu', and subject our 350+ list owners, not to mention our thousands upon thousands of list members, the agony of starting again from scratch? Please tell me it ain't so! Bob Osterlund ------------------------------------------------------------------------------- Robert Osterlund, Unix Systems Manager berto(a)gsbrgo.uchicago.edu Grad School of Business, U of Chicago phone: 773/702-8898 1101 E. 58th Street, #309, Chicago, IL 60637, USA fax: 773/702-0233

2 1

config problems
by Michael Boudreau 11 Feb '00

11 Feb '00

To follow up on my previous message, although the HTML for the list info pages seems to ignore some configuration options (like whether digests are possible, or archives are kept), it appears that *almost* all the list-specific HTML can be edited (one exception: the text beginning "To change your subscription" near the end of the List Info page seems to be globally set). However, the text of the email message welcoming new members comes from a global template, so I can't edit that for a specific list. Make that a feature request. I'm still having the problem that in the welcome message, my subscription page URL is given in the form http://server.org/mailman/options.cgi/listname/mboudreau@journals.uchicago.… but this URL generates an "Error 400: Bad syntax in URI" message from my web server (WN 2.2.2). If I change the URL, substituting "__at__" for "@", it works. I also notice that the URL with "@" seems to work properly with the mailman-users list, though. Any idea what's going on? ================================================= Michael Boudreau Electronic Publishing Developer University of Chicago Press, Journals Division email: mboudreau(a)journals.uchicago.edu phone: 773 753 3298 fax: 773 753 0827 =================================================

1 0

Tutorial for mailman for newbie list-admins?
by Demian Hanks 11 Feb '00

11 Feb '00

Hello All, I have set up new listserver using mailman, and I'm beginning to make it available to users throught our college. Part of my initial motivation for setting up mailman is the fact that I don't have to admin each of the lists. I am a little concerned about the ability of some of my list-admins to use the "best" configurations regarding bounce options, privacy protection, and other configs. So I asked one of our web guys to setup a tutorial of sorts as a resource for these list-admins and I wanted to get some feedback from other people that might be in the same position. Mostly I am interested in making sure that one lists configuration will not adversly affect the other lists. There is a link for the tutorial at http://lists.csbs.utah.edu I also plan on makeing the mailman-faq, list archive and docs available. I would appreciate any suggestions for additions/changes. I'd also like to know if it is possible to lock some configurations like "require confirmation" for all lists on the server, maybe via a cron script that checks the settings once a day, or deep within the mystic of mailman's code. Thanks, Demian Hanks CSBS Network Admin.

1 0

configuration problems
by Michael Boudreau 11 Feb '00

11 Feb '00

I'm setting up a new list with Mailman v1.1 and finding some configuration items either not working or not configurable. - I have selected "No" for "Send monthly password reminders", but the welcome message I got when I joined the list after setting it up still said I would receive a monthly reminder. - I have selected "Yes" for "Show member addrs so they're not directly recognizable as email addrs", but the URL for the subscription page in my welcome message included the "@" sign in my email address, instead of "__at__". Are the email messages from the list configurable as the HTML pages are? - I have selected "No" for "Can list members choose to receive list traffic bunched in daily digests", but the list info page still offers this option (with the "No" and "Yes" labels, minus the radio buttons) Have other people experienced these problems? Are there known workarounds? (I found nothing in the archives about editing the email messages.) ================================================= Michael Boudreau Electronic Publishing Developer University of Chicago Press, Journals Division email: mboudreau(a)journals.uchicago.edu phone: 773 753 3298 fax: 773 753 0827 =================================================

1 0

Incorrect address reported in 'message held' notice to moderator
by Mark Martinec 11 Feb '00

11 Feb '00

Using Mailman 1.1 and Python 1.5.2. The message received by the administrator of the list about a message being held for approval is misleading and not useful: | Subject: Test post approval required for cyrustest(a)ijs.si | | Your authorization is required for a mailing list posting request | approval: | | List: Test(a)ijs.si | Reason held: Moderated list | From: cyrustest(a)ijs.si => ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ I have 'USE_ENVELOPE_SENDER = 1' which works much better for me than relying on broken 'Sender' headers. The reported 'From: cyrustest(a)ijs.si' address is neither the 'From:' field of the post (as the name might suggest) nor the sender address from its envelope header (which would be more logical having set USE_ENVELOPE_SENDER=1), but is the irrelevant contents of the 'Sender:' field. The message should either say 'Sender: cyrustest(a)ijs.si' which would be correct but unimportant, or it should report either the Sender or the envelope sender address based on the value of variable USE_ENVELOPE_SENDER, since this it the only address that really matters (it decides whether the message is passed or held for approval). The incorrect reported address makes it difficult to see the reason why the posting was being held. Regards Mark -- !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !! Mark Martinec (system manager) tel +386 61 177-3575 !! !! J. Stefan Institute, Jamova 39 fax +386 61 219-385 !! !! SI-1000 Ljubljana, Slovenia mark.martinec(a)ijs.si !! !!!!!!!!!!!!!!!!!!!!!!!!!! http://www.ijs.si/people/mark/ !!!!

1 0