Mailman 3 September 2005 - Mailman-Users

looking for information regarding the private archive session cookies
by michael dunston Sept. 30, 2005

Sept. 30, 2005

Can someone tell me where (in Mailman) the private archive session cookies are being set, or where I might find more information about the use of cookies for enforcing private archive access? I am trying to add this level of protection to a swish-e search CGI. Thanks in advance for any information or direction on where to look.

2 1

doesn't work...
by kalin mintchev Sept. 30, 2005

Sept. 30, 2005

can somebody explain this please?... thanks.... -------------------------------------------- # ./remove_members -n -N aaac johnwang(a)aabdc.com # ./remove_members -a -n -N aaac Traceback (most recent call last): File "./remove_members", line 186, in ? main() File "./remove_members", line 176, in main admin_notif, userack) File "/var/mailman/Mailman/MailList.py", line 990, in ApprovedDeleteMember self.removeMember(emailaddr) File "/var/mailman/Mailman/OldStyleMemberships.py", line 220, in removeMember self.__assertIsMember(member) File "/var/mailman/Mailman/OldStyleMemberships.py", line 113, in __assertIsMember raise Errors.NotAMemberError, member Mailman.Errors.NotAMemberError: johnwang(a)aabdc.com --

1 0

umbrella lists and approved senders
by Gary Casterline Sept. 30, 2005

Sept. 30, 2005

We've set up chain of hierarchical lists to accommodate annual groups. Each year we create a list for the new cohorts: class-of-2003(a)example.tld class-of-2004(a)example.tld class-of-2005(a)example.tld and then add the new class-of list to the umbrella list: alumni(a)example.tld Each list is set to allow postings from subscribers and a small set of approved non-subscribed addresses. I'd like to add these approved addresses to the umbrella list and have messages go through without owner/moderator approval to the sublists. As it is now, we have to add the approved addresses to each sublist. Any suggestions? Thanks, _Gary

2 1

Private archive for list
by Darren G Pifer Sept. 29, 2005

Sept. 29, 2005

I have been trying to get to the private archives of a list but when I click on the URL http://list.odu.edu/private/telephone_logs/ I get nothing on the page. I have been able to access other archives of private lists but for some reason I am not seeing any for this list. I have thought about trying this bin/arch --wipe list-name but I don't want to remove the archives. Is there anything I check for or another script to run to find out if a file is corrupt? Just to be sure, I checked that this list does have a mbox in the archives/private/telephone_logs directory. Darren ODU

2 4

apache errors
by Bryan Irvine Sept. 29, 2005

Sept. 29, 2005

I've jsut installed mailman, and think I've done everything right so far. When I try to browse to the mailman site though it doesn't seem to work properly. I've found other similar questions in the archive, but none of those had any resolution. When I browse to http://10.0.253.82/mailman/ I just get Forbidden You don't have permission to access /mailman/ on this server. Here's my httpd.conf ScriptAlias /mailman/ "/usr/local/lib/mailman/cgi-bin/" <Directory "/usr/local/lib/mailman/cgi-bin"> AllowOverride None Options None Order allow,deny Allow from all </Directory> Ideas? --Bryan

4 7

bounce_info_stale_after
by Bill Moseley Sept. 29, 2005

Sept. 29, 2005

Two questions about bounce processing in 2.1.5. First question: The bounce_info_stale_after is regardless of list traffic? I.e. is the bounce information discarded after bounce_info_stale_after days regardless if there's been any outgoing mail? For example, if you have a list where a message goes out just once every week, but you have bounce_info_stale_after less than a week then will a bouncing address *ever* get disabled? Second questions: After bounce_you_are_disabled_warnings_interval is finished is the address really "removed" as the docs say, or just set to "nomail"? I assume it really means "removed". -- Bill Moseley moseley(a)hank.org

2 1

?? restore only 1 list in backup ".tar"
by Alysson Dias Sept. 29, 2005

Sept. 29, 2005

Hi.... How I restore backup (file mailman.tar of complete /home/mailman) of only 1 list in the server?

2 1

Re: [Mailman-Users] Small reply address problem
by lkolchin＠univ.haifa.ac.il Sept. 29, 2005

Sept. 29, 2005

