Mailman 3 July 2002 - Mailman-Developers

[ mailman-Bugs-553033 ] subscribing via web does not work
by noreply＠sourceforge.net 31 Jul '02

31 Jul '02

Bugs item #553033, was opened at 2002-05-06 17:34 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=553033&group_i… Category: Web/CGI Group: 2.1 beta >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: javier wilson (javierwilson) Assigned to: Nobody/Anonymous (nobody) Summary: subscribing via web does not work Initial Comment: Users trying to subscribe via web were redirected to the options web page. This only happened with users using Spanish templates. The problem seems to be in the spanish template listinfo.html Instead of "<MM-Options-Form-Start>" it should say: "<MM-Subscribe-Form-Start>". Is this correct? javier wilson ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-07-31 16:21 Message: Logged In: YES user_id=12800 I believe this has since been fixed. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-05-06 22:57 Message: Logged In: YES user_id=12800 Yes, but someone who speaks Spanish is going to have to update the es/listinfo.html file. I took a quick look and couldn't tell for sure what should be changed. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=553033&group_i…

1 0

[ mailman-Bugs-565808 ] Broken options in Hungarian listinfo
by noreply＠sourceforge.net 31 Jul '02

31 Jul '02

Bugs item #565808, was opened at 2002-06-07 09:16 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=565808&group_i… Category: Web/CGI Group: 2.1 beta >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: szabolcs szigeti (szigi) Assigned to: Nobody/Anonymous (nobody) Summary: Broken options in Hungarian listinfo Initial Comment: Teh Hungarian template for listinfo is broken, instead of setting options, users are taken to subscription. Similar to bug [ 553033 ] "subscribing via web does not work" This should correct it: *** templates/hu/listinfo.html.orig Fri Jun 7 15:10:36 2002 --- templates/hu/listinfo.html Fri Jun 7 15:08:56 2002 *************** *** 127,133 **** <MM-Roster-Option> <MM-Form-End> <p> ! <MM-Subscribe-Form-Start> <MM-Editing-Options> <MM-Form-End> </td> --- 127,133 ---- <MM-Roster-Option> <MM-Form-End> <p> ! <MM-Options-Form-Start> <MM-Editing-Options> <MM-Form-End> </td> ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-07-31 16:20 Message: Logged In: YES user_id=12800 Fixed, thanks. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=565808&group_i…

1 0

[ mailman-Bugs-585484 ] virtual domain lists misdirect autoreply
by noreply＠sourceforge.net 31 Jul '02

31 Jul '02

Bugs item #585484, was opened at 2002-07-23 12:32 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=585484&group_i… Category: bounce detection Group: None >Status: Pending Resolution: None Priority: 5 Submitted By: Byron T. Watts (btwatts) Assigned to: Nobody/Anonymous (nobody) Summary: virtual domain lists misdirect autoreply Initial Comment: Using mailman with virtual domain hosting. Bounced messages for a particular list are going to the wrong list administrator (not even on the same domain). The particular notices that I'm seeing misdirected, are the <i>useridi> is on vacation messages. I am not certain whether other messages are being similarly misdirected. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-07-31 16:12 Message: Logged In: YES user_id=12800 Moving this to status Pending, for lack of more information. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-07-24 11:25 Message: Logged In: YES user_id=12800 Sorry, I'll need more information here. Start with the basics: what OS, what MTA, what version of Python, what version of Mailman. How do you have your MTA configured? Have you set up virtual domain support in Mailman properly (differs depending on the version of Mailman you're using). Please include version numbers for all related software. Also if you can provide a reproducible recipe for seeing the bug, or at least attach copies of misdirected messages, these things would help. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=585484&group_i…

1 0

[ mailman-Bugs-588373 ] bug with 2.1b2 (something with cookies?)
by noreply＠sourceforge.net 31 Jul '02

31 Jul '02

