Mailman 3 October 2000 - Mailman-Users

Digest Mode separator
by stevefx＠us.ibm.com Oct. 20, 2000

Oct. 20, 2000

Greetings all, I received a request from a user that the separator for digest messages be made more distinguishable. He claims that with people quoting other's text frequently it makes it difficult to tell where messages start and stop. I searched the -developers and -users archives but didn't find any discussion of this topic. Is this something that would be considered? Steve Fox IBM Linux Technology Center http://oss.software.ibm.com/developerworks/opensource/linux http://stevefx.rchland.ibm.com (IBM Intranet)

1 0

/admin hanging
by Jeff Warnica Oct. 20, 2000

Oct. 20, 2000

With my upgrade to the most recent beta, /admin is hanging on one list.. I did a check_db on it, and its reported as fine, but manualy doing a add_members also hangs. This only is happenig with one of the lists. Any ideas? -- Jeff Warnica noc(a)w3intetnet.com Network Operations Manager W3 Internet Services Voice: (902) 425-2969 ext. 17 Fax: (902) 425-2822

2 2

New headers?
by Jeff Warnica Oct. 20, 2000

Oct. 20, 2000

Upgrading to beta6 has caused there to be some new headers included in outgoing messages, List-Post etc.. Is there a way to suppress these? -- Jeff Warnica noc(a)w3intetnet.com Network Operations Manager W3 Internet Services Voice: (902) 425-2969 ext. 17 Fax: (902) 425-2822

3 2

Error with Red Hat 7.0
by Stephanie Martinez Oct. 20, 2000

Oct. 20, 2000

I can't figure this one out. I had everything working fine under 6.2. I upgraded my system to 7.0 and I get the following error message when I try to approve a pending email: If you would like to help us identify the problem, please email a copy of this page to the webmaster for this site with a description of what happened. Thanks! Traceback: Traceback (innermost last): File "/home/mailman/scripts/driver", line 96, in run_main main() File "/home/mailman/Mailman/Cgi/admindb.py", line 97, in main mlist.Save() File "/home/mailman/Mailman/MailList.py", line 845, in Save self.SaveRequestsDb() File "/home/mailman/Mailman/ListAdmin.py", line 93, in SaveRequestsDb self.__closedb() File "/home/mailman/Mailman/ListAdmin.py", line 80, in __closedb fp = open(self.__filename, 'w') IOError: [Errno 13] Permission denied: '/home/mailman/lists/seventh-guides/request.db' -------------------------------------------------------------------------------- Python information: Variable Value sys.version 1.5.2 (#1, Aug 25 2000, 09:33:37) [GCC 2.96 20000731 (experimental)] sys.executable /usr/bin/python sys.prefix /usr sys.exec_prefix /usr sys.path /usr sys.platform linux-i386 -------------------------------------------------------------------------------- Environment variables: Variable Value DOCUMENT_ROOT /var/www/html SERVER_ADDR 24.27.56.244 HTTP_ACCEPT_ENCODING gzip, deflate SERVER_PORT 80 PATH_TRANSLATED /var/www/html/seventh-guides REMOTE_ADDR 143.166.99.177 HTTP_VIA 1.0 AUSINETPROXYBU8 HTTP_ACCEPT_LANGUAGE en-us GATEWAY_INTERFACE CGI/1.1 SERVER_NAME castle.hawkbane.net HTTP_CONNECTION Keep-Alive HTTP_USER_AGENT Mozilla/4.0 (compatible; MSIE 5.01; Windows NT 5.0) HTTP_ACCEPT image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, application/vnd.ms-powerpoint, application/vnd.ms-excel, application/msword, */* REQUEST_URI /mailman/admindb/seventh-guides PATH /sbin:/usr/sbin:/bin:/usr/bin:/usr/X11R6/bin QUERY_STRING SCRIPT_FILENAME /home/mailman/cgi-bin/admindb PATH_INFO /seventh-guides HTTP_HOST 24.27.56.244 REQUEST_METHOD GET SERVER_SIGNATURE Apache/1.3.12 Server at castle.hawkbane.net Port 80 SCRIPT_NAME /mailman/admindb SERVER_ADMIN root@localhost SERVER_SOFTWARE Apache/1.3.12 (Unix) (Red Hat/Linux) mod_ssl/2.6.6 OpenSSL/0.9.5a DAV/1.0.1 PHP/4.0.1pl2 mod_perl/1.24 PYTHONPATH /home/mailman HTTP_COOKIE seventh-guides:admin=2802000000695618ef39732800000037303339343735343063313437343031396330633230323935353830393962643238386230316435 SERVER_PROTOCOL HTTP/1.0 REMOTE_PORT 3201 HTTP_REFERER http://24.27.56.244/mailman/admin/seventh-guides/ I get simillar errors if I try to run bin/newlist, etc. Anyone know of a fix for this one? Stephanie

