Hi Cameron. You have two options in this matter (as I see it, I'm sure there are more though)
1) Collect the email from the Shaw account periodically and handle it internally. This can be partially done with FetchMail - which is designed to retrieve mail from a remote mailbox and place it in a local mailbox. I understand it even has a few rules that you can play with to help automate the delivery of messages to appropriate internal mailboxes. The downside is that you'll likely get the bulk of your mail coming into a single internal mailbox, forcing you to manually forward it to the appropriate person. 2) Build your own email server, and ignore the Shaw account. This is the way I personally went - mainly because I didn't want my email address to change if I decided to change my ISP. But, there are other benefits - you get to control how much space your mailbox can take up, you can control how many mailboxes to create, you can control the server (reboot if needed, etc.) and not wait for someone else to look into it. However, there are downsides too - you have to build an email server (which can be simple or complex - depending on your background and needs), you have to manage your bandwidth - too much usage, and the ISP might decide to shut you down, most ISP's don't allow you to run a server on their consumer type accounts (though I've yet to hear of someone being shut down who has responsibly watched their bandwidth utilization). The second option means a few more headaches initially, but once setup you can almost forget about the server. And if you are already running a Linux server, then this is a natural choice. Oh, but you have to leave the server on 24/7 - otherwise you loose the benefits of running your own server. If you decide to go the second route, I'd be happy to help out where I can. I have created a quasi guide for this on my website (http://www.open2space.com/linux/intranet/emailserver.php), though it's a little dated now. In the guide I recommend using Postfix for the mail server, but have since changed my mind and would now recommend qmail. qmail is simpler to get up and running, and the Life with qmail web site is pretty thorough (http://www.lifewithqmail.com). As Jesse mentioned, you'll need a domain name, but you can get some free domain names through dyndns.org and other such sites. If you choose to purchase a domain, then I would recommend looking into www.zoneedit.com for free domain hosting. (I also give some tips and links regarding domain names on my site - there's a link at the top of the page I posted above). I can honestly say that running my own email server is one thing I do NOT regret doing. Good luck. Shawn -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Cameron Nikitiuk Sent: Thursday, March 25, 2004 8:46 PM To: Clug-Talk Subject: [clug-talk] LAN Set-up - E-mail Hi All, Anyone care to take a kick at the cat on this one? I was contemplating downgrading to Shaw Lite speed to save a few dollars but from what I understand it only allows one email address. What I was thinking was to set-up a box on my LAN that would take all messages to that single email address and then forward to LAN where they would be distributed to the correct person. The person on the LAN could then also send out using that e-mail thru the LAN relay. Have I got that correct? Would this necessitate me getting a domain registered or is it something I could do without going that way? I don't want to cut dollars here to spend them elsewhere. You what I mean Vern? Cameron _______________________________________________ clug-talk mailing list [EMAIL PROTECTED] http://clug.ca/mailman/listinfo/clug-talk_clug.ca _______________________________________________ clug-talk mailing list [EMAIL PROTECTED] http://clug.ca/mailman/listinfo/clug-talk_clug.ca