Bugs item #588373, was opened at 2002-07-30 00:33 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=588373&group_i… Category: None >Group: 2.1 beta >Status: Closed >Resolution: Out of Date Priority: 5 Submitted By: Paul Marshall (paulmarshll) Assigned to: Nobody/Anonymous (nobody) Summary: bug with 2.1b2 (something with cookies?) Initial Comment: This is hopefully my third and final stupid question involving mailman. I have mailman 2.1b2 setup and mostly working (I can create lists, and post, etc...). However whenever I try to log into a list via the admin page to edit/delete/whatever to it, it comes up with this bug: Traceback (most recent call last): File "/var/mailman/scripts/driver", line 82, in run_main main() File "/var/mailman/Mailman/Cgi/admin.py", line 82, in main cgidata.getvalue('adminpw', '')): File "/var/mailman/Mailman/SecurityManager.py", line 208, in WebAuthenticate print self.MakeCookie(ac, user) File "/var/mailman/Mailman/SecurityManager.py", line 223, in MakeCookie c = Cookie.SimpleCookie() AttributeError: 'module' object has no attribute 'SimpleCookie' Is this a permissions problem? something to do with creating cookies...Honestly, I have no idea... I've searched some bug databases and most likely passed right over it, however I can't seem to find anything dealing with this error. Thanks for all the help. Paul ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-07-31 16:11 Message: Logged In: YES user_id=12800 Weird! The update script should have gotten rid of those files automatically. It's probably too late for your installation, but if not, try running "bin/update -f" manually and see if the Cookie.pyc file sticks around. ---------------------------------------------------------------------- Comment By: Paul Marshall (paulmarshll) Date: 2002-07-31 12:43 Message: Logged In: YES user_id=582441 I fixed the problem. Apparently I still had Cookie.py and Cookie.pyc, which I deleted, this seemed to fix the problem. Found this on: http://mail.python.org/pipermail-21/mailman-developers/2001- November/010020.html Thanks anyways. This post can be deleted. Paul ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=588373&group_i…

1 0

[ mailman-Bugs-589284 ] Ambiguous user preference
by noreply＠sourceforge.net 31 Jul '02

31 Jul '02

Bugs item #589284, was opened at 2002-07-31 14:35 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=589284&group_i… >Category: Web/CGI Group: 2.1 beta >Status: Closed >Resolution: Out of Date Priority: 5 Submitted By: Nick Arnett (narnett) Assigned to: Nobody/Anonymous (nobody) Summary: Ambiguous user preference Initial Comment: (2.1b2) The heading and text for users to choose whether or not their address is visible are at odds with each other. One or the other needs its logic reversed, else users won't know whether "yes" means their address is concealed or visible, etc. -- Conceal yourself from subscriber list? When someone views the list membership, your email address is normally shown (in an obscured fashion to thwart spam harvesters). If you do not want your email address to show up on this membership roster, select No for this option. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-07-31 16:09 Message: Logged In: YES user_id=12800 Fixed in cvs. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=589284&group_i…

1 0

Re: [Mailman-Users] Adding exception to html-stripping in the archive
by Laurence Berland 31 Jul '02

31 Jul '02

begin quote from Laurence Berland on Wednesday 31 July 2002 12:04 pm > I've already written code that filters the messages on their way to the > archiver, substituting based on regular expressions. It does this in the > Queue/ArchRunner.py file, in just about the last spot before the actual > archiver gets called. It can't go in the archiver, because it needs to be > able to read the mlist variable for configuration and such. I need to be > able to use a regular expression to substitute in a snippet of html code. > This could be used for several things, but my intention is to use it to add > an img tag. Is there a way to configurably get around the html-sanitizing > done by the archiver in some non-kludge way? I'm not sure if anyone is reading these, though I tend to suspect not. In any case, I've found the kludge way to go about doing this, but it's really quite awful. I changed the websafe function in utils.py to just return the very string it is passed. Please tell me there's a better way, as this requires a recompile to change, and it's not something I even want done for every list. If there isn't a better way yet, can anyone think of how to code one? My biggest problem is the lack of an mlist object near many websafe calls, meaning I can't readily grab config variables for a list. > > TIA, > Laurence >

1 0

[ mailman-Patches-573503 ] message-id munge error in ToUsenet.py
by noreply＠sourceforge.net 31 Jul '02

31 Jul '02