3 3

Re: [Mailman] Sending to multiple lists problem
by Nick Marouf Oct. 20, 2000

Oct. 20, 2000

"Barry A. Warsaw" wrote: > > >>>>> "NM" == Nick Marouf <marouf(a)earlham.edu> writes: > > NM> Hi all, I've sent out an email about this from before, and > NM> checked the bugs page, but with still the same problem. > > NM> When I send a message to more that one list, only one of them > NM> gets to the list. I have been trying to find patterns for > NM> this, with no luck. However I get the mailog for a msg ID and > NM> I get this back > > NM> -------------------- [root@yang qfiles]# grep VAA15050 > NM> /var/log/maillog Oct 11 21:44:08 yang sendmail[15050]: > NM> VAA15050: from=<marouf(a)earlham.edu>, size=576, class=0, > NM> pri=90576, nrcpts=3, msgid=<39E5252F.8B2CB1DD(a)earlham.edu>, > NM> proto=ESMTP, relay=IDENT:marouf@blackened.student.earlham.edu > NM> [159.28.163.72] Oct 11 21:44:08 yang sendmail[15051]: > NM> VAA15050: to="| /home/software/mailman/mail/wrapper post > NM> dusko-test" , delay=00:00:00, xdelay=00:00:00, mailer=prog, > NM> stat=Sent Oct 11 21:44:09 yang sendmail[15051]: VAA15050: > NM> to="| /home/software/mailman/mail/wrapper post tomstest" , > NM> delay=00:00:01, xdelay=00:00:01, mailer=prog, stat=Sent Oct 11 > NM> 21:44:09 yang sendmail[15051]: VAA15050: > NM> to="|/home/software/mailman/mail/wrapper post test", > NM> delay=00:00:01, xdelay=00:00:00, mailer=prog, stat=Sent > NM> [root@yang qfiles]# > > NM> ------------------------- > > NM> [root@yang qfiles]# grep VAA15050 * > NM> db87ce92166797b4fb87d4567287e6719aae35b9.msg: by earlham.edu > NM> (8.9.3/8.9.3) with ESMTP id VAA15050; > NM> e8196ba32d986fda376810890252a5a409af9013.msg: by earlham.edu > NM> (8.9.3/8.9.3) with ESMTP id VAA15050; > NM> f0b0d1938a6b4c018dd3972a82f8da088519dc5a.msg: by earlham.edu > NM> (8.9.3/8.9.3) with ESMTP id VAA15050; [root@yang qfiles]# > > NM> ---------------------------- > > NM> I only get one message, the other two mailing list have > NM> different users in them, just incase sendmail was being smart > NM> and checking if the user aliases go to the same user. > > NM> Does anyone have this problem, or has it, Just to know that I > NM> am not the only one running into it. And any help would be > NM> grateley appreciated. > > | TIA, > | Nick > > NM> Running Beta6 on RH6.2 > > I've not been able to reproduce this using the current CVS snapshot > (post-beta6). You might send a message to mailman-users(a)python.org to > see if anybody else has had similar problems. > > -Barry Hi Barry, I installed the latest cvs yesterday and it is working fine now. It also fixed the Oct 20 01:06:00 2000 (31286) Delivery exception: [Errno 75] Value too large for defined data type bug. its strange.. as I have no idea what might have been wrong, or what might have been patched up. Thanks for your help. Nick

