[Mailman-Users] Using topics vs. Additional Lists

Joe Burkhart joe.burkhart at tdhca.state.tx.us
Wed Jun 23 22:43:24 CEST 2004


Now I see that as the admin you can search for a user on the member
management screen then click the hyperlinked email address for them.  (I'm
so used to seeing email addresses linked with mailto: that I don't consider
it might actually go somewhere anymore.)  Thanks for pointing that out.

But, it would be very helpful to be able to query for a list of all members
subscribed to a particular topic from the command line or elsewhere.  Is
that possible?

--Joe

-----Original Message-----
From: Joe Burkhart 
Sent: Wednesday, June 23, 2004 3:35 PM
To: 'Mailman-Users at python.org'
Subject: RE: [Mailman-Users] Using topics vs. Additional Lists


I'm using version 2.1.2, and when you find a member using the member
management screen, there is no listing for topics. Following are the
displayed options:

unsub | member address, member name | mod | hide | nomail | ack | not metoo
| nodupes | digest | plain | language

Any other suggestions?  Maybe there's a way to do this at the command line?

Thanks,

Joe

-----Original Message-----
From: Christopher Adams [mailto:chris.a.adams at state.or.us] 
Sent: Thursday, June 17, 2004 6:33 PM
To: Mailman-Users at python.org
Subject: Re: [Mailman-Users] Using topics vs. Additional Lists


I would say that the main advantage to topics is that the list admin 
only has to maintain one list. Also, the subscribers can opt to receive 
only information defined by topic, or others not defined by any topic.

If you want to check the topics for a particular subscriber, you can 
enter their email address in the user page and see the topics. However, 
you would only be able to do this for each subscriber.

-- 
Christopher Adams




Joe Burkhart wrote:

>First, we're planning a one-way list that our organization will use to
>send updates and news to subscribers and not accept postings from 
>members. We have several categories of messages that may be sent out 
>depending on the program the message pertains to.  We're weighing the 
>benefits of using one main list with different topics setup for each 
>category against using separate lists for each category. Does anyone 
>have an opinion about using topics instead of creating separate lists 
>in our  situation?
>
>Second, one major disadvantage I can see in using topics is that as the
>admin, you can't see which topics a member has selected to receive. So, 
>there's no way to judge the effectiveness/popularity of your topics. Is 
>there some way to see this?
>
>Thanks,
>
>Joe
>
>------------------------------------------------------
>Mailman-Users mailing list
>Mailman-Users at python.org
>http://mail.python.org/mailman/listinfo/mailman-users
>Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
>Searchable Archives: 
>http://www.mail-archive.com/mailman-users%40python.org/
>  
>




------------------------------------------------------
Mailman-Users mailing list
Mailman-Users at python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/




More information about the Mailman-Users mailing list