Mailman 3 - Mailman-Users

Re: [Mailman-Users] Re: wishlist (was Re: [ANNOUNCE] Mailman 1.0b9)
by Per Starback 02 Mar '99

02 Mar '99

I wished for: > > * Add Mail-Followup-To header. (I've done that for myself, but > > I would appreciate not having to do it again, as well as I'd like > > to see more use of this useful although nonstandard header.) and Aaron Schrab wrote: > No! List servers should not be adding Mail-Followup-To headers, that's > something that needs to be done at the sender's end. Well, now Mailman supports inserting those infamous Reply-To headers pointing to the list which is infinitely more objectionable. I can see that a sender might want to set a certain Mail-Followup-To when posting to several mailing lists, for instance, just like you would use Followup-To in Usenet when posting to several groups. Of course that explicitly given header shouldn't be overwritten, but when Mail-Followup-To isn't set I don't see any problem with setting it to the list for a typical discussion list. Many lists inser Reply-To headers to "make it easy for their subscribers". We who refuse to do that think that is should be easy *both* to reply (personally) and to follow-up on a message, and that mail programs [should] have different commands for those things. But then a typical follow-up function of your mail program have to actually work, that is to send the follow-up to the list, without you having to edit the recipient list. I can see that you might still object to this, because header munging is inherently evil or because you have mailing lists which often get posts with other recipients as well (that are not on the list), but supporting this is better than pushing people into Reply-To munging at least. -- Per Starback <starback(a)ling.uu.se> <http://stp.ling.uu.se/~starback/me.html> "Life is but a gamble! Let flipism chart your ramble!" P.S. Not that it matters much anyway, as mailers typically don't know about Mail-Followup-To... P.P.S. More generally this would be possible with a general "add these headers to list mail" option, which maybe would be useful for other things as well, and easy to implement, I guess. (Like the "Header added to mail sent to regular list members"/"Header added to every digest" options, but inserting headers instead of text in the body.)

2 1

TypeError: read-only buffer ...
by Joseph Chin 02 Mar '99

02 Mar '99

hi folks, I have been using Mailman on Red Hat Linux 5.x system since b4 (just upgraded all systems to b9 today), and most things work as advertised. However, there is one problem that won't go away ... An application uses a Java SMTP applet to send notices via email. It works fine unless the recipient address is that of a Mailman list. The following is an excerpt from the bounced mail: ----- The following addresses had permanent fatal errors ----- |"/home/mailman/mail/wrapper post product-support" (expanded from: <support(a)somedomain.com>) ----- Transcript of session follows ----- Traceback (innermost last): File "/home/mailman/scripts/post", line 65, in ? current_list.Post(msg) File "/home/mailman/Mailman/MailList.py", line 1135, in Post sender = self.FindUser(msg.GetSender()) File "/home/mailman/Mailman/Message.py", line 122, in GetSender return string.lower(mail_address) TypeError: read-only buffer, None 554 |"/home/mailman/mail/wrapper post product-support"... unknown mailer error 1 The Mailman list in question works fine when using "normal" mail agents, such as Eudora, Outlook, direct SMTP conversation via telnet to port 25, etc. Any idea? Regards Joe

1 0

BUG REPORT: password lookup
by Brian Ryner 02 Mar '99

02 Mar '99

Ok, I tracked this one down I think. If a user is subscribed with capital letters in the email address using the Mass Subscribe feature, then they go to get their password mailed to them, it fails. This seems to be because when they enter their email address on the listinfo page (and click "edit options") it lowercases it, but the password is stored with an uppercased version of the email address. I see two solutions: - lowercase all emails when they are subscribed from the Mass Subscribe page - locate the correct email case-insensitively when you go to the Edit Options page I don't know enough Python to give you a patch but it doesn't sound too difficult for someone who does know it. Thanks -Brian Ryner bryner(a)uiuc.edu

1 0

GUI misfeature with textarea boxes
by Vivek Khera 02 Mar '99

02 Mar '99

I think that the use of WRAP=soft on the text boxes for things such as the trailer text and list descriptions should be removed. The reason is that carriage returns are significant in these fields and it is not possible to distinguish hard returns you type from the soft returns netscape inserts. The only way right now is to do a "view source" and see where the hard returns are. Simply removing the "WRAP=soft" from these textarea boxes will make it easier to detect these differences. v. -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Vivek Khera, Ph.D. Khera Communications, Inc. Internet: khera(a)kciLink.com Rockville, MD +1-301-545-6996 PGP & MIME spoken here http://www.kciLink.com/home/khera/

1 0

posting restrictions still confusing to me (or not working?)
by Vivek Khera 02 Mar '99

02 Mar '99

I've got a small list for which the following settings control who's allowed to post: Approve by administrator: no member_posting_only: yes list of additional accepted addresses: khera(a)kcilink.com Yet anyone who posts to the list gets deferred for admin approval with the error that they must be on the list to post, including myself. I'm running 1.0b9 (from CVS as of this morning.) It seems to matter little whether I list additional addresses -- if member_posting_only is yes, I *always* get a deferred message. v.

1 0

notes on my first big list message delivery
by Vivek Khera 02 Mar '99

02 Mar '99

