Mailman 3 March 1999 - Mailman-Users

I seek engineering judgment.
by Cameron Laird 26 Mar '99

26 Mar '99

I've done no programming with Mailman. I have a question whose answer is, I suspect, uncontroversial and well-known. I don't know it, though, and don't find it in very quick sweeps through the archives or documents. I'd be happy to have someone just tell me it's already been done, and point me to a reference. The question is this: what's a good place to intercept postings? I want to feed all Mailman traffic--that is, all postings to any of the Mailman-managed lists on my host, but not administrative requests--through an external process (while still having all the usual e-mail deliveries, archiving, ... proceed as always). Where can I best do this? There are lots of choices; I could slide into the "/usr/local/mailman/mail/wrapper post ..." branch, or several places deeper. By "good", I think what I most want is a place that's very loosely coupled with Mailman. Ideally, I could overlay a new release of Mailman, and keep all my functionality either with no change, or a one-liner.

3 2

Re: [Mailman-Users] I seek engineering judgment.
by bruce＠perens.com 26 Mar '99

26 Mar '99

I have an entire virtual domain "lists.hams.com" go to mailman through a script I wrote. That particular script would work as a single-point for filtering on my system, but It depends on using a virtual domain and having Qmail as the MDA. Thanks Bruce

1 0

Re: [Mailman-Users] I seek engineering judgment.
by Cameron Laird 26 Mar '99

26 Mar '99

From bruce(a)perens.com Thu Mar 25 19:53:41 1999 . . . Why not at the point of entry? Intercept mail to listname@hostname with an alias that pipes the mail to your program. Once you finish processing it, execute "~mailman/mail/wrapper post listname" to feed the posting to mailman. Thanks Bruce I have several responses. First, I suspect I wasn't clear in what I wrote before. Imagine I'm on a particular host. So far, I've set up mailing list subject1 subject2 subject3 I want to intercept *all* the Mailman-mediated traffic, so I understand your suggestion to be that I set up three aliases that catch traffic to each of <subject[123]@myhost>. Moreover, I want to automate this, so when someone creates mailing lists subject4 subject5 their traffic also is processed. Automating all that through creation of more aliases--well, that looks like more involve- ment than I imagined. More likely, I think, is that I instruct the MDA to do this. Procmail rules, for example, are supple enough that I can imagine managing them so as to take care of this. Is that what you were describing? That's probably what I'll do, unless someone tells me a good place to shim this into Mailman.

1 0

Re: [Mailman-Users] I seek engineering judgment.
by bruce＠perens.com 26 Mar '99

26 Mar '99

Why not at the point of entry? Intercept mail to listname@hostname with an alias that pipes the mail to your program. Once you finish processing it, execute "~mailman/mail/wrapper post listname" to feed the posting to mailman. Thanks Bruce

1 0

Re: [Mailman-Users] Mailman 1.0b9, password requirement.
by Alan Neiman 25 Mar '99

25 Mar '99

I think #2, or #3 would be great!!! how long do you think it would take? alan > Date: Thu, 25 Mar 1999 17:02:48 +0000 > From: Clark Evans <clark.evans(a)manhattanproject.com> > X-Accept-Language: en > MIME-Version: 1.0 > To: "Barry A. Warsaw" <bwarsaw(a)cnri.reston.va.us> > CC: Dave Sill <de5(a)sws5.ctd.ornl.gov>, mailman-users(a)python.org > Subject: Re: [Mailman-Users] Mailman 1.0b9, password requirement. > Content-Transfer-Encoding: 7bit > X-Mailman-Version: 1.0b9+ > List-Id: Mailman mailing list management users <mailman-users.python.org> > X-BeenThere: mailman-users(a)python.org > > This sounds wonderful, #2 sounds like a nice > compromise! Having the user confirm an unsubscribe > request is a very reasonable thing to do. If they > have to confirm to subscribe, it is a 'reasonable' > that they would expect to confirm an unsubscribe. > > I'm not sure if #3 is necessary, but I'm certain > that #2 would be sufficient to cover my needs. > > Perhaps one more? > > 4. A way to unsubscribe from all of the lists for > a given domain. > > Aka, the majordomo: "unsubscribe * me(a)domain.com" > > Thank you very much for your thoughtful > proposition. It's great. Mailman rocks! > > Best, > > :) Clark Evans > > "Barry A. Warsaw" wrote: > > > > Password-less unsubscribes have been thrashed about a lot. I think > > the general concensus was that we should support the following > > list-wide options: > > > > 1. current situation -- password is required to unsub (yes you can do > > this via email) > > > > 2. confirmation before unsub -- much like subscribing via the web. > > you just need to hit reply. > > > > 3. confirmation after unsub -- don't require password or pre-unsub > > confirm, just remove the addr but send an informational message > > telling them what just happened (in the very rare case of malicious > > unsub). > > > > Does this sound like it would cover what everybody wants? > > > > I seriously doubt this will make it in before 1.0. > > -Barry > > > > ------------------------------------------------------ > > Mailman-Users maillist - Mailman-Users(a)python.org > > http://www.python.org/mailman/listinfo/mailman-users > > ------------------------------------------------------ > Mailman-Users maillist - Mailman-Users(a)python.org > http://www.python.org/mailman/listinfo/mailman-users > Alan Neiman alan.neiman(a)ihs.com Unix System Administrator Information Handling Services -------------------------------------------------------------- ** 1997 & 1998 World Champions ** 17 & 2 -- Simply The Best -- The Broncos -- The Denver Broncos ** 1997 & 1998 World Champions ** --------------------------------------------------------------

