Mailman 3 January 1999 - Mailman-Developers

Re: [Mailman-Developers] Two patches
by Hermann Benedek 18 Jan '99

18 Jan '99

>BUT... Did you try to enter an accented string to a WWW admin page? For >example '=E1ltal=E1nos' (=3D=3D general in Hungarian). It will say >'\341ltal\341nos' next time. If you press a simple OK, you'll see >'\\341ltal\\341nos' next time. This is due to string parsing in Python and I used only english characters (non-accented) in the email-messages. Not too good, but works with all system. I tried to write a 'MIME' line to the header, but I don't know how to do it in the MailCommandhandler.py. Is there a function that writes a string to the header, and can be used from MailCommandhandler? Web-admin page: I have the problem too. It works good until you change the page next time. Regards, Bence

1 0

Two patches
by Hermann Benedek 18 Jan '99

18 Jan '99

I wrote two patches: -sendcommand: it creates two new command. The 'filelist' command sends the list of documents located in the $listdir/documents directory (filenames beginning with a '.' aren't included). The 'send filename' command sends a document to the user via email. This is only a quick code, because I needed it, please comment (I used the another parts of the code, because I'm not perfect in python...) (patch-sendcommand) -hungarian patch: perhaps this is useful for hungarian users. It includes the hungarian version of most of the files in the templates/ directory, and the hungarian version of the e-mail-messages (confirmation, welcome, request etc.) (patch-mailmanhu-1.0b8) Location: ftp://ftp.kma.bme.hu/pub/bence/mailman Regards: Bence

2 1

My new patches
by Balazs Nagy 15 Jan '99

15 Jan '99

Hiyas, I have fixed some bugs in my MTA package and fitted to the latest CVS snapshot. You can download'em from http://www.kva.hu/~mailman/mailman-patches-19910115.tar.bz2 or http://www.kva.hu/~mailman/mailman-patches-19910115.tgz These patches apply 1 - a little code fix for the 'set' email command 2 - CGI extension handling 3 - Usage of Message Transfer Unit (sendmail and others) instead of SMTP (but uses SMTP if MTU sending doesn't work) Download it, apply it, use it, collect it! Send bugs to me, success stories to the list. Regards: Balazs -- #!/bin/perl -sp0777i<X+d*lMLa^*lN%0]dsXx++lMlN/dsM0<j]dsj $/=unpack('H*',$_);$_=`echo 16dio\U$k"SK$/SM$n\EsN0p[lN*1 lK[d2%Sa2/d0$^Ixp"|dc`;s/\W//g;$_=pack('H*',/((..)*)$/)

1 0

[ANNOUNCE] Mailman 1.0b8
by Barry A. Warsaw 14 Jan '99

14 Jan '99

While there are still a few outstanding problems reported by users, I think we've nailed enough bugs since 1.0b7 to warrant a new release, so I'm announcing 1.0b8 tonight. As usual, feel free to pick it up from www.list.org. I think we're getting really close. I'm hoping my last minute changes didn't bust anything, and I'm also hoping we can nail down the last few showstoppers people have reported (in particular the archiving problems). I also want to get Scott's envelope-sender change backed out. Please give 1.0b8 a shot and let us know if you have any problems. Feel free to continue to send ideas and suggestions. I'm in conservative mode now though -- let's get 1.0 out so we can start working on some of those cool ideas. Thanks, -Barry

1 0

Re: [Mailman-Users] Wierd Mailman problem
by Barry A. Warsaw 14 Jan '99

14 Jan '99

