I love Gmail for one thing: it launders spam out of mail going to my searls.com address. I have things set up so Gmail picks it up from my server, and I pick it up from Gmail. Last I checked, there were over 22,000 spams in Gmail’s spam box. And the last I went through ten pages (50 each) of those, there were no false finds.
But lately I haven’t been getting mail to Searls.com. Didn’t know what it was, but my wife just figured it out and provided helpful tech support. I needed to go into Settings in my Gmail account, then to Accounts, then down to Get mail from other accounts, and see when my mail was last picked up. Turns out it was 9 February. Here’s what the Fetch History said…
Now it says this:
So, some questions that maybe some of ya’ll can answer…
- Why did Gmail choke on the “timed out” message from my mail server, and not go back again?
- Why was it checking my server every several minutes before, and only every hour or so now?
- Can I make it speed up somehow? If so, where are those controls?
Here’s hoping my own conundrum may be helpful to others as well. No idea.
It is one helluva spam filter, I gotta say.
Doc, I have a question on which you might have an opinion. I also use gmail to get my ISP (Cox) mail. But I do it by forwarding all mail from Cox to gmail, rather than by pop3 fetch.
Lately I’ve been getting more spam to Cox, and some of it is getting in the gmail Inbox.
Do you think gmail’s spam filter works better if gmail fetches the mail, rather than by forwarding?
> having me think twice (and more) about dependencies on giant providers,
Actually, I’m considering moving the email for netgate.com to Google’s hosted stuff, rather than continuing to operate a hosted server just for email.
Amazon’s S3 outage is worrying though.
i think google’s pipes are getting full…. lots of little signs, and of course some of it could be the www
Maybe its because google’s share prices are dropping so they have to cut costs somewhere…..
Pingback from GNC-2008-02-15 #348 | Geek News Central on April 16, 2009 at 9:47 pm
Comments are now closed.