[arch-dev-public] mailman hiccup
Broke and fixed and broke and fixed mailman tonight. Ignore the goofed commits emails you may have gotten. For documentation purposes, here's what happend: * A few days ago we added a redirect from archlinux.org to www.archlinux.org to address some silly caching issues.\ * This broke mailman's web interface as it was using "archlinux.org" and the redirect was blowing things up (silently) * Used bin/withlist -r fix_url to modify the url for all the lists. This also changed the list's host_name to the same URL. Whoops * Readjusted all the host_name properties to archlinux.org so that the mails work again. Mailman hater for life, Aaron
On Tue, Jan 20, 2009 at 06:49, Aaron Griffin <aaronmgriffin@gmail.com> wrote:
Mailman hater for life, Aaron
Whoever proposes a simple mailing list manager: - Simple postfix integration (no -request, -unsubscribe, etc.: one line in aliases) - So E-mail confirmation through a web link - Simple web interface (PHP or WSGI) - Some sort of SQL for storage - Multiple hostnames support (or better, no real care for hostnames except distinction of MLs) will get my unconditional love! I don't care much about archive either. How hard would that really be? -- Geoffroy Carrier
Geoffroy Carrier wrote:
On Tue, Jan 20, 2009 at 06:49, Aaron Griffin <aaronmgriffin@gmail.com> wrote:
Mailman hater for life, Aaron
Whoever proposes a simple mailing list manager: - Simple postfix integration (no -request, -unsubscribe, etc.: one line in aliases) - So E-mail confirmation through a web link - Simple web interface (PHP or WSGI) - Some sort of SQL for storage - Multiple hostnames support (or better, no real care for hostnames except distinction of MLs) will get my unconditional love!
I don't care much about archive either.
How hard would that really be?
I've been working on my own mailing list manager, it's completely written in PHP and uses SQL as a backend, but at this point a bit specific to our setup. Because our company is all about open source I intend on releasing it as such. It's in need of an overhaul anyway, I'll get hacking at it again ASAP. Glenn
Aaron Griffin schrieb:
Broke and fixed and broke and fixed mailman tonight. Ignore the goofed commits emails you may have gotten.
For documentation purposes, here's what happend:
* A few days ago we added a redirect from archlinux.org to www.archlinux.org to address some silly caching issues.\
Out of curiosity: Why? I hate that every site has to have "www" in front of it, it's silly. Why don't we just have a redirect from www.archlinux.org to archlinux.org?
On Tue, Jan 20, 2009 at 10:47, Thomas Bächler <thomas@archlinux.org> wrote:
Out of curiosity: Why? I hate that every site has to have "www" in front of it, it's silly. Why don't we just have a redirect from www.archlinux.org to archlinux.org?
Those statements might be obvious to you, but I hope some might learn something, and I'll be able to refer to it in the future :) --- Because www designates the *word wide* web, i.e. website available from everywhere and for everyone. It can be seen as a part of the whole company "network" designated by the domain name. Their internal tools (webmail, specific webapps, etc. but also Jabber/SQL/etc. servers), which are only available from inside their building network, or only usable by their members/other tools, are other subparts available through their own sub.domain This tradition predates the availability of the SRV records (for the same domain name, how a specific service can be joined; still generaly unimplemented), so the distinction: 1 - of different servers for different protocols 2 - of different services based on the same protocol (http being the best example) requires different subdomain... It seems nice to use the (short) domain name for the prevalent service, so it points to the website too. Using a redirection permits to keep unique URIs for each resource and gives better positions in search engines. E-mail is an exception thanks to the MX records. Traditions last! Finally the message I wrote for you: public resource <-> URI with www... -- Geoffroy Carrier
On Tue, Jan 20, 2009 at 3:47 AM, Thomas Bächler <thomas@archlinux.org> wrote:
Aaron Griffin schrieb:
Broke and fixed and broke and fixed mailman tonight. Ignore the goofed commits emails you may have gotten.
For documentation purposes, here's what happend:
* A few days ago we added a redirect from archlinux.org to www.archlinux.org to address some silly caching issues.\
Out of curiosity: Why? I hate that every site has to have "www" in front of it, it's silly. Why don't we just have a redirect from www.archlinux.org to archlinux.org?
I'm on your side here, but in all honesty, it's arbitrary. More people on the bug report were for www than not, and Dan got to it first. Why I hate "www": * world wide web... who says that anymore? * For every other service, people are totally fine with using the domain name and letting it decide what to do: ssh archlinux.org NOT ssh ssh.archlinux.org; mailto aaron@archlinux.org NOT mailto aaron@email.archlinux.org; ping archlinux.org NOT ping icmp.archlinux.org; I can go on and on and on. The only benefit I've heard here is relating to using a CNAME for the website DNS, allowing us to redirect web traffic easier, for downtime and the like, but that seems minor, and we can always change an A record too. /me shrugs
participants (4)
-
Aaron Griffin
-
Geoffroy Carrier
-
RedShift
-
Thomas Bächler