Sean Burns wrote: > If you don't want to do it, I don't mind being an admin for it.
Done. Just log in with your @bworks.org username and password: http://mail.google.com/a/bworks.org You are now part of the [EMAIL PROTECTED] list, too. :) > How did you set up the gmail bworks.org thing? Actually, Rick Allard, who has since moved on, initially set things up. It's basically just a few steps: 1) apply for Google Apps for your group 2) once you're approved, adjust the MX records in your DNS 3) add users, aliases, and lists > I don't mind being an admin for it but I think others should too. I > volunteer Theresa and Dan right off the bat. I wouldn't want to > overwhelm Jake with anything that might take away from his > schoolwork, not that this would in the slightest, but he would be > good too. Theresa - Done. Theresa, let one of the admins know if you do not want admin rights. Dan, Jake (although I agree with Sean)? Let an admin know because an @bworks.org address would have to be created first. e-mail [EMAIL PROTECTED] > It's been helpful actually. In addition to the argument that Dan > makes, which I wholeheartedly agree with, I didn't have Jess' email > and thought to send him one via [EMAIL PROTECTED] It was nice > having that available. In fact, I'm going to use mine more. I'm > going to weed out the cowl address and use the [EMAIL PROTECTED] > address as its replacement. BTW, with some SMTP servers and e-mail clients you can do some From header "spoofing." For example, when I use gmail as my SMTP and Thunderbird as my e-mail client, I can send mail as though I am [EMAIL PROTECTED] or [EMAIL PROTECTED] That way when I send a message to people and they hit "reply", it will go back to info or help. That also means that others that are on the info or help list stay in the loop. Regards, - Robert
