Mailman 3 September 2005 - Mailman-coders

[ mailman-Patches-820723 ] Mailman/pipermail/MHonArc integration patch
by SourceForge.net 24 Sep '05

24 Sep '05

Patches item #820723, was opened at 2003-10-09 16:19 Message generated for change (Comment added) made by ppsys You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=820723&group_i… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Pipermail Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Richard Barrett (ppsys) Assigned to: Nobody/Anonymous (nobody) Summary: Mailman/pipermail/MHonArc integration patch Initial Comment: This patch tightly integrates the MHonArc mail-to-HTML convertor with Mailman and its internal pipermail archiving code. The purpose of the patch is to produce a fusion of (hopefully) the best features of pipermail and MHonArc for handling Mailman mailing list archives. For more detail see patch content or http://www.openinfo.co.uk/mailman/patches/mhonarc/index.html ---------------------------------------------------------------------- >Comment By: Richard Barrett (ppsys) Date: 2005-09-23 21:45 Message: Logged In: YES user_id=75166 mhonarc-2.1.6-0.2.patch.gz corrects an error in the modified code of $prefix/bin/arch introduced by the mhonarc-2.1.6-0.1.patch.gz - the problem was not present in patches for previous MM versions. In some circumstances, after running $prefix/bin/arch --wipe, subsequent post to a list my be generated using the wrong archiver. Examining index pages in the archives of a list will show if this problem has affected that list. Reinstallation with this revised patch and rerunning $prefix/bin/arch --wipe should resolve the problem. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2005-08-23 17:43 Message: Logged In: YES user_id=75166 mhonarc-2.1.6-0.1.patch.gz is a MM 2.1.6 compatible version of the patch ---------------------------------------------------------------------- Comment By: dfragos (dfragos) Date: 2005-07-21 15:24 Message: Logged In: YES user_id=1310569 what about MM 2.1.6? ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2004-08-03 10:04 Message: Logged In: YES user_id=75166 mhonarc-2.1.5-0.1.patch.gz is a MM 2.1.5 compatible version of the patch ---------------------------------------------------------------------- Comment By: Martin Mokrejs (mmokrejs) Date: 2004-04-19 23:53 Message: Logged In: YES user_id=696559 I've applied this patch(mhonarc-2.1.4-0.1.patch.gz) and it works great for me. Would someone apply to offcial cvs tree? Thanks. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2004-01-02 15:32 Message: Logged In: YES user_id=75166 mhonarc-2.1.4-0.1.patch is a MM 2.1.4 compatible version of this patch ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-10-22 14:32 Message: Logged In: YES user_id=75166 mhonarc-2.1.3-0.6.patch better supports the use of MHonArc -saveresources option. Also fixes minor HTML syntax error in mhonarc.mrc and author.mrc that affected generated date and author index pages. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-10-14 05:49 Message: Logged In: YES user_id=75166 With mhonarc-2.1.3-0.4.patch, the default path to MHonArc itself defined in Defaults.py is the empty string and, until this is changed, the option to select MHonArc instead of pipermail for per-list archiving is not offered on the web admin GUI. ---------------------------------------------------------------------- Comment By: Richard Barrett (ppsys) Date: 2003-10-10 17:51 Message: Logged In: YES user_id=75166 Under some circumstances, when a single message is passed to MHonArc for archiving via a pipe, MHonArc may finish its processing and exit, closing its STDIN before the Mailman process that invoked it has finished output of the message to the pipe. Mistakenly, the patched pipermail code treated this as an error. mhonarc-2.1.3-0.3.patch corrects this mistake. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=820723&group_i…

1 0

[ mailman-Patches-1301983 ] Fix for lack of date header in new list notification emails
by SourceForge.net 24 Sep '05

24 Sep '05

Patches item #1301983, was opened at 2005-09-23 20:00 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1301983&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: list administration Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Bjorn-Erik Townsend (eriktown) Assigned to: Nobody/Anonymous (nobody) Summary: Fix for lack of date header in new list notification emails Initial Comment: This is a fix for Bug 1212066, where the notification email sent to the Mailman site owner after a new list is created using the Web UI does not include a Date header as required by RFC 2822. The underlying issue appears to be that the notification email is being sent with an outdated or incorrect method (outq.enqueue instead of msg.send). I simply took the same code that is used in the newlist script to do this and added it here, along with the code that it ensures that the header uses the site owner list's preferred language. This patch also includes a fix for a bug that has not been reported, in which notification emails sent upon list removal experience the same issue. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1301983&group_…

