Mailman 3 January 2007 - Mailman-Users

Changing Unsubscribe to NoMail
by Gerald Drouillard Jan. 22, 2007

Jan. 22, 2007

I have a list in which I would like the unsubscribe to set the nomail flag on instead of removing them from the list. The reason being that the list administrators tend to upload new email addresses periodically and we would not like to add someone that has already unsubscribed. Is there a magic switch that will turn unsubscribe behavior into nomail behavior? The mailman command line does not support the nomail option?

2 1

/bin/sh: mailman: command not found
by Ken Cheney Jan. 22, 2007

Jan. 22, 2007

I get a million of these messages from Cron. Subject: [Mailman] Cron <mailman@listserv> mailman/usr/lib/mailman/cron/gate_news I have read that it is because of something messed up with the crontab.in or soemthing. Something to do with the place #6 or something like that. I really did not find the message helpful at all since I know very little about cron in general. Can someone help? Otherwise I have Mailman fully functional on Fedora Core 6 and love it! -----… [View More]

2 1

problems with gid when installing
by Peter Coolen Jan. 22, 2007

Jan. 22, 2007

Hi All, I tried to install mailman on my slackware system with postfix (mysql virtual domains) and apache.. I followed the whole mnual ,except the thing about the virtual domains.. I will do this later on. When i want to go to the page www.domain.tld/mailman/create, I get the error below: Mailman CGI error!!! %s --with-cgi-gidwebCGI--with-mail-gidmail-SThe Mailman CGI wrapper encountered a fatal error. This entry is being stored in your syslog:Group mismatch error. Mailman expected the %… [View More]

2 17

domain in attached file url
by ArteryPlanet.Net :: Manuel Kissoyan Jan. 22, 2007

Jan. 22, 2007

I have the scrub list attatchment option turned on for this mailing lists so when an attatchment is sent to the list rather than emailing it to the subscribers, it creates a link at the bottom of the message that you are supposed to be able to click on and it downloads it via web browser. It used to work fine but for some reason lately it doesnt format the link correctly. In other words, its not adding the domain name to the front of the link. A person has to copy and paste the link … [View More]

2 2

Archivierung
by Michael Barth Jan. 22, 2007

Jan. 22, 2007

Hallo Mailman-Gemeinde, ich wollte fragen, ob es möglich ist bei deaktivierter Archivierungsoption auch die Ablage der Attachements in /usr/local/mailman/archives/private//attachements zu unterbinden und wenn ja, wie? Danke Micha

1 0

Adding disclaimer to message footer via command line
by Leon Kolchinsky Jan. 22, 2007

Jan. 22, 2007

Hello All, Our management decided to add disclaimer to every footer in Digest and Non-digest options. I know that this is a bad netiquette but I have no choice. I have a lot of mailinglists running on my server and I though that may be there is a way to do this addition with some script via command line and add this to all lists, and save from myself doing it via web-interface enormous times. Is there a way of doing that? Best Regards, Leon Kolchinsky

2 2

Bypass List Moderation
by Karl Zander Jan. 21, 2007

Jan. 21, 2007

It is possible to get around list moderation? We have a closed, moderated list. There is only one list administrator. He claims he did not approve a message that was sent on to the list. Is it possible to craft a message that already contains the X-Mailman-Approved-At: header and get by moderation? Are there logs of moderations actions? --Karl

2 3

htdig authorization problem
by Hank van Cleef Jan. 21, 2007

Jan. 21, 2007