Patches item #573503, was opened at 2002-06-25 01:54 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=573503&group_i… Category: None >Group: Mailman 2.0.x >Status: Closed >Resolution: Accepted Priority: 5 Submitted By: Mark Weaver (mdw21) Assigned to: Nobody/Anonymous (nobody) Summary: message-id munge error in ToUsenet.py Initial Comment: # Our Message-ID format is <mailman.secs.pid.listname@hostname> msgid = msg.get('message-id') hackmsgid = 1 if msgid: mo = re.search( msgid, r'<mailman.\d+.\d+.(?P<listname>[^@]+)@(?P<hostname>[^>]+)>') in the re.search, the parameters are the wrong way around. The consequence is that a new message-id is assigned to each message and threading is easily broken. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-07-31 15:31 Message: Logged In: YES user_id=12800 Thanks fixed in MM2.0.x cvs. It'll be part of MM2.0.14 if there ever is one. Patch not relevant for MM2.1. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=573503&group_i…

1 0

Re: [Mailman-Developers] Re: Initial Mailman v2.0 with TMDA and Mime filtering
by J C Lawrence 31 Jul '02

31 Jul '02

On Wed, 31 Jul 2002 11:25:28 -0700 J C Lawrence <J> wrote: > That would be fairly easy under Exim -- you can do all the extra work > between the director and transport. Note: The edits made to exim.conf in my HOW-TO are a simple merge set of the edits required by Mailman's README.Exim and TMDA's. I don't add anything new to the picture there. -- J C Lawrence ---------(*) Satan, oscillate my metallic sonatas. claw(a)kanga.nu He lived as a devil, eh? http://www.kanga.nu/~claw/ Evil is a name of a foeman, as I live.

2 1

Re: Initial Mailman v2.0 with TMDA and Mime filtering
by Jason R. Mastaler 31 Jul '02

31 Jul '02

J C Lawrence <claw(a)kanga.nu> writes: > I built the system with Mailman 2.0, TMDA 0.58, Exim v3, mimefilter, > mimedecode, and procmail. After reading through this, my only concern is that it will only appeal to very few users. * It's too Exim specific. Exim is used less than Sendmail, Postfix or qmail. It would be nice to come up with a more general HOWTO that covers integration with either Sendmail, Postfix or Exim. * The mimefilter/mimedecode stuff is a distraction IMO, and not really relevant to the TMDA integration. * If we can find a way to do this without procmail, that's a bonus. That said, thanks for writing this up. I think it's a good start, and longer overdue. > I started out wanting and trying to use Postfix. The core problem > I hit was making the filter process hung off the alias execute as > the right user. I needed it to execute as the list user so it > would be able to read the Mailman list configurations to verify > subscribers from there. In the qmail HOWTO I'm writing, TMDA is driven from ~mailman's .qmail files, following the setup recommended in README.QMAIL. This solves the problem of access to the MM config.db files of course. > Getting the filter process to execute as 'list' under postfix > proved a bitch. What user is the filter process executed as by default? -- (http://tmda.net/)

1 1

[ mailman-Patches-573508 ] ToUsenet: subject prefix stripping
by noreply＠sourceforge.net 31 Jul '02

31 Jul '02

Patches item #573508, was opened at 2002-06-25 02:03 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=573508&group_i… Category: mail delivery Group: Mailman 2.0.x >Status: Closed Resolution: None Priority: 5 Submitted By: Mark Weaver (mdw21) Assigned to: Nobody/Anonymous (nobody) Summary: ToUsenet: subject prefix stripping Initial Comment: For some inexplicable reason ToUsenet is trying to -add- the subject prefix. Now this doesn't work generally anyway (consider a plain post - this won't do it). Typically, the subject prefix is the list- name, which just replicates information we already have (as we already know which newsgroup we are looking at). Anyway, arguments aside, I've fixed up ToUsenet.py to go the other way and remove subjects. (I would have made this an option, but my Python is non-existent). ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-07-31 14:39 Message: Logged In: YES user_id=12800 I've added something to MM2.1b3 to selectively disable subject munging for usenet gatewayed posts. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-07-31 13:01 Message: Logged In: YES user_id=12800 This patch is only relevant to MM2.0, and that version is in critical bug fix phase only. MM2.1 does it differently, but I'm wondering if the subject should not be added to news bound messages either? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=573508&group_i…

1 0