This new machine is a lot faster. It
runs Apache and its mailing lists are
handled by Mailman so they should be
easier to join, leave and administer.
The new mail server runs the DCC so we
should have less spam although blocking
probably won't start for a few days. In
the mean time, you can see the new X-DCC
headers and use them to filter junk.
http://www.rhyolite.com/anti-spam/dcc/
http://www.rhyolite.com/anti-spam/dcc/greylist.html
During the changeover the cvs repository
for the web site will probably be down
for an hour or 3. the mailing lists may
be down for an hour or so. The web site
should be up continuously.
With the new setup the public mailing
lists are configured to only accept mail
from that list's subscribers but will
accept posts from anyone via usenet. The
reason to make them subscriber-only is
to filter out spam. This setup is nearly
the same as the old one although now its
a bit harder to do cross posts via mail
if you're not subscribed to all the lists.
If you really need to do cross-posts I
suggest posting via nntp.
Mails that aren't accepted will go to
the list's request queue where a
moderator can accept the real posts
and delete the spam. However, there
are over seventy mailing lists and (so
far) only two moderators so it may take
a while for posts to get moderated so
try to use news.mozilla.org for cross
posts.
Mailing lists can be left and joined as
described on the community page at
http://mozilla.org/community.html or
you can use the web interface at
http://mail.mozilla.org/
> We're planning to move www.mozilla.org
> and our mail server to a new machine today.
This is great! Will .htaccess be available for use per-directory and
what will be the default character set for things to be sent as?
--
Brant Langer Gurganus
http://brant.4omega.com
"no" and "apache's default charset" (iso-8859-1, i guess)
.htaccess files are disabled at the moment but now that
I look closer at the allowoverride directive i wouldn't
mind allowing FileInfo. Maybe indexes would be ok too.
I think the reason indexes were disallowed off before
was because of a security issue in our old server. Surely
that's not the case with apache but perhaps there are
places in our tree where its inappropriate? Probably not.
I'll try and think about this more once the dust settles
from the server moves.
"no" and "apache's default charset" (iso-8859-1, i guess)
Axel