Hi, There is a known problem with Microsoft E-mail clients. Client shows the Sender and not From address, this is not a standart behavior, but hey, microsoft don't give a f... about standarts, they make standarts of their own. Just try to use Kmail or another normal mail client and you'll see that the problem gone. Regards, Leon Kolchinsky -----Original Message----- From: mailman-users-bounces+lkolchin=univ.haifa.ac.il(a)python.org [mailto:mailman-users-bounces+lkolchin=univ.haifa.ac.il@python.org] On Behalf Of Sythos Sent: Friday, September 23, 2005 3:35 PM To: mailman-users(a)python.org Subject: Re: [Mailman-Users] Small reply address problem On Fri, Sep 23, 2005 at 12:42:37PM +0100, paul collen wrote: > I was wondering if someone could help with a small annoying problem. > I've inherited a mailman system (2.1.5) but I'm not exactly up to > speed with Linux and GNU software (but I'm trying). The problem we > have is that I can't seem to change the display name of the reply > address. When you receive an email from our live digi-tech list or > even from a test list I've setup it says it's come from > bounces-digi-tech@ or bounces-test@. I've looked through the admin > pages and I've forced the reply address to be digi-tech@ and this > changes the actual reply address to digi-tech@ or test@ but the > display names are still prefixed with bounces-... Is this prefix hidden in a text file somewhere? In admin panel (via web) force "reply-to" header overwrite and set what you want -- Sythos - http://www.sythos.net () ASCII Ribbon Campaign - against html/rtf/vCard in mail /\ - against M$ attachments ------------------------------------------------------ Mailman-Users mailing list Mailman-Users(a)python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/lkolchin%40univ.haifa.… Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp

5 4

subscription via -request
by Jim Savoy Sept. 29, 2005

Sept. 29, 2005

Hi all, I was wondering if there is a way to silently subscribe people to a list via the -request command processor (ie sending email commands to listname-request)? If I send the command: subscribe password nodigest address=janedoe(a)hotmail.com it works fine, but janedoe(a)hotmail.com is then sent a message asking that she confirm the subscription by clicking a link. Our users are confused enough as it is, and we would like to avoid this step. I realize that the confirmation step was created to prevent any old yahoo from subscribing people to lists without their consent, but how would any old yahoo know what the list password is? Seems like an unnecessary extra layer of protection. We are running Mailman 2.1.5. Thanks! - jim - PS I realize that we can silently subscribe people via the GUI and the command line, but we wish to do it via email and -request processor only.

2 1

Unable to create new mail list
by Elvis Fernandes Sept. 29, 2005

Sept. 29, 2005

Hello, I am setting up a brand new mailman server. After doing per the documentation, I tried creating a "testing" test mail list. However, I get an error that says "illegal list name: testing@myhost Any idea's on what I am missing? Here is the string. Thanks Elvis # ./newlist testing Enter the email of the person running the list: elvis.fernandes(a)am.necel.com Initial testing password: Create a new, unpopulated mailing list. Usage: ./newlist [options] [listname [listadmin-addr [admin-password]]] Options: -l language --language=language Make the list's preferred language `language', which must be a two letter language code. -u urlhost --urlhost=urlhost Gives the list's web interface host name. -e emailhost --emailhost=emailhost Gives the list's email domain name. -q/--quiet Normally the administrator is notified by email (after a prompt) that their list has been created. This option suppresses the prompt and notification. -h/--help Print this help text and exit. You can specify as many of the arguments as you want on the command line: you will be prompted for the missing ones. Every Mailman list has two parameters which define the default host name for outgoing email, and the default URL for all web interfaces. When you configured Mailman, certain defaults were calculated, but if you are running multiple virtual Mailman sites, then the defaults may not be appropriate for the list you are creating. You also specify the domain to create your new list in by typing the command like so: newlist --urlhost=www.mydom.ain mylist where `www.mydom.ain' should be the base hostname for the URL to this virtual hosts's lists. E.g. with this setting people will view the general list overviews at http://www.mydom.ain/mailman/listinfo. Also, www.mydom.ain<http://www.mydom.ain/> should be a key in the VIRTUAL_HOSTS mapping in mm_cfg.py/Defaults.py if the email hostname to be automatically determined. If you want the email hostname to be different from the one looked up by the VIRTUAL_HOSTS or if urlhost is not registered in VIRTUAL_HOSTS, you can specify `emailhost' like so: newlist --urlhost=www.mydom.ain --emailhost=mydom.ain mylist where `mydom.ain' is the mail domain name. If you don't specify emailhost but urlhost is not in the virtual host list, then mm_cfg.DEFAULT_EMAIL_HOST will be used for the email interface. For backward compatibility, you can also specify the domain to create your new list in by spelling the listname like so: mylist(a)www.mydom.ain where www.mydom.ain <http://www.mydom.ain/> is used for `urlhost' but it will also be used for `emailhost' if it is not found in the virtual host table. Note that '--urlhost' and '--emailhost' have precedence to this notation. If you spell the list name as just `mylist', then the email hostname will be taken from DEFAULT_EMAIL_HOST and the url will be taken from DEFAULT_URL (as defined in your Defaults.py file or overridden by settings in mm_cfg.py). Note that listnames are forced to lowercase. Illegal list name: testing@myhost #

2 1