Re: [Mailman-Users] How to transfer Majordomo archive to mailman
Hi Bryan, no need to send a post to the list _and_ a cc to me as I am reading the list :-) Bryan Blackwell <[EMAIL PROTECTED]> wrote : > Majordomo doesn't (by default anyway) store its sent messages in an > mbox. My archives are essentially a directory with all the digests. > You can see one of the digests here: > > http://www.corvair.org/chapters/test/v02.n4928.txt As far as I can see you should provide a real mbox where eMails are stored with full headers. If you do not have one, you can only re-post them to the new mailman-list, but I am unsure about that. The initial mbox-conversion to HTML can be done with (Mailman version 2.1.6b3) [EMAIL PROTECTED] /usr/local/mailman/bin: ./arch --help Rebuild a list's archive. Use this command to rebuild the archives for a mailing list. You may want to do this if you edit some messages in an archive, or remove some messages from an archive. Usage: ./arch [options] [] Where options are: -h / --help Print this help message and exit. -q / --quiet Make the archiver output less verbose. --wipe First wipe out the original archive before regenerating. You usually want to specify this argument unless you're generating the archive in chunks. -s N --start=N Start indexing at article N, where article 0 is the first in the mbox. Defaults to 0. -e M --end=M End indexing at article M. This script is not very efficient with respect to memory management, and for large archives, it may not be possible to index the mbox entirely. For that reason, you can specify the start and end article numbers. Where is the path to a list's complete mbox archive. Usually this will be some path in the archives/private directory. For example: % bin/arch mylist archives/private/mylist.mbox/mylist.mbox is optional. If it is missing, it is calculated. If this is not easy enough I cannot be of anymore help as I did my migration with this one. bis dahin/kind regards Martin Mewes -- I am on holiday. Your e-mail has been deleted. -- Mailman-Users mailing list Mailman-Users@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/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
Re: [Mailman-Users] 2 initial config problems (virtual hosts andpermissions)
FH wrote:
>
>1) Error: Unknown virtual host: machine
>I was able to create the mailman list via the cli (step 8) w/o any problems.
>When I try creating a list via the web though I get the above error. I've
>played around w/ a few combinations of machine machine.domain.tld etc in the
>mm_cfg.py file and the add_virtualhost parameter but I still either get the
>error or I get another page which says something about a "bug" in the program
>(funny thing is even when I get this page the list is created).
>
This error occurs because the hostname of the URL used to access the
list create web page is not a key (one of the "URL host" entries) in
the VIRTUAL_HOSTS dictionary.
>FWIW as I mentioned the machine is also our mail server, the hostname command
>returns MACHINE (in case that's important). The DNS name (aka it's not a
>CNAME) of the machine is MACHINE.DOMAIN.TLD (which is also the
>DEFAULT_URL_HOST [set via the configure option]), email though is addressed to
>@DOMAIN.TLD (which is also the DEFAULT_EMAIL_HOST [set via the configure
>option]). As mentioned the error just says "MACHINE" so I've tried things
>like add_defaultdomain ('MACHINE', 'DOMAIN.TLD')
What's this? Do you mean
add_virtualhost('MACHINE', 'DOMAIN.TLD')
which is what you should do to allow 'MACHINE' to be a URL host.
>but that's when I get the
>other "bug" page (apologies I don't have a copy handy but if it's important I
>can probably regenerate it).
If it resulted after adding the above add_virtualhost() in mm_cfg.py, I
don't know why without seeing it.
If you're not actually using virtual hosts, you can set
VIRTUAL_HOST_OVERVIEW = Off
in mm_cfg.py, and it will avoid checks like the one that produces the
above error.
>Also I noticed when I pull up the
>http://machine/mailman/admin page at the bottom is says "Send questions and
>comments to [EMAIL PROTECTED]" that's it not [EMAIL PROTECTED] Is
>that somehow related?
Here again, the host name part of the URL ('machine' in the case of
http://machine/mailman/admin) is looked up in the VIRTUAL_HOSTS
dictionary and the corresponding email host is used inless there is no
such key in which case just the host name is used.
> What's the appropriate syntax so that MACHINE is an
>"acceptable" virtual host.
add_virtualhost('MACHINE', 'DOMAIN.TLD')
>BTW in case it's related I don't have any virtual hosts set in postfix and
>mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain
>myhostname = MACHINE.DOMAIN.TLD
>mydomain = DOMAIN.TLD
>
>
>
>2) Looking at the maillog file I'm seeing this error occasionally
>
>Feb 28 16:31:31 MACHINE postfix/postalias[1765]: [ID 947731 mail.crit] fatal:
>open /local/home/mailman/data/aliases.dir: Permission denied
>
>Applicable info for this error includes:
>MACHINE# ls -al /local/home/mailman/data/
>total 44
>drwxrwsr-x 2 root mailman 512 Feb 28 16:38 ./
>drwxrwsr-x 20 root mailman 512 Feb 28 16:02 ../
>-rw-r- 1 root mailman 41 Feb 28 16:22 adm.pw
>-rw-rw 1 root mailman 1165 Feb 28 16:38 aliases
>-rw-r- 1 mailman mailman0 Feb 28 16:38 aliases.dir
>-rw-r- 1 mailman mailman 1024 Feb 28 16:38 aliases.pag
>
>At one point I did chown aliases* to mailman but it has since reverted. When
>I originally configured mailman I used the --with-mail-gid=postdrop and I
>didn't specify a username (there is obviously a mailman user ;)). Although
>the install.txt file recommended using hash my install of postfix has problems
>w/ that so I'm using:
>alias_maps = dbm:/etc/mail/aliases,dbm:/local/home/mailman/data/aliases
>
>All things postfix are running as the user postfix, all things mailman
>(qrunner is the only continuous process right?) are running as mailman. I did
>put the postfix "user" in the mailman group (mailman isn't in there though)
The 'mailman' user should definitely be in the 'mailman' group.
>thinking that may help but it didn't seem too. BTW the apache server is
>mostly running as nobody, there is one instance that ends up as root. (The
>apache server is brand new too but that install/config seems to have gone ok.
>Eventually though I want to clear up the 1 root instance and integrate SSL in
>but I figured it was best to get the above issues worked out first ;))
>
>What are the proper owner/permission settings for these files?
Have you tried bin/check_perms?
--
Mark Sapiro <[EMAIL PROTECTED]> The 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://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Security Policy:
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.
Re: [Mailman-Users] Moving of the subscribers with their passwords, preferences etc.
I just did exactly this, following the procedure at: http://www.mail-archive.com/mailman-developers@python.org/msg03127.html Worked great. -- -- Bryan Blackwell -- Unix System Administrator [EMAIL PROTECTED] On Feb 28, 2005, at 6:38 PM, Andy wrote: Hi! Is that possible during moving of the lists to a new server to move all users along with their e-mails, names, passwords and preferences they set, so that they would not need to resubscribe (or that list-owner would not need to subscribe them again, what would unfortunately generate new passwords for them)? Which files to move in order to do that? Regards ak -- Mailman-Users mailing list Mailman-Users@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/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
Re: [Mailman-Users] How to transfer Majordomo archive to mailman
I've been looking for an answer to migrating archives as well. The only problem with this procedure is this step: On Feb 28, 2005, at 4:51 PM, Martin Mewes wrote: d) Copy the mbox of the majordomo-list to the correct place of the mailman-mbox Majordomo doesn't (by default anyway) store its sent messages in an mbox. My archives are essentially a directory with all the digests. You can see one of the digests here: http://www.corvair.org/chapters/test/v02.n4928.txt I've taken a look at the old digest_arch script, but I don't know python at all to figure out how to make it work (I tried a pass on some test files, but didn't end up with a useful mbox). I've also dug through the FAQ and the Mailman Users list archive, but I haven't found a posted solution. If someone has made this work and can pass a solution or clue, I'd be grateful. I do know perl and shell scripting well enough to adapt someone else's solution, if something like that exists. Thanks for any insight. -- -- Bryan Blackwell -- Unix System Administrator [EMAIL PROTECTED] -- Mailman-Users mailing list Mailman-Users@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/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
Re: [Mailman-Users] filtering body content
List Manager wrote: > >I know that it has been asked many many times but I haven't seen any >solutions posted about how to filter the body content of the messages. Does >someone have a solution for that? Or even a work-around? I assume you don't mean filtering based on MIME Content-Type: since that is completely doable with the existing content filtering options. Rather, I guess you mean filtering based on the actual contents of the message. To do this, you can create a custom handler module to do the filtering and add it to the pipeline. It could be added either to the GLOBAL_PIPELINE or to a list specific pipline attribute. There are existing patches/handlers to interface for example with SpamAssassin. See for example http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq04.023.htp -- Mark Sapiro <[EMAIL PROTECTED]> The 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://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
Re: [Mailman-Users] Moving of the subscribers with their passwords, preferences etc.
Andy wrote: > >Is that possible during moving of the lists to a new server to move all users >along with their e-mails, names, passwords and preferences they set, so that >they would not need to resubscribe (or that list-owner would not need to >subscribe them again, what would unfortunately generate new passwords for >them)? >Which files to move in order to do that? Move the directories and files in the lists/ directory. At a minimum all you really need for list settings, members, member options and passwords is the lists//config.pck (or config.db for pre 2.1.x) file for each list. You can move a config.* from an older release to a newer release and Mailman should automatically update it on the new release, but I think this is only guaranteed for config.pck files. In the case of a config.db file, there are possible incompatibilities if the Python versions are different on the source and destination. -- Mark Sapiro <[EMAIL PROTECTED]> The 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://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
Re: [Mailman-Users] Full Personalization CC: field
Pantejo, Barbara wrote: >I turned on Full Personalization under the Non-Digestable area, but I >noticed that the name of the mailing list (i.e. the mailing list >description) was sent in the CC: field. What should I do to empty the CC: >field or at least don't send the name of the mailing list in the CC: field? > This is done intentionally so that the list address is in a header to facilitate replies to the list. It is not done if the list is set for "reply goes to list" as the list address is already in Reply-To: in this case. Also, beginning with 2.1.6 (or with the patch at http://sourceforge.net/tracker/index.php?func=detail&aid=1117618&group_id=103&atid=300103), it is not done if the list is "anonymous" as the list address is already in From: and Reply-To: in that case. If the list is fully personalized, not anonymous and not "reply goes to list", the list description and address will be placed in Cc: unless you change the code in Mailman/Handlers/CookHeaders.py to do otherwise. -- Mark Sapiro <[EMAIL PROTECTED]> The 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://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
[Mailman-Users] Moving of the subscribers with their passwords, preferences etc.
Hi! Is that possible during moving of the lists to a new server to move all users along with their e-mails, names, passwords and preferences they set, so that they would not need to resubscribe (or that list-owner would not need to subscribe them again, what would unfortunately generate new passwords for them)? Which files to move in order to do that? Regards ak -- Mailman-Users mailing list Mailman-Users@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/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
Re: [Mailman-Users] block cc?
Chuq Von Rospach wrote: > >On Feb 28, 2005, at 12:59 PM, Christopher Adams wrote: > >> A list owner asked me if a list can be configured so that any message >> sent to the list could not have a cc (carbon copy) attached. > >that'd be a very bad idea. Look at this message, for instance. It'd >block any message sent to the list with reply-to-all. > >you'd be blocking stuff based on a standard operation by many mail >clients. I agree with Chuq, but if you really want to do this, you can go to Privacy options...->Recipient filters and set require_explicit_destination to Yes and max_num_recipients to 2 and then any post which is not addressed to the list and only the list will be held. Neither this nor anything else you can do will stop Bcc: though. -- Mark Sapiro <[EMAIL PROTECTED]> The 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://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
[Mailman-Users] 2 initial config problems (virtual hosts and permissions)
I just started playing around w/ Mailman this morning so I'm VERY new to all
this ;) The initial config and install seemed to go ok but I have a couple of
questions/problems/issues I'd appreciate some help w/. I looked around the
FAQ and found info on 1 of them but I can't seem to figure out the right
syntax to fix my problem.
BTW I used the mailman-install.txt file as my guide. I'm running this on a
Solaris9 machine w/ postfix as the MTA.
1) Error: Unknown virtual host: machine
I was able to create the mailman list via the cli (step 8) w/o any problems.
When I try creating a list via the web though I get the above error. I've
played around w/ a few combinations of machine machine.domain.tld etc in the
mm_cfg.py file and the add_virtualhost parameter but I still either get the
error or I get another page which says something about a "bug" in the program
(funny thing is even when I get this page the list is created).
FWIW as I mentioned the machine is also our mail server, the hostname command
returns MACHINE (in case that's important). The DNS name (aka it's not a
CNAME) of the machine is MACHINE.DOMAIN.TLD (which is also the
DEFAULT_URL_HOST [set via the configure option]), email though is addressed to
@DOMAIN.TLD (which is also the DEFAULT_EMAIL_HOST [set via the configure
option]). As mentioned the error just says "MACHINE" so I've tried things
like add_defaultdomain ('MACHINE', 'DOMAIN.TLD') but that's when I get the
other "bug" page (apologies I don't have a copy handy but if it's important I
can probably regenerate it). Also I noticed when I pull up the
http://machine/mailman/admin page at the bottom is says "Send questions and
comments to [EMAIL PROTECTED]" that's it not [EMAIL PROTECTED] Is
that somehow related? What's the appropriate syntax so that MACHINE is an
"acceptable" virtual host.
BTW in case it's related I don't have any virtual hosts set in postfix and
mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain
myhostname = MACHINE.DOMAIN.TLD
mydomain = DOMAIN.TLD
2) Looking at the maillog file I'm seeing this error occasionally
Feb 28 16:31:31 MACHINE postfix/postalias[1765]: [ID 947731 mail.crit] fatal:
open /local/home/mailman/data/aliases.dir: Permission denied
Applicable info for this error includes:
MACHINE# ls -al /local/home/mailman/data/
total 44
drwxrwsr-x 2 root mailman 512 Feb 28 16:38 ./
drwxrwsr-x 20 root mailman 512 Feb 28 16:02 ../
-rw-r- 1 root mailman 41 Feb 28 16:22 adm.pw
-rw-rw 1 root mailman 1165 Feb 28 16:38 aliases
-rw-r- 1 mailman mailman0 Feb 28 16:38 aliases.dir
-rw-r- 1 mailman mailman 1024 Feb 28 16:38 aliases.pag
At one point I did chown aliases* to mailman but it has since reverted. When
I originally configured mailman I used the --with-mail-gid=postdrop and I
didn't specify a username (there is obviously a mailman user ;)). Although
the install.txt file recommended using hash my install of postfix has problems
w/ that so I'm using:
alias_maps = dbm:/etc/mail/aliases,dbm:/local/home/mailman/data/aliases
All things postfix are running as the user postfix, all things mailman
(qrunner is the only continuous process right?) are running as mailman. I did
put the postfix "user" in the mailman group (mailman isn't in there though)
thinking that may help but it didn't seem too. BTW the apache server is
mostly running as nobody, there is one instance that ends up as root. (The
apache server is brand new too but that install/config seems to have gone ok.
Eventually though I want to clear up the 1 root instance and integrate SSL in
but I figured it was best to get the above issues worked out first ;))
What are the proper owner/permission settings for these files?
Thanks for the hints/clues/suggestions.
--
Mailman-Users mailing list
Mailman-Users@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/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Security Policy:
http://www.python.org/cgi-bin/faqw-mm.py?req=show&fileúq01.027.htp
[Mailman-Users] filtering body content
Hello everyone, I know that it has been asked many many times but I haven't seen any solutions posted about how to filter the body content of the messages. Does someone have a solution for that? Or even a work-around? Best wishes, Rae -- Mailman-Users mailing list Mailman-Users@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/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
[Mailman-Users] Full Personalization CC: field
I turned on Full Personalization under the Non-Digestable area, but I noticed that the name of the mailing list (i.e. the mailing list description) was sent in the CC: field. What should I do to empty the CC: field or at least don't send the name of the mailing list in the CC: field? Thanks for any assistance, Barbara -- Mailman-Users mailing list Mailman-Users@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/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
Re: [Mailman-Users] How to transfer Majordomo archive to mailman
Hi, trishan de Lanerolle <[EMAIL PROTECTED]> wrote : [...] > majordomo. We configured it and set it up on new server. My question > is are there instructions or scripts available to transfer majordomo > archives and subscription lists over to mailman. When I did the move from majordomo to mailman I did it manually for each list (10). a) Send a message to the old majordomo-list that during the next minutes the mailinglist-software will change and posts to the llist will bounce between ... and ... aprox. b) Stop majordomo (delete the /etc/aliases-entry) c) Set up and configure the new mailinglist in mailman, edit /etc/aliases but set a # in front of the aliases for now. c) Mass subscribe the majordomo-members in mailman with notifiers to the people. d) Copy the mbox of the majordomo-list to the correct place of the mailman-mbox e) Rebuilt the HTML-Archive with "arch" http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq04.009.htp More help is available with arch --help on the commandline. f) Edit the /etc/aliases and take away the # infront of the mailman-aliases. g) Send a post to the new mailman-list. Done ... bis dahin/kind regards Martin Mewes -- Sorry to have missed you but I am at the doctors having my brain removed so that I may be promoted to management -- Mailman-Users mailing list Mailman-Users@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/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
Re: [Mailman-Users] block cc?
On Feb 28, 2005, at 12:59 PM, Christopher Adams wrote: A list owner asked me if a list can be configured so that any message sent to the list could not have a cc (carbon copy) attached. that'd be a very bad idea. Look at this message, for instance. It'd block any message sent to the list with reply-to-all. you'd be blocking stuff based on a standard operation by many mail clients. -- Mailman-Users mailing list Mailman-Users@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/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
[Mailman-Users] block cc?
A list owner asked me if a list can be configured so that any message sent to the list could not have a cc (carbon copy) attached. I said I didn't think so and I see that reply headers, though somewhat configurable in Mailman, is not something to mess with. Anyone ever deal with this. I guess that some other mailing list software can do this. -- Christopher Adams -- Mailman-Users mailing list Mailman-Users@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/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
Re: [Mailman-Users] Automated bounce removal
On Mon, 28 Feb 2005, Chance Eppinette wrote: I am new to this list, but have been a long-term Mailman user. My current Mailman version is 2.0.11 I'm pretty sure some bugs related to the bounce runner were fixed in the 2.1 series. (From google searches.) None indicate this one specifically though. We have a list of over 13000 members. I have the bounce options set to remove & notify the administrator when excessive bounces occur for a subscribed member. However, the system is not removing the subscribers after the minimum bounces of 2 occur. Do you still get the notification or is nothing happening related to the bounces? Gerald ULM graduate '99. -- Mailman-Users mailing list Mailman-Users@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/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
[Mailman-Users] How to transfer Majordomo archive to mailman
Hi, I am new to mailman and recently took over the mailing lists administration at my college. The system administrator and I installed and configured mailman to replace the currently used majordomo. We configured it and set it up on new server. My question is are there instructions or scripts available to transfer majordomo archives and subscription lists over to mailman. Mailman is version 2.1.5-6 running on Debian Linux 2.4.26-1-k7. Thank you Trishan Systems & Networking Trinity College Hartford CT -- Mailman-Users mailing list Mailman-Users@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/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
[Mailman-Users] Automated bounce removal
Hello, I am new to this list, but have been a long-term Mailman user. My current Mailman version is 2.0.11 We have a list of over 13000 members. I have the bounce options set to remove & notify the administrator when excessive bounces occur for a subscribed member. However, the system is not removing the subscribers after the minimum bounces of 2 occur. Has anyone encountered this issue and should it be fixed in newer versions? Thanks, Chance Eppinette Technology Support Manager ULM Computing Center [EMAIL PROTECTED] 318-342-5021 (phone) 318-342-5018 (fax) -- Mailman-Users mailing list Mailman-Users@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/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
Re: [Mailman-Users] Populating member name in Mass Subscription
Pantejo, Barbara wrote: >I noticed in the Member Management->Membership List section that a member >name can be associated with the member address. Can I populate the member >name using an uploaded file in the Mass Subscription? In other words, in the >upload file can I place the member name after the member address, with a >space between the email addres and the name? See the FAQ >Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Article 3.44 -- Mark Sapiro <[EMAIL PROTECTED]> The 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://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
[Mailman-Users] Populating member name in Mass Subscription
I noticed in the Member Management->Membership List section that a member name can be associated with the member address. Can I populate the member name using an uploaded file in the Mass Subscription? In other words, in the upload file can I place the member name after the member address, with a space between the email addres and the name? For example, in the upload file it would look like this: [EMAIL PROTECTED] Tom Smith [EMAIL PROTECTED] Bob Jones [EMAIL PROTECTED] William Bell If this cannot be done, how can I populate the member names along with the member addresses in a Mass Subscription method? I appreciate any feedback, Barbara -- Mailman-Users mailing list Mailman-Users@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/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
Re: [Mailman-Users] mailman bug
Thanks Mark, That fixed it, at least temporarily. I did have to change the name with mv before I removed it. Mark Ballard Site Technology Specialist El Molino High School http://www.elmolino.org On Feb 27, 2005, at 10:28 AM, Mark Sapiro wrote: Mark Ballard wrote: Mailman has been working fine for a couple of week now and it just stopped with a bug. Below is what it tells me when I go to admindb on any list. any ideas??? Bug in Mailman version 2.1.2 File "/usr/share/mailman/Mailman/MailList.py", line 487, in __save os.unlink(fname_last) OSError: [Errno 22] Invalid argument: '/private/var/mailman/lists/bulletin/config.pck.last' This problem seems to occur with varying frequency in Mac OSX. See http://www.google.com/search? q=site%3Amail.python.org+%22errno+22%22+config.pck.last The immediate solution is to manually remove the offending config.pck.last file - one person reported he had to rename it with "mv" before he could remove it. No one seems to know what the underlying cause or permanent solution is. -- Mark Sapiro <[EMAIL PROTECTED]> The 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://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
Re: [Mailman-docs] Re: [Mailman-Users] How to get Sender Id from the Mailing List where the annoymous option is set
On Thu, 2005-02-17 at 16:23, Brad Knowles wrote:
> At 3:57 AM -0800 2005-02-08, vijayan p wrote:
>
> > Can anyone tell me how to obtain the statistics of
> > which member has posted how many messages.
>
> I think you'd have to look at the incoming messages in the MTA
> logs, before they get handed off to Mailman. But keep in mind that
> Mailman does not have any facility for creating or monitoring
> statistics, unless you want to create a script to do that.
>
It's also recorded in Mailman's logs (the "post" log).
> > Also is there a way to know who has posted a
> > particular mail.
Yes. look at the post log.
Here is a stats script which does some of what you asked. I wrote it
about 3 years ago...
[EMAIL PROTECTED] Useful_scripts]$ more mm_stats
#! /bin/bash
# Run monthly stats on Meeting maker logs
# - top 10 users of each list
# - Number of attempted posts (per list)
# - Total bytes sent (per list)
# written by Jon Carnes, last modified on Sept 26, 2002
#
# Mailman's log file to be examined for stats
#POST=/home/mailman/logs/post
#
# Run this script the first of the month right after the
# the log files have been rotated. The log file for the
# previous month will then be post.1
POST=/var/log/mailman/post.1
# create temp file to collect stats
TMPFILE=`mktemp /tmp/mm_stats.XX` || exit 1
LIST="`/var/mailman/bin/list_lists |awk '{print $1}' |sed -n '2,$p'`"
for i in $LIST
do
echo "Stats from local Mailman list: $i" > $TMPFILE
echo " " >> $TMPFILE
echo -n " Starting: " >> $TMPFILE
head -1 $POST |cut -f1-3 "-d " >> $TMPFILE
echo -n " Ending:" >> $TMPFILE
tail -1 $POST |cut -f1-3 "-d " >> $TMPFILE
echo " ===" >> $TMPFILE
echo -n "Total posts to the list: " >> $TMPFILE
grep -i "post to $i " $POST |wc -l >> $TMPFILE
echo -n "Total SUCCESSFUL posts to the list: " >> $TMPFILE
grep -i "post to $i " $POST |grep success |wc -l >> $TMPFILE
SIZ=`grep -i "post to $i" $POST |grep success |cut -f2 -d= |cut -f1
-d,`
k=0; for j in $SIZ; do k=$(( j + k )); done
echo " Total bytes" = $k >> $TMPFILE
echo " " >> $TMPFILE
echo "Top 10 posters to the list:" >> $TMPFILE
grep -i "post to $i " $POST |cut -f 10 "-d " |sort |uniq -c \
|sort -bgr |head -10 >> $TMPFILE
echo " " >> $TMPFILE
# Mail collected stats off to the list admin and cc the mailman user
mail -s "Mailman Stats for List: $i" -c mailman $i-admin <$TMPFILE
done
# remove the temp file
rm $TMPFILE
===
Jon Carnes
--
Mailman-Users mailing list
Mailman-Users@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/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Security Policy:
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
