Correction: "To get around this I recommend option #2, however with a modification. > You should setup the mail server to relay all mail via your shaw mail > account (Thus your mail server sends the mail to shaws mail server, and > then out to the real world) OR you can simply setup your mail accounts > to connect to the SMTP server for outbound messages (and your email > server for inbound)."
should have read: To get around this I recommend option #2, however with a modification. You should setup the mail server to relay all mail via the shaw mail server (Thus your own mail server sends the mail to shaws SMTP mail server, and then out to the real world) OR you can simply setup your mail accounts to connect to Shaws SMTP server for outbound messages (and your email server for inbound). On Fri, 2004-03-26 at 01:59, Michael Petch wrote: > I agree with Option #2 as Cameron suggests, however what was not > mentioned is something very important. > > In Cameron's #2 solution you may find that your mail server will not be > able to send mail to some ISP's (Most notable AOL, but many others as > well). The reasoning is that Shaw has published its Residential Dynamic > IP address ranges which are used to curtail spam propogation. > > What does this mean? If you try to send email directly to AOL mail > server you will receive a message back that looks like this (and it will > only be sent ONCE - so if you never see this message you might never > know your outbound mail to aol falls on the floor): > > 554- (RTR:BB) The IP address you are using to connect to AOL is a > dynamic > 554- (residential) IP address. AOL will not accept future e-mail > transactions > 554- from this IP address until your ISP removes this IP address from > its list > 554- of dynamic (residential) IP addresses. For additional information, > 554 please visit �postmaster.info.aol.com. > > ------------- > > To get around this I recommend option #2, however with a modification. > You should setup the mail server to relay all mail via your shaw mail > account (Thus your mail server sends the mail to shaws mail server, and > then out to the real world) OR you can simply setup your mail accounts > to connect to the SMTP server for outbound messages (and your email > server for inbound). > > On Thu, 2004-03-25 at 22:28, Shawn wrote: > > 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 -- Mike Petch CApp::Sysware Consulting Ltd. Suite 1002,1140-15th Ave SW. Calgary, Alberta, Canada. T2R 1K6. (403)804-5700.
signature.asc
Description: This is a digitally signed message part
_______________________________________________ clug-talk mailing list [EMAIL PROTECTED] http://clug.ca/mailman/listinfo/clug-talk_clug.ca
