Re: [Mailman-Users] Unsubscribe Using Web Form
On 11/08/2014 01:14 PM, Greg Sims wrote: It appears that Posting: http://SERVER/mailman/subscribe/LIST_NAME with: email = EMAIL_ADDRESS fullname = USERS_NAME email-button = SubscribeMM-Results always returns the contents of the file subscribe.html even in the presence of an invalid address like 'foo'. Have you modified this template? The standard template contains the tag MM-Results which is replaced by an informative message. Posting: http://SERVER/mailman/options/LIST_NAME with: email = EMAIL_ADDRESS login-unsub = Unsubscribe always returns the string The confirmation email has been sent.. ... I need to find a way to Post a CGI to Unsubscribe that tells my code if the EMAIL_ADDRESS is subscribed to the list and if a validation email was actually sent. As Richard indicated in another reply, if the membership roster is not public, the responses are generic to prevent using the (un)subscribe processes to fish for membership. Set the list's Privacy options... - Subscription rules - private_roster to Anyone and you will get more specific messages. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] mailman and httpd vhost
Igor Gnatenko writes: ScriptAlias mm.clanwars.org:8080 /usr/lib/mailman/cgi-bin/ Your syntax is broken. ScriptAlias Directive Description:Maps a URL to a filesystem location and designates the target as a CGI script Syntax: ScriptAlias URL-path file-path|directory-path The syntax specifies an URL-path, not an URL. mm.clanwars.org:8080 is a perfectly legal POSIX filename, though, so it's probably being interpreted as /mm.clanwars.org:8080/. http://httpd.apache.org/docs/current/mod/mod_alias.html for further details. Regards, -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Mountain Lion server trouble
This is why it's important to keep server configurations in a configuration management system, like Chef, Puppet, cfengine, Ansible, Salt Stack, etc. When set up right, the configuration management will put back any unwanted OS changes, or at the very least tell after an upgrade what files no longer contain your edits. On Tue, Nov 04, 2014 at 11:59:02AM -0500, nxnw wrote: ... 1. Mostly good news - after the OS and server.app upgrades, mailman was (mostly) running. The only thing that was not working was the web interface. After a bit of investigation, I found that the upgrade overwrote /Library/Server/Web/Config/apache2/httpd_server_app.conf, so that file had to be edited (again) to add the following: #Mailman Include /private/etc/apache2/extra/httpd-mailman.conf I put the above right after Include /Library/Server/Web/Config/apache2/other/*.conf. Apache must be restarted after the edit. -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Archive merge and search
PS: I just noticed that I've previously replied directly to you, Mark, instead of the list (pressing Reply instead of Reply list in my email program). Sorry about that. This one should reach the list. On 08/11/2014 04:51, Mark Sapiro wrote: On 11/07/2014 07:22 PM, Hal wrote: Instead of using a temp gfile made with mktemp and then removing it, you can just make something more permanent. e.g. cat mylist.* total /usr/lib/mailman/bin/cleanarch total total_cleaned. Thanks. Unfortunately cleanarch'ing didn't solve my issue. I did some more research and found out that the MBOX format isn't standardized as there are 4 different variations around (http://homepage.ntlworld.com/jonathan.deboynepollard/FGA/mail-mbox-formats.html). Confusing indeed. What's even stranger is that the Majordomo search-interface displays all of those same MBOXes without any issues. Investigating the MBOX files in a text editor I found the problematic ones to have headers starting with From (without the quotes) which the working ones didn't, so I removed all those lines from a couple of MBOX files, imported into the Mailman archives and all looked fine! Obviously I can't check every single posting, so does my discovery and solution sound feasible? Hal -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Archive merge and search
On 11/9/2014 8:37 PM, Hal wrote: Thanks. Unfortunately cleanarch'ing didn't solve my issue. I did some more research and found out that the MBOX format isn't standardized as there are 4 different variations around (http://homepage.ntlworld.com/jonathan.deboynepollard/FGA/mail-mbox-formats.html). Confusing indeed. What's even stranger is that the Majordomo search-interface displays all of those same MBOXes without any issues. Investigating the MBOX files in a text editor I found the problematic ones to have headers starting with From (without the quotes) which the working ones didn't, so I removed all those lines from a couple of MBOX files, imported into the Mailman archives and all looked fine! Obviously I can't check every single posting, so does my discovery and solution sound feasible? Hal When I read a message that has From changed to From (at the beginning of a line), I have to trouble interpreting the mail. The URL above says that the transformation corrupts mailboxes. I would use the term changes, as the e-mail body has been changed. The term corrupted, in my opinion, means something drastic; adding a in front of From does not make the message unintelligible. I dislike the format that uses Content-Length: to determine the end of a message. If I edit an archive file and, say delete one line that contains a password, then I have to change the corresponding Content-Length: line. --Barry Finkel -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
