Mailman 3 January 2004 - Mailman-Developers

Archiving according to arriving date - add this as an option...
by Andrzej Kasperowicz 11 Jan '04

11 Jan '04

I think that there should be an option allowing to archive mails according to date of reception of the posts by mailman, and not date set by user who sends it. That would prevent dates from the future in the archive: 2006, 2011, 2013, 2024, which you can see in many lists, like for example mailman-users archive: http://mail.python.org/pipermail/mailman-users/ Regards Andy

1 0

Conjugation with usenet: private list, open newsgroup.
by Andrzej Kasperowicz 11 Jan '04

11 Jan '04

Admin of my server moved some time ago one of my lists to Mailman, but the other one he did not, because the other one is conjugated with a usenet news group, and he said that he can't do that under mailman, because in order to conjungate it in direction usenet -> list the list would have to be open for everyone, or moderator would have to confirm every post send from persons not subscribed to the list. Is that true? If yes, then... ok I understand the initial legitimate idea that if usenet group is open to everyone then the list should be too, or both should be moderated. The problem is however, that to the mailing list address are coming hundreds of spams *per day* (even though spamassassin is installed), so it cannot be open. I could not also find silly enough moderator to manually delete hundreds of spams daily. The only solution is to allow private list to be conjugated with an open usenet group. I request to allow it in mailman *as soon as possible*. Regards Andy

1 0

troubles with Messages script
by george 09 Jan '04

09 Jan '04

I everybody, a few months ago, I'd submited to the Mailman Users List a problem with the python script Message.py occuring during membership management: http://mail.python.org/pipermail/mailman-users/2003-October/031894.html The same error occurs with Mailman 2.1.4 ((Python 2.3.3): ********** UserNotification.__init__(self, recips, sender, subject, text, lang) File "/var/mailman/Mailman/Message.py", line 206, in __init__ errors='replace') TypeError: __init__() got an unexpected keyword argument 'errors' ********** All is working fine after deleting the argument errors in the following lines : class UserNotification(Message): """Class for internally crafted messages.""" def __init__(self, recip, sender, subject=None, text=None, lang=None): Message.__init__(self) charset = None if lang is not None: charset = Charset(Utils.GetCharSet(lang)) if text is not None: self.set_payload(text, charset) if subject is None: subject = '(no subject)' self['Subject'] = Header(subject, charset, header_name='Subject', errors='replace') <--------here's the problem ! self['From'] = sender if isinstance(recip, ListType): self['To'] = COMMASPACE.join(recip) self.recips = recip else: self['To'] = recip self.recips = [recip] What do you think about that ? -- Pascal GEORGE

1 0

CGI's Not Finding Group
by Emanuel Masciarelli 09 Jan '04

09 Jan '04

I have posted this to the Users list, but have not had a good reply. This is really bugging me and I have no idea what the problem is. OK, I have no idea why this is happening. I am running on YellowDog 3.0.1. The install and everything seems fine, but when I hit a CGI, I get: Mailman CGI error!!! The Mailman CGI wrapper encountered a fatal error. This entry is being stored in your syslog: Failure to find group name nobody. Try adding this group to your system, or re-run configure, providing an existing group name with the command line option --with-cgi-gid. The group nobody does exist. I tried --with-cgi-gid='apache nobody' and apache is also not found. Any ideas on what is going on? Emanuel

1 0

Mysql MemberAdaptor update.
by Kyrian 08 Jan '04

08 Jan '04

FWIW. I've uploaded a new version of the MySQL member adaptor to the Mailman patches Sourceforge thing. Nothing much changed, except it now does a "CREATE IF NOT EXISTS x" on the table required for whichever list it is being called on, which crudely, but effectively gets around the need to manually create the list member tables. I've yet to incorporate suggestions I received from Barry about how the internals of it should work, and when I do that, I guess it will be the next significant release. As a general thought, I'd be interested to know (if anyone can find out for me) how many times that patch has been downloaded from Sourceforge. K.