Last nite, I sent out the first broadcast on one of my lists using Mailman. This list consists of about 7,000 customers. I set up the list to be moderated, and turned on auto-bounce processing (no notify), with a 1 message bounce threshhold. I populated the list from a text file from the old mailing list software. This took about 10 minutes using add_members. Then I sent the email. Immediately, as administrator, I started getting bounce notices in my inbox. Yuck! They seem to be getting processed most of the time, but why do I get copies of them? I'd just as soon let the list software track the bounces and leave me alone. I selected the 'Disable and DON'T notify me' option. I'd really like a 'Remove and DON'T notify me option, as well'. Just how do I tell if a regular user is "disabled" from the members listing? The check for admin emails to the main list and diverting them doesn't seem to work. A few "unsubscribe" messages popped through, and were put in the admin queue rather than actually processed. Is that what's supposed to happen? One thing I'd *really* find useful: a way to lookup users based on a substring. With 7,000+ users, it is laborious to click until I find an address. Overall, it went well. Now I just need to learn Python and start fixing things myself! ;-) v.

1 0

Text mode reporting tool, on number of users in a list
by Rob Thomson 02 Mar '99

02 Mar '99

Hi, I was wondering if anyone could help me out with this problem. I have recently converted my companys mailing list server from majordomo, to mailman. So far I am really impressed wirh the software, it has proveded every feature i have needed, bar one. What i need, is some way to query the system, (from the console) to report back the number of users in a list. It is posible to retrieve this info from the web page, however my supervisors would like the feature whereby they are mailed on a weekly basis, the number of users on each list that we run. Under Majordomo, this was easy, consideringt hat the user lists were just test files. however with the new database format, I am stumped. Does anyone out there know how I can get arround this.?? Rob Thomson

3 2

National fonts and letters
by Janos.Zana＠elfiz2.kee.hu 02 Mar '99

02 Mar '99

Most of Hungarian letters with diacritical symbols are available in mailman. We use the symbol set ISO-8859-2 which consits of two more letters: "o-doubleacute" and "u-doubleacute" (upper- and lowercase). When I wrote them in my pages the mailman converted them - e.g. the "o-doubleacute" was converted as o" (o and doublequote). Do anybody know if there is any possibility using my own national letters or font sets? János Zana -- my "a-acute" is not converted... - - - Good rest to all that keeps the Jungle Law! (Kipling) - - -

1 0

Re: [Mailman-Users] inserting mbox files?
by Corbett J. Klempay 01 Mar '99

01 Mar '99

At 08:22 PM 3/1/99 +0100, you wrote: >According to Corbett J. Klempay: >> the guy who previously ran the list has an mbox file of the last 100+ >> messages from when it was still under majordomo. Is there any way for me >> to have these archived? > >just run > arch <listname> <mboxfile> >as user mailman. arch is in mailman's bin directory. This is exactly what I tried on first guess...and I get this output: [mailman@chimera whs1996.mbox]$ /home/mailman/bin/arch whs1996 whs1996.mbox Pickling archive state into /home/mailman/archives/private/whs1996/pipermail.pck [mailman@chimera whs1996.mbox]$ But when I try to view the archives, I just see: The whs1996 Archives More info on this list... Currently, there are no archives. Any ideas? Is this something broken in b6? (which is what I'm running) CJK

2 1

Re: [Mailman-Users] [ANNOUNCE] Mailman 1.0b9
by Per Starback 01 Mar '99

01 Mar '99

Barry wrote: > But I'd like b10 to be the last beta. It's time to get 1.0 out the > door (I know I've said this before -- this time I mean it :-). That sounds good! As a very new user of Mailman I can say that the beta version number was one thing that made me hesitant about using Mailman when I recently looked around wondering what MLM I should switch to. (I'm finally leaving SmartList after several years.) > Enjoy, and let me know if I missed anything. It's always nice to have the NEWS file or something like that in announcements of new versions so you can decide if you want to upgrade without having to fetch and unpack the whole thing: # Differences between 1.0b8 and 1.0b9 # # - New bin scripts: clone_member, list_members, add_members (a # consolidation of convertlist and populate_new_list which have been # removed). # # - Two new readmes have been added: README.LINUX and README.QMAIL # # - New configure option --with-cgi-ext which can be used if your Web # server requires extensions on CGI scripts. The extension must # include a dot (e.g. --with-cgi-ext=".cgi"). # # - Many bug fixes, including the setgid problem that was causing mail # to be lost on some versions of Linux. Hm, --with-cgi-ext was in 1.0b8 too. At least it's mentioned in the INSTALL there, but I didn't use it. Wish list: * Add Mail-Followup-To header. (I've done that for myself, but I would appreciate not having to do it again, as well as I'd like to see more use of this useful although nonstandard header.) * Possibility for individual list members to say if they want a Subject line [tag] or not. That would mean that there would have to be two versions of each message, but I think that would be worth it as the [tag]/no tag preference is more about the preferences (and mail situation) of individual list members that about the preferences of the list itself or its maintainer. I would never add a tag like that on my lists per default, but if users who want it could get it explicitly that would be nice. * A line at the Membership Management page where you set default attributes for new users in the same way that you can change attributes for the existing users. This more general feature would be instead of the Which delivery mode is the default for new users? and When receiving digests, which format is default? questions on the Digest-member options page. I think I would like to set "hide" by default, and anyway I think it's better for the future to have one general way of setting the default instead of having to add new list options sometimes when new membership options are made. I'm sorry if my wish list consists of things that have been beaten to death here. Being a list manager myself I should know better than to jump in on a list without lurking for some time first. :-) -- Per Starback <starback(a)ling.uu.se> <http://stp.ling.uu.se/~starback/me.html> "Life is but a gamble! Let flipism chart your ramble!"

5 4