1 0

[ mailman-Patches-1123383 ] Daily Status Report script...
by SourceForge.net 23 Sep '05

23 Sep '05

Patches item #1123383, was opened at 2005-02-15 20:14 Message generated for change (Comment added) made by shub You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1123383&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: list administration Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Brad Knowles (shub) Assigned to: Nobody/Anonymous (nobody) Summary: Daily Status Report script... Initial Comment: Folks, I quickly whacked together a Daily Status Report script for Mailman (using Bourne shell, not Python ;), and thought that other folks might be interested in seeing it. The basic concept is a program that gets fired off at 23:59 every night, and goes through a variety of log files looking for entries specific to that date, and indicating problems or certain types of activity that might be of interest to someone trying to administer the server. It also does an "ls -la" of /usr/local/mailman/qfiles/*, so that you can see what is in the queue at the time of the running of the script. My concept was that this daily report would get e-mailed to the admin, or posted to a "reports" mailing list, where they could be archived and kept for future reference. The script does not (yet) do any statistics calculations, although it should be relatively easy to hack together some basic stats using awk, sort, etc.... Anyway, I thought I'd share it and let folks take a look at it, and if anyone has any recommended improvements, we can incorporate those and share them back out with everyone. The code is written under a BSD-style license, so if you don't want to contribute any changes back to me, that's okay. Of course, I would prefer that you did, but I leave the choice up to you. ---------------------------------------------------------------------- >Comment By: Brad Knowles (shub) Date: 2005-09-22 23:17 Message: Logged In: YES user_id=18417 Okay, I took Mark's comments and incorporated them. Adrian Wells also pointed out a log file difference between Mailman 2.1.5 and 2.1.6 that caused the summary of the "smtp" log to be munged. I've now fixed these bugs, deleted the old file, and uploaded the new one (version 0.0.12). Thanks! ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2005-09-11 02:22 Message: Logged In: YES user_id=1123998 Oooops! I mistakenly thought I could add the mmdsr.patch as a downloadable file, but I can't so here it is. Watch out for wrapped lines ... --- mmdsr.orig 2005-09-06 20:37:53.000000000 -0700 +++ mmdsr 2005-09-10 18:33:14.532393572 -0700 @@ -132,6 +132,7 @@ MMDIR="/usr/local/mailman" TMPDIR="/tmp" +LOGDIR="/var/log/mailman" ############################################################################### # Maximum number of subdirectory entries to display in report @@ -234,9 +235,9 @@ $TOUCH $TMPLOG echo "Log file: $LOG" >> $TMP echo "==============================" >> $TMP - $GREP -si "^$DAY [0-9][0-9:]* $YEAR" logs/$LOG >> $TMPLOG + $GREP -si "^$DAY [0-9][0-9:]* $YEAR" $LOGDIR/$LOG >> $TMPLOG - if [ -f "logs/${LOG}" ] ; then + if [ -f "$LOGDIR/${LOG}" ] ; then if [ "${LOG}" = "post" ] ; then @@ -304,9 +305,9 @@ $TOUCH $TMPLOG echo "Log file: $LOG" >> $TMP echo "==============================" >> $TMP - $GREP -si "^$DAY [0-9][0-9:]* $YEAR" logs/$LOG >> $TMPLOG + $GREP -si "^$DAY [0-9][0-9:]* $YEAR" $LOGDIR/$LOG >> $TMPLOG - if [ -f "logs/${LOG}" ] ; then + if [ -f "$LOGDIR/${LOG}" ] ; then if [ "${LOG}" = "error" ] ; then @@ -453,4 +454,4 @@ $CAT $TMP fi -$RM $TMP +$RM -f $TMP $TMPLOG ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2005-09-11 02:16 Message: Logged In: YES user_id=1123998 I tried the script and other than the expected site specific changes, I found two issues which are both addressed by the patch in the mmdsr.patch file. 1) Mailman's log files are not necessarily in $var_prefix/logs/ - they can be in any directory. The patch adds a LOGDIR directory independant of MMDIR. 2) The $TMPLOG file is not removed at completion. The patch removes it. ---------------------------------------------------------------------- Comment By: Brad Knowles (shub) Date: 2005-09-06 14:06 Message: Logged In: YES user_id=18417 Okay, I've deleted the old version of the mmdsr script that was attached, and uploaded the latest version. This is what we're currently using to monitor the lists on python.org, and we have found it very useful. Any comments you may have will be appreciated. ---------------------------------------------------------------------- Comment By: Brad Knowles (shub) Date: 2005-02-22 20:10 Message: Logged In: YES user_id=18417 The UID variable in the current code was already replaced by MYUID, because I got complaints on other platforms. But UID wasn't available to me as a useful constant, so I had to use something else to obtain the value. The recommended patch from tgc99 does work, and I will be uploading a new version of the code soon. ---------------------------------------------------------------------- Comment By: adrianwi (adrianwi) Date: 2005-02-22 15:22 Message: Logged In: YES user_id=1175103 Use of variable named UID does work well with OS X (version 10.2.8). Apparently the variable UID is a constant already in use. When trying to the run the script without modification, I was receiving the following error message: UID: readonly variable This issue was resolved by changing the name of variable, UID, to something else, such as MMUID. Works fine with this change. As an aside (& for what it is worth), the UID grab command suggested by tgc99 on 2005-02-16 03:15 works on this system (OS X - version 10.2.8) ---------------------------------------------------------------------- Comment By: Tom G. Christensen (tgc99) Date: 2005-02-16 08:15 Message: Logged In: YES user_id=1159458 The current UID grab command doesn't work on Solaris (2.6 & 8 tested). I'd recommend this instead: ps -o user -p $$|tail -1 This is tested and works on RH 6.2, RH 7.3, RHEL 2.1, RHEL3, FC3, FreeBSD 4.9, Solaris 2.6, 8. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1123383&group_…

