I have a question- are the geo mailing lists disabled? I just tried to send something out to somervillains@buffistas.org and got a bounceback:
Hi. This is the qmail-send program at yahoo.com.
I'm afraid I wasn't able to deliver your message to
the following addresses.
This is a permanent error; I've given up. Sorry it
didn't work out.
:
205.214.170.170 does not like recipient.
Remote host said: 550 sorry, no mailbox here by that
name. (#5.7.17)
Giving up on 205.214.170.170.
The b.org mailing lists have nothing to do with yahoo. If you got a bounceback from yahoo, it's because one of the Somervillains has a now-defunct yahoo.com email address.
They should be working. I was able to log into the administrative interface, and that seems to work just fine. I'm not sure why your getting the rejection.
eta: And Jon comes through.
hm, ok, I was stupid to put the yahoo thing in there- I sent it FROM a yahoo account which is why that reference is there. Also, the C&P failed because of the auto formatting. Here's the actual thing:
somervillains@buffistas.org>:
205.214.170.170 does not like recipient.
Remote host said: 550 sorry, no mailbox here by that
name. (#5.7.17)
Giving up on 205.214.170.170.
And if it is just a rejection of someone's mailbox in the group, did either of you get the email I sent about Monday night's dinner? If not, then there's a problem...
I had a problem with the DCistas list. I'm not sure that it ever got resolved, since we had our minF2F, so we weren't using it anymore.
:~ kevinbeaumont$ telnet mail.buffistas.org 25
Trying 205.214.170.170...
Connected to mail.buffistas.org.
Escape character is '^]'.
220 ds.buffistas.org ESMTP
HELO pettifog.com
250 ds.buffistas.org
MAIL FROM:serenity@pettifog.com
250 ok
RCPT TO:somervillains@buffistas.org
550 sorry, no mailbox here by that name. (#5.7.17)
By the way, the first MX record (mx2.buffistas.org) gets connection refused on port 25.
I'm going to nuke somervillains and recreate it. Hold tight.
ita, just got the recreation e-mail. I'll go set things up.
edit: I haven't been able to get in there for a while...I assumed it had something to do with the updates, and I've been too busy to look into it. Sorry guys!
Looks like it's working now. Hurray!
Did the same for DC. Others later.