Office 365 and Google Apps both throttle outbound email

Thinking about moving your mail to the cloud? Make sure you understand Microsoft’s and Google’s limitations on the number of emails you can send every day

In a complicated bit of tomfoolery, both Office 365 and Google Apps limit the number of email messages you can send in a day. If you’re thinking about moving to either Office 365 or Google Apps, you should understand how your mail can be blocked in the cloud — and think about paying more for a service that doesn’t block so readily.

There’s been some gnashing of teeth in the Office 365 community about Microsoft Exchange’s forced account shut-down, but many people don’t realize that Google Apps packs similar limitations.

Here’s how it works. Both Office 365 and Google Apps keep track of each individual email account and count how many messages go out from each account.

Office 365 customers that pay for the less-expensive “Small Business and Professionals” or “P” plan are limited to sending 500 emails every 24 hours. They’re also limited to sending 30 messages per minute from each account.

Office 365 customers that shell out for the “Enterprise” or “E” plans get throttled at 1,500 emails every 24 hours. While the official description of the recipient limits defy parsing, it appears as if “E” customers are also limited to 30 emails per minute for each account. (Take a look at Microsoft’s Exchange Server Message and Recipient Limits and see if you can make heads from tails out of it.)

The details are a bit strange. If you send a message to, say, five addresses (either “To” or “CC” or “BCC”), that counts as five sent messages. Easy. If you send a message to a distribution group on the server’s GAL (Global Address List/shared address book), that counts as one outbound message, no matter how many addresses are in the GAL. But if you send a message to a distribution list in your Contacts folder, each individual address gets counted.

For example, say you pay for an Office 365 “P” account, and have a Contacts distribution list consisting of 50 people in your department. Every time you put that distribution list in the To: or CC: or BCC: field of a message, you bump up your 24-hour count by 50 messages. It’s easy to envision a situation where you would hit the 500 message limit. Once a particular email address hits the limit, it’s prevented from sending further messages until the 24-hour running total falls below 500.

If you have an “E” account, the same rules apply, but your 24-hour running total can’t go above 1,500 messages.

Microsoft says “These limits are applied to messages, senders, or recipients to combat spam”. As far as I can tell, it only makes spamming a little more time-consuming and/or expensive — and there’s a very real possibility that a regular Office 365 “P” customer could hit the limit and not have a clue why their mail has been blocked.

(Microsoft’s documentation talks about restricting the number of “message recipients” you can have in a 24-hour period. If you read the details, the restriction doesn’t apply to recipients at all. They’re talking about the number of emails that go out.)

Google’s details are completely different, of course. Rules for the free Google Apps state, “Google will temporarily disable your account if you send messages to more than 500 recipients or if you send a large number of undeliverable messages.” It isn’t clear if the messages to 500 recipients have to go out in the course of a minute, an hour, a day, or a week, although Google assures that if you run afoul of the rule, your account will be reinstated within 24 hours. Google also says that if you use a POP or IMAP client (such as Outlook or Apple Mail) to send your mail, you’re limited to 100 recipients for each message.

If you pay for Google Apps, different rules apply. You can send up to 10,000 messages per day (count the number of entries in the To:, CC:, and BCC: fields), but only 3,000 of those can go outside your primary domain. In addition, you’re limited to sending messages to at most 3,000 unique addresses every day, and up to 2,000 of those can be outside your primary domain.

Clearly, dollar for dollar, Google’s more liberal in its outbound email throttling policies. What isn’t clear is why both Microsoft and Google have two different levels of protection: Pay more money and you can send more spam. It also isn’t clear why going over 500 (or 1,500 or 3,000) messages per day makes you a spammer, drawing the automated ire of the throttling algorithms.

Yet another one of those things Microsoft and Google didn’t warn you about, eh?

Microsoft cloaks AutoRuns in a little bit of mystery

Microsoft’s Sysinternals monitoring suite has just been updated, with a new version of AutoRuns that every Windows user needs. There’s something of a mystery surrounding the update, but it would behoove you to download it now.

Sysinternals, as you probably know, was the brainchild of Windows internals legend (and action adventure novelist) Mark Russinovich and Winternals Software co-founder Bryce Cogswell. Microsoft bought the company and hired Russinovich in 1996, and has distributed free updates to Sysinternals ever since. The Sysinternals package includes several monitoring tools — including Process Monitor, which watches access to the Registry and files — but AutoRuns has always been the most popular.

AutoRuns scans a PC and lists every single program that’s rigged to start automatically. On most computers, the list’s lengthy — and sobering. Of course AutoRuns detects programs that start on boot up and logon — looking at all the obvious and not-at-all-obvious Registry keys and folder locations — but it also tells you about automatically starting drivers, Internet Explorer add-ons and browser helper objects, Explorer shell extensions … and many things you probably never imagined.

AutoRuns not only lists the auto-running programs, it lets you turn individual programs off. There are many minor features, including the ability to filter out Microsoft-signed programs, a quick way to jump to folders holding auto-starting programs, and a command-line version that lets you display file hashes.

AutoRuns doesn’t require installation. It’s a program that runs and collects its information, displays it (with a rather rudimentary user interface), lets you wrangle with your system, then fades away.

Here’s the mystery.

Every time Microsoft updates AutoRuns, it omits a little piece of important information: It doesn’t say what’s been added to the auto-detection scan. This time, we’re informed that AutoRuns 11.1 “adds several new autostart locations” to its scanning regimen, but there isn’t a breath about what locations those might be.

I’m convinced that Russinovich and Microsoft intentionally refrain from disclosing where they’re poking to find auto-running applications because they don’t want to make it easier for system crackers to squirrel away their unwanted programs.

Undaunted, I put AutoRuns 11.0 next to AutoRuns 11.1 and checked. They both run side-by-side, no problem. On my production systems, and a couple of lesser machines — even one PC running Windows 8 Developer Preview — I found exactly no difference in the reported autorunning programs. So I’ll have to take Microsoft’s word for it that there are newly discovered nasty apps out there that haven’t yet invaded my PCs.

Windows Secrets put cleanup apps to the test

I really believe this is one of the best articles ever to appear in Windows Secrets Newsletter. (And I didn’t write it!)

Fred Langa conducted an experiment, comparing three of the leading Registry/system cleanup apps. Although it wasn’t a monstrous test, the results are replicable, reasonably indicative — and not at all surprising. At least, not to me.

If you’ve ever thought of shelling out money for a system tuneup package – in fact, if you’ve ever thought of running a free tuneup – read Fred’s results. If you know anybody who might consider, just for a second, that they should waste spend money on a Windows tuneup program, send them this link.

Windows Secrets Newsletter Top Story.

Will Apple’s “Slide to Unlock” patent stomp on Android or Windows 8?

Short answer: No.

But the long answer is quite interesting, I think.

InfoWorld Tech Watch.

The death of the Start menu

Microsoft’s defense goes into high gear.

Please, Microsoft, don’t take away the Start menu in Windows 8. You know better.

InfoWorld Tech Watch.

Mobile Windows market share stabilizes

… but is it too late to save the patient?

InfoWorld Tech Watch.

Getting the most from Windows Search – Part 2

If you’ve ever run a search in Windows 7, you should see the whole story.

Including the undocumented parts.

Windows Secrets Newsletter’s new Top Story.

The rise and fall of the Windows Desktop Gadget

Microsoft just gave ‘em the axe.

InfoWorld Tech Watch.