1 0

[ mailman-Bugs-1298841 ] withlist locks with -l and -a switches
by SourceForge.net 22 Sep '05

22 Sep '05

Bugs item #1298841, was opened at 2005-09-22 10:17 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1298841&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: command line scripts Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: adrianwi (adrianwi) Assigned to: Nobody/Anonymous (nobody) Summary: withlist locks with -l and -a switches Initial Comment: The following is from <http://www.mail-archive.com/mailman-users%40python.org/msg34340.html> Thanks to Mark for the reply and explaniation. This probably belongs in both the command line scripts and documentation category. >customchange.py is located at the root installation directory >of Mailman. >It contains: > ># Python function to make custom changes >def customchange(m): > curlist = m.real_name > curlist = curlist.lower() > print 'Current list is: ' + curlist > if curlist.startswith('apples'): > print 'Starts with apples! Current host_name is: ' + m.host_name > print 'Changing hostname now...' > m.host_name = 'lists.newlistname.org' > m.Save() > > >This script is then run with withlist: > >./withlist -a -l -r customchange > > >After preforming this, I noticed that the web interface for lists >are not accessible and that the locks directory contains at >least two lock files for every list. This probably should be considered a bug in withlist or at least a documentation deficiency. The problem is when running withlist with -l and -a switches, only the last list is unlocked by withlist. Thus you need to unlock the lists in your script. In your example you could do this two ways 1) make sure you unlock every list, processed or not. # Python function to make custom changes def customchange(m): curlist = m.real_name curlist = curlist.lower() print 'Current list is: ' + curlist if curlist.startswith('apples'): print 'Starts with apples! Current host_name is: ' + m.host_name print 'Changing hostname now...' m.host_name = 'lists.newlistname.org' m.Save() m.Unlock() 2) run withlist with -a but without -l and only lock the lists you're changing. # Python function to make custom changes def customchange(m): curlist = m.real_name curlist = curlist.lower() print 'Current list is: ' + curlist if curlist.startswith('apples'): m.Lock() print 'Starts with apples! Current host_name is: ' + m.host_name print 'Changing hostname now...' m.host_name = 'lists.newlistname.org' m.Save() m.Unlock() 3) Safer still is like 2) with the addition of try: finally: # Python function to make custom changes def customchange(m): curlist = m.real_name curlist = curlist.lower() print 'Current list is: ' + curlist if curlist.startswith('apples'): try: m.Lock() print 'Starts with apples! Current host_name is: ' + m.host_name print 'Changing hostname now...' m.host_name = 'lists.newlistname.org' m.Save() finally: m.Unlock() -- Mark Sapiro ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1298841&group_…

