Tracey McCartney writes: > The question for me always seems to boil down to whether my own sanity is > best preserved trying to fix this where it is or to do yet another host > move. :/
If it's *just* Mailman and you have ssh access (and permission to change the configuration files), we can walk you through it. Keep notes, as a poorly done upgrade by the host could cause the issue to regress. But if otherwise you're satisfied with the host, well, we'll always be here -- no need to change. > I don't know why this host won't get its #$^& together re. Mailman. Well, it could be a symptom of inadequate staffing (in some sense, of course you rarely get more than you pay for). But I suspect many hosting services expect that cPanel and Mailman take care of everything and chalk issue up to user error. It's a compliment to us, of sorts. :-) ------------------------------------------------------ Mailman-Users mailing list [email protected] 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
