[Mailman-Users] Listowner wants to send long messages
Hello Is there a way for the owner of a list to have only their messages auto approved if they are too long? I read the documentation and did not find this issue discussed. Thank you for your help. Jane -- Jane Frizzell Network Services Administrator Bates College Information and Library Services jfriz...@bates.edu 786-6457110 Russell St -- Mailman-Users mailing list Mailman-Users@python.org http://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: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Mailing list
Can your program work on a Mac? Thank you. Leslie King This e-mail message (including any attachments) is for the sole use of the intended recipient(s) and may contain confidential and privileged information. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this message (including any attachments) is strictly prohibited. If you have received this message in error, please contact the sender by reply e-mail message and destroy all copies of the original message (including attachments). -- Mailman-Users mailing list Mailman-Users@python.org http://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: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] FW: [#ZPK-731315]: Mailing list constantly rejecting a member email - please assist
Hello I was hoping you could help. I had email lists under a sub-domain, but decided to move the subdomain to its own webhosting. Part of that migration included moving some email lists across. The problem I have that any list that email are being rejected for list that now exists under the new hosting service but that existed under the old subdomain. Any new list name created is fine. Can you think of any reason for this? You're assistance would be much appreaciated. Regard John Grivas +61 4 1001 7585 -- Forwarded Message From: John Grivas (wotsnext) j...@wotsnext.com.au Date: Tue, 26 Jan 2010 21:25:14 +1100 To: resellersupp...@planetdomain.com Subject: Re: [#ZPK-731315]: Mailing list constantly rejecting a member email - please assist Hi Geoff Sorry, I don't really understand what you have written below. I am a bit confused. The only email account I see under www.shnc.org.au/cpanel is: j...@shnc.org.au The list below are Mailing Lists I created the lists below under the new hosting service. I created them around the 11 Jan 2010. alu...@shnc.org.au commit...@shnc.org.au copperhe...@shnc.org.au deathadd...@shnc.org.au diamondpyth...@shnc.org.au easternmast...@shnc.org.au goldencro...@shnc.org.au memb...@shnc.org.au redbelliedbla...@shnc.org.au redfur...@shnc.org.au soc...@shnc.org.au whistlingbl...@shnc.org.au I don¹t understand what you are suggesting is causing the conflict. I just created another email list shnctes...@shnc.org.au, added j...@wotsnext.com.au to the list. And with this email list I can email OK. So can you provide a solution to eradicting the conflict the is occurring with the other email lists listed above? Regards John From: Geoff Keeys resellersupp...@planetdomain.com Reply-To: resellersupp...@planetdomain.com Date: Mon, 25 Jan 2010 18:02:41 +1100 To: j...@wotsnext.com.au Subject: [#ZPK-731315]: Mailing list constantly rejecting a member email - please assist Hi John, The mailing list in CPanel shows the following email accounts as being part of the mailing list: alu...@shnc.org.au commit...@shnc.org.au copperhe...@shnc.org.au deathadd...@shnc.org.au diamondpyth...@shnc.org.au easternmast...@shnc.org.au goldencro...@shnc.org.au memb...@shnc.org.au redbelliedbla...@shnc.org.au redfur...@shnc.org.au soc...@shnc.org.au whistlingbl...@shnc.org.au This list is in CPanel, in the Mail section, under Mailing lists. My assumption is that this is what is causing the conflict. There should be nothing left under the old hosting with tinkertailor.com.au. Regards, Geoff Team Leader Reseller Support Planet Domain Pty Ltd Ticket Details === Ticket ID: ZPK-731315 Department: Resellers (Mon-Fri) Priority: Low Status: Closed -- End of Forwarded Message -- Mailman-Users mailing list Mailman-Users@python.org http://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: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Listowner wants to send long messages
Jane Frizzell wrote: Is there a way for the owner of a list to have only their messages auto approved if they are too long? I read the documentation and did not find this issue discussed. Thank you for your help. Not per se, but the owner can post with an Approved: password header where passord is the list admin or moderator password to pre-approve her post. -- 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 http://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: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Mailing list
On Mon, Jan 25, 2010 at 16:55, King, Leslie ltk...@emory.edu wrote: Can your program work on a Mac? Stick the word MacOS into the list search page: Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ and you'll find many hits - the first (for me) of which includes a link to installing it. -- Please keep list traffic on the list. Rob MacGregor Whoever fights monsters should see to it that in the process he doesn't become a monster. Friedrich Nietzsche -- Mailman-Users mailing list Mailman-Users@python.org http://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: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Mailing list
King, Leslie wrote: Can your program work on a Mac? The short answer is yes. See the FAQ at http://wiki.list.org/x/O4A9 -- 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 http://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: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Mailing list
On Mon, 25 Jan 2010, King, Leslie wrote: Can your program work on a Mac? You've already had a couple of answers. I have written (and it should be found in the archives) installation instructions for various recent versions of Mac OS X. That said, and with no idea of what your expectations and capabilities are, it is not a piece of consumer software that you just copy on to your Macintosh and double-click. You will be turning your Macintosh into a server (no, you don't need to have Mac OS X Server), you will need a mail server running, you will be downloading the Mailman source and building it (requires Mac OS X Developer Tools), you will be modifying the internal web server on your computer, and you will need to modify system startup files (Mailman runs in the background). In short, you need to be a reasonably skilled system administrator. -- Larry Stone lston...@stonejongleux.com -- Mailman-Users mailing list Mailman-Users@python.org http://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: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] FW: [#ZPK-731315]: Mailing list constantlyrejecting a member email - please assist
John Grivas (wotsnext) wrote: I had email lists under a sub-domain, but decided to move the subdomain to its own webhosting. Part of that migration included moving some email lists across. The problem I have that any list that email are being rejected for list that now exists under the new hosting service but that existed under the old subdomain. Any new list name created is fine. Can you think of any reason for this? You're assistance would be much appreaciated. I can think of two reasons off the top. Aliases and cPanel, although cPanel usually uses exim with a mailman router and transport, so aliases per se is probably not the issue. What is the reason for rejection of the mail to the lists. More below ... -- Forwarded Message From: John Grivas (wotsnext) j...@wotsnext.com.au [...] The only email account I see under www.shnc.org.au/cpanel is: j...@shnc.org.au The list below are Mailing Lists I created the lists below under the new hosting service. I created them around the 11 Jan 2010. alu...@shnc.org.au commit...@shnc.org.au copperhe...@shnc.org.au deathadd...@shnc.org.au diamondpyth...@shnc.org.au easternmast...@shnc.org.au goldencro...@shnc.org.au memb...@shnc.org.au redbelliedbla...@shnc.org.au redfur...@shnc.org.au soc...@shnc.org.au whistlingbl...@shnc.org.au [...] The reference above to cpanel seems to say you moved the lists to a cPanel host. How did you move them? Were they previously cPanel lists. cPanel mungs list names. I.e. the name of the alu...@shnc.org.au list under cPanel is alumni_shnc.org.au and its config.pck, etc are in /usr/local/cpanel/3rdparty/mailman/lists/alumni_shnc.org.au/. I don't know if it is even possible to move a non-cPanel config.pck to cPanel and have it just work. See the FAQ at http://wiki.list.org/x/sYA9. -- 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 http://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: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] FW: [#ZPK-731315]: Mailing list constantly rejecting a member email - please assist
On Tue, 26 Jan 2010, John Grivas (wotsnext) wrote: I had email lists under a sub-domain, but decided to move the subdomain to its own webhosting. Part of that migration included moving some email lists across. The problem I have that any list that email are being rejected for list that now exists under the new hosting service but that existed under the old subdomain. Any new list name created is fine. What happens when you try to post? If you are sent a bounce message, what does it say? Are there errors in Mailman's log files, and if so, what are they? Geoff. -- Mailman-Users mailing list Mailman-Users@python.org http://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: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Private archive nightmare with vhosts
Hello,
I work for a large university and was recently put in charge of consolidating a
bunch of mailman lists from multiple domains onto 1 server.
First problem that I encountered was the single namespace issue with virtual
domains, so i removed the stock Mailman 2.1.12 that came with Ubuntu,
downloaded Mailman 2.1.7 and patched it with
mailman-2.1.7-release-to-vhost.patch from
http://ndim.fedorapeople.org/stuff/mailman-vhost/.
That went pretty smooth, compiled and installed without any major issues.
put these in mm_cfg.py:
DEFAULT_EMAIL_HOST = 'lists.dept.university.edu'
DEFAULT_URL_HOST = 'lists.dept.university.edu'
add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)
add_virtualhost('lists.domain1.net', 'lists.domain1.net')
add_virtualhost('lists.domain2.net', 'lists.domain2.net')
POSTFIX_STYLE_VIRTUAL_DOMAINS = ['lists.domain1.net', 'lists.domain2.net']
After that I setup Postfix, added a new list test-list which was
automatically created in the right place -
/path/to/mailman/lists/lists.domain1.net/test-list/
So no problem here. I subscribed to the list, confirmed the subscription and
sent couple of test messages. Everything worked great.
Next i went to browse the archives and encountered another problem. The URLs
for the Public archives were not right, but I got around it with a simple
Apache rewrite:
RewriteCond %{REQUEST_URI} !^/pipermail/([a-z]+)\.(.*)?$ [NC]
RewriteRule ^/pipermail/(.*)$ /pipermail/%{SERVER_NAME}/$1 [R=301,L]
Basically all it does is insert lists.domainX.net between /pipermail/ and
/test-list/. Public archives are now working with
http://lists.domain1.net/pipermail/lists.domain1.net/test-list/
Next I tried to test Private archives and this is where I hit the wall and need
some help with.
The listinfo page for my test-list showed that the URL for the private archives
was http://lists.domain1.net/private/test-list, so i figured i would be able to
fix it with the same rewrite rule that i used for the Public archives.
However, because private CGI wrapper expects the list name right after
/private/, this URL
http://lists.domain1.net/private/lists.domain1.com/test-list/ did not work, and
all i got was the error message saying that list lists.domain1.net does not
exist
Next, I changed my rewrite rule to redirect me to
http://lists.domain1.com/private/test-l...@lists.domain1.com instead
RewriteCond %{REQUEST_URI} !^/private/(.*)@(.*)?$ [NC]
RewriteRule ^/private/(.*)/$ /private/$...@%{server_name} [R=301,L]
This redirected me to the login page and seemed to work great, until I tried to
login and got hit with the message that test-list does not exist.
After a little digging, I traced the problem to the incorrect html from action,
private.py and private.html template file.
With my very limited [read non-existing] Python knowledge I managed to pass
some arguments to the private.html and change the form action
from http://lists.domain1.com/private/test-list/ to
http://lists.domain1.com/private/test-l...@lists.domain1.com and was able to
login, but now i got another error - Private archive file not found.
I looked at the log file and saw the following error message:
Jan 26 09:31:18 2010 (21196) Private archive file not found:
/path/to/mailman/archives/private/test-l...@lists.domain1.net
Just for the hell of it I decided to create a symbolic link and see if it will
work
ln -s /path/to/mailman/archives/private/lists.domain1.net/test-list
/path/to/mailman/archives/private/test-l...@lists.domain1.net
This seemed to work and i was able to pull up the Private archive page, however
all the links were missing /private/test-l...@lists.domain1.net and looked
like http://lists.domain1.com/2010-January/;
[this part is not really important right now. i guess i will deal with this
problem later.]
Now it looks like the path variable in private.py (line 70 or very close) is
causing the issue:
path = os.environ.get('PATH_INFO')
According to the debug log my PATH_INFO is test-l...@lists.domain1.net, so I
figured I should be able to fix it like so:
path = os.path.join(os.environ.get('SERVER_NAME'), LIST NAME HERE) [
end result has to be lists.domain1.net/test-list ]
But i could not figure out how to pass the list name to os.path.join() and no
matter what I did i either ended up with undeclared variable or some other
related error.
I really hope someone would be able to help me out here or point me in the
right direction.
Thank you in advance,
- Igor
--
Mailman-Users mailing list Mailman-Users@python.org
http://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:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Really obscuring sender addresses
I've set up a read-only announcement mailing list following these guidelines: http://wiki.list.org/pages/viewpage.action?pageId=4030685 I am looking to obscure any reference to the sender's address from list postings. Per the guidelines, this includes (all done via the Web UI): anonymous_list: Yes first_strip_reply_to: Yes reply_goes_to_list: Explicit address reply_to_address: i...@example.com include_rfc2369_headers: Yes include_list_post_header: No However, test messages I've sent to the list still include my address in the message headers: Received: from host.example.com (host.example.com [10.0.0.123]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: dnew...@networktest.com) by mail.example.com (Postfix) with ESMTPSA id 8D354958A2 for announce-l...@lists.example.com; Tue, 26 Jan 2010 11:24:09 -0800 (PST) Is it possible to scrub that Authenticated sender line? thanks dn -- Mailman-Users mailing list Mailman-Users@python.org http://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: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] fun with hostnames.
Hi All, We are trying to configure a setup that would set the list server addresses to be a different hostname than the URL host and admin pages use. For example if we had a machine named foo.interest.com with a DNS alias for fooalias.interest.com , we want our admin pages look to like this. http://foo.interest.com/mailman/listinfo/mailinglist But we want users to send email to: mailingl...@fooalias.interest.com mailto:mailingl...@newfoo.interest.com Does anyone know how to do this? I tried to configure mm_cfg.py like the following: DEFAULT_EMAIL_HOST = 'fooalias.interest.com' DEFAULT_URL_HOST = 'foo.interest.com' And it is mostly working. However the machine is still accepting mail from people who send to: mailingl...@foo.interest.com and we want it to only accept mail sent to mailingl...@fooalias.interest.com Does anyone have an idea how to make this happen? Thanks a bunch John -- Mailman-Users mailing list Mailman-Users@python.org http://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: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Really obscuring sender addresses
David Newman wrote: I am looking to obscure any reference to the sender's address from list postings. Per the guidelines, this includes (all done via the Web UI): anonymous_list: Yes first_strip_reply_to: Yes reply_goes_to_list: Explicit address reply_to_address: i...@example.com include_rfc2369_headers: Yes include_list_post_header: No However, test messages I've sent to the list still include my address in the message headers: Received: from host.example.com (host.example.com [10.0.0.123]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: dnew...@networktest.com) by mail.example.com (Postfix) with ESMTPSA id 8D354958A2 for announce-l...@lists.example.com; Tue, 26 Jan 2010 11:24:09 -0800 (PST) Is it possible to scrub that Authenticated sender line? This is fixed in Mailman 2.1.13 - Received: headers are removed from anonymized posts. If you can't upgrade, you can get the Cleanse.py module from http://bazaar.launchpad.net/~mailman-coders/mailman/2.1/files/head%3A/Mailman/Handlers/ and replace your Mailman/Handlers/Cleanse.py with that one. It should work with any Mailman 2.1.x version. -- 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 http://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: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] fun with hostnames.
Pennington, John wrote: I tried to configure mm_cfg.py like the following: DEFAULT_EMAIL_HOST = 'fooalias.interest.com' DEFAULT_URL_HOST = 'foo.interest.com' That's the way to do it. Plus adding VIRTUAL_HOSTS.clear() add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST) following the above two lines and maybe running fix_url to update lists that were created before the change. See the FAQ at http://wiki.list.org/x/gIA9. And it is mostly working. However the machine is still accepting mail from people who send to: mailingl...@foo.interest.com and we want it to only accept mail sent to mailingl...@fooalias.interest.com Does anyone have an idea how to make this happen? This has to be done in your MTA configuration and how to do it depends on your MTA. The issue is any mail sent to foo.interest.com is delivered to the same machine as mail to fooalias.interest.com and the MTA finds the alias or whatever for the list and delivers the mail. Depending on the MTA and how it delivers to Mailman this may be tricky to resolve. Even if fooalias.interest.com is a virtual domain in the MTA, the normal way of handling this for Mailman is to have a virtual mapping from mailingl...@fooalias.interest.com to the local name mailinglist so this makes mailinglist a valid local name so if foo.interest.com is the local domain, mailingl...@foo.interest.com is also a valid address for the list. -- 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 http://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: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] FW: [#ZPK-731315]: Mailing list constantly rejecting a member email - please assist
Hi, Putting this back on the list. On Wed, 27 Jan 2010, John Grivas (wotsnext) wrote: Hi Geoff The following is the error message received: This email has been automatically rejected because you are not a member of the redfurina-ow...@shnc.org.au mailing list. This looks very odd to me, though others may see some logical reason why the -owner bit is at the end of the list name. If you would like to post a message to this mailing list, please forward your original email to t...@shnc.org.au From: John Grivas (wotsnext) j...@wotsnext.com.au Date: Wed, 27 Jan 2010 10:47:20 +1100 To: redfur...@shnc.org.au Subject: Testting 27.1 But I have since 'deleted' the list redfur...@shnc.org.au and when I send the email, I still get a bounce. So it must be hitting an old configuration of the list. Maybe a stupid question. Did you say you've got two hosts involved in your domain? If so, which one is handling the mail? If it's the one that used to have the lists, did you properly clean out the lists from where they used to be? Geoff. -- Mailman-Users mailing list Mailman-Users@python.org http://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: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Private archive nightmare with vhosts
UGSD wrote:
First problem that I encountered was the single namespace issue with virtual
domains, so i removed the stock Mailman 2.1.12 that came with Ubuntu,
downloaded Mailman 2.1.7 and patched it with
mailman-2.1.7-release-to-vhost.patch from
http://ndim.fedorapeople.org/stuff/mailman-vhost/.
That went pretty smooth, compiled and installed without any major issues.
Before you commit too heavily to this, I suggest you look at the first
570+ lines at
http://bazaar.launchpad.net/~mailman-coders/mailman/2.1/annotate/head%3A/NEWS
and see if you really want to be installing a 4 year old release.
put these in mm_cfg.py:
DEFAULT_EMAIL_HOST = 'lists.dept.university.edu'
DEFAULT_URL_HOST = 'lists.dept.university.edu'
add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)
add_virtualhost('lists.domain1.net', 'lists.domain1.net')
add_virtualhost('lists.domain2.net', 'lists.domain2.net')
POSTFIX_STYLE_VIRTUAL_DOMAINS = ['lists.domain1.net', 'lists.domain2.net']
After that I setup Postfix, added a new list test-list which was
automatically created in the right place -
/path/to/mailman/lists/lists.domain1.net/test-list/
So no problem here. I subscribed to the list, confirmed the subscription and
sent couple of test messages. Everything worked great.
Next i went to browse the archives and encountered another problem. The URLs
for the Public archives were not right, but I got around it with a simple
Apache rewrite:
RewriteCond %{REQUEST_URI} !^/pipermail/([a-z]+)\.(.*)?$ [NC]
RewriteRule ^/pipermail/(.*)$ /pipermail/%{SERVER_NAME}/$1 [R=301,L]
Basically all it does is insert lists.domainX.net between /pipermail/ and
/test-list/. Public archives are now working with
http://lists.domain1.net/pipermail/lists.domain1.net/test-list/
So you can't have lists with names beginning with letters and a dot.
I think a better method would be a separate Alias /pipermail/ directive
in each VirtualHost block.
Next I tried to test Private archives and this is where I hit the wall and
need some help with.
The listinfo page for my test-list showed that the URL for the private
archives was http://lists.domain1.net/private/test-list, so i figured i would
be able to fix it with the same rewrite rule that i used for the Public
archives.
The patch is supposed to present the correct URL for both private and
public archive access. I probably won't have time before Thursday to
look at this in detail (and I only do it at all because OCD is a
terrible thing to waste).
[long sad tale snipped]
You are applying band-aids upon band-aids and you'll never stop the
bleeding until you properly fix the underlying problem.
As I said, because I'm compulsive I will look at this in more detail
and follow up, but probably not for a few days.
--
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
http://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:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Private archive nightmare with vhosts
Before you commit too heavily to this, I suggest you look at the first
570+ lines at
http://bazaar.launchpad.net/~mailman-coders/mailman/2.1/annotate/head%3A/NEWS
and see if you really want to be installing a 4 year old release.
The only reason i chose 2.1.7 is because the patch applied cleanly, but i guess
you are right.
I just sat down and applied the patch to the 2.1.13 source. There few few
rejects, but I went through
all of them and it looks like that code that already made it upstream and
included in 2.1.13.
Compiled and installed it, but for the life of me i cant create a new list for
a virtual domain.
bin/newlist -u lists.domain1.net test-l...@lists.domain1.net
and end up with
Illegal list name: pruchai-t...@lists.calit2.net
This is very strange, because the domain already exists in mm_cfg.py and the
patch applied cleanly to bin/newlist too.
Any idea what may be wrong?
put these in mm_cfg.py:
DEFAULT_EMAIL_HOST = 'lists.dept.university.edu'
DEFAULT_URL_HOST = 'lists.dept.university.edu'
add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)
add_virtualhost('lists.domain1.net', 'lists.domain1.net')
add_virtualhost('lists.domain2.net', 'lists.domain2.net')
POSTFIX_STYLE_VIRTUAL_DOMAINS = ['lists.domain1.net', 'lists.domain2.net']
RewriteCond %{REQUEST_URI} !^/pipermail/([a-z]+)\.(.*)?$ [NC]
RewriteRule ^/pipermail/(.*)$ /pipermail/%{SERVER_NAME}/$1 [R=301,L]
Basically all it does is insert lists.domainX.net between /pipermail/ and
/test-list/. Public archives are now working with
http://lists.domain1.net/pipermail/lists.domain1.net/test-list/
So you can't have lists with names beginning with letters and a dot.
I think a better method would be a separate Alias /pipermail/ directive
in each VirtualHost block.
Right. That was a quick rule and i already realized that couple of my lists are
not gonna work with this.
There is, however, a common name convention, so i will make a better match
later.
As far as virtual hosts go, I'd like to keep configuration to a minimum. As i
mentioned on IRC, I am looking at approximately 20 separate domains and
maintaining 20 separate installations and configs is a management nightmare.
Next I tried to test Private archives and this is where I hit the wall and
need some help with.
The listinfo page for my test-list showed that the URL for the private
archives was http://lists.domain1.net/private/test-list, so i figured i
would be able to fix it with the same rewrite rule that i used for the
Public archives.
As I said, because I'm compulsive I will look at this in more detail
and follow up, but probably not for a few days.
Thanks, Mark! I really appreciate the help.
--
Mailman-Users mailing list Mailman-Users@python.org
http://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:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Mailman and Gmane ?
On Fri, 22 Jan 2010 16:33:07 -0800, Mark Sapiro wrote: John Fitzsimons wrote: Hi Mark, snip You can use something like Jim T's and my mailman-subscribers.py script[1] to screen scrape the web admin Membership List and make a .csv file of the membership together with those options except language that are on the Membership List pages, snip It accesses the list's admin Membership Management... - Membership List pages and parses them to get the data. snip There appears to be a problem here. I get an error. Here is what happened.. C:\mailman-subscribers.py -c http://domain listname_domain password The filename, directory name, or volume label syntax is incorrect. Also, I don't suppose that there is a script to collect all the customising that one has done with a mailing list is there ? Thanks. Regards, John. -- Mailman-Users mailing list Mailman-Users@python.org http://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: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