1 0

[ mailman-Patches-1298355 ] Select language(s) when install
by SourceForge.net 22 Sep '05

22 Sep '05

Patches item #1298355, was opened at 2005-09-22 05:29 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1298355&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: configure/install Group: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 5 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Tokio Kikuchi (tkikuchi) Summary: Select language(s) when install Initial Comment: While the number of translated languages is growing, most users are using only a few languages. With this patch, the site admin can select his/her required languages by an option to the configure script by `--with-languages' and can considerably reduce the install size. This patch is for 2.2.0a0 (most recent CVS as of writing) but also applicable to 2.1.6 except that you may have to regenerate configure script by invoing autoconf command. Patch usage: % cd mailman (src directory) % patch -p0 < /path/to/install_selected_language.patch.txt Configure usage: % ./configure --with-languages="ja fr" ... en+ja+fr % ./configure --with-languages="" ... all available languages % ./configure .... all available languages % ./configure --with-languages="none" ... English only Japanese and Korean codecs are no longer installed by `make install' but availability is checked during the configure run and urge to install if they are absent when CJK languages are included in the language list. I hope skilled developers can review this patch before I check in to the CVS. ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-09-22 05:35 Message: Logged In: YES user_id=67709 Oops, I forgot to check `Upload and Attach a File'. ;-) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1298355&group_…

1 0

[ mailman-Patches-1298355 ] Select language(s) when install
by SourceForge.net 22 Sep '05

22 Sep '05

Patches item #1298355, was opened at 2005-09-22 05:29 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1298355&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: configure/install Group: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 5 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Tokio Kikuchi (tkikuchi) Summary: Select language(s) when install Initial Comment: While the number of translated languages is growing, most users are using only a few languages. With this patch, the site admin can select his/her required languages by an option to the configure script by `--with-languages' and can considerably reduce the install size. This patch is for 2.2.0a0 (most recent CVS as of writing) but also applicable to 2.1.6 except that you may have to regenerate configure script by invoing autoconf command. Patch usage: % cd mailman (src directory) % patch -p0 < /path/to/install_selected_language.patch.txt Configure usage: % ./configure --with-languages="ja fr" ... en+ja+fr % ./configure --with-languages="" ... all available languages % ./configure .... all available languages % ./configure --with-languages="none" ... English only Japanese and Korean codecs are no longer installed by `make install' but availability is checked during the configure run and urge to install if they are absent when CJK languages are included in the language list. I hope skilled developers can review this patch before I check in to the CVS. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1298355&group_…

1 0

[ mailman-Bugs-1059637 ] Leave choice on obfuscation method to sysadmin
by SourceForge.net 21 Sep '05

21 Sep '05