1 0

RPM of Mailman beta6
by Wayne Ringling Oct. 20, 2000

Oct. 20, 2000

Has anyone created a rpm of Beta 6 yet? I found beta5 but want to use the latest and greatest version on a new box. If so please email to me. thanks Wayne Ringling wayner(a)strosniders.com

1 0

qrunner problem
by Jeff Maxwell Oct. 20, 2000

Oct. 20, 2000

I am having a problem with qrunner. I first get a message that the lists config.db is not writable. I change the permissions and then am able to send one message to the list, after the mail goes through the config.db is again unwritable. -rwxrwsr-x 1 mailman mailman 1706 Oct 19 22:21 admindbpreamble.html* -rw-rw---- 1 mailman mailman 3004 Oct 20 08:12 config.db -rwxrwsr-x 1 nobody mailman 3004 Oct 20 00:55 config.db.last* -rwxrwsr-x 1 mailman mailman 189 Oct 19 22:21 handle_opts.html* -rwxrwsr-x 1 mailman mailman 900 Oct 19 22:21 headfoot.html* -rwxrwsr-x 1 mailman mailman 3136 Oct 19 22:21 listinfo.html* -rw-rw-r-- 1 mailman mailman 6015 Oct 20 08:12 next-digest -rw-rw-r-- 1 mailman mailman 195 Oct 20 08:12 next-digest-topics -rwxrwsr-x 1 mailman mailman 4106 Oct 19 22:21 options.html* -rwxrwsr-x 1 mailman mailman 2 Oct 20 00:35 request.db* -rwxrwsr-x 1 mailman mailman 1169 Oct 19 22:21 roster.html* -rwxrwsr-x 1 mailman mailman 198 Oct 19 22:21 subscribe.html* Subject: cron: /usr/local/bin/python -S /home/mailman/cron/qrunner Traceback (most recent call last): File "/home/mailman/cron/qrunner", line 278, in ? kids = main(lock) File "/home/mailman/cron/qrunner", line 234, in main mlist = open_list(listname) File "/home/mailman/cron/qrunner", line 174, in open_list mlist = MailList.MailList(listname, lock=0) File "/home/mailman/Mailman/MailList.py", line 79, in __init__ self.Load() File "/home/mailman/Mailman/MailList.py", line 877, in Load dict, e = self.__load(dbfile) File "/home/mailman/Mailman/MailList.py", line 854, in __load fp = open(dbfile) IOError: [Errno 13] Permission denied: '/home/mailman/lists/test-list/config.db' -- Jeff Maxwell jeff(a)crossvalley.com

1 0

Re: [Mailman-Users] Q?: recipient's email address in msg footer
by Nigel Metheringham Oct. 20, 2000

Oct. 20, 2000

boris(a)openair.com said: > Is this something that is planned for future versions? To make the > modification to my local copy, where should I start looking? Couldn't > I just append some text just before the mail is sent? Mailman sends out one copy of the message to a (large) number of recipients. To do what you want you need to make each message be sent to a single recipient. This means for my 1000 member list, Mailman would inject 1000 entries into the mail queue, rather than the few it does now (Mailman does split the outgoing set into chunks of subscribers, but its of the order of a hundred or more addresses per mail transaction rather than one). Generating a mail transaction per recipient will have *serious* effects on the efficiency of the MTA subsystem (although some will be happier than others - qmail might like it), and certainly result in you temporarily using (list members) * (message size) spool space which would kill some systems. In some cases it would also increase your outgoing delivery bandwidth requirements. To implement this within Mailman would require a few changes to be made - maybe you could get away with adding a new mail injector, but I think that moving the footer generation would also be needed, requiring a fair bit of work. You *could* potentially do this in the MTA although I consider it *very* bad policy to change mail bodies within the MTA - adding a per recipient header would be possible, at a cost of outgoing delivery aggregation being destroyed. Nigel. -- [ - Opinions expressed are personal and may not be shared by VData - ] [ Nigel Metheringham Nigel.Metheringham(a)VData.co.uk ] [ Phone: +44 1423 850000 Fax +44 1423 858866 ]