>>>>> "GH" == George Hartz <georgeh(a)blowtorch.com> writes: GH> The web interface seems to work okay, although I don't get GH> anything in the archives. Should clicking on the archives link GH> work before any messages have been posted to the list? No, that's a buglet. The archive link is not functional until at least one message has been posted to the list. GH> Anyway the problem I seem to be having is that Mailman is GH> failing without any errors at all. User and group ID's seem to GH> be set correctly. The wrapper programs aren't logging any GH> errors for bad UID's. (And running the programs as an GH> incorrect user *does* log them, so I know the logging itself GH> works. I'm sure you know that if the error occurs because of a gid mismatch, in either the CGI wrapper or the mail wrapper, errors are only logged to syslog, not to $prefix/logs/error. For mail, you ought to also get a bounce containing the error message, and for CGI -- with the next version -- you will get a more useful Web diagnostic page. Once control has been passed to the Python world (e.g. the `driver' script for CGI, or `post' for mail), then errors get logged to Mailman's log files. Note that a misconfiguration of syslog or your mail system might mean that those pre-Python errors are getting lost. [This is probably more useful to mailman-developers] Once you're in the Python world, there are several ways to log error messages for debugging. My favorite is, once I have a MailList object, I like to call the LogMsg() method with kind=='debug', kind of like so: mlistobj.LogMsg('debug', 'I got to here: %s', 'foo method') This will timestamp the message, and write it to $prefix/errors/debug. -Barry

2 2

BUG: virtual hosting (was Re: [Mailman-Users] Bug in b7?)
by Greg Stein 13 Jan '99

13 Jan '99

Ken Manheimer wrote: > On Wed, 13 Jan 1999, Greg Stein wrote: > ... > > Could this be due to the "per-virtual host" list option? I don't recall > > exactly how/where you set that, but I've got it set on my mailman > > installation. Lists will only appear if the hostname in the URL matches > > the hostname listed in the configuration for the "URL root" or whatever it > > is called. > > Correct - jason, you might try adding the line: > > VIRTUAL_HOST_OVERVIEW = 0 > > to the end of Mailman/mm_cfg.py. > > By inhibiting VIRTUAL_HOST_OVERVIEW you set the overview pages to show > all the advertised hosts, not just the hosts which have a "preferred" > host name that's the same as the one by which people are getting to the > overview page. If it works, then you may want to check the setting for > DEFAULT_HOST_NAME, also in mm_cfg.py (or Defaults.py in the same dir, if > it was never overridden). You can also specify the preferred host name > on a per-list basis - it's one of the the options at the bottom of the > admin 'general options' page. Speaking of virtual hosts... BUG REPORT: When the automated, monthly reminder goes out, the text uses a host name that might not apply to all the mailing lists in the combined reminder(!). I got a number of emails on January 1 when people received their mailing list reminder for harleydavidson.com (I run a mailing list for that domain). People couldn't quite see how the Python2C Announcement list should be hosted on harleydavidson.com :-) The combined report is cool and all :-), but I would recommend that it only combines reports for lists on the same virtual host! thx -g -- Greg Stein, http://www.lyra.org/

2 1

Digests and Cron and Signals
by Greg Stein 13 Jan '99

13 Jan '99

[ responding from the archive, so this message will be formatted funny... ] ----INCLUDED MESSAGE---- I have upgraded mailman to the new release, 1.0b7, on my redhat 5 system. $ uname -a Linux jerrya 2.0.32 #4 Wed Jan 7 23:14:32 CST 1998 i486 unknown I still receive the following message every day when the digests go out. They are going out successfully, but this message still gets delivered. [snip of Cron Daemon traceback...] ----INCLUDED MESSAGE---- Actually, if you run MULTIPLE lists, then your mail is NOT being delivered. The traceback will occur on the FIRST mail list, preventing the rest from being delivered. I run into this EVERY day with mine and I patched my installation to ignore the error so that digests can go out for all lists. I put in a hack, though, to ignore it (similar to Barry's). I'm going to try Harald's signal patch (cool!) and report back on its success. If I stop getting my noon cron reports of failure, then we'll be golden. Note: mine is occuring on a RedHat 5.1 system. -g -- Greg Stein, http://www.lyra.org/

1 1

mailman FAQ?
by Ken Manheimer 12 Jan '99

12 Jan '99

I'm scrambling with a job change (possibly an exciting one for mailman, as well as for me), but have an idea i'd like to put out there, in the meanwhile. Barry, and harald, and others - thanks all! - have been answering some questions that are clearly coming up Frequently - seems like perfect fodder for the start of a mailman FAQ. Would anyone like to form such a thing? How about a mailman faq wizard, somewhere on list.org? Or maybe python.org? I won't have time to set it up - but it probably ought be... (The questions that i clearly see are setting of the mailman UID/GID, debugging it when it goes awry, and dealing with the archives stuff, particularly the slightly surprising fact that a public archive link is not created until the first posting, while the actual private-dir file already is there. While barry's recent checkin to make the UID/GID setting error message provide more info should go a long way to helping (and ought to be factored in to any explanation), it still may be worth answering OAFA - once and for all. Any other hidden items worth mentioning?) ken manheimer klm(a)python.org

2 1

error message from cron
by Gergely Madarasz 11 Jan '99

11 Jan '99

Hello, Since I upgraded to 1.0b7 I get a couple of these messages each day. Any ideas why ? Traceback (innermost last): File "/usr/lib/mailman/cron/run_queue", line 27, in ? OutgoingQueue.processQueue() File "/usr/lib/mailman/Mailman/OutgoingQueue.py", line 126, in processQueue Utils.TrySMTPDelivery(recip,sender,text,full_fname) File "/usr/lib/mailman/Mailman/Utils.py", line 217, in TrySMTPDelivery OutgoingQueue.dequeueMessage(queue_entry) File "/usr/lib/mailman/Mailman/OutgoingQueue.py", line 184, in dequeueMessage os.unlink(q_entry) os.error: (2, 'No such file or directory') Greg

3 2

colored columns in memberlist management table
by Peter Gervai 10 Jan '99

10 Jan '99

Would be quite easy to gray the background of even coloumns of the membership management table to make it easier to see which switch goes for what settings. And maybe the header at the end of the table wouldn't hurt as well. (My screen is maybe too small and the header gets scrolled off the screen when I go to the bottom of the memberlist.) bye, grin

1 0