I had my mailman up and quit working last week, possibly related to someone removing a couple of lists, but I can find no clue as to why. I installed a fresh 2.1.5 (I think the previous was at 2.1.3), to no avail. I'm not asking for help debugging the problem, as not only is this not the right place, but short of getting someone to root around my system, I don't think it would even be possible. What I would like is a pointer to some sort of architectural overview, so *I* can root around my system myself, with a better idea of where I'm headed than tracing the code line by line. http://zope.org/Members/bwarsaw/MailmanDesignNotes/SplittingQrunner gave some hints, but I couldn't find anything more detailed... Thanks!
The error logs are usually pretty helpful when I'm trying to debug a
problem. Have you checked there for any useful messages?
DallasOn Dec 21, 2004, at 12:08 AM, Alan Batie wrote:
I had my mailman up and quit working last week, possibly related to
someone removing a couple of lists, but I can find no clue as to why.
I installed a fresh 2.1.5 (I think the previous was at 2.1.3), to no
avail. I'm not asking for help debugging the problem, as not only is
this not the right place, but short of getting someone to root around
my system, I don't think it would even be possible. What I would like
is a pointer to some sort of architectural overview, so *I* can root
around my system myself, with a better idea of where I'm headed than
tracing the code line by line.
http://zope.org/Members/bwarsaw/MailmanDesignNotes/SplittingQrunner
gave some hints, but I couldn't find anything more detailed...
Thanks!
Mailman-Developers mailing list Mailman-Developers@python.org http://mail.python.org/mailman/listinfo/mailman-developers Unsubscribe:
http://mail.python.org/mailman/options/mailman-developers/ dallas%40dreamhost.com
Alan Batie wrote:
What I would like is a pointer to some sort of architectural overview, so *I* can root around my system myself, with a better idea of where I'm headed than tracing the code line by line. http://zope.org/Members/bwarsaw/MailmanDesignNotes/SplittingQrunner gave some hints, but I couldn't find anything more detailed... Thanks!
I know this isn't what you asked for, and you may have already seen it, but you might find http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq03.014.htp of some use.
-- Mark Sapiro <msapiro@value.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
"Alan" == Alan Batie <alan@batie.org> writes:
Alan> What I would like is a pointer to some sort of architectural
Alan> overview, so *I* can root around my system myself, with a
Alan> better idea of where I'm headed than tracing the code line
Alan> by line.I haven't looked at the web code, but when I went in and did some surgery a couple months ago, I found the architecture of the mail-handling code is pretty well reflected in the directory structure. Also, looking at the backtraces in error messages is quite informative about structure, although it only tells you about the one path to the leaf. So I found it fairly easy to find the stuff of interest.
You might also want to look at some of the notes for Mailman3 in the Mailman3 tree, and compare its source tree structure to Mailman2.
-- Institute of Policy and Planning Sciences http://turnbull.sk.tsukuba.ac.jp University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Ask not how you can "do" free software business; ask what your business can "do for" free software.
Stephen J. Turnbull wrote:
You might also want to look at some of the notes for Mailman3 in the Mailman3 tree, and compare its source tree structure to Mailman2.
Thanks for all the pointers; I haven't had a chance to dig in yet, but I did get the mail flowing again by moving out a large batch of messages that were in the out queue for a particular list. The list-owner had been twiddling a bunch of the moderation settings to basically make it an announce only list, and had also had some complaints about message duplication on a large scale. With the lists working again, it'll be lower priority, but I'll see what I can make out of things...
On Tue, 2004-12-21 at 03:08, Alan Batie wrote:
I had my mailman up and quit working last week, possibly related to someone removing a couple of lists, but I can find no clue as to why. I installed a fresh 2.1.5 (I think the previous was at 2.1.3), to no avail. I'm not asking for help debugging the problem, as not only is this not the right place, but short of getting someone to root around my system, I don't think it would even be possible. What I would like is a pointer to some sort of architectural overview, so *I* can root around my system myself, with a better idea of where I'm headed than tracing the code line by line. http://zope.org/Members/bwarsaw/MailmanDesignNotes/SplittingQrunner gave some hints, but I couldn't find anything more detailed... Thanks!
I wish we had them. What's around is quite scattered, which is probably par for the course for most FOSS projects (but makes my commercial project manager skin crawl ;). Alas, I'm still waiting for that rich uncle to help us do things right. :)
That said, another semi-useful source of information is the big comment at the top of IncomingRunner.py, which shows how mail messages flow through the system -- somewhat.
Plus, I'm offended that you don't consider our code so beautifully transparent that the elegance of our architectural sand sculpture is not immediately evident simply through osmosis. The noive of some people.
(Kidding of course! :)
-Barry
participants (5)
-
Alan Batie -
Barry Warsaw -
Dallas Bethune -
Mark Sapiro -
Stephen J. Turnbull