[Mailman-Users] some suggestions for mailman 2
wildfire at progsoc.uts.edu.au
Thu Aug 31 01:57:17 CEST 2000
On Wed, Aug 30, 2000 at 11:23:39AM -0700, J C Lawrence wrote:
> On Wed, 30 Aug 2000 12:04:07 +1100
> Anand Kumria <wildfire at progsoc.uts.edu.au> wrote:
> > I've now been using Mailman (note no studly caps) for a while so,
> > here are some comments:
> > - I've placed my lists at /lists/ instead of /mailman/ so
> > that required a patch to SecurityManager.py to send cookies with
> > the right path
> I do the same, as you can see here:
> This has required no patching to any of the Mailman sources, other
> than the normal Defaults.py/mm_cfg.py business.
> (Yes, I know I'm running v1.1, but the same was true when testing
> out moving to one of the v2 betas (I'm not ready to roll it into
> production there))
Strange, I'm using 1.1 as well and in SecurityManager.py, I traced my
administration authentication problem down to:
--- /usr/lib/mailman/Mailman/SecurityManager.py-dist Mon Jun 19 02:15:40 2000+++ /usr/lib/mailman/Mailman/SecurityManager.py Mon Jun 19 02:18:14 2000
@@ -94,7 +94,8 @@
c = Cookie.Cookie()
c[key] = [client_ip, issued, expires, mac]
# place in oven,
- path = urlparse(self.web_page_url) # '/mailman'
+ #path = urlparse(self.web_page_url) # '/mailman'
+ path = '/lists'
c[key]['path'] = path
# and bake until golden brown
c[key]['expires'] = mm_cfg.ADMIN_COOKIE_LIFE
Otherwise things were working correctly.
>From the corresponding mm_cfg.py:
DEFAULT_HOST_NAME = 'slug.org.au'
DEFAULT_URL = 'http://slug.org.au/lists/'
> > - I'd be *most useful* to have a another subscriber option
> > which indicated that the subscriber wasn't really a person but
> > was, in reality, a sublist. For those subscribers monthly notices
> > (which should also be a per-subscriber thing IMO) and other
> > administrativia would be sent to owner-<subscriber> (or
> > <subscriber>-owner, or <subscriber>-admin).
> This is what the umbrella options are for.
Yes but it is currently an all or nothing affair (afaict). Either all your
list members are people or they are all sublists and never the two shall
I've unfortunately inhereted a list with mixed subscribers. But even if I
hadn't I can see great uses with having `sublist' be a per subscriber
option - for large lists you could have domain based feeders, etc.
> > - I'd love to be able to edit messages that get held for
> > approval. So that I can remove HTML from some email, reset the
> > reply-to to somewhere more appropriate or simply trim things down
> > and insert a "modified by whomever" message.
> On v2 you can.
Great, I'll probably check it out shortly.
More information about the Mailman-Users