From curtis at backupcentral.com Wed Sep 1 08:29:01 2010 From: curtis at backupcentral.com (W. Curtis Preston) Date: Tue, 31 Aug 2010 23:29:01 -0700 Subject: [Mailman-Users] Cannot set digest mode via URL In-Reply-To: References: <92AEA513-B26A-4F11-9F6F-31FA9AD35A07@shub-internet.org> <20100829145910.GG4925@inocybe.localdomain> Message-ID: I asked my hosting company liquidweb to talk to cpanel. Liquidweb has always given me great support (24x7 I might add), but at this point they are at a loss and are as much at the whim of cpanel as I am. Since they do not appear to distribute the source of Mailman with cpanel (at least I can't find it), I have asked Liquidweb to ask cpanel to provide it. In addition, I have asked them to explain why a "real" install of Mailman can do what I'm asking and there's can't. I will keep you abreast of the responses. On Sun, Aug 29, 2010 at 8:43 PM, W. Curtis Preston wrote: > > > On Sun, Aug 29, 2010 at 3:34 PM, Brad Knowles wrote: > >> >> Oh, and for me, it has nothing to do with sullying our reputation. It has >> much more to do with crippling our ability to support our customers, because >> experience has taught us that many of these vendors want to ship code >> without providing any of the actual support costs. >> >> If they're going to externalize onto us (a non-profit, unpaid, volunteer >> organization) all of their customer support costs for this part of their >> commercial package that they may sell for large sums of money, then as I see >> it they owe us one of two things: >> > > Brad you bring up a good point that I don't think everyone is aware of. > Those of using a "commercial distro" of Mailman should get our support for > said installation said group. I suppose if I was doing something normal, I > would. However, I didn't even think to ask them because I figured the > answer would be "You're trying to do WHAT?" Well, that's not supported... > > But you know what? I never even asked, so I think I will. > > > From mark at msapiro.net Wed Sep 1 15:52:19 2010 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 1 Sep 2010 06:52:19 -0700 Subject: [Mailman-Users] Cannot set digest mode via URL In-Reply-To: Message-ID: W. Curtis Preston wrote: >I asked my hosting company liquidweb to talk to cpanel. Liquidweb has >always given me great support (24x7 I might add), but at this point they are >at a loss and are as much at the whim of cpanel as I am. > >Since they do not appear to distribute the source of Mailman with cpanel (at >least I can't find it), I have asked Liquidweb to ask cpanel to provide it. >In addition, I have asked them to explain why a "real" install of Mailman >can do what I'm asking and there's can't. Your problem has nothing to do with cPanel. Perhaps the answer got lost in the noise, but you can find it at . WRT cPanel source, the most significant mods are their own list creation process and their mailman router for exim. See cPanel's mailman installation is at /usr/local/cpanel/3rdparty/mailman on the cPanel server as noted in our FAQ at . -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From joe at free-proxie123.ath.cx Wed Sep 1 16:02:12 2010 From: joe at free-proxie123.ath.cx (Joe Curto) Date: Wed, 01 Sep 2010 16:02:12 +0200 Subject: [Mailman-Users] Mass flag change Message-ID: <4C7E5CE4.9030703@free-proxie123.ath.cx> Hi guys, need an help. I've just created a new list with about 8500 users. Is it possibile (during the creation or after created) to set a flag on or off massively ? Creating the list sets le flag 'text' mail on and I need to set this flag off for all the users. Thank for any help. Joe From mark at msapiro.net Wed Sep 1 16:33:02 2010 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 1 Sep 2010 07:33:02 -0700 Subject: [Mailman-Users] Ban_list In-Reply-To: <4C7D1B58.3000309@dei.uc.pt> Message-ID: Ricardo Ruivo wrote: > there is any option to notify, by email, the user when he attempts to >subscibe and list and his email bellow to ban_list? If the banned user attempts to subscribe by email, he will receive an email response. If he attempts to subscribe via the web, there is no option to send him an email notice. > Another question. It is possible to configure the following message >(thats appers when a ban_list users attens to subscribe by web interface >that mailling list) > >so Subscription results >The email address you supplied is banned from this mailing list. If you >think this restriction is erroneous, please contact the list owners at >[EMAIL]. This message is hard coded in the Mailman/Cgi/subscribe.py module. You would have to edit that module to change it. If the list language is not English, you could edit the translation of the message in the message catalog for the language (messages/XX/LC_MESSAGES/mailman.po) and run msgfmt to rebuild mailman.mo. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Wed Sep 1 16:38:26 2010 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 1 Sep 2010 07:38:26 -0700 Subject: [Mailman-Users] Resident messages for moderation after removingMailman In-Reply-To: <4C7C9C41.8080008@rosedu.org> Message-ID: Razvan Deaconescu wrote: > >I've encountered a problem regarding pending messages for the internal >mailman list for Mailman. > >Each day at 8:00AM, as Mailman admin/owner I was getting a message with >the subject "6 Mailman moderator request(s) waiting". The message >mentioned accessing the URL >"http://${hostname}/cgi-bin/mailman/admindb/mailman". However, accessing >it (and typing in the requested password) revealed no pending posts >(such as those described in the message). See the FAQ at >The latest message was dated 28th of December 2009 (quite a while ago). > >About a week ago I decided to uninstall the Mailman instance but that >message is still sent each day at 8:00AM. I've reinstalled it, accessed >the above URL, but there are still no pending posts. > >I've done a recursive grep in /var/lib/mailman (I'm using Debian) for >parts of the message (but found nothing). I've checked all cron entries >(/etc/cron*, /var/spool/cron/crontabs/*) but found nothing relevant. > >Could someone please point me to where those pending requests are held >and how can I get rid of them and stop that message from being delivered? Based on the above, they are probably coming from a different server. Examine the Received: headers of the notice to see where it originates and uninstall Mailman or the list or stop running Mailman's cron/checkdbs on that server. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Wed Sep 1 16:45:16 2010 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 1 Sep 2010 07:45:16 -0700 Subject: [Mailman-Users] Bad/Invalid email address In-Reply-To: <4C7CB56E.6070808@kezia.com> Message-ID: Fabien COMBERNOUS wrote: > >I'm using a domain name in my LAN. This domain is used only in my LAN >and it is a root domain, ie no dot added. A mail is foo at domain, not >foo at domain.lan. > >We mailman does not want to subscribe mail like foo at domain ? Mailman minimally checks email addresses for syntactic validity. One of the checks is that the domain have at least one dot. If you want to allow domains with no dot, find the definition of ValidateEmail in Mailman/Utils.py and delete or comment the two lines if len(domain_parts) < 2: raise Errors.MMBadEmailError, s -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Wed Sep 1 17:00:35 2010 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 1 Sep 2010 08:00:35 -0700 Subject: [Mailman-Users] Mass flag change In-Reply-To: <4C7E5CE4.9030703@free-proxie123.ath.cx> Message-ID: Joe Curto wrote: > >I've just created a new list with about 8500 users. Is it possibile >(during the creation or after created) to set a flag on or off massively >? Creating the list sets le flag 'text' mail on and I need to set this >flag off for all the users. First of all, that flag only affects the format of the digest if the user is a digest member. It has no effect on individual messages. The default setting of that flag for new users is on the admin Digest options page When receiving digests, which format is default? (Edit mime_is_default_digest) To set that flag off for all current users, use withlist. Give the command bin/withlist -l LISTNAME and then at the interactive prompts (shown for clarity) enter >>> from Mailman import mm_cfg >>> for member in m.getMembers(): ... m.setMemberOption(member, mm_cfg.DisableMime, 0) ... <- 'enter' only, no input >>> m.Save() >>> <- enter control-D to exit -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From razvan at rosedu.org Wed Sep 1 17:26:59 2010 From: razvan at rosedu.org (Razvan Deaconescu) Date: Wed, 01 Sep 2010 18:26:59 +0300 Subject: [Mailman-Users] Resident messages for moderation after removingMailman In-Reply-To: References: Message-ID: <4C7E70C3.3010204@rosedu.org> On 09/01/2010 05:38 PM, Mark Sapiro wrote: > Razvan Deaconescu wrote: >> >> I've encountered a problem regarding pending messages for the internal >> mailman list for Mailman. >> >> Each day at 8:00AM, as Mailman admin/owner I was getting a message with >> the subject "6 Mailman moderator request(s) waiting". The message >> mentioned accessing the URL >> "http://${hostname}/cgi-bin/mailman/admindb/mailman". However, accessing >> it (and typing in the requested password) revealed no pending posts >> (such as those described in the message). > > See the FAQ at Many thanks! I've located the actual server and used the information in the above link. Razvan From rruivo at dei.uc.pt Wed Sep 1 18:04:19 2010 From: rruivo at dei.uc.pt (Ricardo Ruivo) Date: Wed, 01 Sep 2010 17:04:19 +0100 Subject: [Mailman-Users] Ban_list In-Reply-To: References: Message-ID: <4C7E7983.8020303@dei.uc.pt> First of all my thanks for the quick response. Which file I must edit to change the message sent by email? I have already changed the file Mailman/Cgi/subscribe.py but despite the message displayed on the web interface have been changed, the message sent by e-mail remains the original. Best regards, Ricardo Ruivo On 01-09-2010 15:33, Mark Sapiro wrote: > Ricardo Ruivo wrote: > >> there is any option to notify, by email, the user when he attempts to >> subscibe and list and his email bellow to ban_list? > > > If the banned user attempts to subscribe by email, he will receive an > email response. > > If he attempts to subscribe via the web, there is no option to send him > an email notice. > > >> Another question. It is possible to configure the following message >> (thats appers when a ban_list users attens to subscribe by web interface >> that mailling list) >> >> so Subscription results >> The email address you supplied is banned from this mailing list. If you >> think this restriction is erroneous, please contact the list owners at >> [EMAIL]. > > > This message is hard coded in the Mailman/Cgi/subscribe.py module. You > would have to edit that module to change it. If the list language is > not English, you could edit the translation of the message in the > message catalog for the language (messages/XX/LC_MESSAGES/mailman.po) > and run msgfmt to rebuild mailman.mo. > -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 260 bytes Desc: OpenPGP digital signature URL: From mark at msapiro.net Wed Sep 1 18:49:13 2010 From: mark at msapiro.net (Mark Sapiro) Date: Wed, 1 Sep 2010 09:49:13 -0700 Subject: [Mailman-Users] Ban_list In-Reply-To: <4C7E7983.8020303@dei.uc.pt> Message-ID: Ricardo Ruivo wrote: > >Which file I must edit to change the message sent by email? Mailman/Commands/cmd_subscribe.py and after editing the file you will need to restart Mailman. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From curtis at backupcentral.com Thu Sep 2 09:06:55 2010 From: curtis at backupcentral.com (W. Curtis Preston) Date: Thu, 2 Sep 2010 00:06:55 -0700 Subject: [Mailman-Users] Cannot set digest mode via URL In-Reply-To: References: Message-ID: Mark, I did see that answer, and did use rawurlencode to encode the email strings, and it's still not working. On Wed, Sep 1, 2010 at 6:52 AM, Mark Sapiro wrote: > W. Curtis Preston wrote: > > >I asked my hosting company liquidweb to talk to cpanel. Liquidweb has > >always given me great support (24x7 I might add), but at this point they > are > >at a loss and are as much at the whim of cpanel as I am. > > > >Since they do not appear to distribute the source of Mailman with cpanel > (at > >least I can't find it), I have asked Liquidweb to ask cpanel to provide > it. > >In addition, I have asked them to explain why a "real" install of Mailman > >can do what I'm asking and there's can't. > > > Your problem has nothing to do with cPanel. Perhaps the answer got lost > in the noise, but you can find it at > . > > WRT cPanel source, the most significant mods are their own list > creation process and their mailman router for exim. See > > > cPanel's mailman installation is at /usr/local/cpanel/3rdparty/mailman > on the cPanel server as noted in our FAQ at > . > > -- > Mark Sapiro The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > > From rruivo at dei.uc.pt Thu Sep 2 10:57:56 2010 From: rruivo at dei.uc.pt (Ricardo Ruivo) Date: Thu, 02 Sep 2010 09:57:56 +0100 Subject: [Mailman-Users] Ban_list In-Reply-To: References: Message-ID: <4C7F6714.9050902@dei.uc.pt> Many thanks. Work lick a charm :) Ricardo Ruivo On 01-09-2010 17:49, Mark Sapiro wrote: > Ricardo Ruivo wrote: >> >> Which file I must edit to change the message sent by email? > > > Mailman/Commands/cmd_subscribe.py and after editing the file you will > need to restart Mailman. > -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 260 bytes Desc: OpenPGP digital signature URL: From stephen at xemacs.org Thu Sep 2 11:28:20 2010 From: stephen at xemacs.org (Stephen J. Turnbull) Date: Thu, 02 Sep 2010 18:28:20 +0900 Subject: [Mailman-Users] Cannot set digest mode via URL In-Reply-To: <7E99F9E8-ABC8-4A82-A57E-62892815CA26@shub-internet.org> References: <92AEA513-B26A-4F11-9F6F-31FA9AD35A07@shub-internet.org> <20100829145910.GG4925@inocybe.localdomain> <93841744-F23C-4406-BE97-04745E6E961C@shub-internet.org> <877hj853fq.fsf@uwakimon.sk.tsukuba.ac.jp> <7E99F9E8-ABC8-4A82-A57E-62892815CA26@shub-internet.org> Message-ID: <871v9c4hqj.fsf@uwakimon.sk.tsukuba.ac.jp> Brad Knowles writes: > On Aug 29, 2010, at 7:50 PM, Stephen J. Turnbull wrote: > > > I don't like cPanel's way of operating, and I agree that Apple's > > interaction with the open source community *outside of Darwin* > > takes a lot more out than it puts back in. Still, the GPL > > doesn't give any cause for action AFAICS. > If there are no courses of action open to us in the courts in these > matters, I don't really see what you want from Apple, unless it's an LBO by the FSF. They follow the rules of the licensed software they use, as far as I know (and in particular for Mailman, I published the URL to the sources for the Mac OS X Server version of Mailman; there are in fact about 10 of them there). In fact Apple publishes a whole shitload of open source software (the Darwin OS) developed in part through substantial Apple expense. True, most of that software is only of value to Apple customers, but that beats the hell out of, say, the HURD, which is of value to no one. From cacities at yahoo.com Thu Sep 2 21:00:18 2010 From: cacities at yahoo.com (Doug Warren) Date: Thu, 2 Sep 2010 12:00:18 -0700 (PDT) Subject: [Mailman-Users] making the "Your name" Field required Message-ID: <518567.49239.qm@web120601.mail.ne1.yahoo.com> Hello ? I am new to mailman and just learning the basics. I am looking for away to make the "your name" field on the subscription page required for our private list. I have changed the (optional) to (required) on the screen but I have been unable to find out how to get the list to make it a mandatory field. I am hoping someone will be able to give me some pointers on this. ? any help would be greatly appreciated ? thank you ? Doug From kcrawford at bepress.com Thu Sep 2 20:01:21 2010 From: kcrawford at bepress.com (Kit Crawford) Date: Thu, 2 Sep 2010 11:01:21 -0700 Subject: [Mailman-Users] Having trouble with spam filters syntax Message-ID: Hi folks, I can't seem to get the correct syntax for filtering based on the Subject line. I want to auto-accept all email that contains the phrase "Digital Commons" in the Subject line. I am using Mailman version 2.1.9. I've run some tests and the Subject line header for every test is: Subject: Interested in Digital Commons tour and the action is set to Accept. The following regex filters did not work: subject: .*digital commons ^subject: .*digital commons \nsubject: .*digital commons Subject: .*Digital Commons ^Subject: .*Digital Commons \nSubject: .*Digital Commons subject: .*digital commons.* ^subject: .*digital commons.* \nsubject: .*digital commons.* Subject: .*Digital Commons.* ^Subject: .*Digital Commons.* \nSubject: .*Digital Commons.* Not sure what other syntax to try! If anyone has any insight on this vexing problem, I surely would appreciate some assistance. Regards, Kit -- Kit Crawford kcrawford at bepress.com From mark at msapiro.net Fri Sep 3 04:18:32 2010 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 2 Sep 2010 19:18:32 -0700 Subject: [Mailman-Users] Cannot set digest mode via URL In-Reply-To: Message-ID: ----- Original Message --------------- Subject: Re: [Mailman-Users] Cannot set digest mode via URL From: "W. Curtis Preston" Date: Thu, 2 Sep 2010 00:06:55 -0700 To: Mark Sapiro Cc: Brad Knowles , mailman-users at python.org, Todd Zullinger >--0003255768ee9cfa06048f417582 >Content-Type: text/plain; charset=ISO-8859-1 > >Mark, > >I did see that answer, and did use rawurlencode to encode the email strings, >and it's still not working. Go to the web admin Membership Management... -> Membership List page(s) and view the page source. Each user's row should look like
username at gmail.com
The only thing that changed on this page changed between Mailman 2.1.9 and 2.1.10 and that was the encoding of '@' as '%40' in the email addresses, and also encoding of a few other characters, double-quote in particular. Ther chould be no differences between cPanel's page and the corresponding upstream Mailman page. I note in your original post, you said: >First you have to subscribe them, then you would issue the following URL: > >http:///mailman/admin//members?user=& > >_digest=1&setmemberopts_btn=Submit%20Your%20Changes&allmodbit_val=0& >_language=en&_nodupes=1&adminpw= > > >This has also worked for a few years, but I just found out that it isn't >working. I can set someone to digest mode by manually accessing that same >page, but the URL no longer does the job. When I issue the URL manually in >my browser, instead of setting the user to digest mode and returning me to >the screen with the user on it, it returns me to the /members page, >displaying a list of users. Which is exactly what I would expect. That URL is equivalent to checking the user's 'digest box on the membership list and clicking Submit Your Changes. It will normally return to the same page. I have not looked to see if this is an issue, but there is one potential glitch. If the number of list members exceeds admin_member_chunksize, there will be an additional query fragment in the URL like http:///mailman/admin//members?letter="u" for an email address beginning with "u". In fact it can be even more complex if the number of users beginning with a single letter exceeds admin_member_chunksize. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Fri Sep 3 05:53:45 2010 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 2 Sep 2010 20:53:45 -0700 Subject: [Mailman-Users] Having trouble with spam filters syntax In-Reply-To: Message-ID: Kit Crawford wrote: > >I can't seem to get the correct syntax for filtering based on the Subject >line. I want to auto-accept all email that contains the phrase "Digital >Commons" in the Subject line. > >I am using Mailman version 2.1.9. I've run some tests and the Subject line >header for every test is: > >Subject: Interested in Digital Commons tour > >and the action is set to Accept. > >The following regex filters did not work: > >subject: .*digital commons > >^subject: .*digital commons > >\nsubject: .*digital commons > >Subject: .*Digital Commons > >^Subject: .*Digital Commons > >\nSubject: .*Digital Commons > >subject: .*digital commons.* > >^subject: .*digital commons.* > >\nsubject: .*digital commons.* > >Subject: .*Digital Commons.* > >^Subject: .*Digital Commons.* > >\nSubject: .*Digital Commons.* > >Not sure what other syntax to try! If anyone has any insight on this vexing >problem, I surely would appreciate some assistance. All of the above should work, but the ones that don't start with '^' or '\n' may be too generous. e.g. they will accept X-Bogus-Header: something about a subject: with digital commons I suspect your underlying issue is that the 'accept' action for header_filter_rules does not mean accept this post bypassing all other potential membership checks and miscellaneous holds. It just means pass the header_filter_rules check. If you want to unconditionally accept a message based on the Subject: header, you need to create a custom handler for that. See the FAQ at . -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From curtis at backupcentral.com Fri Sep 3 05:54:20 2010 From: curtis at backupcentral.com (W. Curtis Preston) Date: Thu, 2 Sep 2010 20:54:20 -0700 Subject: [Mailman-Users] Cannot set digest mode via URL In-Reply-To: References: Message-ID: Mark, I really appreciate your assistance on this. I did look at the source for the members page, which is how I constructed the GET query in the first place. The only thing that changed on this page changed between Mailman 2.1.9 > and 2.1.10 and that was the encoding of '@' as '%40' in the email > addresses, and also encoding of a few other characters, double-quote > in particular. > I understand that. > Ther chould be no differences between cPanel's page and the > corresponding upstream Mailman page. > I agree. I don't think so either. > > I note in your original post, you said: > > >First you have to subscribe them, then you would issue the following URL: > > > >http:///mailman/admin//members?user=& > > > >_digest=1&setmemberopts_btn=Submit%20Your%20Changes&allmodbit_val=0& > >_language=en&_nodupes=1&adminpw= > > > > > >This has also worked for a few years, but I just found out that it isn't > >working. I can set someone to digest mode by manually accessing that same > >page, but the URL no longer does the job. When I issue the URL manually > in > >my browser, instead of setting the user to digest mode and returning me to > >the screen with the user on it, it returns me to the /members page, > >displaying a list of users. > > > Which is exactly what I would expect. That URL is equivalent to > checking the user's 'digest box on the membership list and clicking > Submit Your Changes. It will normally return to the same page. > I believe what I should be seeing is what happens when you enter a user's email address in the search box and THEN click the digest button. I should see the list of just the user I'm setting, and the check box for digest should be checked. But that's not what's happening. I get returned to the default members list (not just the list of the member I'm working on) and then if I check the user I was trying to set, the digest box is not checked. I'm not complaining so much about what screen I get taken to, but that it's not setting the digest mode for the user, even though I'm using the new encoded email addresses in my GET query. I have not looked to see if this is an issue, but there is one > potential glitch. If the number of list members exceeds > admin_member_chunksize, there will be an additional query fragment in > the URL like > > http:///mailman/admin//members?letter="u" > > for an email address beginning with "u". In fact it can be even more > complex if the number of users beginning with a single letter exceeds > admin_member_chunksize. > Again I'm not having a problem interpreting what is being displayed on the screen. I'm having a problem that I can't set the digest mode via this URL that appears to be valid: http:// /mailman/admin//members?user=&_digest=1&setmemberopts_btn=Submit%20Your%20Changes&allmodbit_val=0&_language=en&_nodupes=1&adminpw=> This URL used to work and now it doesn't, even if I use the new style of email addresses. I've also tried to do things like emailaddress_digest=on/off instead of 1/0, but that doesn't seem to help either. I just can't seem to figure out the magic incantation. ;) TIA for any help. From mark at msapiro.net Fri Sep 3 06:13:34 2010 From: mark at msapiro.net (Mark Sapiro) Date: Thu, 2 Sep 2010 21:13:34 -0700 Subject: [Mailman-Users] Cannot set digest mode via URL In-Reply-To: Message-ID: W. Curtis Preston wrote: >> >... it returns me to the /members page, >> >displaying a list of users. >> >> >> Which is exactly what I would expect. That URL is equivalent to >> checking the user's 'digest box on the membership list and clicking >> Submit Your Changes. It will normally return to the same page. >> > >I believe what I should be seeing is what happens when you enter a user's >email address in the search box and THEN click the digest button. I should >see the list of just the user I'm setting, and the check box for digest >should be checked. Only if you also put "findmember=" in the POST data or query fragment. >But that's not what's happening. I get returned to the >default members list (not just the list of the member I'm working on) Which is expected with your URL >and >then if I check the user I was trying to set, the digest box is not >checked. Which is the problem we're trying to solve. >I'm not complaining so much about what screen I get taken to, but >that it's not setting the digest mode for the user, even though I'm using >the new encoded email addresses in my GET query. > >I have not looked to see if this is an issue, but there is one >> potential glitch. If the number of list members exceeds >> admin_member_chunksize, there will be an additional query fragment in >> the URL like >> >> http:///mailman/admin//members?letter="u" >> >> for an email address beginning with "u". In fact it can be even more >> complex if the number of users beginning with a single letter exceeds >> admin_member_chunksize. >> > >Again I'm not having a problem interpreting what is being displayed on the >screen. I'm having a problem that I can't set the digest mode via this URL >that appears to be valid: > >http:// >/mailman/admin//members?user=&_digest=1&setmemberopts_btn=Submit%20Your%20Changes&allmodbit_val=0&_language=en&_nodupes=1&adminpw=> > >This URL used to work and now it doesn't, even if I use the new style of >email addresses. And I am suggesting (although I haven't verified that this is or isn't a problem) that because your URL is for the first (default) page of the alphabetically chunked listing, your URL is not for a page that contains the targeted user and that may be why it doesn't work. I suggest you could try two things to either validate or repudiate this suggestion. 1) set admin_member_chunksize to a number greater than the number of list members and then try your URL. 2) add findmember= to the query fragments in your URL. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From curtis at backupcentral.com Fri Sep 3 09:01:01 2010 From: curtis at backupcentral.com (W. Curtis Preston) Date: Fri, 3 Sep 2010 00:01:01 -0700 Subject: [Mailman-Users] Cannot set digest mode via URL In-Reply-To: References: Message-ID: So it seems I misunderstood your previous post. Sorry about that. I followed your suggestion. Both of them, actually. I tried all of the following URLs, to no avail. The first two do at least display just the username in question. I did change the chunksize variable and did the latter two URLs, and that didn't work either. (In case it's not obvious, I tried using the values off/on and 0/1 in case that was the problem.) http://domain.com/mailman/admin/listname/members?findmember=username%40gmail.com&user=username%40gmail.com&username%40gmail.com_unsub=0&username%40gmail.com_mod=0&username%40gmail.com_hide=0&username%40gmail.com_nomail=0&username%40gmail.com_ack=0&username%40gmail.com_notmetoo=0&username%40gmail.com_nodupes=0&username%40gmail.com_digest=1&username%40gmail.com_plain=0&username%40gmail.com_language=en&setmemberopts_btn=Submit%20Your%20Changes&allmodbit_val=0&adminpw=password http://domain.com/mailman/admin/listname/members?findmember=username%40gmail.com&user=username%40gmail.com&username%40gmail.com_unsub=off&username%40gmail.com_mod=off&username%40gmail.com_hide=off&username%40gmail.com_nomail=off&username%40gmail.com_ack=off&username%40gmail.com_notmetoo=off&username%40gmail.com_nodupes=off&username%40gmail.com_digest=on&username%40gmail.com_plain=off&username%40gmail.com_language=en&setmemberopts_btn=Submit%20Your%20Changes&allmodbit_val=off&adminpw=password http://domain.com/mailman/admin/listname/members?user=username%40gmail.com&username%40gmail.com_unsub=off&username%40gmail.com_mod=off&username%40gmail.com_hide=off&username%40gmail.com_nomail=off&username%40gmail.com_ack=off&username%40gmail.com_notmetoo=off&username%40gmail.com_nodupes=off&username%40gmail.com_digest=on&username%40gmail.com_plain=off&username%40gmail.com_language=en&setmemberopts_btn=Submit%20Your%20Changes&allmodbit_val=0&adminpw=password http://domain.com/mailman/admin/listname/members?user=username%40gmail.com&username%40gmail.com_unsub=0&username%40gmail.com_mod=0&username%40gmail.com_hide=0&username%40gmail.com_nomail=0&username%40gmail.com_ack=0&username%40gmail.com_notmetoo=0&username%40gmail.com_nodupes=0&username%40gmail.com_digest=1&username%40gmail.com_plain=0&username%40gmail.com_language=en&setmemberopts_btn=Submit%20Your%20Changes&allmodbit_val=0&adminpw=password From brad at shub-internet.org Fri Sep 3 09:30:19 2010 From: brad at shub-internet.org (Brad Knowles) Date: Fri, 3 Sep 2010 02:30:19 -0500 Subject: [Mailman-Users] Cannot set digest mode via URL In-Reply-To: References: Message-ID: <4F7EE148-69D3-455B-87A6-5AD48EF07FF8@shub-internet.org> On Sep 3, 2010, at 2:01 AM, W. Curtis Preston wrote: > So it seems I misunderstood your previous post. Sorry about that. I followed your suggestion. Both of them, actually. I tried all of the following URLs, to no avail. The first two do at least display just the username in question. I did change the chunksize variable and did the latter two URLs, and that didn't work either. (In case it's not obvious, I tried using the values off/on and 0/1 in case that was the problem.) I'm sure Mark will correct me if I'm wrong, but I assume you stopped and restarted Mailman after making the chunksize change? I don't think that this is something that is baked into the list when it's created, but is instead something that can be changed after-the-fact, and all that should be required is a restart. But there's something tickling in the back of my brain regarding this, and I can't figure out what it is.... -- Brad Knowles LinkedIn Profile: From geoff at QuiteLikely.com Fri Sep 3 11:08:52 2010 From: geoff at QuiteLikely.com (Geoff Shang) Date: Fri, 3 Sep 2010 12:08:52 +0300 (IDT) Subject: [Mailman-Users] Cannot set digest mode via URL In-Reply-To: <4F7EE148-69D3-455B-87A6-5AD48EF07FF8@shub-internet.org> References: <4F7EE148-69D3-455B-87A6-5AD48EF07FF8@shub-internet.org> Message-ID: On Fri, 3 Sep 2010, Brad Knowles wrote: > I'm sure Mark will correct me if I'm wrong, but I assume you stopped and > restarted Mailman after making the chunksize change? I don't think that > this is something that is baked into the list when it's created, but is > instead something that can be changed after-the-fact, and all that > should be required is a restart. I doubt this needs a restart, as member chunk size is something a list owner can change on the admin pages. Geoff. From mark at msapiro.net Fri Sep 3 17:46:41 2010 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 3 Sep 2010 08:46:41 -0700 Subject: [Mailman-Users] Cannot set digest mode via URL In-Reply-To: Message-ID: Geoff Shang wrote: >On Fri, 3 Sep 2010, Brad Knowles wrote: > >> I'm sure Mark will correct me if I'm wrong, but I assume you stopped and >> restarted Mailman after making the chunksize change? I don't think that >> this is something that is baked into the list when it's created, but is >> instead something that can be changed after-the-fact, and all that >> should be required is a restart. > >I doubt this needs a restart, as member chunk size is something a list >owner can change on the admin pages. Geoff is correct. admin_member_chunksize is a list attribute and simply changing a list attribute never requires a restart. Further, in this case, we are dealing with CGIs, and the CGI scripts are always loaded as a new process by the web server, so changes that affect only the CGI scripts don't require a restart either. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From cacities at yahoo.com Fri Sep 3 18:51:12 2010 From: cacities at yahoo.com (Doug Warren) Date: Fri, 3 Sep 2010 09:51:12 -0700 (PDT) Subject: [Mailman-Users] set the "your name" field to Required Message-ID: <689659.62304.qm@web120608.mail.ne1.yahoo.com> Hello ? I am new to Mailman so please bear with me. I am trying to set the "Your name" field on the subscription page of our entire list to required, but I have been unable to find the commands to set this up. I have changed the "(optional)" to ?(required)? on the subscription HTML page on a test list and that looks good, but they users can submit a subscription with out submitting ?that information. ?Any help will be greatly appreciated. ? Thank you Doug? From mark at msapiro.net Fri Sep 3 18:58:49 2010 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 3 Sep 2010 09:58:49 -0700 Subject: [Mailman-Users] Cannot set digest mode via URL In-Reply-To: Message-ID: W. Curtis Preston wrote: > >So it seems I misunderstood your previous post. Sorry about that. I >followed your suggestion. Both of them, actually. I tried all of the >following URLs, to no avail. The first two do at least display just the >username in question. I did change the chunksize variable and did the >latter two URLs, and that didn't work either. (In case it's not obvious, I >tried using the values off/on and 0/1 in case that was the problem.) I finally had some time to devote to debugging this, and I know what the problem is. The 2.1.10 change was made because the local part of an email address can be quoted with a double quote as in "john&jane"@example.com. The presence of those double quotes would break the HTML for the membership list page by creating things like /mailman/admin//members/add?subscribe_or_invite=0&send_welcome_msg_to_this_batch=0&send_notifications_to_list_owner=0&subscribees=user at example.com&user=user%2540example.com&user%2540example.com_digest=1&user%2540example.com_nodupes=1&user%2540example.com_plain=1&setmemberopts_btn=1&adminpw= Note the following: I have specified subscribees instead of subscribees_upload as in the OP. This doesn't matter; either will work, but subscribees is shorter. Note the address here is raw, not encoded. I have corrected send_notifications_to_list_owner which was notification_to_list_owner in the OP. I have omitted allmodbit_val=0 since this is ignored unless allmodbit_btn is present. I have setmemberopts_btn=1 since the actual value is ignored - only the presence or absence of the key is significant. I have omitted the '=0' option settings. In most cases (language is an exception), ommitting a setting is the same as setting it to unchecked or empty. This does mean that settings which are on by default must be explicitly set whether you do it with one step or two or they will be turned off. The exception is language which will be unchanged if omitted. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Fri Sep 3 19:26:54 2010 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 03 Sep 2010 10:26:54 -0700 Subject: [Mailman-Users] making the "Your name" Field required In-Reply-To: <518567.49239.qm@web120601.mail.ne1.yahoo.com> References: <518567.49239.qm@web120601.mail.ne1.yahoo.com> Message-ID: <4C812FDE.6030001@msapiro.net> On 9/2/2010 12:00 PM, Doug Warren wrote: > > I am new to mailman and just learning the basics. I am looking for away to make > the "your name" field on the subscription page required for our private list. I > have changed the (optional) to (required) on the screen but I have been unable > to find out how to get the list to make it a mandatory field. I am hoping > someone will be able to give me some pointers on this. This is tricky. Presumably you know how to edit the listinfo template to change (optional) to (required). You will note that the actual text box for entry of the real name is generated by the tag in the listinfo template. This tag expands to in the generated HTML. It would be nice if you could just replace the tag with its expansion and just add a 'REQUIRED' attribute, but I don't think HTML has such an attribute for INPUT elements. What this means is you would have to look also at the tag which expands to and add some ONCLICK= javascript to enforce an entry for fullname. But, there are multiple problems with this. The first issue is that due to XSS protection, you can't put things like ONCLICK in HTML templates edited via the web admin interface. You would have to have access to the Mailman server and create an edited template as discussed in the FAQ at . Another way to do it would be to just remove the subscribe form and replace it with a link to your own subscribe page (see ). Beyond that, even if you made a bomb proof page that would refuse to allow subscription without a real name, it wouldn't prevent a user from subscribing by email without a real name. You could (if you have access) modify the Mailman code to require a real name for subscription, but even this could be effectively bypassed by a user providing a bogus name. Perhaps a better approach is to set your list's Privacy options... -> Subscription rules -> subscribe_policy to "Require approval" and just not approve any requests that don't provide an acceptable real name. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From mark at msapiro.net Fri Sep 3 19:37:50 2010 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 3 Sep 2010 10:37:50 -0700 Subject: [Mailman-Users] Cannot set digest mode via URL In-Reply-To: Message-ID: Mark Sapiro wrote: > >Note also that you can subscribe the user and set options with a single >GET URL. For example: > >http:///mailman/admin//members/add?subscribe_or_invite=0&send_welcome_msg_to_this_batch=0&send_notifications_to_list_owner=0&subscribees=user at example.com&user=user%2540example.com&user%2540example.com_digest=1&user%2540example.com_nodupes=1&user%2540example.com_plain=1&setmemberopts_btn=1&adminpw= > Note that the /add in the above is not required. It could just as well be http:///mailman/admin//members?subscribe_or_invite=0&send_welcome_msg_to_this_batch=0&send_notifications_to_list_owner=0&subscribees=user at example.com&user=user%2540example.com&user%2540example.com_digest=1&user%2540example.com_nodupes=1&user%2540example.com_plain=1&setmemberopts_btn=1&adminpw= The only difference is what the results page is. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan From curtis at backupcentral.com Fri Sep 3 20:10:44 2010 From: curtis at backupcentral.com (W. Curtis Preston) Date: Fri, 3 Sep 2010 11:10:44 -0700 Subject: [Mailman-Users] Cannot set digest mode via URL In-Reply-To: References: Message-ID: All I can say is http://www.backupcentral.com/ha.mp3 !!!! It works! Thank you so much for your help with this! The following URL will set an existing user's digest flag on and nothing else: http://domain.com/mailman/admin/listname/members?user=user%2540gmail.com&user%2540gmail.com_digest=1&setmemberopts_btn=1&adminpw=password The opposite (digest=0) doesn't turn it off. I don't need it for me, but I am curious about your thoughts on that, as I plan to help update the FAQ with what we've learned here. The other tip you gave also works: http:///mailman/admin/ > > > /members/add?subscribe_or_invite=0&send_welcome_msg_to_this_batch=0&send_notifications_to_list_owner=0&subscribees= > user at example.com&user=user%2540example.com > &user%2540example.com_digest=1&user%2540example.com_nodupes=1&user%2540example.com_plain=1&setmemberopts_btn=1&adminpw= That does indeed subscribe them and set them to digest mode. That will simplify my code. Did I mention this is what I'm hearing: http://www.backupcentral.com/ha.mp3?? Thanks, Mark. Your internal knowledge of Mailman was really needed to figure this out. You could have just said "Dude, that's not really how Mailman was meant to be used..." but you didn't. Thank you, thank you, thank you. > > From mark at msapiro.net Fri Sep 3 20:34:00 2010 From: mark at msapiro.net (Mark Sapiro) Date: Fri, 3 Sep 2010 11:34:00 -0700 Subject: [Mailman-Users] Cannot set digest mode via URL In-Reply-To: Message-ID: W. Curtis Preston wrote: > >All I can say is http://www.backupcentral.com/ha.mp3 !!!! > >It works! Thank you so much for your help with this! > >The following URL will set an existing user's digest flag on and nothing >else: >http://domain.com/mailman/admin/listname/members?user=user%2540gmail.com&user%2540gmail.com_digest=1&setmemberopts_btn=1&adminpw=password > >The opposite (digest=0) doesn't turn it off. I don't need it for me, but I >am curious about your thoughts on that, as I plan to help update the FAQ >with what we've learned here. Actually, the way the code works (and it works that way because of the way most browsers work) setting a key to any value, e.g. user%2540gmail.com_digest=1 or even user%2540gmail.com_digest=0 will set the corresponding option on. To set an option off for a user you just include "user=user%2540gmail.com" and omit the user%2540gmail.com_