Bugs item #1059637, was opened at 2004-11-03 12:14 Message generated for change (Comment added) made by magicfab You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1059637&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Pipermail Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Alster (alster) Assigned to: Nobody/Anonymous (nobody) Summary: Leave choice on obfuscation method to sysadmin Initial Comment: As far as I know, currently the way pipermail obfuscates email addresses is hardcoded to "user at domain.com". This is really easy to harvest. It may be a better idea to leave the method of obfuscation to the mailman (sys)admin (not list admin). This will result in increased diversity of obfuscation methods on the several pipermail setups and thus to decreased harvesting. ---------------------------------------------------------------------- Comment By: Fabián A. Rodríguez S. (magicfab) Date: 2005-09-21 12:21 Message: Logged In: YES user_id=92045 This would also affect messages that are already archived or the existing methods for archival of messages. See this in the Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq04.034.htp Some docs on making your lists less vulnerable to harvesting: http://www.list.org/mailman-member/node40.html Other related threads: http://mail.python.org/pipermail/mailman-developers/2004-February/016569.ht… http://zope.org/Members/bwarsaw/MailmanDesignNotes/MailmanProblems ---------------------------------------------------------------------- Comment By: Fabián A. Rodríguez S. (magicfab) Date: 2005-09-21 12:03 Message: Logged In: YES user_id=92045 I agree this should be addressed as more and more bots & agents harvest public lists for this information. Even private lists that are not tuning 2.1.6 may be vulnerable to this harvesting method. I'd like to suggest to use a random obfuscation method *for each message* . ---------------------------------------------------------------------- Comment By: Jean Delvare (khali) Date: 2005-07-18 06:15 Message: Logged In: YES user_id=66405 I would second this request. The current obfuscation scheme is next to useless. I understand that it would make little sense hardcoding a more complex obfuscation scheme, as it could easily be reverse-engineered. However, if the obfuscation method was left to the administrator, there would be virtually as many different obfuscation schemes as sites, so reverse-engineering would be much more difficult, if impossible. As a side note, I wonder why there is no option in mailman to plain discard the e-mail addresses from the Archive. This should be even more simple to implement, and sufficient at least for my own needs. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1059637&group_…

1 0

[ mailman-Bugs-1059637 ] Leave choice on obfuscation method to sysadmin
by SourceForge.net 21 Sep '05

21 Sep '05

Bugs item #1059637, was opened at 2004-11-03 12:14 Message generated for change (Comment added) made by magicfab You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1059637&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Pipermail Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Alster (alster) Assigned to: Nobody/Anonymous (nobody) Summary: Leave choice on obfuscation method to sysadmin Initial Comment: As far as I know, currently the way pipermail obfuscates email addresses is hardcoded to "user at domain.com". This is really easy to harvest. It may be a better idea to leave the method of obfuscation to the mailman (sys)admin (not list admin). This will result in increased diversity of obfuscation methods on the several pipermail setups and thus to decreased harvesting. ---------------------------------------------------------------------- Comment By: Fabián A. Rodríguez S. (magicfab) Date: 2005-09-21 12:03 Message: Logged In: YES user_id=92045 I agree this should be addressed as more and more bots & agents harvest public lists for this information. Even private lists that are not tuning 2.1.6 may be vulnerable to this harvesting method. I'd like to suggest to use a random obfuscation method *for each message* . ---------------------------------------------------------------------- Comment By: Jean Delvare (khali) Date: 2005-07-18 06:15 Message: Logged In: YES user_id=66405 I would second this request. The current obfuscation scheme is next to useless. I understand that it would make little sense hardcoding a more complex obfuscation scheme, as it could easily be reverse-engineered. However, if the obfuscation method was left to the administrator, there would be virtually as many different obfuscation schemes as sites, so reverse-engineering would be much more difficult, if impossible. As a side note, I wonder why there is no option in mailman to plain discard the e-mail addresses from the Archive. This should be even more simple to implement, and sufficient at least for my own needs. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1059637&group_…

1 0

[ mailman-Bugs-1230865 ] spam filters get removed when changing other privacy pages
by SourceForge.net 21 Sep '05

21 Sep '05

Bugs item #1230865, was opened at 2005-07-01 10:51 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1230865&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: security/privacy Group: None >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Alex (ams001) Assigned to: Nobody/Anonymous (nobody) Summary: spam filters get removed when changing other privacy pages Initial Comment: Originally reported in 1020013 http://sourceforge.net/tracker/?group_id=103&atid=100103&func=detail&aid=10… This problem still very annoyingly ocurrs in the 2.1.6 release which appears not to include the patch submitted. I have updated the patch against 2.1.6 and included it below. ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-09-21 04:30 Message: Logged In: YES user_id=67709 Fixed in CVS. (2.2.0a0) ---------------------------------------------------------------------- Comment By: Alex (ams001) Date: 2005-07-08 17:29 Message: Logged In: YES user_id=1156173 Unfortunately this patch does not fix all occurances of the problem. I can reliably "lose" all spam filters entered by going directly to the spam filter section after logging out. To reproduce: 1. Login as list admin 2. Goto Privacy / Spam filters and create a spam filter 3. Logout 4. Modify logout URL from .../<listname>/logout to .../<listname>/privacy/spam 5. Enter password and observe absense of Spam filter. The worrying thing is that it appears to be the login through the privacy/spam script that kills the spam filter. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1230865&group_…