2 2

Why Multipart with 7bit messages?
by Michael Heydekamp 07 Jan '04

07 Jan '04

Hi, I just realized that Mailman 2.1.3 sometimes (and IMO unnecessarily) creates Multipart messages upon appending the mailing list footer. After some investigation I found out that it does so only if the mail body does not contain any 8bit characters. If it contains 8bit characters then everything is fine. Is this a bug or by design and what can I do to avoid it? Strange: I'm not seeing this behaviour in this very list... Michael

2 4

bug in Mailman 2.1.4 ??
by Martin Maechler 07 Jan '04

07 Jan '04

Dear MM developers, we had activated mailman 2.1.4 this morning, and things (at least e-mail) seemed to work fine. Only later we found that with the web interface we get a big problems, for administrative things, both user subscription or adminstrator login. Our setup: Mail server is on Solaris 8; Web server (apache) on Linux Redhat 9. This had worked fine with Mailman 2.1.3. to which we had to revert ASAP. We got the following in a browser window. Do you have any ideas what could have gone wrong? Regards, Martin Maechler <maechler(a)stat.math.ethz.ch> http://stat.ethz.ch/~maechler/ Seminar fuer Statistik, ETH-Zentrum LEO C16 Leonhardstr. 27 ETH (Federal Inst. Technology) 8092 Zurich SWITZERLAND phone: x-41-1-632-3408 fax: ...-1228 <>< ------------------------------------------------------- Bug in Mailman version 2.1.4 We're sorry, we hit a bug! 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 (most recent call last): File "/sfs/s/solaris/8/app/mailman-sfs/2.1.4/scripts/driver", line 87, in run_main main() File "/sfs/s/solaris/8/app/mailman-sfs/2.1.4/Mailman/Cgi/admindb.py", line 176, in main mlist.Save() File "/sfs/s/solaris/8/app/mailman-sfs/2.1.4/Mailman/MailList.py", line 526, in Save self.__save(dict) File "/sfs/s/solaris/8/app/mailman-sfs/2.1.4/Mailman/MailList.py", line 485, in __save if mm_cfg.SYNC_AFTER_WRITE: AttributeError: 'module' object has no attribute 'SYNC_AFTER_WRITE' Python information: Variable Value sys.version 2.3 (#1, Oct 16 2003, 05:04:34) [GCC 3.2.2 20030222 (Red Hat Linux 3.2.2-5)] sys.executable /scratch/local/bin/python sys.prefix /scratch/local/app/python/current sys.exec_prefix /scratch/local/app/python/current sys.path /scratch/local/app/python/current sys.platform linux2 Environment variables: Variable Value SSL_VERSION_INTERFACE mod_ssl/2.0.40 SSL_SERVER_I_DN_OU Department of Mathematics SSL_CIPHER_EXPORT false SSL_SERVER_S_DN_Email webmaster(a)math.ethz.ch SERVER_SOFTWARE Apache/2.0.40 (Red Hat Linux) SCRIPT_NAME /mailman/admindb SSL_SERVER_A_KEY rsaEncryption SSL_SERVER_S_DN_ST Switzerland SERVER_SIGNATURE Apache/2.0.40 Server at www.stat.math.ethz.ch Port 443 REQUEST_METHOD GET HTTP_KEEP_ALIVE 300 SERVER_PROTOCOL HTTP/1.1 SSL_SERVER_S_DN /C=CH/ST=Switzerland/L=Zurich/O=ETH Zurich/OU=Seminar for Statistics/CN=www.stat.math.ethz.ch/emailAddress=webmaster(a)math.ethz.ch HTTP_ACCEPT_CHARSET ISO-8859-1,utf-8;q=0.7,*;q=0.7 SSL_CIPHER DHE-RSA-AES256-SHA SSL_SERVER_V_START Feb 7 16:20:08 2003 GMT SSL_SESSION_ID B3A4068B5FE1BF5724E1A013A8D807BEA289E9C2707F87655F146278FF232E04 SSL_CLIENT_VERIFY NONE SSL_SERVER_I_DN_ST Switzerland HTTP_CONNECTION keep-alive HTTP_COOKIE bioconductor+admin=2802000000695287f93f732800000035346463373631326663616634306662353561373066346663323939393332316662336230396362 SERVER_NAME www.stat.math.ethz.ch REMOTE_ADDR 155.52.45.201 SSL_CIPHER_ALGKEYSIZE 256 SSL_SERVER_I_DN /C=CH/ST=Switzerland/L=Zurich/O=ETH Zurich/OU=Department of Mathematics/CN=ISG D-MATH/emailAddress=webmaster(a)math.ethz.ch SSL_SERVER_I_DN_C CH SSL_SERVER_M_VERSION 1 SSL_SERVER_I_DN_O ETH Zurich SSL_SERVER_M_SERIAL 07 SERVER_ADDR 129.132.148.136 DOCUMENT_ROOT /var/www/vhosts/sfs/htdocs SSL_SERVER_S_DN_OU Seminar for Statistics SERVER_PORT 443 SSL_SERVER_I_DN_Email webmaster(a)math.ethz.ch SSL_VERSION_LIBRARY OpenSSL/0.9.7a PYTHONPATH /sfs/s/solaris/8/app/mailman-sfs/2.1.4 SCRIPT_FILENAME /var/www/vhosts/sfs/mailman/admindb SERVER_ADMIN webmaster(a)math.ethz.ch SSL_SERVER_S_DN_O ETH Zurich SSL_SERVER_A_SIG md5WithRSAEncryption SSL_SERVER_S_DN_L Zurich HTTP_HOST www.stat.math.ethz.ch SCRIPT_URL /mailman/admindb/bioconductor HTTPS on SSL_SERVER_I_DN_L Zurich PATH_TRANSLATED /var/www/vhosts/sfs/htdocs/bioconductor HTTP_CACHE_CONTROL max-age=0 SSL_SERVER_S_DN_C CH REQUEST_URI /mailman/admindb/bioconductor HTTP_ACCEPT text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,video/x-mng,image/png,image/jpeg,image/gif;q=0.2,*/*;q=0.1 SCRIPT_URI https://www.stat.math.ethz.ch/mailman/admindb/bioconductor SSL_SERVER_S_DN_CN www.stat.math.ethz.ch HTTP_USER_AGENT Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3) Gecko/20030314 GATEWAY_INTERFACE CGI/1.1 SSL_PROTOCOL TLSv1 REMOTE_PORT 44320 HTTP_ACCEPT_LANGUAGE en-us,en;q=0.5 SSL_SERVER_V_END Feb 4 16:20:08 2013 GMT SSL_SERVER_I_DN_CN ISG D-MATH QUERY_STRING SSL_CIPHER_USEKEYSIZE 256 HTTP_ACCEPT_ENCODING gzip,deflate,compress;q=0.9 UNIQUE_ID kvDr3oGElIIAAE4-T6UAAAAZ PATH_INFO /bioconductor

