Re: [Mailman-Users] OT: Firefox Crashing on Admin Pages
Hank: Just thought I'd let you know that recent updates to Firefox and extensions (and maybe something else) solved the problem of FF crashing on Mm admin pages. I can again access those pages without problems ... Thanks for your ideas to fix it as well! -Kenneth -- 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] mailman user account and login
I thought I'd pose this question to the list. The mailman installation manual seems to imply that the mailman account should be added with no ability to log in to it. I translated what appeared to me to be the sense of the line given to Solaris. However, after having gone through several fire drills of resetting file owner from root to mailman, I've set the account up with the directory /usr/local/mailman and NP in the /etc/shadow file. This allows me to su - mailman from root, but not to get a login from anywhere else. This is the same setup as is used for other Solaris blind accounts. Is there any real reason not to use the account this way? I'm aware that Mailman security is based on group identity, not user, but external programs such as htdig running under cron need to have uid mailman in files it writes to or to be set up as a mailman-uid program. My personal preference is to set the needed uid's in the mailman runtime tree. Hank -- 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] separate mailman and web servers
Le Samedi 3 Février 2007 22:50, Mark Sapiro a écrit : Peter wrote: Le Samedi 3 Février 2007 15:37, Patrick Bogen a écrit : On 1/31/07, Peter Matulis [EMAIL PROTECTED] wrote: Can someone explain to me how mailman and the web server can exist on separate machines? I am new to mailman and I'm having a hard time understanding how mailman communicates with its web server. I have a new client that connects to an external web server to add list members but mailman (and postfix) runs on a local system. I believe this would have to work with Mailman acting upon and reading from files that are stored in such a way that the external web server can access them. This means: (a) The files are stored on the Mailman server, and the web server accesses them through something like NFS. (b) The files are stored on the web server, and the mailman server accesses them through something like NFS. (c) The files are stored in a third server, and both the web server and the mailman server access them through something like NFS. No, the web server is on the internet and the mailman server is on the lan. Thank you for this informative reply. I'm not sure how the fact that one machine is 'on the internet' and the other is 'on the lan' relates to Patrick's answer, so let's go back to your original question. Well he is mentioning NFS so it sounded like he presumed both servers were on the internal lan. Mailman's web pages are built by CGIs which access basic Mailman classes, methods and functions defined in a set of Mailman modules. These classes, methods and functions access various Mailman data. Most of this is the list's configuration and membership which is normally a Mailman list object saved as a Python pickle in /some/path/to/lists/listname/config.pck. Ok. Mailman's email processing is done by a set of qrunner processes accessing the same Modules and data as above. There is one (or possibly more) qrunner process for each queue - in, out, archive, commands, bounces, news, retry and virgin. Ok. Incoming mail is normally piped by the incoming MTA to a wrapper which invokes a script to store the message in a queue to be processed by one of the qrunners. Somehow Postfix on my lan must have this wrapper configured to talk to the Mailman also running on the localhost. If both the web pages and the lists are accessing and updating 'live' data, and the web server and the qrunners are not on the same machine, they must be accessing the same list data via some file sharing scheme. Normally, they would also access the same Mailman modules, but this isn't necessary. There must be some synchronization happening somewhere because changes are being made on the web server. If the web is used only for inquiry and not update, it could be operating on copies which are updated periodically, but if the web interface is used to make any changes, both it and the qrunners must access the same data and queues. The client has told me that they access the web server to make changes. PM -- 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] separate mailman and web servers
Peter wrote: Incoming mail is normally piped by the incoming MTA to a wrapper which invokes a script to store the message in a queue to be processed by one of the qrunners. Somehow Postfix on my lan must have this wrapper configured to talk to the Mailman also running on the localhost. Normally in this situation (Postfix and Mailman on the same machine), Postfix has a set of aliases for each list address that cause it to pipe the incoming list mail to Mailman's mail wrapper with the appropriate 'action' and listname arguments. Often, with Postfix, these aliases are in a file of Mailman aliases maintained by Mailman. If both the web pages and the lists are accessing and updating 'live' data, and the web server and the qrunners are not on the same machine, they must be accessing the same list data via some file sharing scheme. Normally, they would also access the same Mailman modules, but this isn't necessary. There must be some synchronization happening somewhere because changes are being made on the web server. Yes, and normally, this is done through some kind of shared file system so both the web server and the Mailman's qrunners are actually accessing the same files. -- 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
