Mailman 3 June 2002 - Mailman-Developers

bug demonstration 12345678911234567892123456789312345678941234567895123456789612345678971234567898112345678911234567892123456789112345678911234567892123456789 more text
by Marc MERLIN 05 Jun '02

05 Jun '02

If this works as expected, all the headers below the subject line should end up in the mail body. I've been tracking this bug for a while, apparently mailman's header parsing chokes when you have a header that contains more than 80 (maybe 100?) characters in a row without a space. This breaks horribly when you run spamassassin, due to headers like: X-Spam-Status: No, hits=2.0 required=7.0 tests=SUBJ_ENDS_IN_Q_MARK,TO_LOCALPART_EQ_REAL,X_NOT_PRESENT,RCVD_IN_VADUL,X_RCVD_IN_DUL_FH version=2.21 But it also breaks because outlook has a bug where Message-IDs listed in the References header aren't always separated by spaces. I'm hoping that Barry or someone else can nail this quicker than I can find out which part of mailman may even be responsible for that (I'm still quite busy hacking on exim and spamassassin for sf.net right now) Marc -- Microsoft is to operating systems & security .... .... what McDonalds is to gourmet cooking Home page: http://marc.merlins.org/ | Finger marc_f(a)merlins.org for PGP key

4 5

Contributing code?
by David Gibbs 03 Jun '02

03 Jun '02

Folks: How does one go about contributing code? I've made some small changes in my cvs sandbox that I think would be useful for the core code. Do I mail them to someone (Barry?) for consideration, post them here, what? The mods I made are fairly simple ... when the admlogin, options, and private templates are loaded, the cursor is automaticly placed in the first form field on the page. I made similar changes in 2.0.11 and my list owners love it. Thanks! david

3 10

[ mailman-Patches-563686 ] Position cursor in login templates
by noreply＠sourceforge.net 03 Jun '02

03 Jun '02

Patches item #563686, was opened at 2002-06-02 19:03 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=300103&aid=563686&group_id… Category: Web UI Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: David Gibbs (midrangeman) Assigned to: Nobody/Anonymous (nobody) Summary: Position cursor in login templates Initial Comment: Some of my list owners wanted the cursor to be positioned in the password field for the admin & admindb pages. So I hacked a tiny bit of javascript to position the cursor in the first form field on the admlogin, options, and private templates. All languages. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=300103&aid=563686&group_id…

1 0

MimeFilter integration with Mailman
by J C Lawrence 03 Jun '02

03 Jun '02

<<Reply-To set to mailman-users(a)python.org>> A while back I noticed that while we'd been happily recommending MimeFilter for stripping unwanted MIME parts from messages before they got to mailman, nobody had bothered to say how to run it beyond "chuck it in the alias file". Problem: those instructions (generally) won't work. Reason: Mimefilter tries to create files and a temp directory in its CWD, and at least under postfix that means /var/spool/postfix which here is root.root/0755 (and I'm not about to change that). So I spent some time this morning and threw something together a little slicker. Its essentially a wrapper around Mailman's wrapper. What I got seems to work. I don't and won't claim beauty. --<cut>-- #!/bin/bash # Syntax: # # mimestrip <action> <target> # # Both arguments will be passed to /var/lib/mailman/mail/wrapper # in the same order, without change. # # All other arguments will be gleefully discarded. # # Author: J C Lawrence <claw(a)kanga.nu> # ACTION=$1 TARGET=$2 export PATH=/usr/local/bin:/bin:/usr/bin:/usr/X11R6/bin:/sbin:/usr/sbin # -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= # Config (Edit this bit to suit your setup!) # -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= # Safe working directory for mimefilter. We need to do this as # postfix by default will execute this script in /var/spool/postfix and # mimefilter will try and create temp directories and files under there. # Note: Make sure that the value of tmpdir is writeable by the UID or GID # that this script will execute under. tmpdir="/tmp/mimestrip.${$}" # Do you want to save an mbox of the messages before filtering # in $savefile_pre? (0/1) save_pre=1 # Do you want to save an mbox of the messages after filtering # in $savefile_post? (0/1) save_post=1 # File to save pre-filtered messages in savefile_pre="/tmp/mimestrip.prefilter" # File to same post filtered messages in savefile_post="/tmp/mimestrip.postfilter" # Send a copy of every processed message to the list maintainer? (Y/N) copy_maintainer="y" # -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= # MimeFilter setup (Don't edit from here down) # -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= # The name of the mailing list this message is intended for. Used # as the return address of the warning issued to the orginal author # if the message is not already clean. export list=${USER} # The address of the mailing list this message is intended for. # Used in the X-Loop field of the warning issued to the original # author if the message is not already clean. export listaddr=${USER}@${DOMAIN} # The administrative (owner) address of the mailing list this # message is inteded for. Used in the return address of the warning # issued to the original author if the message is not already clean. export listreq=${USER}-admin@${DOMAIN} # The email address of the maintainer of the mailing list this # message is inteded for. If it is defined, it is used to send the # maintainer original carbon copies of messages that have been # modified by this filter -- if filter_mime_cc_maintainer is # affermative, of course. export maintainer=${USER}-owner@${DOMAIN} # A boolean flag: if affermative (i.e., if it matches the /y/i Perl # regular expression), the mimefilter script will send carbon copies # of every cleaned (modified) message to the maintainer of the # mailing list the message is intended for. export filter_mime_cc_maintainer=${copy_maintainer} # -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= # Start working # -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= # Build a safe working directory for mimefilter. We need to do this as # postfix by default will execute this script in /var/spool/postfix and # mimefilter will try and create temp directories and files under there, # which will fail on permissions. # Note: Make sure that the value of tmpdir is writeable by the UID or GID # that this script will execute under. rm -rf ${tmpdir} 2> /dev/null mkdir ${tmpdir} cd ${tmpdir} # Working files (over-engineered and IO heavy, but useful during debugging # and tuning of the filter setup) tmpfile="mimestrip.$$" holdfile="mimehold.$$" # DEBUG #pwd > /tmp/mimestrip.pwd #set > /tmp/mimestrip.env # Get the inbound message from stdin and run it thru mimefilter with # copies saved for before and after. The mimestrip.err file should # always be empty. I found it useful for debugging. Nuke freely. # Note: If there's an "X-MimeStrip: No" header (actually anywhere in the # message), then don't run this message thru mimefilter but pass it # straight on to the mailman wrapper. cat > ${holdfile} grep -i "^X-MimeStrip:[ \t]*No" ${holdfile} if [ $? ] then cat ${holdfile} | /usr/bin/mimefilter > ${tmpfile} 2> /tmp/mimestrip.err # If there's nothing left of the message (less than 5 lines), don't # bother sending it forward to Mailman. count=`cat ${tmpfile} | wc -l` if [ $count -gt 5 ] then cat ${tmpfile} | /var/lib/mailman/mail/wrapper ${ACTION} ${TARGET} fi else # We found a header so send it thru unfiltered. cat ${tmpfile} | /var/lib/mailman/mail/wrapper ${ACTION} ${TARGET} fi # Save copies of the before and after messages off to a temp file for # analysis/debugging if [ $save_pre -eq 1 ] then cat ${holdfile} >> /tmp/mimestrip.prefilter echo >>/tmp/mimestrip.prefilter fi if [ $save_post -eq 1 ] then cat ${tmpfile} >> /tmp/mimestrip.postfilter echo >> /tmp/mimestrip.postfilter fi # Clean up rm -rf ${tmpdir} exit 0 --<cut>-- Notes: Use in your Mailman alias file as so (for a list called "test"): test: "|/some/path/here/mimestrip post test" More simply just replace the normal /var/lib/mailman/mail/wrapper" with the call to mimestrip. The script is Postfix specific in that it expects the $USER and $DOMAIN in its environment to be respectively set to the LHS and RHS of the address the message was sent to. Hack freely for your MTA of choice if it does something different. Why not use demime which does all sorts of cool things like Yahoo signature removal and getting rid of unnecessary quoted-printable? demime strips all MIME parts, which is fine if that's what you want. However there are certain MIME parts that I specifically want to let thru to my lists (eg message/rfc822), and I rather like some of mimefilter's other features thta demime doesn't share like emailing the original poster with a warning that parts were removed from their message. Yeah, those extra messages are annoying to the posters. They're intended to be and I like that. I don't want posters sending unwanted MIME parts to my lists. Note: You can turn off that feature in Mimefilter's config. I also wanted a way to send MIME messages thru to my lists without doing any MIME stripping. A bypass if you would. Typically I'd use this for valid/valuable list messages which contain useful MIME parts (eg an attached image such as a graph diagramming the message content) that would otherwise be stripped my the mimefilter. In the end I did this via a custom X-header: X-MimeStrip: No. Strong suggestion: Configure your lists to hold messages with that header for moderator approval. This will allow you to catch abuse by too-clever posters. Mailman v2.1 largely removes need for this mimestrip filter. If all you want is mimestripping then Mailman 2.1 should be more than enough. However I want more than that. I want mimefilter's annoying messages to posters of unwanted MIME, I want the bypass, I want the ability to save the before and after filtering messages etc, and I really want the ability to ad-hoc extend the filter with other little toys and trinkets as I go along (eg a quoted-printable flattener will likely be next for me here). Adding in something like SpamAssassin into the mail processing pipe with a custom handling rule (eg silently discard messages with high enough scores before passing them thru mimefilter) would be trivially easy and is left as an exercise for the reader. This is barely if at all tested. Caveat Emptor and all that rot. Yeah, I should put this in the FAQ and I hopefully will after I've run it thru a few more exercises here. Enjoy. -- 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.

1 0

Re: [Mailman-Developers] bug demonstration
by Marc MERLIN 03 Jun '02

03 Jun '02

On Sun, Jun 02, 2002 at 12:14:08AM -0700, Marc MERLIN wrote: > 12345678911234567892123456789312345678941234567895123456789612345678971234567898112345678911234567892123456789112345678911234567892123456789 > more text > Message-ID: <20020602071408.GC12014(a)merlins.org> > Mail-Followup-To: mailman-developers(a)python.org > References: <20020602065442.GA12014(a)merlins.org> > Mime-Version: 1.0 > Content-Type: text/plain; charset=us-ascii > Content-Disposition: inline > In-Reply-To: <20020602065442.GA12014(a)merlins.org> > User-Agent: Mutt/1.3.28i > X-Sysadmin: BOFH > X-URL: http://marc.merlins.org/ > X-Operating-System: Proudly running Linux > 2.4.14-lvm1.0.1rc4-ext3-0.9.15-grsec-1.8.8-servers11/Debian woody > X-Mailer: Some Outlooks can't quote properly without this header > X-Spam-Status: No, hits=-4.3 required=5.0 > tests=IN_REP_TO,LARGE_HEX,BODY_PYTHON_ZOPE version=2.20 > X-Spam-Level: > X-BeenThere: mailman-developers(a)python.org > X-Mailman-Version: 2.1b2+ > Precedence: bulk > List-Help: <mailto:mailman-developers-request@python.org?subject=help> > List-Archive: <http://mail.python.org/pipermail-21/mailman-developers> > List-Unsubscribe: <http://mail.python.org/mailman-21/listinfo/mailman-developers>, > <mailto:mailman-developers-request@python.org?subject=unsubscribe> > List-Subscribe: <http://mail.python.org/mailman-21/listinfo/mailman-developers>, > <mailto:mailman-developers-request@python.org?subject=subscribe> > List-Post: <mailto:mailman-developers@python.org> > List-Id: GNU Mailman developers <mailman-developers.python.org> > Sender: mailman-developers-bounces+mailman-developers-local=merlins.org(a)python.org > Errors-To: mailman-developers-bounces+mailman-developers-local=merlins.org(a)python.org > > On Sat, Jun 01, 2002 at 11:54:42PM -0700, Marc MERLIN wrote: > > If this works as expected, all the headers below the subject line should > > end up in the mail body. > > Son of a... Ahah, and now it barfs on python.org too. I don't get this bug, I really don't... Marc -- Microsoft is to operating systems & security .... .... what McDonalds is to gourmet cooking Home page: http://marc.merlins.org/ | Finger marc_f(a)merlins.org for PGP key

3 4

2.1b4 bug or my problem?
by Luigi Rosa 03 Jun '02

03 Jun '02

I just installed 2.1b4 on a fresh Linux installation. Everything is working well except for the URL in the headers and in the web pages. The hostname of the Linux box is mail.hypertrek.info and this is a part of mm_cfg.py: DEFAULT_EMAIL_HOST = 'mail.hypertrek.info' DEFAULT_URL_HOST = 'mail.hypertrek.info' DEFAULT_URL_PATTERN = 'http://%s/mailman/' add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST) DEFAULT_HOST_NAME = DEFAULT_EMAIL_HOST DEFAULT_URL = DEFAULT_URL_PATTERN % DEFAULT_URL_HOST HOME_PAGE = 'index.html' MAILMAN_SITE_LIST = 'mailman' With this settings, the header of the messages of each list and the mailto URL of the web pages are http://mail/mailman.... With the withlist inbterface I tried to change the web_page_url parameter of each list from 'mail' to 'http://mail.hypertrek.info' and the mailto url werw ok, but the headers of the messages and the URL of teh web pages were http://mail.hypertrek.info/... without mailman The question is: can I set the web_page_url variable to 'http://mail.hypertrek.info/mailman/' or there is another solution for this issue? Thanks. Ciao, luigi

2 1

Re: [Mailman-Users] "Host name this list prefers"
by Danny Terweij 02 Jun '02

02 Jun '02

steven <hostmaster(a)shults.org> heeft geschreven: > Hi, > > How do I get the field labelled "Host name this list prefers" on the > admin page "mailing list administration > General Options Section" to correctly handle a sub-domain (aka three > part machine name, e.g. foo.domain.com) so that mail sent from > adminstrative aliases comes from > listname-admin(a)foo.domain.dom instead of listname-admin(a)domain.dom ? Hi, I have the same question asked at the dev list ( a few days ago). Here with Mailman 2,1b2 same problem. Danny,

3 3

[ mailman-Bugs-563336 ] Unexpected MMBadUserError with MM-2.0.11
by noreply＠sourceforge.net 02 Jun '02

02 Jun '02

Bugs item #563336, was opened at 2002-06-02 00:48 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=563336&group_id… Category: (un)subscribing Group: 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: Federico Sevilla III (jijo) Assigned to: Nobody/Anonymous (nobody) Summary: Unexpected MMBadUserError with MM-2.0.11 Initial Comment: Just upgraded to Mailman 2.0.11. The upgrade itself worked fine, and basic tests after the upgrade seem to have worked okay, and mail has been getting delivered. However I got an email (as administrator) about an unexpected Mailman error. I have yet to get a complaint from our users so I do not know exactly what caused the problem. All I can deduce from the logs is that at around the same time, someone was subscribing/unsubscribing via email. The error message I got by email was: -----[ START ]----- An unexpected Mailman error has occurred in MailCommandHandler.ParseMailCommands(). Here is the traceback: Traceback (most recent call last): File "/usr/lib/mailman/Mailman/MailCommandHandler.py", line 223, in ParseMailCommands self.__dispatch[cmd](args, line, msg) File "/usr/lib/mailman/Mailman/MailCommandHandler.py", line 364, in ProcessSetCmd self.ConfirmUserPassword(sender, args[2]) File "/usr/lib/mailman/Mailman/SecurityManager.py", line 144, in ConfirmUserPassword raise Errors.MMBadUserError MMBadUserError -----[ END ]----- Some more miscellaneous information: - system is Debian GNU/Linux - mailman package is mailman-2.0.11-1 - python package is python-2.1.3-3 If anyone has tips as to where to dig for more information on the cause of this unexpected error, please do let me know and I will be more than happy to supply the missing details. It would also help calm my nerves if I knew whether this was fatal or not. :) ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=563336&group_id…

1 0

[ mailman-Bugs-563328 ] confirmation strings don't work 2.1b2+
by noreply＠sourceforge.net 02 Jun '02

02 Jun '02

Bugs item #563328, was opened at 2002-06-01 16:08 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=563328&group_id… Category: bounce detection Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Marc Merlin (marcmerlin) Assigned to: Nobody/Anonymous (nobody) Summary: confirmation strings don't work 2.1b2+ Initial Comment: I'm using a CVS tree tha's up to date I got this mail (because my spamassassin is boucing the mails, and the list mostly gets spams). No big deal, except that the URL tells me the confirmation string is incorrect and even if I re-enter it in the "Otherwise, re-enter your confirmation string." page, it still doesn't work. What can I do to help debug this/provide more info? ----- Forwarded message from web-team-request(a)svlug.org ----- From: web-team-request(a)svlug.org To: me@domain X-List-Administrivia: yes Subject: confirm 834fdd960d02e8e77409e82c626b698f96fb434a Your membership in the mailing list web-team has been disabled due to excessive bounces. You will not get any more messages from this list until you re-enable your membership. You will receive 3 more reminders like this before your membership in the list is deleted. To re-enable your membership, you can simply respond to this message (leaving the Subject: line intact), or visit the confirmation page at http://lists.svlug.org/lists/confirm/web-team/834fdd960d02e8e77409e82c626b6… fb434a You can also visit your membership page at http://lists.svlug.org/lists/options/web-team/merlin%40svlug.org (...) ----- End forwarded message ----- ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=563328&group_id…

1 0

Wrong domain choosed when creating a new list (mm2.1b2)
by Danny Terweij 02 Jun '02

02 Jun '02

Hi, These are my mm_cfg settings: DEFAULT_EMAIL_HOST = 'lnx.p-s.nl' DEFAULT_URL_HOST = 'www.p-s.nl' DEFAULT_URL_PATTERN = 'http://%s:81/mailman/' DEFAULT_HOST_NAME = DEFAULT_URL_HOST DEFAULT_URL = DEFAULT_URL_PATTERN % DEFAULT_URL_HOST VIRTUAL_HOST_OVERVIEW = 0 When i do creating a new list : ./newlist [root@lnx bin]# ./newlist Enter the name of the list: testlist-1 Enter the email of the person running the list: danny(a)terweij.nl Initial testlist-1 password: [aliases shown] Hit enter to notify testlist-1 owner... When i hit it and check my mailbox of danny(a)terweij.nl : mailman-admin(a)www.p-s.nl <mailman-admin(a)www.p-s.nl> wrote: > The mailing list `testlist-1' has just been created for you. The > following is some basic information about your mailing list. It is using DEFAULT_URL_HOST or DEFAULT_HOST_NAME instead of DEFAULT_EMAIL_HOST. (in my case... the lists are not runing on www.p-s.nl, but on www.p-s.nl : 81 redirected internaly to my linux host lnx.p-s.nl) Where can i change this? Danny.

2 2