Scott Harney wrote: > Petri Laihonen wrote: >> Ha! More interesting information.... >> I will take another look at Google mail stuff..... >> Thanks.... >> >> Now, Does anyone know a good reason not to look into google provided >> services? >> Some of my concerns would be: >> - my stuff would be indexed on the server other than my own, who >> will have access to this data? >> - same above concern, if I choose to use their web apps (word >> processing etc....) >> - While I'm not a security expert, Is my data safer on my own server >> than on google servers? >> - is google becoming a M$ like bully while they grow .... >> - anything else? >> > > Those are all things you'll have to consider whether or not you trust > google over, say, Cox ;-) . Obviously it will be more expensive to > host it all on your on server. If you're buying from, say, slicehost, > you have to trust them as well though to a somewhat lesser degree. > > If you stand up a physical box at a co-lo, that can be quite > expensive. Also, managing a "real" mail server (and DNS) can get very > complicated very quickly. How well do you understand SMTP and related > protocols, mail filtering (because you will need to filter), DNS and > MX records, the various spam blocklists, and security/patching? > Unfortunately, it's not as simple as typing "apt-get install postfix"; > you really need to have a good understanding of the network protocols > involved and how you are going to address spam and virus traffic. > There are numerous discussion about perfect mail server setups using > various debian distributions and combinations of mail server software > (postfix, qmail) that can be easily found using ... well ... um... Google. > > Please don't interpret this as me encouraging you to avoid setting up > your own mail server. I'm just pointing some things to start > researching if you choose to learn about it by doing. Things to google > on: postfix, qmail, SMTP AUTH, TLS, submission port 587, > tmda.sourceforge.net, spamassassin, clamav, amavisd, MX records, > Sender policy framework (http://www.openspf.org), etc ,etc ,etc :-) > Pretty much the reason for looking other options than my own mails server is that I'm kind of tired managing one, mostly due to reasons already pointed out. Learning all the new tricks for spam/virus filtering while still providing the service sometimes takes way too much of my time. I have never offered SMTP except for myself and my employees. For other entities which I happen to host websites etc... I do provide secure POP3 and/or forwarding services. (I have not allowed insecure POP for years....)
For DNS I use my hosting providers, but will sufficiently manage it myself via web interface. (unless I need to change IP address for over ~10 records.... that would be a time for a TroubleTicket) I will definitely take a look at the google options now that my favorite IMAP is supported and see if that would be the way to go.... Most likely I would still keep some of my own domains at my own servers. Petri
_______________________________________________ General mailing list [email protected] http://mail.brlug.net/mailman/listinfo/general_brlug.net
