Any chance of forging ahead with this, now that I have availed the server??
On Fri, Jun 10, 2011 at 19:33, Odhiambo Washington <odhia...@gmail.com>wrote: > > > On Thu, Jun 9, 2011 at 01:34, Barry Warsaw <ba...@list.org> wrote: > >> On Jun 08, 2011, at 04:20 PM, Odhiambo Washington wrote: >> >> >Is a valid MX record a MUST for this project? >> > >> >My test box is inside a 2Mbps symmetric connection from anywhere (USofA, >> etc) >> >but it does not have a valid MX record. Will that do? If it must have, >> then >> >I will need to register a domain name and talk to the ISP to do the >> mappings. >> > >> >However, if this test is non-intrusive to Exim, then I can use one of the >> >production servers I use. >> > >> >PS: My hope is that we'll be using Exim as the MTA:) >> >> As long as you can send email to foo-l...@example.com, I think that's all >> that >> matters for right now. >> >> My idea is that we'd bring up a test domain with a couple of test lists, >> and >> let people subscribe and unsubscribe via email (e.g. foo-join@example.comand >> foo-le...@example.com). Then people could post test messages to the list >> and >> we'd all see how MM3 performed under real-world conditions. >> >> A few other things: >> >> * My main goal right now is to get the core to releasable state by >> 11.11.11. >> This probably means it's got to go to beta fairly soon, probably no later >> than the end of the northern hemisphere summer (probably best right after >> GSoC ends). >> >> * We don't need to wait until the web ui is ready, so we'll start with >> just >> the email interface. >> >> * Probably best to run the system off of bzr trunk. That way, you can >> much >> more quickly deploy bug fixes during this test phase. >> >> * I actually don't need shell access if you're willing and able to >> maintain >> the system, provide logs if necessary, update the bzr branch, etc. >> >> * I think the risk is small, but you should be prepared to deal with any >> runaway mail storms. Since most of the queuing architecture is a fairly >> straight port from MM2, and we have at least a *decade* of experience >> with >> that subsystem, we should be in good shape. But the MM3 code has been >> refactored and updated to more modern Pythonic idioms, so it's entirely >> possible that some catastrophic bug was introduced. Don't be afraid, but >> be >> prepared. :) >> >> -Barry >> > > Hello Barry, > > I have crafted a subdomain for this purpose. > > The 'domain' will be jaribu.kictanet.or.ke. The DNS portions have just > been done a few hours ago so they need some hours to propagate, otherwise > the IP is 196.200.26.114 > Please dig your e-mails (btn me and you) for your logon credentials. > The host already has Apache22, Exim-4.76, etc. > > Nigel's been quiet! > > > -- > Best regards, > Odhiambo WASHINGTON, > Nairobi,KE > +254733744121/+254722743223 > _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ > I can't hear you -- I'm using the scrambler. > Please consider the environment before printing this email. > > -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254733744121/+254722743223 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ I can't hear you -- I'm using the scrambler. Please consider the environment before printing this email.
<<image001.png>>
<<image001.png>>
_______________________________________________ Mailman-Developers mailing list Mailman-Developers@python.org http://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
