Re: [Mailman-Users] Private archive access

Peter wrote: > >Just an question about access to a private archive.I n the past I run an >archive that was protected via htaccees. >With a user name and password every one has the access to the archive. >With mailman and its archiver (nice by the way) the directory is >protected via the users em

Re: [Mailman-Users] Recovering a config.pck file from the output ofdumpdb

Kelly Jones wrote: >I backup my mailman config.pck files nightly by running "dumpdb >config.pck" and storing the output (the output of dumpdb is easier to >read and easier to diff [for CVS'd backups] than the config.pck file >itself). > >How do I get back config.pck from the output of dumpdb? > >I

[Mailman-Users] Recovering a config.pck file from the output of dumpdb

I backup my mailman config.pck files nightly by running "dumpdb config.pck" and storing the output (the output of dumpdb is easier to read and easier to diff [for CVS'd backups] than the config.pck file itself). How do I get back config.pck from the output of dumpdb? In other words, what command

[Mailman-Users] Private archive access

Hello Just an question about access to a private archive.I n the past I run an archive that was protected via htaccees. With a user name and password every one has the access to the archive. With mailman and its archiver (nice by the way) the directory is protected via the users email adress an

Re: [Mailman-Users] us-ascii problem with new install in Ubuntu(SOLVED)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Jan 10, 2007, at 2:26 PM, Barry Finkel wrote: > I read the entire bug page trail, and I am trying to understand it. > I looked at my 2.1.9 source test installation (on Solaris 10, where I > installed into /opt/mailman), and I see things in the > >

Re: [Mailman-Users] us-ascii problem with new install in Ubuntu(SOLVED)

Mark Sapiro wrote: >> Some additional information: >> >> This is mailman 2.1.8-2ubuntu2. >> >> The reference to the 'bug fix' is at >> >> in which is found >> >> * Make sure we don't ship /var/lib/mailm

Re: [Mailman-Users] Email address with trailing space

Trader Joe wrote: >While doing "mass subscription", I accidently put in >an extra space at the end of several email addresses >and now I'm unable to unsubscribe or remove these >email via Web tools. Anyone know how to remove these? What Mailman version is this? I am unable to duplicate this wit

Re: [Mailman-Users] us-ascii problem with new install in Ubuntu(SOLVED)

Mark Sapiro wrote: > Some additional information: > > This is mailman 2.1.8-2ubuntu2. > > The reference to the 'bug fix' is at > > in which is found > > * Make sure we don't ship /var/lib/mailman/pyt

Re: [Mailman-Users] Email address with trailing space

Trader Joe wrote: > While doing "mass subscription", I accidently put in > an extra space at the end of several email addresses > and now I'm unable to unsubscribe or remove these > email via Web tools. Anyone know how to remove these? > > You have to escape them, try preceding the space with "

Re: [Mailman-Users] us-ascii problem with new install in Ubuntu(SOLVED)

Mark Sapiro wrote: > >It seems that the basic issue is that the Mailman installation in some >Ubuntu distributions is missing the pythonlib/ directory containing >the appropriate Python email library. This is intentional on Ubuntu's >part. It is a 'bug fix'. Some additional information: This is

[Mailman-Users] Email address with trailing space

While doing "mass subscription", I accidently put in an extra space at the end of several email addresses and now I'm unable to unsubscribe or remove these email via Web tools. Anyone know how to remove these? Example: I put the address as "[EMAIL PROTECTED] " instead of "[EMAIL PROTECTED]". I r

Re: [Mailman-Users] us-ascii problem with new install in Ubuntu (SOLVED)

In an off-list exchange regarding an issue previously posted at and , we may have arrived at a solution/work-around. It seems that the basic issue is

Re: [Mailman-Users] getting correct alias domain in message headers

Mark Sapiro wrote: > >I am not an MTA expert, and even if I were, you haven't told me what >the MTA is, so I can't help further. This is a question for your MTA >support resources. In a brief, off-list exchange, Hank wrote the following: Anyway, I thought I'd post the "fix" for sendmail for the

Re: [Mailman-Users] make issues

Dan and Jodi Zemke wrote: >Any insight about these >errors would be greatly appreciated. > >./configure --prefix=/usr/local/mailman-2.1.9 Is the directory into which you unpacked the tarball also /usr/local/mailman-2.1.9 ? The directory in which you unpack, configure and make should not be the

Re: [Mailman-Users] logs no longer working

Webmaster wrote: >okay I found them. thanks. how can I change their location so fedora's >logrotate is integrated? In mm_cfg.py, set LOG_DIR = '/var/log/mailman' or wherever you want them. -- Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers, San Francisco Bay Area, Californ

Re: [Mailman-Users] logs no longer working

okay I found them. thanks. how can I change their location so fedora's logrotate is integrated? - Original Message - From: "Mark Sapiro" <[EMAIL PROTECTED]> To: "Webmaster" <[EMAIL PROTECTED]>; Sent: Tuesday, January 09, 2007 1:07 PM Subject: Re: [Mailman-Users] logs no longer working

Re: [Mailman-Users] Mailman-Users Digest, Vol 35, Issue 14

dont u guys think it a bit convrinent that so many things that are unlikely to happen if left to the general percentages are happening ? seems your not seeing the obvious. you got a very smart bug. Never Miss a