Notes on upgrading to the current CVS tree of Mailman:
- I ran configure and make as myself, su'ed to mailman, and then ran into some trouble on the "make install" because some files aren't world-readable:
scripts/driver Numerous templates/*.txt files Mailman/Logging/*.py
But it's much less error-prone to do everything as the mailman user...
The documentation should mention that you should alias /pipermail/ to <prefix>/public_html/archives/ .
The mailbox-format archive is stored as a gzip'ped file, but referenced in the HTML in uncompressed form. Why? Are you expected to configure the Web server to automatically uncompress it? If so, how do you do that?
Is there any way to clear out my test e-mails from the archives? Since Mailman has just been set up, it would be fine with me if I could just blow away public_html/archives; would it be created again?
-- A.M. Kuchling http://starship.skyport.net/crew/amk/ "Are you ready for me? Are you ready for my indifference? For my abysmal disinterest? Are you ready to have the lies and conceits of your life peeled away like so many layers of skin? Are you ready for the truth?" "Ahhh... No, I... I don't really think I am..." -- The Truth and Michael Smith, in ENIGMA #4: "And Then What?"
"AMK" == Andrew M Kuchling <akuchlin@cnri.reston.va.us> writes:
AMK> Notes on upgrading to the current CVS tree of Mailman:
AMK> * I ran configure and make as myself, su'ed to mailman, and
AMK> then ran into some trouble on the "make install" because some
AMK> files aren't world-readable:
| scripts/driver
| Numerous templates/*.txt files
| Mailman/Logging/*.pyI believe I've fixed all the permission problems for the files in the CVS repository. I'm probably the biggest culprit, my umask used to be set up bogusly and I haven't been able to get CVS to fix the permission on files in the repository automatically. We developers just need to be careful when we check stuff in.
-barry
"AMK" == Andrew M Kuchling <akuchlin@cnri.reston.va.us> writes:
AMK> But it's much less error-prone to do everything as the
AMK> mailman user...I would like a guiding principle to be that the installation does not require you to be any special user (mailman or root). That may not be possible but so far it has been. If it really is not possible, then we'll have to add an extra step to the installation process -- one that you would execute after the main install, and which you would do as the special user. I'm looking into this.
-Barry
Been looking through the docs and the archives for getting pipermail to work with mailman. I am using mailman-1.0b5. Any links or hints on how to get it up and running???
TIA Michael
I'm thinking that if you can, you might as well just hold off on it for a bit; Pipermail support was checked into the development CVS tree the week before last, and a new release (with Pipermail support) is in the works for the not-so-distant future.
Corbett J. Klempay Quote of the Week: http://www2.acm.jhu.edu/~cklempay "Keep your faith in all beautiful things; in the sun when it is hidden, in the Spring when it is gone."
PGP Fingerprint: 7DA2 DB6E 7F5E 8973 A8E7 347B 2429 7728 76C2 BEA1
On Mon, 19 Oct 1998, Michael Ghens wrote:
Been looking through the docs and the archives for getting pipermail to work with mailman. I am using mailman-1.0b5. Any links or hints on how to get it up and running???
TIA Michael
Mailman-Users maillist - Mailman-Users@python.org http://www.python.org/mailman/listinfo/mailman-users
participants (4)
-
Andrew M. Kuchling -
Barry A. Warsaw -
Corbett J. Klempay -
Michael Ghens