I just succeeded in blowing away my spooled mail, so no longer have what was in this thread (yes, I can look at the mailman-users archives). Thankyew Thunderbird, which linked to my local spool instead of the external one it was supposed to. Getting back to the salient points: If the htdig access ever actually worked in the private directory, I can't confirm reliably. Inputs from my listers aren't sufficiently accurate for me to work with (this would be the third case where some of … [View More]them thought it was working and it wasn't). The error log indicates failures from the time that the archives and htdig data base were built, and are in sufficient quantity that I believe that this problem has existed since I brought them on line. I have checked the problem with a Firefox 1.5.0.9, a late Mozilla build and Netscape 4.78) ancient, but it's the Solaris 9 default). The Apache is 1.13.34 (Solaris 9 build). There is a later version in the Solaris 9 patch cluster, but I am not going to run patching on this box until I can finish building the Mailman installation on another box and switch over. I doubt that this is an Apache problem. The httpd.conf on this site is "right out of the Mailman install guide." I am not using https, and all of the mailman stuff is in one directory tree without symbolic links. Default URL in mm_cfg.py is for the DNS domain being used, and I ran withlist/fix_url to point to that domain before going on-line. Running with Firefox, I cleared the cache and all cookies, then retested as a user, going from the listinfo page. This URL is: http://www.mercedeslist.com/mailman/listinfo/mercedes The archives page is: http://www.mercedeslist.com/mailman/private/mercedes/ As I have said, that directory tree is all in one place on one filesystem. Running as a user, after having assured that Firefox is "cold" (cache cleared, one cookie present), I can get an article to display through htdig by filling in either the account name or the password. Both are not needed. However, for the user account, the name or password has to be correct. If one of the two fields is correct, bogus information in the other does not prevent access. However, in true user state, one field has to be correct. The cookie held by the browser does not go away, and does not appear to be altered. It is valid for authorization to go to the options field without having to revalidate. Hank -- Hank van Cleef (vancleef(a)lostwells.net, hvanclee(a)nyx.net) 1986 420SEL "A stranger in paradise" (Fremont Co. Wyoming) 1986 GMC 1500 6.2 diesel pickup "Seen one, seen them all" [View Less]

2 3

doc patch for postfix virtual domain config
by Paul Fox Jan. 20, 2007

Jan. 20, 2007

hi -- i'm new at both mailman and postfix, but i thought i'd try and reduce someone else's pain when trying to do what i've been trying to do. i spent a bunch of time last night very confused because i couldn't do a configuration of a mailman list in a postfix virtual domain. from what i read in the docs, it seemed like it should "Just Work". and it would have, except i made one crucial mistake. it turns out that the information i needed to do it right was in the output of "bin/newlist -h", … [View More]but not in any other doc that i found. (it may be elsewhere, i just didn't find it elsewhere, even after a lot of searching.) the missing piece was that when setting up the list, _that's_ when you have to declare it as being in a virtual domain. not later. and while there's an oblique reference in section 6.1.2 to the "host_name attribute" of a list, this didn't jump out at me, and it might not have helped -- it's the only reference in the docs. here's a doc patch that would have helped me a lot. (i don't have tex or texinfo installed, so i wasn't able to actually try this patch.) it might also be worth adding mention of the postfix-to-mailman-2.1.py script that's fairly widely found when googling, if only to explain why one doesn't need it. i understand that while this works (and i assume is similar to fil(a)rezo.net's technique, referenced in the docs), it's sub-optimal especially in the face of spam dictionary attacks. (at least, i read that somewhere on the internet last night -- so it must be true!) anyway, i didn't add anything about this, because i don't really feel qualified, but again, it would have helped. thanks, paul --- mailman-install.tex.orig Sat Jan 20 14:46:39 2007 +++ mailman-install.tex Sat Jan 20 15:03:19 2007 @@ -555,6 +555,23 @@ against the \var{host_name} attribute of mailing lists objects, and must be an exact match. +Note that virtual alias mappings will only be created (obviously) by +\program{bin/genaliases} for lists which are addressed in a virtual domain. +Thus, if you ran +\begin{verbatim} + % bin/newlist mylist +\end{verbatim} +then you will not get virtual alias mappings in +\file{/usr/local/mailman/data/virtual-mailman}, but if you ran +\begin{verbatim} + % bin/newlist mylist(a)dom2.ain +\end{verbatim} +(which will set the \var{host_name} attribute for the list) then +you will. (You will, however, get direct alias entries, i.e. in +\file{/usr/local/mailman/data/aliases}, for both virtual and non-virtual +lists -- both sets of entries are necessary for lists in virtual +domains to work.) + Here's an example. Say that Postfix is configured to handle the virtual domains \code{dom1.ain}, \code{dom2.ain}, and \code{dom3.ain}, and further that in your \file{main.cf} file you've got the following settings: =--------------------- paul fox, pgf(a)foxharp.boston.ma.us (arlington, ma, where it's 21.0 degrees) [View Less]

1 0

Mailman users list
by Charles M. Owen Jan. 20, 2007

Jan. 20, 2007

I gather from what I read, that if I don't own the server my list is hosted, there is no way to get a full membership list with emails and names. I have found some reference to changing the general information page, but again I don't own the installed instance of Mailman. Charles

3 6