3 3

Maildir support for archives
by Fil 07 Jan '04

07 Jan '04

Hi, is it possible to change the archives/list.mbox/list.mbox from mbox format to Maildir format? It seems obvious but... I couldn't find how. Maybe "external_archiver" should call a the procmail delivery agent? -- Fil

1 0

Aprove/accept
by Somuchfun 06 Jan '04

06 Jan '04

I noticed that the terminology used to accept messages for moderation is not always the same. In some screens the term "approve" is used and in others "accept". Can this be changed in the next version so the term is always the same to avoid confusion for new admins? thanks

1 0

Tweaking Mail->News Gateway
by Michael Heydekamp 06 Jan '04

06 Jan '04

Hi Mailman developers, we at freexp.de are setting up Mailman and INN and are trying to get the Mail<->News facility to work. We are neither familiar with Mailman nor with Python, just being poor old Pascal programmers. ;) I have been in touch with Brad Knowles before and he advised me to ask here. We have three mailing lists and three corresponding newsgroups, which shall be gated bidirectional. It even works but what is puzzling us is that in Mail->News direction Mailman always creates an own MsgID. This screws up threading by references: If a newsgroup user replies to a posting that has been gated from the mailing list to the newsgroup, then - from the perspective of the mailing list users - his references point to a "wrong" MsgID when they receive this followup posting being gated from the newsgroup to the mailing list. I found the respective code in Queue/NewsRunner.py and also read the explanation why Mailmain is creating own MsgIDs (I'll come back to this later on). I changed the code as follows: ----------8<---------- # Our Message-ID format is <mailman.secs.pid.listname@hostname> msgid = msg['message-id'] hackmsgid = True if msgid: hackmsgid = False # mo = mcre.search(msgid) # if mo: # lname, hname = mo.group('listname', 'hostname') # if lname == mlist.internal_name() and hname == mlist.host_name: # hackmsgid = False if hackmsgid: del msg['message-id'] msg['Message-ID'] = Utils.unique_message_id(mlist) ----------8<---------- It is not really clear to me how Python can know where a conditional statement such as "if msgid:" ends (just by the indention?), but this piece seems to work: The MsgID is now being left untouched. This is question #1: Is this code OK? I'm also not sure if the variable 'msgid' contains a boolean or a string...? Now to the more important issues: I understand that there are two main reasons why Mailman wants to create an own MsgID upon gating Mail->News, one of them being to avoid loops. Even after I changed the code as above, I still can't see a loop. I first thought Mailman might check the MsgID of a posting upon deciding whether it should be gated from the newsgroup to the mailing list, but this is obviously not the case. I've had a look into cron/gate_news.py but couldn't figure out exactly how Mailman is taking that decision. This is question #2: How does Mailman know if the mailing list has already seen a posting or not? Anyway, the second and more important reason for creating own MsgIDs seems to be the issue of an XPost to two (or more) Usenet-gated mailing lists. This is indeed a problem and I understand the background. Thus we'd like to tweak Mailman in a way that it does the following: 1. Say we have the mailing lists ml-1, ml-2 and ml-3 and the corresponding newsgroups ng-1, ng-2 and ng-3. Now a mail comes in, being addressed to ml-1 and ml-2 (which thus should be gated to ng-1 and ng-2). In fact, two physical mails will come in, and obviously Mailman does now create two physical postings, one addressed to ng-1, the other one addressed to ng-2. This in fact creates the problem of duplicate MsgIDs. But what Mailman should do is to create *one* physical posting, x-posted to ng-1 and ng-2 ("Newsgroups: ng-1,ng-2"). This would mean that upon dealing with the mail to ml-1 it would have to check if the addresses in the To: and Cc: headers contain more than one of "our" mailing lists and if these mailing lists are being gated to "our" Newsgroups. If so, then an x-posting as described shall be created. When Mailman now has to deal with the second mail to ml-2 (with the same MsgID) it shall *not* create another posting anymore. Can this be accomplished (and if yes, how)? 2. Of course, if a mail does not have a MsgID at all, then Mailman should still create its own MsgID. Any hint will be appreciated (and again, please consider that we are newbees with regards to Mailman and Python). Even if we would have to hardcode some strings (of mailing lists and/or newsgroups) this would be a better solution than no solution. Michael

2 5

Syntax error
by Stonewall Ballard 05 Jan '04

05 Jan '04

I just grabbed the latest version from CVS, and found a couple of syntax errors in messages/ca/LC_MESSAGES/mailman.po Messed up string quoting. - Stoney -- Stonewall Ballard stoney(a)sb.org http://stoney.sb.org/

2 1

RELEASED Mailman 2.1.4
by barry＠python.org 04 Jan '04

04 Jan '04

I have released Mailman 2.1.4, a bug fix release that also contains support for four new languages: Catalan, Croatian, Romanian, and Slovenian. This release also contains a fix for a cross-site scripting vulnerability in the 'admin' cgi script (see CAN-2003-0965). There is also an expanded ability to filter message headers, nominally to provide better support when Mailman is used in conjunction with upstream spam and virus filters. The full source tarball has been made available from the usual sites. Sorry, there is no patch available yet, but you should be able to install Mailman 2.1.4 over your existing 2.1.x installation. See http://sourceforge.net/project/showfiles.php?group_id=103 for links to the downloadable files. After installing, be sure you restart your Mailman daemon by doing a "mailmanctl restart". IMPORTANT: You will want to re-run configure before doing a make install. See also: http://www.list.org http://mailman.sf.net http://www.gnu.org/software/mailman Enjoy, and have a Happy New Year. -Barry -------------------- snip snip -------------------- 2.1.4 (31-Dec-2003) - Close some cross-site scripting vulnerabilities in the admin pages (CAN-2003-0965). - New languages: Catalan, Croatian, Romanian, Slovenian. - New mm_cfg.py/Defaults.py variable PUBLIC_MBOX which allows the site administrator to disable public access to all the raw list mbox files (this is not a per-list configuration). - Expanded header filter rules under Privacy -> Spam Filters. Now you can specify regular expression matches against any header, with specific actions tied to those matches. - Rework the SMTP error handling in SMTPDirect.py to avoid scoring bounces for all recipients when a permanent error code is returned by the mail server (e.g. because of content restrictions). - Promoted SYNC_AFTER_WRITE to a Default.py/mm_cfg.py variable and make it control syncing on the config.pck file. Also, we always flush and sync message files. - Reduce archive bloat by not storing the HTML body of Article objects in the Pipermail database. A new script bin/rb-archfix was added to clean up older archives. - Proper RFC quoting for List-ID descriptions. - PKGDIR can be passed to the make command in order to specify a different directory to unpack the distutils packages in misc. (SF bug 784700). - Improved logging of the origin of subscription requests. - Bugs and patches: 832748 (unsubscribe_policy ignored for unsub button on member login page), 846681 (bounce disabled cookie was always out of date), 835870 (check VIRTUAL_HOST_OVERVIEW on through the web list creation), 835036 (global address change when the new address is already a member of one of the lists), 833384 (incorrect admin password on a hold message confirmation attachment would discard the message), 835012 (fix permission on empty archive index), 816410 (confirmation page consistency), 834486 (catch empty charsets in the scrubber), 777444 (set the process's supplemental groups if possible), 860135 (ignore DiscardMessage exceptions during digest scrubbing), 828811 (reduce process size for list and admin overviews), 864674/864676 (problems accessing private archives and rosters with admin password), 865661 (Tokio Kikuchi's i18n patches), 862906 (unicode prefix leak in admindb), 841445 (setting new_member_options via config_list), n/a (fixed email command 'set delivery')

3 2

Problem with msgfmt.py? Or the language file?
by Ron Jarrell 02 Jan '04

02 Jan '04

Sorry if this is an old one; I'm soooo behind on mailman-developers.. I skimmed through, and didn't see anything that lept out at me. Trying to build 2.1.4. /usr/local/bin/python ../build/bin/msgfmt.py -o ca/LC_MESSAGES/mailman.mo ca/LC_MESSAGES/mailman.po Traceback (most recent call last): File "../build/bin/msgfmt.py", line 203, in ? main() File "../build/bin/msgfmt.py", line 199, in main make(filename, outfile) File "../build/bin/msgfmt.py", line 151, in make l = eval(l) File "<string>", line 1 """"" >Python regular expression</a>. When entering backslashes, do so\n" ^ SyntaxError: invalid token *** Error code 1 (ignored) It *was* doing this on nearly every file. I wiped out the messages directory, re synced it with cvs, did a distclean and a make, and got it down to just the one error in the ca set. It was the same invalid token for the others too, before. Running Python 2.2, not 2.2.1...

3 2