No exim4, no spamassassin, no clam-av, no figuring out which indexer to use, or any of that. Just a forward on the incoming mail.
I actually miss running my own email domain, the privacy of it, not the actual administration. I stopped when I had gotten so crazy with aliases and disposable addresses that the spam overwhelmed me. Wasn't worth the time to 'do it right,' and I gave up my privacy for the simplicity of GMail.
I would love to leave GMail and take my privacy back, but I haven't found an acceptable alternative yet.
i fail to see how making good use of available resources is "cheating". the idea isn't to win some geek hair-shirt contest; it is to get email delivered to your domain.
There are many email providers you can use with your own domain. For example, rackspace is $2 a user a month. https://www.rackspace.com/apps/email_hosting/rackspace_email... I'm not sure why people are jumping from "Google won't do this for free for me anymore" to "I must do it myself".
It's pretty easy actually but when authorizing GMail to add a new sender address it usually mails a verification code to that address. Which, in this case would come back into the same Gmail inbox.
So if you have a [email protected] forwarding to [email protected], then the verification code would be sent by gmail to [email protected], which in turn, due to your forward settings, would redirect all mail to [email protected].
The difference is that when sending mail from your Gmail.com inbox as opposed to the Google apps inbox for [email protected] is that when you send a mail via gmail (even if you fake the sender), the signed-by field will contain "gmail.com". On the other hand, Google apps for domains will set the signed-by field value to "Y.Z" (which would be your domain name).
As far as I know, this is the only difference. In Gmail, you can even set the default sender-address as your custom domain address so you don't need to set it everytime you reply to/compose new emails. And, unless you think/feel that signed-by: domain.name is cool, you're not really missing anything.
[email protected] on behalf of Rob Aley [[email protected]]
It maybe looks a little unprofessional, but as long as your gmail account isn't something like [email protected] or [email protected], its not too bad.
for now
Why? I have two VPSs with the main and backup SMTP servers and with continuous replications of emails between them and I pay less than half. Not to mention they double as web servers, IRC bouncers, etc.
And no matter what I did to reduce spam, about 10 messages a day always made it through.
I probably never get the same traffic as you do, but to me the best decision I made was enabling catch-all and using different addresses for each service out there.
In my case, spammers only send to three types of addresses:
- Random (jumble of numbers and letters@mydomain): very easy to block with a couple of programming lines.
- Fake but plausible (support@, bob@): just blacklist them once.
- Leaked (from websites and such): same as above, nuke it. Only happened to me once.
All in all, I never had to set up SpamAssassin or deal with dropped emails because of untrusted sources. Blocking by destination is much cleaner.
There are no internet authorities that control mail delivery, either, BTW. Many sites use heuristics to control mail acceptance, however, including third-party whitelists and blacklists. It can suck if you get on a blacklist, but experienced mail administrators only use whitelists and blacklists as one of many metrics regarding mail spamminess. Indicators of good mail like "most of the words in this message are non-spam words" often provide an order of magnitude more ham points than blacklists contribute spam points, so important messages will probably not be dropped even if you're on a blacklist. Of course, many sites have less clever schemes because there is a lot of spam and not a lot of sysadmin time to waste tweaking spam filtering rules.
Mail is hard.
In any case, from a decade of listening to the random things he's had to deal with, I certainly have to agree with your final comment.
I think there are probably some MTAs that will STARTTLS for normal SMTP connections, but again, I've never heard of anyone using SSL/TLS as a spam-filtering criterion. (I might look through my old logs to see if anyone other than me ever issued STARTTLS on my mail server. But I'm guessing the number was near zero.)
Last year I moved and my IP address changed (ISP didn't). I expected to lose the "reputation" the previous one had built up. But I did not have any problems whatsoever. I do hear rumors like yours every now and again but I have a hard time believing them.
I think that large email providers, the likes of Gmail/Hotmail, actually look at the email addresses / domains / servers that their clients send email to. Then they assign trust to those tokens. If you're a large provider, you can do many things with the data you get from your own customer's behaviour. How about looking at accounts that have been in use for some time, seen regular web interface action, and send email to other @hotmail/gmail accounts that actually get read and not flagged spam? If those accounts send mail to my mailserver, then my mail server / domain must have something good going for it. Well that's what I would do if I were running a huge setup anyway...
As for incoming spam: I'm using various postfix tricks, greylisting, and dspam. I have no problems. I should write a howto ;-)
This does not include incoming bandwidth, bandwidth used by your IMAP or webmail client, or DNS lookups that you'll do for every message received. (Also, spam filtering is CPU-intensive, so if you get a lot of email, a Micro instance may not be big enough.)
This doesn't include a secondary MX, either. (I like the DynDNS secondary MX service, personally, which is ~$30 a year IIRC.)
Just tell me where to sign up (next year when AWS free tier expires).
Sleep on it I guess, see how it looks in the morning.
I use Google Apps to host 4 email addresses for my personal domain.
Personal email Online shopping email Forums/Programming email Facebook-only email (so people can't search for me)
I use it for me. I wouldn't pay $20/month for such a service, and Google is smart for not taking free away from existing customers.
(And, when I was first doing this, someone trying to hire me for a job couldn't email me, because their hosting provider was once friendly to spammers and my aggressive blacklisting rejected their TCP connections. Oops.)
Running an email server is hard and very few people regret paying an expert to do it for them.
(As many HN readers know, I work for Google. But I'm not telling you that you should or should not use Google's product here, only that running an email server is not trivial.)