3 2

Mailman-Bug with faked spam headers and some suggestions new features
by Steffen Bardolatzi Oct. 20, 2000

Oct. 20, 2000

This looks like a nasty bug ... We are running Mailman for some time now - one of the liste is a "half-open" one with these settings: - everyone can post - bccs to the list are not permitted (to avoid spams, works fine) - some alias-names for some users who regulary post to a different adress but bcc to our's Recently a spam message with a visible to-entry in the mail header arrived here: "To: <>" in the fields displayed by mail clients. This caused to log Mailman Beta 6 the following files into the error- logfile: Oct 08 23:53:01 2000 (25258) Delivery exception: read-only character buffer, None Oct 08 23:53:01 2000 (25258) Traceback (innermost last): File "/var/mailman/Mailman/Handlers/HandlerAPI.py", line 82, in do_pipeline func(mlist, msg, msgdata) File "/var/mailman/Mailman/Handlers/Hold.py", line 173, in process if mlist.require_explicit_destination and \ File "/var/mailman/Mailman/MailList.py", line 1208, in HasExplicitDest addr = string.lower(addr) TypeError: read-only character buffer, None ... these lines were repeated each *2* minutes for more than 10 hours (until I deleted the db-, and msg-file in the qfiles directory). The original msg-file time was exactly the one of the first log in the log file. In this *first* log I could read something like "implicit header..." followed by the endlessly repeated actual error-log above. ------------------------------- In addition to this here are some more minior bugs: - In case some e-mails are sent with qp-7bit-code the archiver does *not* covert them back into the acutal 8 bit characters - which makes it more diffucult to read the postings in the archive unless you are get used to qp-coding. As for 8 bit characters it works fine. Some of the affected mail clients are Pegasus und Outlook Express (according to some header analyses on an unregular bases). E-Mails are send just fine with no problems. - In case some people send M$-attachments the archive does not interpret this mime code and displays if just as if it was plain text. A nice *new* feature was if there was displayed a link for non-text-files like: download this file. - It would be fine if the archive would *not* display both the text and html code (in source code) if some people send a message with html *and* txt - the default might be *only* to render the html part readable (as e.g. done my pine). In general it would be fine if the archive was mime-aware ... there are too many users out there who have not yet learnt to send e-mails in plain text. - In case there are packet losses and timeouts during processing some admin-(mail)-requests Mailman does recognize the changes but does endlessly attempt to load the updated admin-requests site. ------------------------------------------- - sugestion for a new feature: I was told to disable the unsubscribe-funktion for a special list: I edited the list option's site *and* disabled the request e-mail adress (else I had to filter out unsubscribe in the subject and body with procmail or so). So far this works fine *but* has been some work. Therefore a switch like: "unsubscribe yes no" would be a good idea - maybe on a per-list bases in the mydefauls.py-file. Thanks in advance and thaks for such a great mailing list manager! PS.: I hope it's ok if I send it to mailman-users and mailman-developers and sorry about the length. Anyway Mailman seems to get better with each Beta version.

2 1

how to change MM-Archive when externally archiving lists under virtual domains
by Alex Aminoff Oct. 20, 2000

Oct. 20, 2000

I want to use an external archiving program (in this case MHonArc). I set the PUBLIC_EXTERNAL_ARCHIVER and PRIVATE_EXTERNAL_ARCHIVER to appropriate strings in mm_cfg.py, but that only sets the default. I also want to be able to change where the archive of each list lives. This requires changing 1) the URL used to get to the archives from the list info page, and 2) the external archiver command line. I presume these variables are kept in lists/<listname>/config.db. How do you change these things on an existing list? There does not seem to be a place in the html admin interface to do that. - Alex Aminoff alex_aminoff(a)alum.mit.edu http://www.basespace.net/~alex/consult/

2 1