Re: [Mailman-Users] Lists disappearing after 2.1.17 upgrade
On 12/18/2013 04:01 PM, Sarasvati wrote: Today I upgraded Mailman from 2.1.15 to 2.1.17. And my public lists just disappeared! I mean, when I go to the page: http://www.unicode.org/mailman/listinfo/ I see only one test list that was made months ago. The lists I've made within the last couple of days don't show up. (They never had any traffic yet, they were just made.) Before the upgrade, they showed up in the public listing. Now they don't. The individual admin pages for them still seem to work, and the lists of subscribers are still there. And I assume if you go to the specific listinfo, i.e. http://www.unicode.org/mailman/listinfo/LISTNAME, that works too. Double check that the list's web admin Privacy options... - advertised setting is Yes. See the FAQ at http://wiki.list.org/x/lYA9. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Lists disappearing after 2.1.17 upgrade
Mark, Thank you so much! That particular FAQ helped, and now I can see my lists again! :-) Yes, they were appearing in the list info, and all were set public. I have only a single domain, so I set VIRTUAL_HOST_OVERVIEW = Off in mm_cfg.py and that did it. Thanks again! On 12/19/2013 7:09 AM, Mark Sapiro wrote: On 12/18/2013 04:01 PM, Sarasvati wrote: Today I upgraded Mailman from 2.1.15 to 2.1.17. And my public lists just disappeared! I mean, when I go to the page: . And I assume if you go to the specific listinfo, i.e. http://www.unicode.org/mailman/listinfo/LISTNAME, that works too. Double check that the list's web admin Privacy options... - advertised setting is Yes. See the FAQ at http://wiki.list.org/x/lYA9. -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Lists disappearing after 2.1.17 upgrade
Hello. My site isn't yet using Mailman, but have an installation with some test lists. I tried to find an answer in the archives, but no luck... Today I upgraded Mailman from 2.1.15 to 2.1.17. And my public lists just disappeared! I mean, when I go to the page: http://www.unicode.org/mailman/listinfo/ I see only one test list that was made months ago. The lists I've made within the last couple of days don't show up. (They never had any traffic yet, they were just made.) Before the upgrade, they showed up in the public listing. Now they don't. The individual admin pages for them still seem to work, and the lists of subscribers are still there. Anyone know how to fix this, to make the lists visible again? Thanks for any help or pointers to solutions... R. -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] lists lost labels (and footers) after moving mailman to a new server
Hi, We have recently upgraded our web server to one with bigger capacity. Actual moving occurred earlier today and was done by our hosting provider (since we don't have access to root to our dedicated server). Moving involved transferring all services active, including our mailman lists. Once moving has been completed we can see the lists have been actually moved, apparently correctly, configuration parameters remain the same as they were before, but, curiously enough, the messages are distributed without the usual label and without the footer, even though both label and footer are well defined in the configuration page and were working nicely in the old server configuration. According to the hosting provider they transferred everything to the new server, including all parameters of the list. They have been investigating the cause of these missing labels and footers but so far could not find any obvious cause. Things that I have tried so far: 1) Deleting the label, saving parameters, re-installing the label, saving parameters. Doesn't work, messages continue to be posted without label. 2) I created a new list in the new server, created a label for it, and, in this case, messages are posted with label in this newly created list in the new server location I am using mailman 2.1.11 I have been searching for similar posts before posting this to the list. I couldn't find any. Thanks for help and suggestions. best regards Lluis -- Dr. Lluis Montoliu Investigador Cientifico - Research Scientist CSIC Centro Nacional de Biotecnologia (CNB-CSIC) Campus de Cantoblanco C/ Darwin, 3 28049 Madrid (Spain) Tel. +34-91-5854844 / Fax +34-91-5854506 e-mail: monto...@cnb.csic.es WEB: http://www.cnb.csic.es/~montoliu/ -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] lists lost labels (and footers) after moving mailman to a new server
Thanks Mark, yes I am referring to subject_prefix (and footers) and I am using only the web interface. Good suggestion about mailman pointing to a different config file, but that would be strange since everything worked before (regarding labels and footers) in the old server. Will transmit your suggestions to our hosting. Thanks again Lluia -- Lluis Montoliu, PhD Research Scientist CSIC Centro Nacional de Biotecnologia (CNB) Darwin 3, 28049 Madrid - Spain Tel. +34 915854844 email: monto...@cnb.csic.es web: http://www.cnb.csic.es/~montoliu El 08/07/2013, a las 10:12 PM, Mark Sapiro m...@msapiro.net escribió: On 07/08/2013 12:12 PM, Lluis Montoliu wrote: Once moving has been completed we can see the lists have been actually moved, apparently correctly, configuration parameters remain the same as they were before, but, curiously enough, the messages are distributed without the usual label and without the footer, even though both label and footer are well defined in the configuration page and were working nicely in the old server configuration. I assume by 'label' you mean subject_prefix. According to the hosting provider they transferred everything to the new server, including all parameters of the list. They have been investigating the cause of these missing labels and footers but so far could not find any obvious cause. Things that I have tried so far: 1) Deleting the label, saving parameters, re-installing the label, saving parameters. Doesn't work, messages continue to be posted without label. I would not expect this to change anything. Presumably you are changing these things via the web admin interface. Is this using the same configuration file (lists/LISTNAME/config.pck) as the running Mailman? I.e. is the web server pointing at a different file, maybe a backup made during migration or even the old server? 2) I created a new list in the new server, created a label for it, and, in this case, messages are posted with label in this newly created list in the new server location So Mailman is properly processing it. Thus, if it exists in the web interface, it should be processed unless the web server and the Mailman qrunners are using different copies of the list's config.pck. Thanks for help and suggestions. If the hosting provider can't solve this, ask them to join this list and contact us directly. -- Mark Sapiro m...@msapiro.netThe 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://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/montoliu%40cnb.csic.es -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Lists created via web admin seem to be entirelyseparate from lists created from command line
All of this says that your web server does not point to the same
mailman instance that Postfix points to and that you are accessing
from the command line.
Check the path in your Mailman ScriptAlias in your web server config.
Yes the ScriptAlias is pointing to /usr/lib/cgi-bin/. At that location I
see the mailman executables which correspond to the various web
functions, as expected. I searched for other instances of these same
executables using locate, and all I found was a location where three
executables with the same name (admin, confirm, and subscribe) at
/var/lib/mailman/scripts. I don't know if these locations are equivalent
or not.
These are the locations where the Ubuntu ppa installer placed them. I
realize this list is not the place to ask about Ubuntu-specific
installation, but I haven't received a reply on the Ubuntu forum so far.
I need to see where postfix is pointing. As I understand it, it's the
mailman entry in postfix's master.cf that determines this. There I
have the entry as specified in the mailman documentation:
mailman unix - n n - - pipe
flags=FR user=list argv=/usr/lib/mailman/bin/postfix-to-mailman.py
${nexthop} ${user}
Per man page for master(5) this is supposed to mean that executabe
'mailman' is present relative to the path specified by postfix param
queue_directory. The value of that variable (as determined by running
postconf queue_directory) is /var/spool/postfix. There is no executable
named 'mailman' at that location, so I'm not clear on how postfix is
invoking mailman on incoming mail, but that seems to be where the
problem lies.
-Mark
--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Lists created via web admin seem to beentirelyseparate from lists created from command line
Mark Leone wrote:
Yes the ScriptAlias is pointing to /usr/lib/cgi-bin/. At that location I
see the mailman executables which correspond to the various web
functions, as expected. I searched for other instances of these same
executables using locate,
Is your locate index up to date?
Search for files named config.pck. See if there is more than one lists/
directory containing things like lists/LISTNAME/config.pck.
Preferrably use 'find / -name config.pck'.
and all I found was a location where three
executables with the same name (admin, confirm, and subscribe) at
/var/lib/mailman/scripts. I don't know if these locations are equivalent
or not.
The files in /usr/lib/cgi-bin/ are compiled binary wrappers (so they
can be SETGID) that do nothing more than validate the real GID and
then invoke the python script. I am however surprised that the scripts
are in /var and not /usr.
If you do 'strings' on the files in /usr/lib/cgi-bin/, you should see
the path to the scripts directory they're using. E.g.
[mark@sbh16 ~]$ strings mmp/cgi-bin/admin | grep scripts
/usr/local/mailman/scripts/
These are the locations where the Ubuntu ppa installer placed them. I
realize this list is not the place to ask about Ubuntu-specific
installation, but I haven't received a reply on the Ubuntu forum so far.
I need to see where postfix is pointing. As I understand it, it's the
mailman entry in postfix's master.cf that determines this. There I
have the entry as specified in the mailman documentation:
mailman unix - n n - - pipe
flags=FR user=list argv=/usr/lib/mailman/bin/postfix-to-mailman.py
${nexthop} ${user}
Per man page for master(5) this is supposed to mean that executabe
'mailman' is present relative to the path specified by postfix param
queue_directory. The value of that variable (as determined by running
postconf queue_directory) is /var/spool/postfix. There is no executable
named 'mailman' at that location, so I'm not clear on how postfix is
invoking mailman on incoming mail, but that seems to be where the
problem lies.
The above master.cf entry defines a 'mailman' transport that pipes mail
to the script at /usr/lib/mailman/bin/postfix-to-mailman.py. Assuming
that is how mail is being delivered to Mailman (you can verify this
from the Postfix log entries), you should be able to see what
installation it is pointing to be just reading it. I don't think I
have ever seen the Debian/Ubuntu version of this (officially
unsupported - how many times have I written that this week?) script,
but the one I have has a configuration setting on the 4th line like
MailmanHome = /var/mailman; # Mailman home directory.
--
Mark Sapiro m...@msapiro.netThe 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://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Lists created via web admin seem to beentirelyseparate from lists created from command line
mailman unix - n n - - pipe
flags=FR user=list argv=/usr/lib/mailman/bin/postfix-to-mailman.py
${nexthop} ${user}
Per man page for master(5) this is supposed to mean that executabe
'mailman' is present relative to the path specified by postfix param
queue_directory. The value of that variable (as determined by running
postconf queue_directory) is /var/spool/postfix. There is no
executable
named 'mailman' at that location, so I'm not clear on how postfix is
invoking mailman on incoming mail, but that seems to be where the
problem lies.
The above master.cf entry defines a 'mailman' transport that pipes mail
to the script at /usr/lib/mailman/bin/postfix-to-mailman.py. Assuming
that is how mail is being delivered to Mailman (you can verify this
from the Postfix log entries), you should be able to see what
installation it is pointing to be just reading it. I don't think I have
ever seen the Debian/Ubuntu version of this (officially unsupported -
how many times have I written that this week?) script, but the one I
have has a configuration setting on the 4th line like
MailmanHome = /var/mailman; # Mailman home directory.
Thanks for all the info. I've narrowed down the locations, but I'm still not
quite there.
I updated the locate database, and then using locate and find, I see that
the only place any lists are defined is at /var/lib/mailman/lists
The wrapper executables in the directory pointed to by apache's ScriptAlias
for /mailman are pointing to /var/lib/mailman/scripts. However, that
location is actually a sym link pointing to /usr/lib/mailman/scripts (which
is where you said you expected them to be)
This surprises me because when I create a list using the web interface, its
file does not appear in /var/lib/mailman/lists (or anywhere). The list files
only appear in that directory when I create them from the command line. But
the above seems to indicate that the web app is pointing to the same mailman
instance where the scripts eventually get written.
So then the remaining question is which mailman is postfix invoking? In the
postfix log file, when an e-mail comes in, I see
Mar 13 17:24:59 mal-s5610f postfix/pipe[20980]: 1F8E618006D:
to=testlist2-requ...@lists.midnightjava.net, relay=mailman, delay=0.33,
delays=0.12/0.01/0/0.2, dsn=2.0.0, status=sent (delivered via mailman
service)
I don't think that tells us the location, so I then looked at the script
being invoked via the master.cf entry (the unsupported file
postfix-to-mailman.py). I'm not a python programmer, but I understand the
basics. So I'm not sure I correctly resolved the location of the mailman
executable. What I see is
import paths
mm_pgm = os.path.join(paths.prefix, 'mail', 'mailman')
I don't see any reference to module paths in the python API, so I'm assuming
that's a custom module, and that the line above is resolving the path
mail/mailman relative to the path pointed to by the mailman config variable
'prefix'. If this is so, then that's 'var/lib/mailman' as that's the value
set for 'prefix' in Defaults.py, and it's not overridden in mm_cfg.py. (As
an aside, I put in some print and sys.stderr.write statements to get the
value of paths.prefix, thinking they would show up in either postfix or
mailman log files, but they do not.)
So if my assumption above is correct, then both postfix and apache are
pointing to the same instance of mailman. And when I create a list from the
command line I use /var/lib/mailman/bin/newlist, which is a sym link to
/usr/lib/mailman/bin/newlist, so this is also the same mailman instance.
So perhaps my assumption above can be corrected? One other thing I'm going
to try is checking whether apache is configured to allow following of sym
links for the ScriptAlias location. The wrapper executables there are not
sym links, but they're pointing to the python scripts they execute via sym
links, so perhaps I need the option enabled for following sym links.
Otherwise the mystery remains.
-Mark
--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Lists created via web admin seem to beentirelyseparate from lists created from command line
On 3/13/2012 3:52 PM, Mark Leone wrote: This surprises me because when I create a list using the web interface, its file does not appear in /var/lib/mailman/lists (or anywhere). The list files only appear in that directory when I create them from the command line. But the above seems to indicate that the web app is pointing to the same mailman instance where the scripts eventually get written. So are you even getting to the web server on this machine? Check your DNS. Check the Apache logs on this machine to see if you are even accessing this Apache. -- Mark Sapiro m...@msapiro.netThe 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://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Lists created via web admin seem to beentirelyseparate from lists created from command line
On 3/13/2012 3:52 PM, Mark Leone wrote: So then the remaining question is which mailman is postfix invoking? In the postfix log file, when an e-mail comes in, I see Mar 13 17:24:59 mal-s5610f postfix/pipe[20980]: 1F8E618006D: to=testlist2-requ...@lists.midnightjava.net, relay=mailman, delay=0.33, delays=0.12/0.01/0/0.2, dsn=2.0.0, status=sent (delivered via mailman service) I don't think that tells us the location, so I then looked at the script being invoked via the master.cf entry (the unsupported file postfix-to-mailman.py). I'm not a python programmer, but I understand the basics. So I'm not sure I correctly resolved the location of the mailman executable. What I see is import paths mm_pgm = os.path.join(paths.prefix, 'mail', 'mailman') The paths.py that is being imported is in the same directory as postfix_to_mailman.py, i.e., /usr/lib/mailman/bin/paths.py I don't see any reference to module paths in the python API, so I'm assuming that's a custom module, and that the line above is resolving the path mail/mailman relative to the path pointed to by the mailman config variable 'prefix'. If this is so, then that's 'var/lib/mailman' as that's the value set for 'prefix' in Defaults.py, and it's not overridden in mm_cfg.py. (As an aside, I put in some print and sys.stderr.write statements to get the value of paths.prefix, thinking they would show up in either postfix or mailman log files, but they do not.) It's the value of prefix defined in /usr/lib/mailman/bin/paths.py, but we know that's the same as used by bin/newlist. We also know that Mailman and Postfix are working together. It's only the web UI that's not working. So if my assumption above is correct, then both postfix and apache are pointing to the same instance of mailman. And when I create a list from the command line I use /var/lib/mailman/bin/newlist, which is a sym link to /usr/lib/mailman/bin/newlist, so this is also the same mailman instance. So perhaps my assumption above can be corrected? One other thing I'm going to try is checking whether apache is configured to allow following of sym links for the ScriptAlias location. The wrapper executables there are not sym links, but they're pointing to the python scripts they execute via sym links, so perhaps I need the option enabled for following sym links. Otherwise the mystery remains. Web create is apparently creating lists because it either creates the list or returns an error. If it succeeds, the list's lists/LISTNAME/config.pck file is created somewhere. -- Mark Sapiro m...@msapiro.netThe 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://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Lists created via web admin seem to beentirelyseparate from lists created from command line
Web create is apparently creating lists because it either creates the list or returns an error. If it succeeds, the list's lists/LISTNAME/config.pck file is created somewhere. You know the great thing about the Internet is that when you do something dumb, you get to share it with lots of other people, and have them join you in running in the circles you created. You cracked the code. I was hitting an entirely different web server. I set up Mailman and Postfix on my wife's Mac originally, and before I got the two working together I decided to host them on my Ubuntu system instead. I have two NAT'd ports for web access, going to the Mac and the Ubuntu system, and guess which one I was hitting until now. When I go to the right port, I see all the lists and users I created previously. Sorry for the error, but at least I learned some things about Mailman-Postfix interop. And I appreciate your help. -Mark -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Lists created via web admin seem to be entirely separate from lists created from command line
I just installed Mailman 2.1.14 and got it integrated with Postfix, on Ubuntu 11.04. I can create a list via the web admin interface, and add members to it. But no such list exists if I run bin/list_lists. If I run bin/newlist without creating a list via the web admin interface, I can send mail to the list, but when I try to administer it via the web interface, it doesn't exist. If I then create the list at the web interface, there is no connection between the web instance and the instance reachable via e-mail. That is, I add a member via the web interface, but when I send mail from that address, it's sent to the list moderator for vetting because it supposedly came from a non-member. And in similar fashion I get an e-mail at the list-admin address, telling me that I have a post to disposition. But when I click on the link in the e-mail, the Mailman web app says there are no pending requests. I've created three lists from scratch, including the sitelist, and I get this behavior each time. I assume I've got something misconfigured, as I haven't seen this behavior reported by anyone else. What configuration settings should I check, and is there a way to force synchronization of the web interface with the command line interface? -Mark -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Lists created via web admin seem to be entirely separate from lists created from command line
I just installed Mailman 2.1.14 and got it integrated with Postfix, on Ubuntu 11.04. I can create a list via the web admin interface, and add members to it. But no such list exists if I run bin/list_lists. If I run bin/newlist without creating a list via the web admin interface, I can send mail to the list, but when I try to administer it via the web interface, it doesn't exist. If I then create the list at the web interface, there is no connection between the web instance and the instance reachable via e-mail. That is, I add a member via the web interface, but when I send mail from that address, it's sent to the list moderator for vetting because it supposedly came from a non-member. And in similar fashion I get an e-mail at the list-admin address, telling me that I have a post to disposition. But when I click on the link in the e-mail, the Mailman web app says there are no pending requests. I've created three lists from scratch, including the sitelist, and I get this behavior each time. I assume I've got something misconfigured, as I haven't seen this behavior reported by anyone else. What configuration settings should I check, and is there a way to force synchronization of the web interface with the command line interface? -Mark -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Lists break when host_name is removed
Hi Mark, --On 2. Juni 2008 18:22:09 -0700 Mark Sapiro [EMAIL PROTECTED] wrote: Sebastian Hagedorn wrote: | | every once in a while one of our list owners shoots themselves in the | foot by deleting the value in host_name. That breaks the list almost | completely. Is there a way for us to override that setting, so that list | admins can't change it or the changed value isn't used? Probably the easiest way is to find the following lines in Mailman/Gui/General.py and remove or comment them out. thanks, that did the trick. As a follow-up now I wonder how I can determine if that setting has been changed. The config_list -o command doesn't seem to print it!? I'm a bit worried that there may be time bombs, i.e. lists that have been misconfigured when that GUI option still existed. The way it is now I wouldn't even be able to confirm that, it seems. -- .:.Sebastian Hagedorn - RZKR-R1 (Gebäude 52), Zimmer 18.:. Zentrum für angewandte Informatik - Universitätsweiter Service RRZK .:.Universität zu Köln / Cologne University - ✆ +49-221-478-5587.:. .:.:.:.Skype: shagedorn.:.:.:. pgpPVmzTxTr6z.pgp Description: PGP signature -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] Lists break when host_name is removed
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Sebastian Hagedorn wrote: | Hi Mark, | | --On 2. Juni 2008 18:22:09 -0700 Mark Sapiro [EMAIL PROTECTED] wrote: | | Sebastian Hagedorn wrote: | | | | every once in a while one of our list owners shoots themselves in the | | foot by deleting the value in host_name. That breaks the list almost | | completely. Is there a way for us to override that setting, so that | list | | admins can't change it or the changed value isn't used? | | Probably the easiest way is to find the following lines in | Mailman/Gui/General.py and remove or comment them out. | | thanks, that did the trick. As a follow-up now I wonder how I can | determine if that setting has been changed. The config_list -o command | doesn't seem to print it!? I'm a bit worried that there may be time | bombs, i.e. lists that have been misconfigured when that GUI option | still existed. The way it is now I wouldn't even be able to confirm | that, it seems. config_list -o only outputs those list attributes which are in the GUI. Since you removed host_name from the GUI, config_list -o no longer prints it. If you do not use virtual domains, the easiest thing is to run bin/withlist -a -l -r fix_url -- -v which will set host_name to the DEFAULT_URL_HOST value and web_page_url to the value of DEFAULT_URL_PATTERN interpolated with the value of DEFAULT_URL_HOST. The '-- -v' is optional and causes the command to report the web_page_url and host_name settings for each list after they are set. If you have more than one domain, you need to do something like #!/bin/sh for list in lists_in_www.example.com_domain ; do ~ bin/withlist -l -r fix_url $list -u www.example.com -v done for each domain. If you just want to see the host_names, you can copy the following to bin/show_host_name.py - cut here-- def show_host_name(mlist): ~print 'list: %s, host_name: %s' % (mlist.real_name, mlist.host_name) - cut here-- and run bin/withlist -a -r show_host_name - -- Mark Sapiro [EMAIL PROTECTED]The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (MingW32) iD8DBQFIRUyRVVuXXpU7hpMRAt+CAJ9SID68b0Bz6ZUR/KQwM22B5LvzaACfdyS0 ynzMm8ZoVhZiXqtRURMRrdM= =eQGX -END PGP SIGNATURE- -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] Lists break when host_name is removed
--On 3. Juni 2008 06:52:17 -0700 Mark Sapiro [EMAIL PROTECTED] wrote: config_list -o only outputs those list attributes which are in the GUI. Ah, tricky! If you just want to see the host_names, you can copy the following to bin/show_host_name.py - cut here-- def show_host_name(mlist): ~print 'list: %s, host_name: %s' % (mlist.real_name, mlist.host_name) - cut here-- and run bin/withlist -a -r show_host_name Great! That way I was able to verify quickly that all lists are configured correctly. Thank you very much! This withlist mechanism is pretty cool, I must say. -- .:.Sebastian Hagedorn - RZKR-R1 (Gebäude 52), Zimmer 18.:. Zentrum für angewandte Informatik - Universitätsweiter Service RRZK .:.Universität zu Köln / Cologne University - ✆ +49-221-478-5587.:. .:.:.:.Skype: shagedorn.:.:.:. pgpdAERfxdiBZ.pgp Description: PGP signature -- 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=showamp;file=faq01.027.htp
[Mailman-Users] Lists break when host_name is removed
Hi, every once in a while one of our list owners shoots themselves in the foot by deleting the value in host_name. That breaks the list almost completely. Is there a way for us to override that setting, so that list admins can't change it or the changed value isn't used? Thanks, Sebastian -- .:.Sebastian Hagedorn - RZKR-R1 (Gebäude 52), Zimmer 18.:. Zentrum für angewandte Informatik - Universitätsweiter Service RRZK .:.Universität zu Köln / Cologne University - ✆ +49-221-478-5587.:. .:.:.:.Skype: shagedorn.:.:.:. pgpqoh6tj2zm1.pgp Description: PGP signature -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] Lists break when host_name is removed
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sebastian Hagedorn wrote:
|
| every once in a while one of our list owners shoots themselves in the
| foot by deleting the value in host_name. That breaks the list almost
| completely. Is there a way for us to override that setting, so that list
| admins can't change it or the changed value isn't used?
Probably the easiest way is to find the following lines in
Mailman/Gui/General.py and remove or comment them out.
~('host_name', mm_cfg.Host, WIDTH, 0,
~ _('Host name this list prefers for email.'),
~ _(The host_name is the preferred name for email to
~ mailman-related addresses on this host, and generally
should be
~ the mail host's exchanger address, if any. This setting
can be
~ useful for selecting among alternative names of a host
that has
~ multiple addresses.)),
This will remove the setting from the General Options page.
- --
Mark Sapiro [EMAIL PROTECTED]The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (MingW32)
iD8DBQFIRJzBVVuXXpU7hpMRAgcBAKCSDdzpvDMvMvQbv++qScnTbicOMACfXgrN
+1wIqEq2JQM8AJxINDAcb6Q=
=ghOL
-END PGP SIGNATURE-
--
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=showamp;file=faq01.027.htp
[Mailman-Users] lists name caracters
Hi, Greetings from spain. Actually, our lists name includes a dot . in their names (i.e. [EMAIL PROTECTED]) In our new hosting, they are unable to configure mailman in order to accept the . dot character in the list name. If I create a list with a dot in the name it will be created ok, you can subscribe people, but when we send a mail to [EMAIL PROTECTED] it will not be delivered and says: This is an automatically generated Delivery Status Notification Delivery to the following recipient failed permanently: [EMAIL PROTECTED] Technical details of permanent failure: PERM_FAILURE: SMTP Error (state 13): 550 sorry, no mailbox here by that name. (#5.7.17) ¿any idea in orde to solve the problem withs dots? Thanks and sorry about my English. -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] lists name caracters
Antonio Guerrero wrote: Actually, our lists name includes a dot '.' in their names (i.e. [EMAIL PROTECTED]) ' In our new hosting, they are unable to configure mailman in order to accept the '.' dot character in the list name. If I create a list with a dot in the name it will be created ok, you can subscribe people, but when we send a mail to [EMAIL PROTECTED] it will not be delivered and says: This is an automatically generated Delivery Status Notification Delivery to the following recipient failed permanently: [EMAIL PROTECTED] Technical details of permanent failure: PERM_FAILURE: SMTP Error (state 13): 550 sorry, no mailbox here by that name. (#5.7.17) This has nothing to do with Mailman per se. This is an issue with the incoming MTA that receives the mail for delivery to mailman. There are three possibilities that I see. The first possibility is that list creation requires a manual 'alias' installation by the host and they have not done that, and the problem has nothing to do with the '.', but rather is due to this being a new list and the mail delivery aliases for it not being installed. The second possibility is that they have some automated way of installing aliases or recognizing list names which is confused by the '.'. The third possibility is the MTA is configured to treat a '.' in the local part in some special way. -- 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=showamp;file=faq01.027.htp
[Mailman-Users] Lists not Sending
I'm running into a problem today with posting and receiving through lists. This morning posts to the list were being sent and received fine, and now the posts are being sent through the email client correctly (I checked with a non-list email address), but nothing is being posted to the list. I've been back through the settings and nothing seems to be off on the list. Nothing is in the archives, and nothing is being held for moderation. Thanks. Tom -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] Lists stop working
A correction to the 'analysis' below: -- -- A message from a newly added subscriber is accepted, logged in the -- -- archive, and distributed to all the members of the mailing list. -- -- I just reconfirmed this, by adding myself again with yet another new -- address, then sending a message to the list from that new subscriber. -- The message was logged in the archive and was distributed to all members; -- I received a copy of the message at my old email address. The comment ... and was distributed to all members turns out to be incorrect. Messages from 'new' subscribers are delivered by MailMan to *some* existing members of the mailing list, but definitely not all of them. The bottom line is that for the moment, our attempts to detect any pattern in what messages get redistributed to whom has been unsuccessful. We do know that the messages are being received, logged in the list archive, and (at least sometimes) distributed to *some* members of the mailing list. I suspect that MailMan logs will point to the root cause of the problem fairly quickly, at least for someone with even a moderate understanding of how MailMan processes list messages and where MailMan logs those activities. Our ISP's tech support person is trying again to escalate our problem to cPanel. Beau -- Date: Fri, 27 Apr 2007 18:21:05 -0700 (PDT) -- -- -- BTW, what do you consider the 'current release' of Mailman? -- -- Sorry, I should have been specific: -- -- X-Mailman-Version: 2.1.9.cp2 -- -- which my ISP said was current. I don't know the significance of -- the .cp2, but 2.1.9 is the latest stable release according to -- http://sourceforge.net/project/showfiles.php?group_id=103 -- -- -- Also, I just had a sudden thought. Do your list(s) have topics defined -- -- and if not, did they ever? -- -- No and no. -- -- -- Thanks for the suggestion, but I don't believe it applies in our case. -- -- There are several hundred subscribers on each list, with over 200 -- -- different mail domains (hence many different servers). -- -- -- -- A message from a newly added subscriber is accepted, logged in the -- -- archive, and distributed to all the members of the mailing list. -- -- I just reconfirmed this, by adding myself again with yet another new -- address, then sending a message to the list from that new subscriber. -- The message was logged in the archive and was distributed to all members; -- I received a copy of the message at my old email address. -- -- -- A message from a existing subscriber is accepted, logged in the -- -- archive, confirming that it was seen and processed (at some level) -- -- by Mailman. The message *is* distributed to the newly added members -- -- of the mailing list. But it is not distributed to any of the existing -- -- members. -- -- This I cannot reconfirm at the moment. -- -- I sent another message to the list from my old address. The message -- was logged in the list archive, but does not appear to have been -- distributed to anyone on the mailing list (new or old). -- -- However: the first new user account we added to the list posted one -- message. That message is in the list archive, and I have the copy -- of that message that I received via the mailing list at my old address. -- -- So, something is going on but I have not yet characterized it completely. -- -- -- This makes no sense in terms of Mailman. Mailman builds the recipient -- -- list for a message independently of where it came from except that the -- -- sender only will be removed if the sender's 'not metoo' option is -- -- selected. -- -- Side note: the not metoo option is not working for us. -- I verified that the new accounts that I added do not have -- the not metoo option set, and the the default setting for -- the list does not have the not metoo option enable.d -- -- (Too many double negatives :-) ) The point being that for -- our mailing lists, the poster should receive a copy of his -- own message, but that is not happening. -- -- -- I do not have direct access to the list server system; I am working -- -- through our ISP's support service. Any suggestions for what I can -- -- tell them to look for, in Mailman log files or queues or other places, -- -- to see why Mailman does not redistribute a message: -- -- -- -- - from an existing subscriber -- -- - to any existing subscriber -- -- -- -- but (as far as we can tell) is working correctly in all other permutations? -- -- Thanks very much for the pointers below. I've passed them on to our ISP -- and I'll follow up to the list once I hear back. -- -- Beau -- -- -- They should look in Mailman's smtp log for entries like -- -- -- -- Apr 27 16:31:49 2007 (pid) message-id smtp for nnn recips, completed -- -- in t.ttt seconds -- -- -- -- to verify that nnn is the expected number, i.e. the number of regular -- -- (non-digest) members with delivery enabled, possibly minus 1 for the -- -- poster if the poster has 'not
Re: [Mailman-Users] Lists stop working
[EMAIL PROTECTED] wrote: The comment ... and was distributed to all members turns out to be incorrect. Messages from 'new' subscribers are delivered by MailMan to *some* existing members of the mailing list, but definitely not all of them. The bottom line is that for the moment, our attempts to detect any pattern in what messages get redistributed to whom has been unsuccessful. We do know that the messages are being received, logged in the list archive, and (at least sometimes) distributed to *some* members of the mailing list. I suspect that MailMan logs will point to the root cause of the problem fairly quickly, at least for someone with even a moderate understanding of how MailMan processes list messages and where MailMan logs those activities. I suspect that Mailman's logs will not point to the root cause, because I suspect this problem is outbound from Mailman. I may be wrong about this, but whether or not it's Mailman's problem, Mailman's smtp log will verify whether or not the posts are being sent from Mailman to the expected number of recipients in each case. Our ISP's tech support person is trying again to escalate our problem to cPanel. Your ISP's tech support should first use Mailman's smtp log to see whether or not it is Mailman dropping recipients. If it is Mailman, then cPanel is the correct place to go. If not, then start looking at the outgoing MTA's logs to see what happens after Mailman. -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] Lists stop working
[EMAIL PROTECTED] writes: I do not have direct access to the list server system; I am working through our ISP's support service. Any suggestions for what I can tell them to look for I'd suggest just giving them this address. Support implies that they know what they are doing, and will do it for you. That includes getting consulting help when they don't have expertise in-house. Support is part of the advertised service, isn't it? Why should you have to be posting here, except to provide details that the support staff overlooked or doesn't have? Why should we be guessing what information the ISP is looking at, but isn't telling us? OTOH, we don't charge ISPs to post to this list, any more than we charge list admins or users. There are plenty of people who ask for help on this list as part of their paid duties, and nobody asks or cares; we just help them out. So tell your ISP to *please* write us. This is *their* problem, and they should not impose it on you. It can't slow things down, either, as there is almost certainly nothing useful you can do without their intervention. If they won't, I think it's obvious what your next step is. Cheers, -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] Lists stop working
Mark Sapiro writes: This can be tricky. LOG_DIR is defined in Defaults.py in terms of VAR_PREFIX. If VAR_PREFIX is redefined in mm_cfg.py, this will not redefine LOG_DIR as LOG_DIR was already defined in Defaults.py in terms of the Defaults.py definition of VAR_PREFIX. 2.1.9's Defaults.py has the following warning, which applies to both LOG_DIR and VAR_PREFIX. So if either appears in mm_cfg.py, there are legitimate grounds for a harsh complaint to the vendor or installer. # # Nothing below here is user configurable. Most of these values are in this # file for internal system convenience. Don't change any of them or override # any of them in your mm_cfg.py file! # -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] Lists stop working
On Thursday 26 April 2007 22:49:21 [EMAIL PROTECTED] wrote: Did you ever find a solution to this issue? I realize that this is a really old posting: I send an eMail to one of the lists, I can see in my /var/log/maillog; Jun 10 11:27:03 osiris sendmail[2756]: h5A9R392002756: from=Niklas.Nikitin at xxx http://mail.python.org/mailman/listinfo/mailman-users , size=502, class=0, nrcpts=1, msgid=5.2.1.1.2.20030610112857.00b9b740 at xxx http://mail.python.org/mailman/listinfo/mailman-users , proto=ESMTP, daemon=MTA, relay=cassini.xxx [193.10.220.37] Jun 10 11:27:03 osiris sendmail[2757]: h5A9R392002756: to=|/usr/local/mailman/mail/mailman post nicke-test, ctladdr=nicke-test at xxx http://mail.python.org/mailman/listinfo/mailman-users (8/0), delay=00:00:00, xdelay=00:00:00, mailer=prog, pri=30704, dsn=2.0.0, stat=Sent that the server is receiving the eMail and is forwarding it to Mailman. But in Mailman's logs I will not find any information that it has received the eMail and no eMail is sent to the members on the list. If I dump all members of the list to a file, remove the list, create the list again and add all members, the list is working again for a while, and then it repeats again. but I've run into a very similar problem with two mailing lists that are managed using the current release of Mailman. The first symptom was that messages sent to the mailing lists were not distributed to the list, and did not show up in the list archive. After my ISP reinstalled Mailman, messages to the list started to show up in the list archive again. But the messages were still not distributed to members of the list. We found that if we add a new user, then a message to the list *is* delivered to that new user, but still not to any of the existing users. If the *new* user posts a message, that message appears in the list archive and the message is delivered to the entire mailing list. There doesn't seem to be a way to dump and reload the mailing list that preserves all per-list-member configuration options, so if possible, we'd like to avoid that workaround. Especially if it only works temporarily. Any insight / help / pointers appreciated. I had an oddity which may/maynot have some relevance.. We subscribed someone to a list with a specific email address. They confirmed the subscription using web interface. Subsequently mails from that member were received in the way you described and were passed to mailman but did not get posted to the list. I suggest you examine the headers of incoming mails,as they are intially received, and outgoing mails to those subscribers who are not receiving the mails.. There could be some changes being made to the headers either by the subscribers server or your own that is causing mails to be not delivered. david -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] Lists stop working
[EMAIL PROTECTED] wrote: Did you ever find a solution to this issue? I realize that this is a really old posting: I send an eMail to one of the lists, I can see in my /var/log/maillog; Jun 10 11:27:03 osiris sendmail[2756]: h5A9R392002756: from=Niklas.Nikitin at xxx http://mail.python.org/mailman/listinfo/mailman-users , size=502, class=0, nrcpts=1, msgid=5.2.1.1.2.20030610112857.00b9b740 at xxx http://mail.python.org/mailman/listinfo/mailman-users , proto=ESMTP, daemon=MTA, relay=cassini.xxx [193.10.220.37] Jun 10 11:27:03 osiris sendmail[2757]: h5A9R392002756: to=|/usr/local/mailman/mail/mailman post nicke-test, ctladdr=nicke-test at xxx http://mail.python.org/mailman/listinfo/mailman-users (8/0), delay=00:00:00, xdelay=00:00:00, mailer=prog, pri=30704, dsn=2.0.0, stat=Sent that the server is receiving the eMail and is forwarding it to Mailman. But in Mailman's logs I will not find any information that it has received the eMail and no eMail is sent to the members on the list. If I dump all members of the list to a file, remove the list, create the list again and add all members, the list is working again for a while, and then it repeats again. but I've run into a very similar problem with two mailing lists that are managed using the current release of Mailman. The first symptom was that messages sent to the mailing lists were not distributed to the list, and did not show up in the list archive. After my ISP reinstalled Mailman, messages to the list started to show up in the list archive again. But the messages were still not distributed to members of the list. We found that if we add a new user, then a message to the list *is* delivered to that new user, but still not to any of the existing users. If the *new* user posts a message, that message appears in the list archive and the message is delivered to the entire mailing list. There doesn't seem to be a way to dump and reload the mailing list that preserves all per-list-member configuration options, so if possible, we'd like to avoid that workaround. Especially if it only works temporarily. Any insight / help / pointers appreciated. today I have a similar (or the same?) problem. Running Mailman V2.1.9. Symptoms in my case: a new member (added with the command line utility add_members) is subscribed properly, the associated mail address gets a welcome message (so far so good), but mail to the mailing list arrives at Mailman, but is not distributed to the new user. I tried adding a second user, but the same problem. I have checked a number of things from the FAQ to diagnose the problem but I see nothing unusual. No traces in the logs directory. And I'm sure Mailman has accepted the mail for further processing (I can see from the mail logs). How can I trace these messages in Mailman? I looked in the qfiles/ subdirectories, but no files there... Is there any logging/debugging that can be turned on to see what steps Mailman takes to a) process the mail, (b) expand the mailing list and c) deliver the mail to the mail server. SMTP settings are default. Or is there any utility to quickly see what messages are in the Mailman queue for processing? /rolf -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] Lists stop working
Rolf E. Sonneveld writes: today I have a similar (or the same?) problem. Running Mailman V2.1.9. Symptoms in my case: a new member (added with the command line utility add_members) is subscribed properly, the associated mail address gets a welcome message (so far so good), but mail to the mailing list arrives at Mailman, but is not distributed to the new user. I tried adding a second user, but the same problem. Have posts ever been delivered to any user? If not, the most likely Mailman-related problem is that due to your settings, the posts are being held. Have you checked the moderation interface? More likely IMO is that Mailman never received the posts because of failure to start Mailman's qrunners properly, or misconfiguration of the MTA. I have checked a number of things from the FAQ to diagnose the problem but I see nothing unusual. No traces in the logs directory. And I'm sure Mailman has accepted the mail for further processing (I can see from the mail logs). On the contrary, if Mailman isn't writing to its logs and there's nothing in the qfiles directories, it seems very likely that Mailman has never received the messages. Are there entries in logs/qrunner showing that all qrunners are working? Mine says: Oct 18 17:14:29 2006 (15648) ArchRunner qrunner started. Oct 18 17:14:30 2006 (15649) BounceRunner qrunner started. Oct 18 17:14:33 2006 (15650) CommandRunner qrunner started. Oct 18 17:14:35 2006 (15653) NewsRunner qrunner started. Oct 18 17:14:35 2006 (15655) VirginRunner qrunner started. Oct 18 17:14:35 2006 (15651) IncomingRunner qrunner started. Oct 18 17:14:35 2006 (15654) OutgoingRunner qrunner started. Oct 18 17:14:36 2006 (15656) RetryRunner qrunner started. Does ps show that they are still running? Fairly early in message processing, Mailman logs to either logs/post (showing that the post was accepted) or to logs/vette (indicating that the post was held or rejected, and why). When the post is delivered, there will be an entry in logs/smtp for each batch of deliveries (usually one per remote host, or one per user if personalization or VERP is being used). Are there really no logs at all? If there are logs, what do they say? How can I trace these messages in Mailman? I looked in the qfiles/ subdirectories, but no files there... Have you checked your MTA's queue? Based on your statements that there is nothing in the logs and nothing in the queues, I have to believe they're never getting to Mailman at all. Is there any logging/debugging that can be turned on No; the logs described plus the qfiles contain all the information that you should need for problems related to the delivery pipeline. Or is there any utility to quickly see what messages are in the Mailman queue for processing? To see what's there, I just use ls -R /var/lib/mailman/qfiles (YMMV depending on where Mailman is installed). To examine the qfiles themselves, use cd /var/lib/mailman; bin/show_qfiles qfiles/in/* (again, the cd directory will vary according to your installation). -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] Lists stop working
Stephen J. Turnbull wrote: Fairly early in message processing, Mailman logs to either logs/post (showing that the post was accepted) or to logs/vette (indicating that the post was held or rejected, and why). One minor point here. The post log entry is not written until the message is delivered by SMTPDirect. When the post is delivered, there will be an entry in logs/smtp for each batch of deliveries (usually one per remote host, or one per user if personalization or VERP is being used). Actually, if nothing goes wrong, there will be only one entry in the smtp log covering all deliveries. If things go wrong there will be perhaps multiple entries in both smtp and smtp-failure logs. In spite of the minor corrections above, Stephen's advice is excellent. To elaborate on Rolf's question about how Mailman processes a post. Assuming a standard configuration where the MTA delivers to the mail/mailman wrapper. 1) The MTA pipes the message to the wrapper which passes it to the scripts/post script which in turn places it in the qfiles/in queue. Nothing is logged in Mailman, but the MTA normally logs the delivery. 2) IncomingRunner picks up the queue entry from qfiles/in and passes it through a pipeline of handlers (GLOBAL_PIPELINE - defined in Defaults.py, possibly modified in mm_cfg.py - unless the list defines a pipeline attribute to override it). The initial handlers check header_filter_rules, look for an Approved: header and possibly generate an autoresponse. The next set of handlers checks for moderation and other holds and does content filtering, emergency moderation and topic flagging. Any of these handlers can raise exceptions to request IncomingRunner to discard, reject or hold the message at that point. Discards and holds are logged in the vette log. Rejects are not logged, but result in a reject message to the poster. Any other exceptions cause the message to be moved to qfiles/shunt and the exception is logged in the error log. The next set of handlers determines the recipient addresses and possibly removes and/or modifies some message headers. Then handlers add the message to lists/listname/digest.mbox if the list is digestable (and possibly trigger a digest on size), add the message to qfiles/archive for processing by ArchRunner, possibly add the message to qfiles/news for processing by NewsRunner, update the list's last_post_time, send an acknowledgement to the poster if requested, and add the message to qfiles/out for processing by OutgoingRunner. 3) ArchRunner picks up the queue entry from qfiles/archive and adds it the the list's archive. 4)NewsRunner picks up the queue entry from qfiles/news and delivers it to Usenet. 5)OutgoingRunner picks up the queue entry from qfiles/out and calls SMTPDirect to deliver it to the outgoing MTA via SMTP. SMTPDirect logs posts to the post log and logs a bit more detail to the smtp log. Any SMTP failures are logged to the smtp-failure log and treated as bounces or queued for retry as appropriate. 6) Any unanticipated exceptions in any of the runners cause the message to be moved to qfiles/shunt and the exception to be logged in the error log. -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] Lists stop working
Mark Sapiro writes: Stephen J. Turnbull wrote: When the post is delivered, there will be an entry in logs/smtp for each batch of deliveries (usually one per remote host, or one per user if personalization or VERP is being used). Actually, if nothing goes wrong, there will be only one entry in the smtp log covering all deliveries. If things go wrong there will be perhaps multiple entries in both smtp and smtp-failure logs. Ah, OK ... the 1 recips logs I'm seeing are mass signups and perhaps bounce checks. Sorry for the inaccuracy. -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] Lists stop working
Hello, Mark, Mark Sapiro wrote: Stephen J. Turnbull wrote: Fairly early in message processing, Mailman logs to either logs/post (showing that the post was accepted) or to logs/vette (indicating that the post was held or rejected, and why). One minor point here. The post log entry is not written until the message is delivered by SMTPDirect. OK, thus only after the message has been delivered to at least one subscriber (or the first MTA in the chain of delivery to at least one subscriber). When the post is delivered, there will be an entry in logs/smtp for each batch of deliveries (usually one per remote host, or one per user if personalization or VERP is being used). Actually, if nothing goes wrong, there will be only one entry in the smtp log covering all deliveries. If things go wrong there will be perhaps multiple entries in both smtp and smtp-failure logs. In my case there were no entries in smtp nor in smtp-failure. In spite of the minor corrections above, Stephen's advice is excellent. To elaborate on Rolf's question about how Mailman processes a post. Thanks _very much_ for the detailed explanation of the inner working of Mailman. I really appreciate your detailed description! Assuming a standard configuration where the MTA delivers to the mail/mailman wrapper. 1) The MTA pipes the message to the wrapper which passes it to the scripts/post script which in turn places it in the qfiles/in queue. Nothing is logged in Mailman, but the MTA normally logs the delivery. Now here's the problem, I think. The MTA logs the message as being delivered to Mailman (via the wrapper script $MAILMANDIR/mailman/bin/mailman), so from the MTA's point of view it's done. Now, as the sent message cannot be found under qfiles, and as none of the $MAILMANDIR/logs/* files is modified, it seems as if the message disappeared in a black hole. Is there no way to enable debugging in the wrapper script? It would show the first action of Mailman, I assume. 2) IncomingRunner picks up the queue entry from qfiles/in and passes it through a pipeline of handlers (GLOBAL_PIPELINE - defined in Defaults.py, possibly modified in mm_cfg.py - unless the list defines a pipeline attribute to override it). The initial handlers check header_filter_rules, look for an Approved: header and possibly generate an autoresponse. The next set of handlers checks for moderation and other holds and does content filtering, emergency moderation and topic flagging. Any of these handlers can raise exceptions to request IncomingRunner to discard, reject or hold the message at that point. Discards and holds are logged in the vette log. Rejects are not logged, but result in a reject message to the poster. Any other exceptions cause the message to be moved to qfiles/shunt and the exception is logged in the error log. The next set of handlers determines the recipient addresses and possibly removes and/or modifies some message headers. Then handlers add the message to lists/listname/digest.mbox if the list is digestable (and possibly trigger a digest on size), add the message to qfiles/archive for processing by ArchRunner, possibly add the message to qfiles/news for processing by NewsRunner, update the list's last_post_time, send an acknowledgement to the poster if requested, and add the message to qfiles/out for processing by OutgoingRunner. FYI I made sure that the recipients where no digest users. 3) ArchRunner picks up the queue entry from qfiles/archive and adds it the the list's archive. 4)NewsRunner picks up the queue entry from qfiles/news and delivers it to Usenet. 5)OutgoingRunner picks up the queue entry from qfiles/out and calls SMTPDirect to deliver it to the outgoing MTA via SMTP. SMTPDirect logs posts to the post log and logs a bit more detail to the smtp log. Any SMTP failures are logged to the smtp-failure log and treated as bounces or queued for retry as appropriate. 6) Any unanticipated exceptions in any of the runners cause the message to be moved to qfiles/shunt and the exception to be logged in the error log. /rolf -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] Lists stop working
Rolf E. Sonneveld wrote: Mark Sapiro wrote: One minor point here. The post log entry is not written until the message is delivered by SMTPDirect. OK, thus only after the message has been delivered to at least one subscriber (or the first MTA in the chain of delivery to at least one subscriber). Yes, the first MTA, namely the one on localhost, port 25 unless overridden by SMTPHOST/SMTPPORT in mm_cfg.py. There is no guarantee this MTA has sent the message further. You need to refer the the MTA's logs for that. In my case there were no entries in smtp nor in smtp-failure. So the message didn't get that far. 1) The MTA pipes the message to the wrapper which passes it to the scripts/post script which in turn places it in the qfiles/in queue. Nothing is logged in Mailman, but the MTA normally logs the delivery. Now here's the problem, I think. The MTA logs the message as being delivered to Mailman (via the wrapper script $MAILMANDIR/mailman/bin/mailman), so from the MTA's point of view it's done. Now, as the sent message cannot be found under qfiles, and as none of the $MAILMANDIR/logs/* files is modified, it seems as if the message disappeared in a black hole. Is there no way to enable debugging in the wrapper script? It would show the first action of Mailman, I assume. There are at least two possibilities here. 1) The post was rejected (not held or discarded). A reject is not logged, but there should be an associated entry in Mailman's smtp log with a mailman generated message-id and 1 recipient for the reject message sent to the poster. 2) The wrapper is for a different Mailman installation with a different qfiles directory and probably no qrunners running and probably different log files too. The wrapper itself (I would expect it to be located at $MAILMANDIR/mail/mailman, not $MAILMANDIR/mailman/bin/mailman) has the path to the scripts/ directory compiled in and doesn't have any debug switches. It will invoke the scripts/post script and presumably this happens OK or it will return a failure status to the MTA which would be logged by the MTA. You can add debugging to the scripts/post script. If you look at this script, you will see that it already detects a missing or invalid list name from the wrapper and writes to stderr which is logged to both the post and error logs. You could add some more output, say by adding the last two lines of inq = get_switchboard(mm_cfg.INQUEUE_DIR) inq.enqueue(sys.stdin.read(), listname=listname, tolist=1, _plaintext=1) print sys.stderr, 'Post for %s queued in %s' \ % (listname, mm_cfg.INQUEUE_DIR) If you don't see this in the post and error logs, you are not looking at the right installation or (third possibility) the right log files. Look in mm_cfg.py/Defaults.py for the definition of LOG_DIR and anything else used in its definition. This can be tricky. LOG_DIR is defined in Defaults.py in terms of VAR_PREFIX. If VAR_PREFIX is redefined in mm_cfg.py, this will not redefine LOG_DIR as LOG_DIR was already defined in Defaults.py in terms of the Defaults.py definition of VAR_PREFIX. -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] Lists stop working
-- On Thursday 26 April 2007 22:49:21 [EMAIL PROTECTED] wrote: -- Did you ever find a solution to this issue? -- -- I realize that this is a really old posting: -- --I send an eMail to one of the lists, I can see in my /var/log/maillog; -- -- Jun 10 11:27:03 osiris sendmail[2756]: h5A9R392002756: -- from=Niklas.Nikitin at xxx -- http://mail.python.org/mailman/listinfo/mailman-users , -- size=502, class=0, nrcpts=1, -- msgid=5.2.1.1.2.20030610112857.00b9b740 at xxx -- http://mail.python.org/mailman/listinfo/mailman-users , -- proto=ESMTP, daemon=MTA, -- relay=cassini.xxx [193.10.220.37] -- -- Jun 10 11:27:03 osiris sendmail[2757]: h5A9R392002756: -- to=|/usr/local/mailman/mail/mailman post nicke-test, -- ctladdr=nicke-test at xxx -- http://mail.python.org/mailman/listinfo/mailman-users -- (8/0), delay=00:00:00, xdelay=00:00:00, -- mailer=prog, pri=30704, dsn=2.0.0, stat=Sent -- --that the server is receiving the eMail and is forwarding it to -- Mailman. But in Mailman's logs I will not find any information -- that it has received the eMail and no eMail is sent to the members -- on the list. If I dump all members of the list to a file, remove -- the list, create the list again and add all members, the list is -- working again for a while, and then it repeats again. -- -- but I've run into a very similar problem with two mailing lists that are -- managed using the current release of Mailman. -- -- The first symptom was that messages sent to the mailing lists were not -- distributed to the list, and did not show up in the list archive. -- -- After my ISP reinstalled Mailman, messages to the list started to show -- up in the list archive again. But the messages were still not distributed -- to members of the list. -- -- We found that if we add a new user, then a message to the list *is* -- delivered to that new user, but still not to any of the existing users. -- -- If the *new* user posts a message, that message appears in the list -- archive and the message is delivered to the entire mailing list. -- -- There doesn't seem to be a way to dump and reload the mailing list that -- preserves all per-list-member configuration options, so if possible, -- we'd like to avoid that workaround. Especially if it only works -- temporarily. -- -- Any insight / help / pointers appreciated. -- -- I had an oddity which may/maynot have some relevance.. -- -- We subscribed someone to a list with a specific email address. -- They confirmed the subscription using web interface. Subsequently -- mails from that member were received in the way you described and -- were passed to mailman but did not get posted to the list. -- -- I suggest you examine the headers of incoming mails,as they are -- intially received, and outgoing mails to those subscribers who are -- not receiving the mails.. There could be some changes being made to -- the headers either by the subscribers server or your own that is -- causing mails to be not delivered. Thanks for the suggestion, but I don't believe it applies in our case. There are several hundred subscribers on each list, with over 200 different mail domains (hence many different servers). A message from a newly added subscriber is accepted, logged in the archive, and distributed to all the members of the mailing list. A message from a existing subscriber is accepted, logged in the archive, confirming that it was seen and processed (at some level) by Mailman. The message *is* distributed to the newly added members of the mailing list. But it is not distributed to any of the existing members. I do not have direct access to the list server system; I am working through our ISP's support service. Any suggestions for what I can tell them to look for, in Mailman log files or queues or other places, to see why Mailman does not redistribute a message: - from an existing subscriber - to any existing subscriber but (as far as we can tell) is working correctly in all other permutations? Thanks. Beau -- david -- -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] Lists stop working
[EMAIL PROTECTED] wrote: Thanks for the suggestion, but I don't believe it applies in our case. There are several hundred subscribers on each list, with over 200 different mail domains (hence many different servers). A message from a newly added subscriber is accepted, logged in the archive, and distributed to all the members of the mailing list. A message from a existing subscriber is accepted, logged in the archive, confirming that it was seen and processed (at some level) by Mailman. The message *is* distributed to the newly added members of the mailing list. But it is not distributed to any of the existing members. This makes no sense in terms of Mailman. Mailman builds the recipient list for a message independently of where it came from except that the sender only will be removed if the sender's 'not metoo' option is selected. I do not have direct access to the list server system; I am working through our ISP's support service. Any suggestions for what I can tell them to look for, in Mailman log files or queues or other places, to see why Mailman does not redistribute a message: - from an existing subscriber - to any existing subscriber but (as far as we can tell) is working correctly in all other permutations? They should look in Mailman's smtp log for entries like Apr 27 16:31:49 2007 (pid) message-id smtp for nnn recips, completed in t.ttt seconds to verify that nnn is the expected number, i.e. the number of regular (non-digest) members with delivery enabled, possibly minus 1 for the poster if the poster has 'not metoo' and possibly minus a very few more if the post has direct To:, Cc:, Resent-To: or Resent-Cc: recipients who are candidate recipients with the 'nodups' option selected. Also look in the smtp-failure log to see if there are any failed recipients of the message. Assuming this is OK, the problem is outbound of mailman. They should check MTA logs to see that the message is received from Mailman It may be received in more that one transaction with anywhere between 1 and several hundred recipients per transaction depending on Mailman settings, but they should add up to the number Mailman reports in the smtp log. Then only the MTA can say what it did with the message(s) after that. If it should turn out that the smtp log verifies that mailman is not sending from 'existing subscribers' to 'existing subscribers', i.e. messages from existing subscribers have a small 'nnn recips' equal to only 'new subscribers', then we can look at adding debugging logging to the handlers that build the recips list. BTW, what do you consider the 'current release' of Mailman? Also, I just had a sudden thought. Do your list(s) have topics defined and if not, did they ever? -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] Lists stop working
-- BTW, what do you consider the 'current release' of Mailman? Sorry, I should have been specific: X-Mailman-Version: 2.1.9.cp2 which my ISP said was current. I don't know the significance of the .cp2, but 2.1.9 is the latest stable release according to http://sourceforge.net/project/showfiles.php?group_id=103 -- Also, I just had a sudden thought. Do your list(s) have topics defined -- and if not, did they ever? No and no. -- Thanks for the suggestion, but I don't believe it applies in our case. -- There are several hundred subscribers on each list, with over 200 -- different mail domains (hence many different servers). -- -- A message from a newly added subscriber is accepted, logged in the -- archive, and distributed to all the members of the mailing list. I just reconfirmed this, by adding myself again with yet another new address, then sending a message to the list from that new subscriber. The message was logged in the archive and was distributed to all members; I received a copy of the message at my old email address. -- A message from a existing subscriber is accepted, logged in the -- archive, confirming that it was seen and processed (at some level) -- by Mailman. The message *is* distributed to the newly added members -- of the mailing list. But it is not distributed to any of the existing -- members. This I cannot reconfirm at the moment. I sent another message to the list from my old address. The message was logged in the list archive, but does not appear to have been distributed to anyone on the mailing list (new or old). However: the first new user account we added to the list posted one message. That message is in the list archive, and I have the copy of that message that I received via the mailing list at my old address. So, something is going on but I have not yet characterized it completely. -- This makes no sense in terms of Mailman. Mailman builds the recipient -- list for a message independently of where it came from except that the -- sender only will be removed if the sender's 'not metoo' option is -- selected. Side note: the not metoo option is not working for us. I verified that the new accounts that I added do not have the not metoo option set, and the the default setting for the list does not have the not metoo option enable.d (Too many double negatives :-) ) The point being that for our mailing lists, the poster should receive a copy of his own message, but that is not happening. -- I do not have direct access to the list server system; I am working -- through our ISP's support service. Any suggestions for what I can -- tell them to look for, in Mailman log files or queues or other places, -- to see why Mailman does not redistribute a message: -- -- - from an existing subscriber -- - to any existing subscriber -- -- but (as far as we can tell) is working correctly in all other permutations? Thanks very much for the pointers below. I've passed them on to our ISP and I'll follow up to the list once I hear back. Beau -- They should look in Mailman's smtp log for entries like -- -- Apr 27 16:31:49 2007 (pid) message-id smtp for nnn recips, completed -- in t.ttt seconds -- -- to verify that nnn is the expected number, i.e. the number of regular -- (non-digest) members with delivery enabled, possibly minus 1 for the -- poster if the poster has 'not metoo' and possibly minus a very few -- more if the post has direct To:, Cc:, Resent-To: or Resent-Cc: -- recipients who are candidate recipients with the 'nodups' option -- selected. -- -- Also look in the smtp-failure log to see if there are any failed -- recipients of the message. -- -- Assuming this is OK, the problem is outbound of mailman. They should -- check MTA logs to see that the message is received from Mailman It may -- be received in more that one transaction with anywhere between 1 and -- several hundred recipients per transaction depending on Mailman -- settings, but they should add up to the number Mailman reports in the -- smtp log. -- -- Then only the MTA can say what it did with the message(s) after that. -- -- If it should turn out that the smtp log verifies that mailman is not -- sending from 'existing subscribers' to 'existing subscribers', i.e. -- messages from existing subscribers have a small 'nnn recips' equal to -- only 'new subscribers', then we can look at adding debugging logging -- to the handlers that build the recips list. -- -- BTW, what do you consider the 'current release' of Mailman? -- -- Also, I just had a sudden thought. Do your list(s) have topics defined -- and if not, did they ever? -- -- -- -- 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:
Re: [Mailman-Users] Lists stop working
On 4/27/07, [EMAIL PROTECTED] wrote: Sorry, I should have been specific: X-Mailman-Version: 2.1.9.cp2 That's cPanel. See FAQ 6.11. We have no way of verifying what they may have done to the stock Mailman code once they took it and modified it to their purposes. At best, we can try to guess. -- Brad Knowles [EMAIL PROTECTED], Consultant Author LinkedIn Profile: http://tinyurl.com/y8kpxu Slides from Invited Talks: http://tinyurl.com/tj6q4 -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] Lists stop working
[EMAIL PROTECTED] wrote: X-Mailman-Version: 2.1.9.cp2 which my ISP said was current. I don't know the significance of the .cp2, but 2.1.9 is the latest stable release according to http://sourceforge.net/project/showfiles.php?group_id=103 As Brad points out this is a cPanel release (specifically the second Cpanel release based on 2.1.9), and Brad refers you to the FAQ on cPanel Mailman. Side note: the not metoo option is not working for us. I verified that the new accounts that I added do not have the not metoo option set, and the the default setting for the list does not have the not metoo option enable.d (Too many double negatives :-) ) The point being that for our mailing lists, the poster should receive a copy of his own message, but that is not happening. This could be a cPanel issue. Also, there is a gmail issue. A user with a gmail account will never receive a copy of her own post because gmail sees it as a duplicate of the outgoing message in the 'sent' folder and discards it. This is a gmail feature. People have complained to gmail, so far AFAIK without any relief or known workaround. As far as cPanel is concerned, as Brad says, we can only guess. They modify Mailman in significant ways, and they don't share those mods with us. Someone once pressed them referring to the GPL and they shared some of their virtual hosting mods, but they have mods in several areas that we have never seen (although we have seen some of the negative consequences). Needless to say, this creates a very bad situation when we try to help cPanel users, since unless the issue is something we specifically recognize, we don't know whether it is a general Mailman issue or a cPanel issue, and if it's the latter we can't get under the hood to do a more detailed diagnosis. -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] Lists stop working
On 4/27/07, Mark Sapiro wrote: Needless to say, this creates a very bad situation when we try to help cPanel users, since unless the issue is something we specifically recognize, we don't know whether it is a general Mailman issue or a cPanel issue, and if it's the latter we can't get under the hood to do a more detailed diagnosis. I should point out that there are other cPanel users on this list, and they may be able to give you some assistance that we cannot. We'll continue to try to help as best we can, but we're going to be limited in what we can do. Unfortunately, we're dependant on the rest of the cPanel/Mailman community to help pitch in here, because the assistance we can provide is very limited. -- Brad Knowles [EMAIL PROTECTED], Consultant Author LinkedIn Profile: http://tinyurl.com/y8kpxu Slides from Invited Talks: http://tinyurl.com/tj6q4 -- 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=showamp;file=faq01.027.htp
[Mailman-Users] Lists stop working
Did you ever find a solution to this issue? I realize that this is a really old posting: I send an eMail to one of the lists, I can see in my /var/log/maillog; Jun 10 11:27:03 osiris sendmail[2756]: h5A9R392002756: from=Niklas.Nikitin at xxx http://mail.python.org/mailman/listinfo/mailman-users , size=502, class=0, nrcpts=1, msgid=5.2.1.1.2.20030610112857.00b9b740 at xxx http://mail.python.org/mailman/listinfo/mailman-users , proto=ESMTP, daemon=MTA, relay=cassini.xxx [193.10.220.37] Jun 10 11:27:03 osiris sendmail[2757]: h5A9R392002756: to=|/usr/local/mailman/mail/mailman post nicke-test, ctladdr=nicke-test at xxx http://mail.python.org/mailman/listinfo/mailman-users (8/0), delay=00:00:00, xdelay=00:00:00, mailer=prog, pri=30704, dsn=2.0.0, stat=Sent that the server is receiving the eMail and is forwarding it to Mailman. But in Mailman's logs I will not find any information that it has received the eMail and no eMail is sent to the members on the list. If I dump all members of the list to a file, remove the list, create the list again and add all members, the list is working again for a while, and then it repeats again. but I've run into a very similar problem with two mailing lists that are managed using the current release of Mailman. The first symptom was that messages sent to the mailing lists were not distributed to the list, and did not show up in the list archive. After my ISP reinstalled Mailman, messages to the list started to show up in the list archive again. But the messages were still not distributed to members of the list. We found that if we add a new user, then a message to the list *is* delivered to that new user, but still not to any of the existing users. If the *new* user posts a message, that message appears in the list archive and the message is delivered to the entire mailing list. There doesn't seem to be a way to dump and reload the mailing list that preserves all per-list-member configuration options, so if possible, we'd like to avoid that workaround. Especially if it only works temporarily. Any insight / help / pointers appreciated. Beau -- 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=showamp;file=faq01.027.htp
[Mailman-Users] Lists nested in other lists
I know I have seen some documentation on being able to have lists nested in other lists. I can't seem to locate it now. What I want to do is have someone subscribe to a list such as - hockey player - and by virtue of subscribing to that list they are part of the Athletics list. So they will then receive messages sent to both the Athletics list and the Hockey Player lists. Is this possible? - Cheap Talk? Check out Yahoo! Messenger's low PC-to-Phone call rates. -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] Lists nested in other lists
On 1/25/07, Ken Cheney [EMAIL PROTECTED] wrote: I know I have seen some documentation on being able to have lists nested in other lists. I can't seem to locate it now. What I want to do is have someone subscribe to a list such as - hockey player - and by virtue of subscribing to that list they are part of the Athletics list. So they will then receive messages sent to both the Athletics list and the Hockey Player lists. What you're looking for are umbrella lists. Basically, the 'hockey players list' is a member of the 'Athletics' list. There are some options to help with this, such as setting the Athletics list not to send password reminders (since the password reminder would go to all of the hockey players list. -- - Patrick Bogen -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] Lists not shown on listinfo-site
Mark Sapiro schrieb: IT-Support @ AStA TU Darmstadt wrote: Patrick Bogen schrieb: Have you tried following FAQ 4.62 http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq04.062.htp ? I could not figure it out yet - I still have to study the FAQ article you told me - I'll give you feedback as soon as possible! I have edited the above FAQ article to try to make it more clear. If you've looked at the prior version, you might find the current version more helpful. Hello Mark, hello Patrick, I read the article again and found the solution here: http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq04.029.htp I had to do a withlist -l -a -r fix_url cause obviously after fixing apache, configuration of mailman was touched (by me?). Now the lists appear again and I also tweaked it to ssl-support :-) Thanks for your help! Very good support on this list!!! Best wishes, Ivan -- 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=showamp;file=faq01.027.htp
[Mailman-Users] lists within lists
Hi all, We're running a site with a mailman 2.1.5 configuration with 40-50 lists on it, and some lists have a list address as a subscriber to the list.. ie the general@ list might have a bunch of individual addresses and an otherlist@ address also as a member, (and the otherlist@ also contains individual addresses) So, what happens, is that when an email is sent to the general@ list it gets subject modified [General] as normal, but the people on the otherlist@ also get rewritten so they get mail that appears as [Otherlist][General] Subject line.. My question is, is there a way to have mailman not include the 2nd subject tag when posting to the general@ list (for the otherlist@ subscribers)? but also still retain it when sending explicitly to otherlist@ Cheers Spyro -- This message and its attachments may contain legally privileged or confidential information. This message is intended for the use of the individual or entity to which it is addressed. If you are not the addressee indicated in this message, or the employee or agent responsible for delivering the message to the intended recipient, you may not copy or deliver this message or its attachments to anyone. Rather, you should permanently delete this message and its attachments and kindly notify the sender by reply e-mail. Any content of this message and its attachments, which does not relate to the official business of the sending company must be taken not to have been sent or endorsed by the sending company or any of its related entities. No warranty is made that the e-mail or attachment(s) are free from computer virus or other defect. -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] lists within lists
Spyro Polymiadis wrote: My question is, is there a way to have mailman not include the 2nd subject tag when posting to the general@ list (for the otherlist@ subscribers)? but also still retain it when sending explicitly to otherlist@ Not without modifying Mailman code. -- 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=showamp;file=faq01.027.htp
[Mailman-Users] lists within lists
Hi all, We're running a site with a mailman 2.1.5 configuration with 40-50 lists on it, and some lists have a list address as a subscriber to the list.. ie the general@ list might have a bunch of individual addresses and an otherlist@ address also as a member, (and the otherlist@ also contains individual addresses) So, what happens, is that when an email is sent to the general@ list it gets subject modified [General] as normal, but the people on the otherlist@ also get rewritten so they get mail that appears as [Otherlist][General] Subject line.. My question is, is there a way to have mailman not include the 2nd subject tag when posting to the general@ list (for the otherlist@ subscribers)? but also still retain it when sending explicitly to otherlist@ Cheers Spyro This message and its attachments may contain legally privileged or confidential information. This message is intended for the use of the individual or entity to which it is addressed. If you are not the addressee indicated in this message, or the employee or agent responsible for delivering the message to the intended recipient, you may not copy or deliver this message or its attachments to anyone. Rather, you should permanently delete this message and its attachments and kindly notify the sender by reply e-mail. Any content of this message and its attachments, which does not relate to the official business of the sending company must be taken not to have been sent or endorsed by the sending company or any of its related entities. No warranty is made that the e-mail or attachment(s) are free from computer virus or other defect. -- 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=showamp;file=faq01.027.htp
[Mailman-Users] lists within lists
Hi all, We're running a site with a mailman 2.1.5 configuration with 40-50 lists on it, and some lists have a list address as a subscriber to the list.. ie the general@ list might have a bunch of individual addresses and an otherlist@ address also as a member, (and the otherlist@ also contains individual addresses) So, what happens, is that when an email is sent to the general@ list it gets subject modified [General] as normal, but the people on the otherlist@ also get rewritten so they get mail that appears as [Otherlist][General] Subject line.. My question is, is there a way to have mailman not include the 2nd subject tag when posting to the general@ list (for the otherlist@ subscribers)? but also still retain it when sending explicitly to otherlist@ Cheers Spyro -- 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=showamp;file=faq01.027.htp
[Mailman-Users] lists within lists
Hi all, We're running a site with a mailman 2.1.5 configuration with 40-50 lists on it, and some lists have a list address as a subscriber to the list.. ie the general@ list might have a bunch of individual addresses and an otherlist@ address also as a member, (and the otherlist@ also contains individual addresses) So, what happens, is that when an email is sent to the general@ list it gets subject modified [General] as normal, but the people on the otherlist@ also get rewritten so they get mail that appears as [Otherlist][General] Subject line.. My question is, is there a way to have mailman not include the 2nd subject tag when posting to the general@ list (for the otherlist@ subscribers)? but also still retain it when sending explicitly to otherlist@ Cheers Spyro -- This message and its attachments may contain legally privileged or confidential information. This message is intended for the use of the individual or entity to which it is addressed. If you are not the addressee indicated in this message, or the employee or agent responsible for delivering the message to the intended recipient, you may not copy or deliver this message or its attachments to anyone. Rather, you should permanently delete this message and its attachments and kindly notify the sender by reply e-mail. Any content of this message and its attachments, which does not relate to the official business of the sending company must be taken not to have been sent or endorsed by the sending company or any of its related entities. No warranty is made that the e-mail or attachment(s) are free from computer virus or other defect. -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] Lists not shown on listinfo-site
IT-Support @ AStA TU Darmstadt wrote: Patrick Bogen schrieb: Have you tried following FAQ 4.62 http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq04.062.htp ? I could not figure it out yet - I still have to study the FAQ article you told me - I'll give you feedback as soon as possible! I have edited the above FAQ article to try to make it more clear. If you've looked at the prior version, you might find the current version more helpful. -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] Lists not shown on listinfo-site
Patrick Bogen schrieb: On 7/18/06, IT-Support @ AStA TU Darmstadt [EMAIL PROTECTED] wrote: The mailman listinfo-site is available, but the lists are not shown. Ah, sorry, that wasn't very clear. Have you tried following FAQ 4.62 http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq04.062.htp ? Hello Patrick, thanks for your message! I could not figure it out yet - I still have to study the FAQ article you told me - I'll give you feedback as soon as possible! Thanks again! Ivan -- 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=showamp;file=faq01.027.htp
[Mailman-Users] Lists not shown on listinfo-site
Hello, we had some problems with apache2 and mailman - after upgrading the server the lists are not shown anymore on the listinfo-site http://myserver/mailman/listinfo Under /var/lib/mailman/list my lists are still there - i guess the databaseconfig isn't read properly or could it be missconfiguration in apache2? Thanks! Ivan -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] Lists not shown on listinfo-site
On 7/18/06, IT-Support @ AStA TU Darmstadt [EMAIL PROTECTED] wrote: we had some problems with apache2 and mailman - after upgrading the server the lists are not shown anymore on the listinfo-site http://myserver/mailman/listinfo Under /var/lib/mailman/list my lists are still there - i guess the databaseconfig isn't read properly or could it be missconfiguration in apache2? Most likely ah issue with apache2. Can you paste your Apache config directives regarding Mailman, and the ones you included in your Apache2 config? (Grepping the old configfiles for 'mailman' should be sufficient to find the interesting ones.) -- - Patrick Bogen -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] Lists not shown on listinfo-site
Patrick Bogen schrieb: On 7/18/06, IT-Support @ AStA TU Darmstadt [EMAIL PROTECTED] wrote: we had some problems with apache2 and mailman - after upgrading the server the lists are not shown anymore on the listinfo-site http://myserver/mailman/listinfo Under /var/lib/mailman/list my lists are still there - i guess the databaseconfig isn't read properly or could it be missconfiguration in apache2? Most likely ah issue with apache2. Can you paste your Apache config directives regarding Mailman, and the ones you included in your Apache2 config? (Grepping the old configfiles for 'mailman' should be sufficient to find the interesting ones.) Hello Patrick, thhanks ffor your mail! The mailman listinfo-site is available, but the lists are not shown. The conf under /etc/apache2/sites-available/default looks like this (Debian): NameVirtualHost * VirtualHost *:80 ServerAdmin [EMAIL PROTECTED] DocumentRoot /var/www/ Directory / Options FollowSymLinks AllowOverride None /Directory Directory /var/www/ Options Indexes FollowSymLinks MultiViews AllowOverride None Order allow,deny allow from all # This directive allows us to have apache2's default start page # in /apache2-default/, but still have / go to the right place # RedirectMatch ^/$ /asta/ FilesMatch ^cms$ ForceType application/x-httpd-php /FilesMatch /Directory ScriptAlias /cgi-bin/ /usr/lib/cgi-bin/ Directory /usr/lib/cgi-bin AllowOverride None Options ExecCGI -MultiViews +SymLinksIfOwnerMatch Order allow,deny Allow from all /Directory ScriptAlias /mailman/ /usr/lib/cgi-bin/mailman/ Directory /usr/lib/cgi-bin/mailman/ AllowOverride None Options ExecCGI Order allow,deny Allow from all /Directory ErrorLog /var/log/apache2/error.log # Possible values include: debug, info, notice, warn, error, crit, # alert, emerg. LogLevel warn CustomLog /var/log/apache2/access.log combined ServerSignature On Alias /doc/ /usr/share/doc/ Directory /usr/share/doc/ Options Indexes MultiViews FollowSymLinks AllowOverride None Order deny,allow Deny from all Allow from 127.0.0.0/255.0.0.0 ::1/128 /Directory /VirtualHost Apache2.conf: # Based upon the NCSA server configuration files originally by Rob McCool. # Changed extensively for the Debian package by Daniel Stone [EMAIL PROTECTED] # and also by Thom May [EMAIL PROTECTED]. # ServerRoot: The top of the directory tree under which the server's # configuration, error, and log files are kept. # # NOTE! If you intend to place this on an NFS (or otherwise network) # mounted filesystem then please read the LockFile documentation # (available at URL:http://www.apache.org/docs/mod/core.html#lockfile); # you will save yourself a lot of trouble. ServerRoot /etc/apache2 # The LockFile directive sets the path to the lockfile used when Apache # is compiled with either USE_FCNTL_SERIALIZED_ACCEPT or # USE_FLOCK_SERIALIZED_ACCEPT. This directive should normally be left at # its default value. The main reason for changing it is if the logs # directory is NFS mounted, since the lockfile MUST BE STORED ON A LOCAL # DISK. The PID of the main server process is automatically appended to # the filename. LockFile /var/lock/apache2/accept.lock # PidFile: The file in which the server should record its process # identification number when it starts. PidFile /var/run/apache2.pid # Timeout: The number of seconds before receives and sends time out. TimeOut 300 # KeepAlive: Whether or not to allow persistent connections (more than # one request per connection). Set to Off to deactivate. KeepAlive on # MaxKeepAliveRequests: The maximum number of requests to allow # during a persistent connection. Set to 0 to allow an unlimited amount. # We recommend you leave this number high, for maximum performance. MaxKeepAliveRequests 100 # KeepAliveTimeout: Number of seconds to wait for the next request from the # same client on the same connection. KeepAliveTimeout 15 ## ## Server-Pool Size Regulation (MPM specific) ## # prefork MPM # StartServers . number of server processes to start # MinSpareServers .. minimum number of server processes which are kept spare # MaxSpareServers .. maximum number of server processes which are kept spare # MaxClients ... maximum number of server processes allowed to start # MaxRequestsPerChild .. maximum number of requests a server process serves IfModule prefork.c StartServers 5
Re: [Mailman-Users] Lists not shown on listinfo-site
On 7/18/06, IT-Support @ AStA TU Darmstadt [EMAIL PROTECTED] wrote: The mailman listinfo-site is available, but the lists are not shown. Ah, sorry, that wasn't very clear. Have you tried following FAQ 4.62 http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq04.062.htp ? -- - Patrick Bogen -- 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=showamp;file=faq01.027.htp
[Mailman-Users] lists stop working
I have a small mailman (2.1.x) installation with a few lists. They just stopped working the other day. I did a mailmanctl restart and that did not fix it but a stop and then a start did. I saw nothing in the logs to indicate why the lists stopped working. How does one go about debugging this sort of thing? Thanks Chad --- Chad Leigh -- Shire.Net LLC Your Web App and Email hosting provider chad at shire.net -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] lists stop working
Chad Leigh -- Shire.Net LLC wrote: I have a small mailman (2.1.x) installation with a few lists. They just stopped working the other day. I did a mailmanctl restart and that did not fix it but a stop and then a start did. I saw nothing in the logs to indicate why the lists stopped working. How does one go about debugging this sort of thing? Probably one or more of your qrunners stopped. At this point, you can look at Mailman's qrunner log and possibly see entries about runners stopping and being restarted until the limit is reached. If so, there will also be a small bit of information as to why (what signal or condition) caused the runner to stop. There may also be something in Mailman's 'error' log from the same time. If it happens again see items 5 - 8 at http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq03.014.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=showamp;file=faq01.027.htp
Re: [Mailman-Users] lists stop working
On Jul 14, 2006, at 9:20 PM, Mark Sapiro wrote:
Chad Leigh -- Shire.Net LLC wrote:
I have a small mailman (2.1.x) installation with a few lists. They
just stopped working the other day. I did a mailmanctl restart and
that did not fix it but a stop and then a start did. I saw nothing
in the logs to indicate why the lists stopped working.
How does one go about debugging this sort of thing?
Probably one or more of your qrunners stopped. At this point, you can
look at Mailman's qrunner log and possibly see entries about runners
stopping and being restarted until the limit is reached. If so, there
will also be a small bit of information as to why (what signal or
condition) caused the runner to stop.
Jul 12 16:51:50 2006 (70376) Master qrunner detected subprocess exit
(pid: 5860, sig: None, sts: 1, class: OutgoingRunner, slice: 1/1)
[restarting]
Jul 12 16:51:50 2006 (70376) Qrunner OutgoingRunner reached maximum
restart limit of 10, not restarting.
There may also be something in
Mailman's 'error' log from the same time.
Jul 12 16:51:50 2006 qrunner(5860): Traceback (most recent call last):
Jul 12 16:51:50 2006 qrunner(5860): File /usr/local/mailman/bin/
qrunner, line 270, in ?
Jul 12 16:51:50 2006 qrunner(5860): main()
Jul 12 16:51:50 2006 qrunner(5860): File /usr/local/mailman/bin/
qrunner, line 230, in main
Jul 12 16:51:50 2006 qrunner(5860): qrunner.run()
Jul 12 16:51:50 2006 qrunner(5860): File /usr/local/mailman/
Mailman/Queue/Runner.py, line 87, in run
Jul 12 16:51:50 2006 qrunner(5860): self._cleanup()
Jul 12 16:51:50 2006 qrunner(5860): File /usr/local/mailman/
Mailman/Queue/OutgoingRunner.py, line 134, in _cleanup
Jul 12 16:51:50 2006 qrunner(5860): BounceMixin._cleanup(self)
Jul 12 16:51:50 2006 qrunner(5860): File /usr/local/mailman/
Mailman/Queue/BounceRunner.py, line 132, in _cleanup
Jul 12 16:51:50 2006 qrunner(5860): self._register_bounces()
Jul 12 16:51:50 2006 qrunner(5860): File /usr/local/mailman/
Mailman/Queue/BounceRunner.py, line 120, in _register_bounces
Jul 12 16:51:50 2006 qrunner(5860): mlist.registerBounce(addr,
msg, day=day)
Jul 12 16:51:50 2006 qrunner(5860): File /usr/local/mailman/
Mailman/Bouncer.py, line 131, in registerBounce
Jul 12 16:51:50 2006 qrunner(5860): time.strftime('%d-%b-%Y',
day + (0,)*6))
Jul 12 16:51:50 2006 qrunner(5860): ValueError : day of year out of
range
If it happens again see items 5 - 8 at
http://www.python.org/cgi-bin/faqw-mm.py?
req=showfile=faq03.014.htp.
I shall take a look.
thanks
Chad
---
Chad Leigh -- Shire.Net LLC
Your Web App and Email hosting provider
chad at shire.net
--
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=showamp;file=faq01.027.htp
Re: [Mailman-Users] lists stop working
Chad Leigh -- Shire.Net LLC wrote:
Jul 12 16:51:50 2006 qrunner(5860): File /usr/local/mailman/
Mailman/Bouncer.py, line 131, in registerBounce
Jul 12 16:51:50 2006 qrunner(5860): time.strftime('%d-%b-%Y',
day + (0,)*6))
Jul 12 16:51:50 2006 qrunner(5860): ValueError : day of year out of
range
This is a known incompatibility between Mailman 2.1.5 (and below) and
python 2.4 and up. See
http://mail.python.org/pipermail/mailman-users/2005-March/043640.html
and
https://sourceforge.net/tracker/?func=detailatid=100103aid=1394696group_id=103.
--
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=showamp;file=faq01.027.htp
[Mailman-Users] Lists
Hi, I am new to List Servers, and I have a question. I am currently working on a school district list server. For some reason I cannot see all the lists. I logged in to the console and ran the list_lists command it showed my lists but I want to see it from top to bottom. Is there a command to show all the list with a pause option? Thanks Eric -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] Lists
Eric Sangalang wrote: I am new to List Servers, and I have a question. I am currently working on a school district list server. For some reason I cannot see all the lists. I logged in to the console and ran the list_lists command it showed my lists but I want to see it from top to bottom. Is there a command to show all the list with a pause option? bin/list_lists [options] | more or if you prefer bin/list_lists [options] | less See 'man more' and/or 'man less'. -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] lists/create screen
I set VIRTUAL_HOST_OVERVIEW = Off and that seems to have resolved the problem I outlined below. I know nothing about Python at the moment, so hacking the *.py files for customized functionality (by me) is probably not happening anytime soon, not without a mess ;-) Thank you. Mark Sapiro wrote: Forrest Aldrich wrote: I have a new mailman instance set up - via a proxied connection. I've since found that doing it this way is more complex (but not my choice). Several items need to be addressed. Another one I found was this on the screen for lists/create: our.internal.host.net:1 mailing lists - Admin Links Welcome! There currently are no publicly-advertised Mailman http://www.gnu.org/software/mailman/index.html mailing lists on our.internal.host.net:1.To visit the administrators configuration page for an unadvertised list, open a URL similar to this one, but with a '/' and the list name appended. If you have the proper authority, you can also create a new mailing list http://gr1.sca.manyone.net:10016/lists/create. General list information can be found at the mailing list overview page http://gr1.sca.manyone.net:10016/lists/listinfo. (Send questions and comments to [EMAIL PROTECTED]:1 mailto:[EMAIL PROTECTED]:10016.) I'm not sure if this is a simple template that needs to be edited or if there's a more eloquent way to get these links to reflect the proper external links/hosts we want people to see. I think you have a real problem here. I hope you are not trying to use virtual hosts too as that will really complicate things. Assuming not, set VIRTUAL_HOST_OVERVIEW = Off in mm_cfg.py. This will allow all public lists to at least appear on the listinfo and admin overview pages. As far as the host names our.internal.host.net:1 and gr1.sca.manyone.net:10016 in the above are concerned, I'm confused. These should not be different (unless you've changed DEFAULT_URL_PATTERN replacing %s with gr1.sca.manyone.net:10016) as they both are obtained from Utils.get_domain(). Anyway, these come from the environment variables HTTP_HOST or SERVER_NAME and are the actual host name which would be the real host, not the proxy. To make these be the proxy, I think you'd have to hack Mailman/Cgi/admin.py where this page is built on the fly (not from template) or better, change Mailman/Utils.py to always return the name of the proxy - you could at least make it an mm_cfg.py variable. -- 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=showamp;file=faq01.027.htp
[Mailman-Users] lists/create screen
Hi there, I have a new mailman instance set up - via a proxied connection. I've since found that doing it this way is more complex (but not my choice). Several items need to be addressed. Another one I found was this on the screen for lists/create: our.internal.host.net:1 mailing lists - Admin Links Welcome! There currently are no publicly-advertised Mailman http://www.gnu.org/software/mailman/index.html mailing lists on our.internal.host.net:1.To visit the administrators configuration page for an unadvertised list, open a URL similar to this one, but with a '/' and the list name appended. If you have the proper authority, you can also create a new mailing list http://gr1.sca.manyone.net:10016/lists/create. General list information can be found at the mailing list overview page http://gr1.sca.manyone.net:10016/lists/listinfo. (Send questions and comments to [EMAIL PROTECTED]:1 mailto:[EMAIL PROTECTED]:10016.) I'm not sure if this is a simple template that needs to be edited or if there's a more eloquent way to get these links to reflect the proper external links/hosts we want people to see. Thanks. -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] lists/create screen
Forrest Aldrich wrote: I have a new mailman instance set up - via a proxied connection. I've since found that doing it this way is more complex (but not my choice). Several items need to be addressed. Another one I found was this on the screen for lists/create: our.internal.host.net:1 mailing lists - Admin Links Welcome! There currently are no publicly-advertised Mailman http://www.gnu.org/software/mailman/index.html mailing lists on our.internal.host.net:1.To visit the administrators configuration page for an unadvertised list, open a URL similar to this one, but with a '/' and the list name appended. If you have the proper authority, you can also create a new mailing list http://gr1.sca.manyone.net:10016/lists/create. General list information can be found at the mailing list overview page http://gr1.sca.manyone.net:10016/lists/listinfo. (Send questions and comments to [EMAIL PROTECTED]:1 mailto:[EMAIL PROTECTED]:10016.) I'm not sure if this is a simple template that needs to be edited or if there's a more eloquent way to get these links to reflect the proper external links/hosts we want people to see. I think you have a real problem here. I hope you are not trying to use virtual hosts too as that will really complicate things. Assuming not, set VIRTUAL_HOST_OVERVIEW = Off in mm_cfg.py. This will allow all public lists to at least appear on the listinfo and admin overview pages. As far as the host names our.internal.host.net:1 and gr1.sca.manyone.net:10016 in the above are concerned, I'm confused. These should not be different (unless you've changed DEFAULT_URL_PATTERN replacing %s with gr1.sca.manyone.net:10016) as they both are obtained from Utils.get_domain(). Anyway, these come from the environment variables HTTP_HOST or SERVER_NAME and are the actual host name which would be the real host, not the proxy. To make these be the proxy, I think you'd have to hack Mailman/Cgi/admin.py where this page is built on the fly (not from template) or better, change Mailman/Utils.py to always return the name of the proxy - you could at least make it an mm_cfg.py variable. -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] Lists are missing
Ok the archives and members are now there! When I look at the web interface. However now the messages dont go through and when I click on the message in the archives (web interface) I get: Forbidden You don't have permission to access /pipermail/leveebreak/2005-January/thread.html on this server. Additionally, a 403 Forbidden error was encountered while trying to use an ErrorDocument to handle the request. Is this a permissions problem? SC From: John Dennis [EMAIL PROTECTED] To: Scot Condry [EMAIL PROTECTED], mailman-users@python.org Subject: Re: [Mailman-Users] Lists are missing Date: Thu, 17 Feb 2005 01:02:30 -0500 Scot Condry wrote: Thanks. That got me in the right direction that I got mailman working again and postfix needed to know where the aliases had moved to. But now I have created a new list named the same as the old list and it is working. But I would like to move all the old users, password, archives etc. to the new directories. Is that possible? If you copy the following 3 directories you should pick up your old list and member data. /var/mailman/archives-- /var/lib/mailman/archives /var/mailman/data-- /var/lib/mailman/data /var/mailman/lists -- /var/lib/mailman/lists You may also want to copy over the pending queue files: /var/mailman/qfiles -- /var/spool/mailman -- John Dennis [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=showamp;file=faq01.027.htp
Re: [Mailman-Users] Lists are missing
OK the list is working and the web interface is only hald working. I can figure that out in time. Thanks for your help! SC From: scot condry [EMAIL PROTECTED] To: [EMAIL PROTECTED], mailman-users@python.org Subject: Re: [Mailman-Users] Lists are missing Date: Thu, 17 Feb 2005 09:57:23 -0800 Ok the archives and members are now there! When I look at the web interface. However now the messages dont go through and when I click on the message in the archives (web interface) I get: Forbidden You don't have permission to access /pipermail/leveebreak/2005-January/thread.html on this server. Additionally, a 403 Forbidden error was encountered while trying to use an ErrorDocument to handle the request. Is this a permissions problem? SC From: John Dennis [EMAIL PROTECTED] To: Scot Condry [EMAIL PROTECTED], mailman-users@python.org Subject: Re: [Mailman-Users] Lists are missing Date: Thu, 17 Feb 2005 01:02:30 -0500 Scot Condry wrote: Thanks. That got me in the right direction that I got mailman working again and postfix needed to know where the aliases had moved to. But now I have created a new list named the same as the old list and it is working. But I would like to move all the old users, password, archives etc. to the new directories. Is that possible? If you copy the following 3 directories you should pick up your old list and member data. /var/mailman/archives-- /var/lib/mailman/archives /var/mailman/data-- /var/lib/mailman/data /var/mailman/lists -- /var/lib/mailman/lists You may also want to copy over the pending queue files: /var/mailman/qfiles -- /var/spool/mailman -- John Dennis [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/scotcondry%40hotmail.com Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp -- 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=showamp;file=faq01.027.htp
RE: [Mailman-Users] Lists are missing
I recently upgraded (*not* a fresh install) from Fedora 2 to Fedora 3. Seems as though everything came over OK except my Mailman is messed up now. Emails to my list are not being distributed and when I go to the mailman listinfo page it says I have no lists, when I had three. Only one of these was actually in use, but anyone know what FC3 might have done to change things? FC3 relocated the installation directories for mailman to be FHS compliant and allow better integration with SELinux, this is documented in /usr/share/doc/mailman-*/INSTALL.REDHAT and it explains the directories you need to move if you are trying to overlay a new release on an old release and want to preserve a previous installation. -- John Dennis [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=showamp;file=faq01.027.htp
RE: [Mailman-Users] Lists are missing
Thanks. That got me in the right direction that I got mailman working again and postfix needed to know where the aliases had moved to. But now I have created a new list named the same as the old list and it is working. But I would like to move all the old users, password, archives etc. to the new directories. Is that possible? SC -Original Message- From: John Dennis [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 16, 2005 7:15 AM To: 'scot condry'; mailman-users@python.org Subject: RE: [Mailman-Users] Lists are missing I recently upgraded (*not* a fresh install) from Fedora 2 to Fedora 3. Seems as though everything came over OK except my Mailman is messed up now. Emails to my list are not being distributed and when I go to the mailman listinfo page it says I have no lists, when I had three. Only one of these was actually in use, but anyone know what FC3 might have done to change things? FC3 relocated the installation directories for mailman to be FHS compliant and allow better integration with SELinux, this is documented in /usr/share/doc/mailman-*/INSTALL.REDHAT and it explains the directories you need to move if you are trying to overlay a new release on an old release and want to preserve a previous installation. -- John Dennis [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=showamp;file=faq01.027.htp
Re: [Mailman-Users] Lists are missing
Scot Condry wrote: Thanks. That got me in the right direction that I got mailman working again and postfix needed to know where the aliases had moved to. But now I have created a new list named the same as the old list and it is working. But I would like to move all the old users, password, archives etc. to the new directories. Is that possible? If you copy the following 3 directories you should pick up your old list and member data. /var/mailman/archives-- /var/lib/mailman/archives /var/mailman/data-- /var/lib/mailman/data /var/mailman/lists -- /var/lib/mailman/lists You may also want to copy over the pending queue files: /var/mailman/qfiles -- /var/spool/mailman -- John Dennis [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=showamp;file=faq01.027.htp
[Mailman-Users] Lists are missing
I recently upgraded (*not* a fresh install) from Fedora 2 to Fedora 3. Seems as though everything came over OK except my Mailman is messed up now. Emails to my list are not being distributed and when I go to the mailman listinfo page it says I have no lists, when I had three. Only one of these was actually in use, but anyone know what FC3 might have done to change things? Thanks, SC -- 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=showamp;file=faq01.027.htp
[Mailman-Users] Lists in OSX
I am trying to configure mailing list in Mac OSX Server 10.3.5. I am having trouble posting to the list, or I should say my test users are having trouble. Upon posting to a list this message is sent back: This is the Postfix program at host test.org. I'm sorry to have to inform you that the message returned below could not be delivered to one or more destinations. For further assistance, please send mail to postmaster If you do so, please include this problem report. You can delete your own text from the message returned below. The Postfix program [EMAIL PROTECTED]: mail for server.test.org loops back to myself Reporting-MTA: dns; test.org Arrival-Date: Thu, 30 Sep 2004 13:34:37 -0400 (EDT) Final-Recipient: rfc822; [EMAIL PROTECTED] Action: failed Status: 5.0.0 Diagnostic-Code: X-Postfix; mail for server.test.org loops back to myself I am quite green at this and any help would be appreciated Thanks Derrick -- Mailman-Users mailing list [EMAIL PROTECTED] 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/
Re: [Mailman-Users] Lists in OSX
At 2:00 PM -0400 2004-09-30, Derrick Seymour wrote: [EMAIL PROTECTED]: mail for server.test.org loops back to myself This is an MTA problem, not a problem with Mailman. I suggest you use the online documentation at http://www.postfix.org/ to help you find the solution. -- Brad Knowles, [EMAIL PROTECTED] Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety. -- Benjamin Franklin (1706-1790), reply of the Pennsylvania Assembly to the Governor, November 11, 1755 SAGE member since 1995. See http://www.sage.org/ for more info. -- Mailman-Users mailing list [EMAIL PROTECTED] 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] Lists
Hi, I am interested in your mailing lists, but am curious how secure the lists are - are names distributed to any companies? (I am basically concerned about spam, since it is a free service) Thanks! Kristal Kristal Hebden School of IST 329H IST Building University Park PA 16802 Phone: 814-863-8833 Fax: 814-865-7559 __ I did not wish to live what was not life, living is so dear; nor did I wish to practise resignation, unless it was quite necessary. - H.D. Thoreau -- Mailman-Users mailing list [EMAIL PROTECTED] 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/
Re: [Mailman-Users] Lists
At 8:53 AM -0400 2004-07-15, Kristal Hebden wrote: I am interested in your mailing lists, but am curious how secure the lists are - are names distributed to any companies? (I am basically concerned about spam, since it is a free service) I don't understand your question. Can you clarify? By default, mailing lists created via Mailman will be publicly accessible, but the mailing list administrator can choose to create private lists instead. The list archives can either be public or private, separately from the list itself (i.e., you can have private archives of a public list, or public archives of a private list, in addition to the obvious choices). You can also choose not to archive lists. -- Brad Knowles, [EMAIL PROTECTED] Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety. -- Benjamin Franklin (1706-1790), reply of the Pennsylvania Assembly to the Governor, November 11, 1755 SAGE member since 1995. See http://www.sage.org/ for more info. -- Mailman-Users mailing list [EMAIL PROTECTED] 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] Lists work, but no archives
Hi, I'm a newbie using Mailman 2.1.5 on Linux (Redhat 9) with sendmail. I was able to install Mailman and create lists via the web. The lists work; messages sent to it go out to subscribers. The problem is that, even though I have set the Archive option via the web interface, none of my lists is archiving. When I go to the archive page via html, I get No messages have been posted to this list yet, so the archives are currently empty. I thought I had perhaps made a mistake with the pipermail alias in Apache, but when I go to http://www.storydynamics.com/pipermail/ I see what appears to be the correct list (i.e., one link for each of my mailing lists). I have searched my logs, at least the ones I could find. The only two logs in /usr/local/mailman/logs are error and subscribe. Subscribe looks reasonable; error is empty. I'm not sure exactly how to read all the other logs I have found in /var/log/ and in /var/log/httpd, but no entry seems relevant on the face of it. I don't know what other logs I should be trying to read. I have also searched the archives for help at http://www.mail-archive.com, with no success. Does anyone have an idea what I could have done wrong? Or at least where else to look? Thanks! Doug Lipman -- *** Doug Lipman, P.O. Box 441195, West Somerville, MA 02144 Web page: http://storydynamics.com Free monthly email newsletter, eTips from the Storytelling Coach. A wonderful, chock full of provocative ideas, storytelling newsletter. I like it a lot! - Loretta Greene (Tempe, AZ) *** -- Mailman-Users mailing list [EMAIL PROTECTED] 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/
Re: [Mailman-Users] Lists work, but no archives - more info
Additional info, which I'm sure is more to the core of my problem: I was wrong that the lists work. In fact, any message I send - from any sender, registered or not - to the [EMAIL PROTECTED] address is sent on to the sender. When I fill out the subscription form at http://www.storydynamics.com/mailman/listinfo/myw, it appears that I am completing the process. But: 1. no confirmation email comes to the new member or to me as administrator. 2. the subscriber list remains empty, too. 3. no other previously registered subscribers get copies of the mail. I guess the archiving problem is just a symptom of whatever is causing this problem. Any ideas? Doug Hi, I'm a newbie using Mailman 2.1.5 on Linux (Redhat 9) with sendmail. I was able to install Mailman and create lists via the web. The lists work; messages sent to it go out to subscribers. The problem is that, even though I have set the Archive option via the web interface, none of my lists is archiving. When I go to the archive page via html, I get No messages have been posted to this list yet, so the archives are currently empty. I thought I had perhaps made a mistake with the pipermail alias in Apache, but when I go to http://www.storydynamics.com/pipermail/ I see what appears to be the correct list (i.e., one link for each of my mailing lists). I have searched my logs, at least the ones I could find. The only two logs in /usr/local/mailman/logs are error and subscribe. Subscribe looks reasonable; error is empty. I'm not sure exactly how to read all the other logs I have found in /var/log/ and in /var/log/httpd, but no entry seems relevant on the face of it. I don't know what other logs I should be trying to read. I have also searched the archives for help at http://www.mail-archive.com, with no success. Does anyone have an idea what I could have done wrong? Or at least where else to look? Thanks! Doug Lipman -- *** Doug Lipman, P.O. Box 441195, West Somerville, MA 02144 Web page: http://storydynamics.com Free monthly email newsletter, eTips from the Storytelling Coach. A wonderful, chock full of provocative ideas, storytelling newsletter. I like it a lot! - Loretta Greene (Tempe, AZ) *** -- Mailman-Users mailing list [EMAIL PROTECTED] 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/ -- *** Doug Lipman, P.O. Box 441195, West Somerville, MA 02144 Phone: (781) 391-3672. Fax: (781) 391-6341. Toll-free: (888) 446-4738 Story Dynamics: workshops, performances, coaching Web page: http://storydynamics.com Free monthly email newsletter, eTips from the Storytelling Coach. A wonderful, chock full of provocative ideas, storytelling newsletter. I like it a lot! - Loretta Greene (Tempe, AZ) Upcoming workshops: http://storydynamics.com/Services/upcoming.html The Soul of Hope: http://SoulOfHope.net The Hasidic Stories Home Page: http://www.HasidicStories.com *** -- *** Doug Lipman, P.O. Box 441195, West Somerville, MA 02144 Phone: (781) 391-3672. Fax: (781) 391-6341. Toll-free: (888) 446-4738 Story Dynamics: workshops, performances, coaching Web page: http://storydynamics.com Free monthly email newsletter, eTips from the Storytelling Coach. A wonderful, chock full of provocative ideas, storytelling newsletter. I like it a lot! - Loretta Greene (Tempe, AZ) Upcoming workshops: http://storydynamics.com/Services/upcoming.html The Soul of Hope: http://SoulOfHope.net The Hasidic Stories Home Page: http://www.HasidicStories.com *** -- Mailman-Users mailing list [EMAIL PROTECTED] 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/
Re: [Mailman-Users] lists that are members of each other - bad idea?
Barnaby Scott wrote on Mon, 10 May 2004 05:06:09 -0700 (PDT): Does anyone have any suggestions about my original query then (about 'affilate' members a couple of threads back)? Was it that where you wanted to have some not real members be able to join in certain discussions they were allowed to? I think the best way to achieve your goal is to set up two lists. Kai -- Kai Schätzl, Berlin, Germany Get your web at Conactive Internet Services: http://www.conactive.com IE-Center: http://ie5.de http://msie.winware.org -- Mailman-Users mailing list [EMAIL PROTECTED] 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/
Re: [Mailman-Users] lists that are members of each other - bad idea?
At 5:06 AM -0700 2004/05/10, Barnaby Scott wrote: Does anyone have any suggestions about my original query then (about 'affilate' members a couple of threads back)? Not really. You could play around with the topics stuff, but I'm not sure that's going to do what you want. I strongly suspect that you may have to hack some Python code to get Mailman to do what you want. -- Brad Knowles, [EMAIL PROTECTED] They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety. -Benjamin Franklin, Historical Review of Pennsylvania. SAGE member since 1995. See http://www.sage.org/ for more info. -- Mailman-Users mailing list [EMAIL PROTECTED] 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] lists that are members of each other - bad idea?
I posted a question a couple of days ago about a particular Mailman set-up I wanted to achieve, but have since thought it would be better to ask a simpler and more specific question: Does anyone know the consequences of setting up two lists which are members of each other? I don't want to do something which will cause an endless loop and bring down the wrath of my hosting company upon myself! Presumably the X-BeenThere header should come into play to avoid such an eventuality, but will it work in these circs? Or even if it does work, should one not do this sort of thing for other reasons? Thanks __ Do you Yahoo!? Win a $20,000 Career Makeover at Yahoo! HotJobs http://hotjobs.sweepstakes.yahoo.com/careermakeover -- Mailman-Users mailing list [EMAIL PROTECTED] 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/
Re: [Mailman-Users] lists that are members of each other - bad idea?
At 12:06 AM -0700 2004/05/10, Barnaby Scott wrote: Does anyone know the consequences of setting up two lists which are members of each other? I believe that would be very bad news. Presumably the X-BeenThere header should come into play to avoid such an eventuality, but will it work in these circs? Or even if it does work, should one not do this sort of thing for other reasons? The risk is that you will have set up a potentially serious loop, for which there is only one way to detect and stop it before there is a melt down. All it would take is a misconfigured client or MTA to remove certain headers before sending the message on, and you and everyone else would be toast. Before you take a shotgun with a hair trigger and load it with thermonuclear shells, you might want to give some consideration to what it might do when you go away and leave it pointed in your direction -- especially when there are children and pets around, any one of which might accidentally set it off. -- Brad Knowles, [EMAIL PROTECTED] They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety. -Benjamin Franklin, Historical Review of Pennsylvania. SAGE member since 1995. See http://www.sage.org/ for more info. -- Mailman-Users mailing list [EMAIL PROTECTED] 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/
Re: [Mailman-Users] lists that are members of each other - bad idea?
Kinda what I feared! Does anyone have any suggestions about my original query then (about 'affilate' members a couple of threads back)? Thanks --- Brad Knowles [EMAIL PROTECTED] wrote: At 12:06 AM -0700 2004/05/10, Barnaby Scott wrote: Does anyone know the consequences of setting up two lists which are members of each other? I believe that would be very bad news. Presumably the X-BeenThere header should come into play to avoid such an eventuality, but will it work in these circs? Or even if it does work, should one not do this sort of thing for other reasons? The risk is that you will have set up a potentially serious loop, for which there is only one way to detect and stop it before there is a melt down. All it would take is a misconfigured client or MTA to remove certain headers before sending the message on, and you and everyone else would be toast. Before you take a shotgun with a hair trigger and load it with thermonuclear shells, you might want to give some consideration to what it might do when you go away and leave it pointed in your direction -- especially when there are children and pets around, any one of which might accidentally set it off. -- Brad Knowles, [EMAIL PROTECTED] They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety. -Benjamin Franklin, Historical Review of Pennsylvania. SAGE member since 1995. See http://www.sage.org/ for more info. __ Do you Yahoo!? Win a $20,000 Career Makeover at Yahoo! HotJobs http://hotjobs.sweepstakes.yahoo.com/careermakeover -- Mailman-Users mailing list [EMAIL PROTECTED] 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] Lists not showing up in listinfo page, (yup I read the FAQ.)
Before you flame, I've read the FAQ and noted the section on this symptom. But it hasn't addressed my problem. If you hit this URI: http://cactusairforce.org/mailman/listinfo You see all lists (including Mailman?!) but if you instead hit this one: http://www.cactusairforce.org/mailman/listinfo you only see the CAF and the Recruitment_list From the FAQ: 1. the value of the list's 'advertised' option (the first one on the page) of the Privacy Options Section of the list's admin web GUI. This isn't the problem. 2. the value of VIRTUAL_HOST_OVERVIEW in $prefix/Mailman/Defaults.py or mm_cfg.py. If this is set to true (usually 1) then you may be experiencing the effect of Mailman Virtual Host feature. In that case the address in the URL used to access listinfo is compared to the address in the list's 'web_page_url' option (the last one) of the General Options Section of the list's admin web GUI. If they are not the same, the list is not added to the listinfo page returned. If I change this value in Defaults.py (it doesn't appear in mm_cfy.py) to 0, I *can* see all of the lists, unfortunately it also displays all the lists from the other (non virtual) domain on this server. Also, I've checked in the GUI, there is no entry for 'web_page_url' there is one for 'host_name' but this is set for cactusairforce.org (in all the lists). Distro: SuSE Pro 8.2, (x86) mailman-2.1.1-91 -Mettius -- Mailman-Users mailing list [EMAIL PROTECTED] 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] Lists stopped working
I host 5 lists using mailman and all of them have stopped working. Mail sent to them is not going through and not found in archives. There are no error messages. Can someone please tell me where I might begin to look for the problem? ThIA for any direction and/or help, JO http://www.jetler.com -- Mailman-Users mailing list [EMAIL PROTECTED] 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/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Lists stopped working
jo I host 5 lists using mailman and all of them have stopped working. jo Mail sent to them is not going through and not found in archives. jo There are no error messages. Can someone please tell me where I jo might begin to look for the problem? Is mailman running? You din't identify your system, but on my Linux system I have lots of mailman-ish processes: % ps auxww | egrep mailman mailman 24530 0.0 0.4 4096 3088 ?S04:02 0:00 /usr/local/bin/python /etc/rc.d/init.d/mailmanctl start mailman 24535 0.0 0.5 5272 4040 ?S04:02 0:00 qrunner /home/mailman21/bin/qrunner --runner=ArchRunner:0:1 -s mailman 24536 0.0 0.5 5376 4204 ?S04:02 0:00 qrunner /home/mailman21/bin/qrunner --runner=BounceRunner:0:1 -s mailman 24537 0.0 0.5 5308 4168 ?S04:02 0:00 qrunner /home/mailman21/bin/qrunner --runner=CommandRunner:0:1 -s mailman 24538 0.0 0.6 5884 4736 ?S04:02 0:00 qrunner /home/mailman21/bin/qrunner --runner=IncomingRunner:0:1 -s mailman 24542 0.0 0.5 5304 4076 ?S04:02 0:00 qrunner /home/mailman21/bin/qrunner --runner=NewsRunner:0:1 -s mailman 24543 0.0 0.6 6316 5160 ?S04:02 0:00 qrunner /home/mailman21/bin/qrunner --runner=OutgoingRunner:0:1 -s mailman 24544 0.0 0.6 5976 4808 ?S04:02 0:00 qrunner /home/mailman21/bin/qrunner --runner=VirginRunner:0:1 -s skip 22599 0.0 0.0 1764 624 pts/1S11:46 0:00 egrep mailman Assuming you're on a Linux system and Mailman is properly installed, you might want to try (as root): /etc/rc.d/init.d/mailmanctl start -- Skip Montanaro Got gigs? http://www.musi-cal.com/submit.html Got spam? http://spambayes.sf.net/ [EMAIL PROTECTED] -- Mailman-Users mailing list [EMAIL PROTECTED] 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/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Lists stopped working
On Fri, 2004-01-02 at 12:32, JO wrote: I host 5 lists using mailman and all of them have stopped working. Mail sent to them is not going through and not found in archives. There are no error messages. Can someone please tell me where I might begin to look for the problem? ThIA for any direction and/or help, JO http://www.jetler.com Check out FAQ 3.14 which is dedicated to resolving this problem. Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Sounds like (Mailman versions 2.0.x or lower) your cron daemon stopped running, or (Mailman versions 2.1.x or above) your mailman daemon is stopped. Good Luck - Jon Carnes -- Mailman-Users mailing list [EMAIL PROTECTED] 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/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Lists of lists question...
Nope, that only tells me how to create an umbrella list but doesn't tackle the important issue of only allowing members of the sublists to post to the umbrella list. -John At 12:18 18/06/2003, Richard Barrett wrote: At 19:58 18/06/2003, John Lockard wrote: I have several lists that in best practice I'd like to remain hierarchical. Example: staff.all(all staff) staff.pt (PT staff) staff.ft (FT staff) I would prefer to add full time staff members to the staff.ft list only and part time staff members to the staff.pt list only, and have staff.pt and staff.ft be members of staff.all. I would like to have all of the staff lists be restricted so that only members of the staff lists (staff.pt and staff.ft) be able to post to any of the staff lists. I would prefer to not have to add a full time staff member to staff.all and staff.ft. To allow a full time staff member to post to staff.all I would like to be able to just add him/her to the staff.ft list and not have to add them to an allow list in staff.all. Is there a way (or an easy way) to do this with Mailman? The following page in the Mailman FAQ might give you some useful hints: http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq03.005.htp -- Richard Barrett http://www.openinfo.co.uk -- --jlockard - Welcome to the Psychic Admin hotline. Don't call us, we'll call you. - KSon -- Mailman-Users mailing list [EMAIL PROTECTED] 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/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Lists of lists question...
At 18:08 25/06/2003, John Lockard wrote: Nope, that only tells me how to create an umbrella list but doesn't tackle the important issue of only allowing members of the sublists to post to the umbrella list. The last part of the FAQ entry under the line reading The work-around for this is to setup a script that builds a Mega-list out of other lists on your server is why I pointed you at that FAQ entry. What you want to do is going to be a problem with umbrella lists whereas he synthesised superior list may give you the flexibility you want on the posting front. You may have to edit the script presented source code but it is a start.It may not be that elegant but other subscribers to mailman-users are said to swear by it. Just a thought. -John At 12:18 18/06/2003, Richard Barrett wrote: At 19:58 18/06/2003, John Lockard wrote: I have several lists that in best practice I'd like to remain hierarchical. Example: staff.all(all staff) staff.pt (PT staff) staff.ft (FT staff) I would prefer to add full time staff members to the staff.ft list only and part time staff members to the staff.pt list only, and have staff.pt and staff.ft be members of staff.all. I would like to have all of the staff lists be restricted so that only members of the staff lists (staff.pt and staff.ft) be able to post to any of the staff lists. I would prefer to not have to add a full time staff member to staff.all and staff.ft. To allow a full time staff member to post to staff.all I would like to be able to just add him/her to the staff.ft list and not have to add them to an allow list in staff.all. Is there a way (or an easy way) to do this with Mailman? The following page in the Mailman FAQ might give you some useful hints: http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq03.005.htp -- Richard Barrett http://www.openinfo.co.uk -- --jlockard - Welcome to the Psychic Admin hotline. Don't call us, we'll call you. - KSon -- Mailman-Users mailing list [EMAIL PROTECTED] 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/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/r.barrett%40openinfo.co.uk -- Richard Barrett http://www.openinfo.co.uk -- Mailman-Users mailing list [EMAIL PROTECTED] 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/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Lists of lists question...
I have several lists that in best practice I'd like to remain hierarchical. Example: staff.all(all staff) staff.pt (PT staff) staff.ft (FT staff) I would prefer to add full time staff members to the staff.ft list only and part time staff members to the staff.pt list only, and have staff.pt and staff.ft be members of staff.all. I would like to have all of the staff lists be restricted so that only members of the staff lists (staff.pt and staff.ft) be able to post to any of the staff lists. I would prefer to not have to add a full time staff member to staff.all and staff.ft. To allow a full time staff member to post to staff.all I would like to be able to just add him/her to the staff.ft list and not have to add them to an allow list in staff.all. Is there a way (or an easy way) to do this with Mailman? -John -- --jlockard - Gravity is a harsh mistress. - The Tick --- John M. Lockard | U of Michigan - School of Information Sys Admin III | 400 West Hall - 550 E. University. Ave. [EMAIL PROTECTED] |Ann Arbor, MI 48109-1092 www.umich.edu/~jlockard | 734-615-8776 | 734-764-2475 FAX --- -- Mailman-Users mailing list [EMAIL PROTECTED] 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/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Lists of lists question...
At 19:58 18/06/2003, John Lockard wrote: I have several lists that in best practice I'd like to remain hierarchical. Example: staff.all(all staff) staff.pt (PT staff) staff.ft (FT staff) I would prefer to add full time staff members to the staff.ft list only and part time staff members to the staff.pt list only, and have staff.pt and staff.ft be members of staff.all. I would like to have all of the staff lists be restricted so that only members of the staff lists (staff.pt and staff.ft) be able to post to any of the staff lists. I would prefer to not have to add a full time staff member to staff.all and staff.ft. To allow a full time staff member to post to staff.all I would like to be able to just add him/her to the staff.ft list and not have to add them to an allow list in staff.all. Is there a way (or an easy way) to do this with Mailman? The following page in the Mailman FAQ might give you some useful hints: http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq03.005.htp -John -- --jlockard - Gravity is a harsh mistress. - The Tick --- John M. Lockard | U of Michigan - School of Information Sys Admin III | 400 West Hall - 550 E. University. Ave. [EMAIL PROTECTED] |Ann Arbor, MI 48109-1092 www.umich.edu/~jlockard | 734-615-8776 | 734-764-2475 FAX --- -- Richard Barrett http://www.openinfo.co.uk -- Mailman-Users mailing list [EMAIL PROTECTED] 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/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Lists stop working
Hi, I have some problems with my Mailman server. I am running Mailman 2.1.2 (installed from source) on a RedHat 8.0 Linux server (using Sendmail version 8.12.8-5.80). The problem is the following: I send an eMail to one of the lists, I can see in my /var/log/maillog; Jun 10 11:27:03 osiris sendmail[2756]: h5A9R392002756: from=[EMAIL PROTECTED], size=502, class=0, nrcpts=1, msgid=[EMAIL PROTECTED], proto=ESMTP, daemon=MTA, relay=cassini.xxx [193.10.220.37] Jun 10 11:27:03 osiris sendmail[2757]: h5A9R392002756: to=|/usr/local/mailman/mail/mailman post nicke-test, ctladdr=[EMAIL PROTECTED] (8/0), delay=00:00:00, xdelay=00:00:00, mailer=prog, pri=30704, dsn=2.0.0, stat=Sent that the server is receiving the eMail and is forwarding it to Mailman. But in Mailmans logs I will not find any information that it has received the eMail and no eMail is sent to the members on the list. If I dump all members of the list to a file, remove the list, create the list again and add all members, the list is working again for a while, and then it repeats again. It is not all lists that behave like above, other lists are working just fine! Niklas -- Mailman-Users mailing list [EMAIL PROTECTED] 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/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Lists not showing up in listinfo
* Listmom ([EMAIL PROTECTED]) wrote: Greetings all. I'm having a small problem after moving a list to a new server. After importing all the files located under mailman/lists, I can no longer see the public lists when I go to http://lists.doman.com/mailman/listinfo Did you run the $prefix/bin/fix_url.py script? -- Matthew Davis http://dogpound.vnet.net/ An algorithm must be seen to be believed. - D. E. Knuth -- Mailman-Users mailing list [EMAIL PROTECTED] 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/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Lists not showing up in listinfo
Greetings all. I'm having a small problem after moving a list to a new server. After importing all the files located under mailman/lists, I can no longer see the public lists when I go to http://lists.doman.com/mailman/listinfo Help. -- Mailman-Users mailing list [EMAIL PROTECTED] 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/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Lists stopped for dns problems ?
Hi! I have two middle-size lists at a debian server (mailman version: 2.0.11) with exim 3.35 I have the following problem: Both lists stopped, the qrunner process got locked, the posts come in, but does not go out. I have the smtp-failure log full of these: 451 [EMAIL PROTECTED] (Cannot check [EMAIL PROTECTED] at this time - please try later) I read the exim-users archive, and finally found that it's often caused by dns problems. I thought, that such a problem will not cause mailman to stop, but to put these users to nomail. The only thing i could do it to put them to nomail manually and then clear the qfiles dir, because after putting them to nomail the .db files countained their address and the system tried to send mails to them. Is there any solution for this problem ? Best regards, -- Peter DOMA [EMAIL PROTECTED] -- Mailman-Users mailing list [EMAIL PROTECTED] 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/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Lists stopped for dns problems ?
On Mon, 2003-03-10 at 10:32, DOMA Peter wrote: Both lists stopped, the qrunner process got locked, the posts come in, but does not go out. I have the smtp-failure log full of these: 451 [EMAIL PROTECTED] (Cannot check [EMAIL PROTECTED] at this time - please try later) I read the exim-users archive, and finally found that it's often caused by dns problems. Ideally you fix the DNS problems if this is a general problem other than with a number of specific addresses. However there are a set of approaches for this as a general problem:- 1. Run a local caching DNS server, especially if you are more than a 100Mbit link from whatever resolver you use. Make sure the MTA is using that resolver. djb's dnscache works OK for this - see http://cr.yp.to/djbdns.html 2. Don't do DNS lookup (ie recipient verification) in the MTA for Mailman traffic. Instead let the MTA sort it out and deal with the bounces. For exim do something like:- receiver_verify_hosts = !127.0.0.1/8:0.0.0.0/0 to prevent verifies on mail recipients from a local Mailman install. Either of these will help, although you main answer - and a way of speeding things up for mailman submission is to do (2). (1) will generally speed the MTA. This stuff *is* in the FAQ. See http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq06.002.htp http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq06.006.htp http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq06.008.htp [OK, I admit I have slightly modified the first 2 of these in the light of this question, and although I am sure the stuff about DNS caches is in there somewhere I have explicitly created the 3rd FAQ entry there on DNS cache usage. If people hate those answers please fix them!] Nigel. -- [ Nigel Metheringham [EMAIL PROTECTED] ] [ - Comments in this message are my own and not ITO opinion/policy - ] -- Mailman-Users mailing list [EMAIL PROTECTED] 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/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Lists stopped for dns problems ?
Hi! Ideally you fix the DNS problems if this is a general problem other than with a number of specific addresses. However there are a set of approaches for this as a general problem:- 1. Run a local caching DNS server, especially if you are more than a 100Mbit link from whatever resolver you use. Make sure the MTA is using that resolver. djb's dnscache works OK for this - see http://cr.yp.to/djbdns.html 2. Don't do DNS lookup (ie recipient verification) in the MTA for Mailman traffic. Instead let the MTA sort it out and deal with the bounces. For exim do something like:- receiver_verify_hosts = !127.0.0.1/8:0.0.0.0/0 to prevent verifies on mail recipients from a local Mailman install. The second solution is great for me, i put it in, and the submission time went down from ~28.5sec to ~0.05 sec :) Thanks a lot Peter -- Mailman-Users mailing list [EMAIL PROTECTED] 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/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Lists work, web doesn't.
On 15 Feb 2003, Jon Carnes wrote: There are a bunch of things to check - and you have probably already checked them: - rights on the complete directory structure for Mailman (check each directory and subdirectory to make sure that apache can get to the cgi's and the lists). I've used check_perms repeatedly. There's a security cron job running on my computer currently which keeps aggressively switching the permissions on the mailman directory to something less dangerous, but switching the permissions back to what they're supposed to be doesn't seem to have any effect on the problem, whatsoever. (I've tried it several times, out of exasperation.) - can you create a new list and access it? New lists seem to behave exactly like the old ones. - are you running straight http or https? I'm running with defaults. - what do the web legs say - any warnings or errors? Nothing but some punk kid failing to compromise my system this morning. Tess -- Mailman-Users mailing list [EMAIL PROTECTED] 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/ This message was sent to: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Lists work, web doesn't.
On Sun, 2003-02-16 at 11:38, Tess Snider wrote: On 15 Feb 2003, Jon Carnes wrote: There are a bunch of things to check - and you have probably already checked them: - rights on the complete directory structure for Mailman (check each directory and subdirectory to make sure that apache can get to the cgi's and the lists). I've used check_perms repeatedly. There's a security cron job running on my computer currently which keeps aggressively switching the permissions on the mailman directory to something less dangerous, but switching the permissions back to what they're supposed to be doesn't seem to have any effect on the problem, whatsoever. (I've tried it several times, out of exasperation.) Hmmm, It's been awhile since I played with FreeBSD (I like OpenBSD a bit more). It sounds like a rights problem. Try commenting out the security job for a bit and then opening up the rights on the whole Mailman directory structure - just as a test. In the past some folks running BSD have had similar problems due to rights on the directory structure. BTW: Mailman's check_perms program doesn't check the whole directory tree, just the part from ~mailman on down. If mailman's directory is hung off an inaccessible root directory then external apps (like say apache) could have real difficulty in reading your lists. I'm guessing that you are not running the Apache server in a chroot'ed environment. Jon Carnes -- Mailman-Users mailing list [EMAIL PROTECTED] 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/ This message was sent to: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Lists work, web doesn't.
On 16 Feb 2003, Jon Carnes wrote: Hmmm, It's been awhile since I played with FreeBSD (I like OpenBSD a bit more). FreeBSD? This is Linux! ;) It sounds like a rights problem. Try commenting out the security job for a bit and then opening up the rights on the whole Mailman directory structure - just as a test. In the past some folks running BSD have had similar problems due to rights on the directory structure. I'm going to poke around, and figure out where this security thing is. It's driving me batty. Mandrake put it on, automatically, and while I appreciate its concern for the security of my machine, I don't like things clobbering my deliberately-set permissions! BTW: Mailman's check_perms program doesn't check the whole directory tree, just the part from ~mailman on down. If mailman's directory is hung off an inaccessible root directory then external apps (like say apache) could have real difficulty in reading your lists. It's just in the regular old default /home/mailman. There should be nothing wrong with my /home directory, because I can browse to my ~user (/home/user) directories just fine. I'm guessing that you are not running the Apache server in a chroot'ed environment. No, it's not chrooted, and hasn't been, to date. (Which is not to say I won't do that in the future, but I'd like to have everything working before going off and doing something that's going to break it all, again. ;) ) Tess -- Mailman-Users mailing list [EMAIL PROTECTED] 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/ This message was sent to: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Lists work, web doesn't.
On Sun, 2003-02-16 at 12:51, Tess Snider wrote: On 16 Feb 2003, Jon Carnes wrote: Hmmm, It's been awhile since I played with FreeBSD (I like OpenBSD a bit more). FreeBSD? This is Linux! ;) Sorry! I just read another post before writing this and dropped a few synaptic links. I'm using Mandrake myself right now. It's just in the regular old default /home/mailman. There should be nothing wrong with my /home directory, because I can browse to my ~user (/home/user) directories just fine. So you are running version 2.1.13? What happens when you look for the lists via http://127.0.0.1/mailman/admin -- Mailman-Users mailing list [EMAIL PROTECTED] 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/ This message was sent to: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Lists work, web doesn't.
Oh boy, I am at the end of my rope. I recently upgraded my Mandrake distro on my mailman server, and my lists seem to be delivering mail just fine, but I can't reach the web pages for them at all. Whenever I try to reach them using the URL in the subscription email, I get: -- No such list [List Name] There currently are no publicly-advertised mailman mailing lists on [Server Name]. To visit the info page for an unadvertised list, open a URL similar to this one, but with a '/' and the right list name appended. List administrators, you can visit the list admin overview page to find the management interface for your list. (Send questions or comments to [EMAIL PROTECTED]) - Where [List Name] is the name of the list and [Server Name] is the server. Now, before everyone says, The server name needs to match the one for the list! I already checked that. The server name is right. Besides that, I tried it with every other combination I could think of, and I have VIRTUAL_HOST_OVERVIEW set to 0 in the mm_cfg.py, anyway. And yes, the list is advertised (and even if it wasn't, it should still come up correctly when I go straight to its URL!). I'm using Postfix for my mail and Apache for my web server. I'm currently configured with mail gid mailman and cgi gid apache. Anyone have any clues? Thanks for your time! Tess -- Mailman-Users mailing list [EMAIL PROTECTED] 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/ This message was sent to: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Lists work, web doesn't.
There are a bunch of things to check - and you have probably already checked them: - rights on the complete directory structure for Mailman (check each directory and subdirectory to make sure that apache can get to the cgi's and the lists). - can you create a new list and access it? - are you running straight http or https? - what do the web legs say - any warnings or errors? On Sat, 2003-02-15 at 20:36, Tess Snider wrote: Oh boy, I am at the end of my rope. I recently upgraded my Mandrake distro on my mailman server, and my lists seem to be delivering mail just fine, but I can't reach the web pages for them at all. Whenever I try to reach them using the URL in the subscription email, I get: -- No such list [List Name] There currently are no publicly-advertised mailman mailing lists on [Server Name]. To visit the info page for an unadvertised list, open a URL similar to this one, but with a '/' and the right list name appended. List administrators, you can visit the list admin overview page to find the management interface for your list. (Send questions or comments to [EMAIL PROTECTED]) - Where [List Name] is the name of the list and [Server Name] is the server. Now, before everyone says, The server name needs to match the one for the list! I already checked that. The server name is right. Besides that, I tried it with every other combination I could think of, and I have VIRTUAL_HOST_OVERVIEW set to 0 in the mm_cfg.py, anyway. And yes, the list is advertised (and even if it wasn't, it should still come up correctly when I go straight to its URL!). I'm using Postfix for my mail and Apache for my web server. I'm currently configured with mail gid mailman and cgi gid apache. Anyone have any clues? Thanks for your time! Tess -- Mailman-Users mailing list [EMAIL PROTECTED] 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/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/jonc%40nc.rr.com -- Mailman-Users mailing list [EMAIL PROTECTED] 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/ This message was sent to: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Lists periodically vanishing
Interesting, so you have both archives working in parallel: Pipermail and Mhonarc? That sounds like a hack. And I'm assuming that you are running a 2.0.x version install. I think that if you upgrade to 2.1.x you will remove the problem. The ubiquitous qrunner was replaced with various sub-processes that each do individual tasks - one such task is archiving. An other alternative is to copy the archive MBox periodically to a separate location and then point Mhonarc to the copy of Mbox, then it won't hold open the one used by Pipermail when Mhonarc does its re-indexing and discovery of new messages. I run Mhonarc differently. I simply subscribe a local user to my list and let Mhonarc use the mbox from the local user. You might think about that as an alternative for yourself. Good Luck! On Wed, 2003-01-08 at 14:18, Tom Maddox wrote: Hi, everyone, I've just been assigned the task of managing an existing mailman installation, and it's evidently been having a recurring problem with lists mysteriously vanishing for some short period of time and then reappearing, occasionally in a corrupted state (membership list and config settings hosed, etc.) The symptoms I've observed are as follows: 1) Mail sent to a list will bounce with a message like the following: - The following addresses had permanent fatal errors - [EMAIL PROTECTED] (reason: Data format error) - Transcript of session follows - list: Mailbox does not exist 501 5.6.0 Data format error 2) Attempting to access the archive web page for the list returns a 404 Not found error, although it *is* possible to access the standard information page about the list. Relevant system information: FreeBSD 4.7-STABLE #0 sendmail 8.12.6 Mailman 2.0.8 The mailman archives are also being archived by mhonarc v.2.5.13; archiving by mhonarc happens every 15 minutes. It scans for changes in the mailman archives and then updates its own copy as necessary (at least, that's how I think it works). I would guess it's possible that mhonarc is locking the list archive file and causing concurrency issues and disruptions in the list as a result. Any thoughts? Thanks, Tom -- Mailman-Users mailing list [EMAIL PROTECTED] 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/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/jonc%40nc.rr.com -- Mailman-Users mailing list [EMAIL PROTECTED] 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/ This message was sent to: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