1 0

Non-web interface?
by Steve Dinn 25 Mar '99

25 Mar '99

Hey, I'm brand new to mailman, and this may be a very obvious question, but here goes: Is there a way to manage a maliing list without using the web-based administration portion? In particular, I have a few messages sent to my list that came to me for approval or rejection. The message gives me a URL to go to. Unfortuneatly, I don't run a web server on that box. Is there a way to approve or deny a post by using a command line utility? Thanks. -- Steve Dinn email: mailto:sdinn@spine.cx www: http://users.andara.com/~sdinn "UNIX *is* user friendly...It's just selective about who its friends are."

1 0

Weird Configuration Error
by John Rizzo 25 Mar '99

25 Mar '99

Hi guys.. I was wondering if someone could help me out with this error. Ok I recently had a disk failure but I was able to tar the mailman directory on the bad disk. I then reinstalled mailman 1.0b8 and copied all the things I thought needed to be copied. I copied the directories in /var/lib/mailman/lists and the /var/lib/mailman/archives. I then created a test list and attepted to use that. It works.. But the lists that I copied do not work. I don't see any other problems with the list, ie I can edit the config stuff for each list in the web interface. Just to make sure I did the simple things. 1. yes I recreated the /etc/aliases file 2. I am using smrsh and I did create a link from /var/lib/mailman/mail/wrapper to /usr/adm/sm.bin 3. I did re-edit the /var/lib/mailman/Mailman/mm_cfg.py and /var/lib/mailman/Mailman/Defaults.py One thing do I have to worry about group privleges or something like that and if so what? Here is the error I get when I send email to the old lists. ----- The following addresses had permanent fatal errors ----- "|/usr/adm/sm.bin/wrapper post acminfo" (expanded from: <acminfo(a)acm.njit.edu>) ----- Transcript of session follows ----- Traceback (innermost last): File "/var/lib/mailman/scripts/post", line 65, in ? current_list.Post(msg) File "/usr/lib/mailman/Mailman/MailList.py", line 1042, in Post self.AddRequest('post', Utils.SnarfMessage(msg), File "/usr/lib/mailman/Mailman/ListAdmin.py", line 45, in AddRequest self.Save() File "/usr/lib/mailman/Mailman/MailList.py", line 683, in Save file = aside_new(fname, fname_last, reopen=1) File "/usr/lib/mailman/Mailman/MailList.py", line 1209, in aside_new os.unlink(new_name) os.error: (13, 'Permission denied') 554 "|/usr/adm/sm.bin/wrapper post acminfo"... unknown mailer error 1 the actual message then follows. John Rizzo Work Email: jrizzo(a)iconnet.net NJIT A.C.M. President Personal Email: follower(a)acm.njit.edu Qwest Internet Solutions Pager: jrizzo.pager(a)qwest.com

1 0

Importing into archives
by Terry Grace 25 Mar '99

25 Mar '99

When trying to import text files into a list archive using the command "./arch test-list /home/tgrace/ntlist/test-list/LL990312.LOG", I get: Pickling archive state into /home/mailman/archives/private/test-list/pipermail.pck LL990312.LOG contains only a single e-mail message (including smtp headers) with no special formatting or special characters. Nothing gets entered into the archives. Anyone have any ideas on how to correct?

1 0

help
by Jose Travieso 25 Mar '99

25 Mar '99

Ive looked thru the web interface options and have not seen any options for what i need done. I need to make the list send an email message like this: Example: "TO: someone(a)someplace.com FROM: mylist@listhost..com To make the e-mail message look like if it was specifically written for them. Not like: Example: "TO: mylist(a)listhost.com FROM: mylist(a)listhost.com" I dont know much python but if someone knows which file or files i will need to tweak please tell me. Thanks

1 0

Re: [Mailman-Users] RFC for List Message Header Fields
by J C Lawrence 25 Mar '99

25 Mar '99

On Wed, 24 Mar 1999 12:08:57 -0500 (EST) Darren Henderson<darren(a)jasper.somtel.com> wrote: > Email is not the web the web is not email. I don't like bluring the > distinction. URL != web. > It assumes a lot about about users and the state of the world. It > may lead people to think that embeding html in email is a good > thing. This seems rather a stretch. > While a lot of people use netscape etc to do mail a lot of people > don't. Yes, the latest versions of pine have the capability of > dealing with urls but the older ones don't and a lot of sites aren't > upgrading. > Most people see their mail with a limited number of headers, these > won't be visible to them. Yes they can look at the other headers but > most don't know too. Eventually mua's could be altered to display > those paticular headers by default as it stands currently I don't > think any of them do. My interpretation of this: Users of older software won't see and therefore won't use the new headers. This seems no loss. Users of older software who do know how to see those headers won't know what to do with them. These are the same people who are confused by bounces messages -- hardly a critical public. Users of newer software that either presents, of provides easy access to the functionality indicated by the new headers will gain something useful. This seems something worthy, especially in encouraging the development of MUA's. > No earth shattering reasons really. Mostly personal preference I > guess. Me? I mostly don't care. However it is a checkbox item and I'm quite certain that somebody does care, and will care that they are able to turn that feature on or off. That seems worth noticing. -- J C Lawrence Internet: claw(a)kanga.nu ----------(*) Internet: coder(a)kanga.nu ...Honorary Member of Clan McFud -- Teamer's Avenging Monolith...

1 0