1 0

[ mailman-Bugs-1296367 ] can't subscribe - does not like recipient
by SourceForge.net 20 Sep '05

20 Sep '05

Bugs item #1296367, was opened at 2005-09-20 14:56 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1296367&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: (un)subscribing Group: None Status: Open Resolution: None Priority: 5 Submitted By: troels knak-nielsen (swaxi) Assigned to: Nobody/Anonymous (nobody) Summary: can't subscribe - does not like recipient Initial Comment: I have a general problem subscribing to lists at sourceforge. I get the confirmation-mail, which tells me to reply. When I do, I recieve a failure-notice from my mail-agent. Appearently sourceforge doesn't like me. How's that ? Copy of failurenotice below : Return-Path: <> Delivered-To: troels(a)kyberfabrikken.dk Received: (qmail 17352 invoked for bounce); 20 Sep 2005 12:40:39 -0000 Date: 20 Sep 2005 12:40:39 -0000 From: MAILER-DAEMON(a)freja.yanet.dk To: troels(a)kyberfabrikken.dk Subject: failure notice X-UM-Flags: \SEEN Hi. This is the qmail-send program at freja.yanet.dk. I'm afraid I wasn't able to deliver your message to the following addresses. This is a permanent error; I've given up. Sorry it didn't work out. <simpletest-support-request(a)lists.sourceforge.net>: 66.35.250.206 does not like recipient. Remote host said: 550-Verification failed for <troels(a)kyberfabrikken.dk> 550-Called: 81.7.136.34 550-Sent: RCPT TO:<troels(a)kyberfabrikken.dk> 550-Response: 553 sorry, your envelope sender has been denied (#5.7.1) 550 Sender verify failed Giving up on 66.35.250.206. --- Below this line is a copy of the message. Return-Path: <troels(a)kyberfabrikken.dk> Received: (qmail 17341 invoked by uid 613); 20 Sep 2005 12:40:32 -0000 Received: from localhost (HELO Yanetdkwebmail) (127.0.0.1) by localhost with SMTP; 20 Sep 2005 12:40:32 -0000 Received: from client 212.242.176.101 for UebiMiau2.7 (webmail client); Tue, 20 Sep 2005 14:40:32 +0100 Date: Tue, 20 Sep 2005 14:40:32 +0100 From: "Troels Knak-Nielsen" <troels(a)kyberfabrikken.dk> To: simpletest-support-request(a)lists.sourceforge.net Reply-to: "Troels Knak-Nielsen" <troels(a)kyberfabrikken.dk> Subject: SV: Simpletest-support -- confirmation of subscription -- request 766612 X-Priority: 3 X-Mailer: Yanet.dk - webmail X-Original-IP: 212.242.176.101 Content-Transfer-Encoding: 8bit Return-Path: troels(a)kyberfabrikken.dk X-MSMail-Priority: Medium Importance: Medium Content-Type: text/plain; charset="iso-8859-1"; MIME-Version: 1.0 -- mvh troels www.kyberfabrikken.dk --------- Original Besked -------- fra: simpletest-support-request(a)lists.sourceforge.net Til: troels(a)kyberfabrikken.dk <troels(a)kyberfabrikken.dk> Emne: Simpletest-support -- confirmation of subscription -- request 766612 Dato: 20/09/05 13:40 > > Simpletest-support -- confirmation of subscription -- request 766612 > > We have received a request from 212.242.176.101 for subscription of > your email address, <troels(a)kyberfabrikken.dk>, to the > simpletest-support(a)lists.sourceforge.net mailing list. To confirm the > request, please send a message to > simpletest-support-request(a)lists.sourceforge.net, and either: > > - maintain the subject line as is (the reply's additional "Re:" is > ok), > > - or include the following line - and only the following line - in the > message body: > > confirm 766612 > > (Simply sending a 'reply' to this message should work from most email > interfaces, since that usually leaves the subject line in the right > form.) > > If you do not wish to subscribe to this list, please simply disregard > this message. Send questions to > simpletest-support-admin(a)lists.sourceforge.net. > > > > > ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1296367&group_…

1 0