But Google doesn't have an FBL (I.e. ARF based reporting) so that isn't possible.

This actually doesn't work like that. At the same presentation they announced this new feature at they said that the spam filtering was very specific to individuals. Using seed addresses isn't very effective for determining delivery.

Their postmaster team, historically, has been very difficult to contact for this kind of information. That appears to be changing given some further, as yet unannounced, changes they are making.

Why do you assume that because its on GitHub that its public? Many companies and individuals have private repos on GitHub.

The OSS movement shouldn't care about what other people think. Software is created and put out in the wild in the hope that others will benefit. Whether a particular class of people use it or not is typically irrelevant (unless they are the target of the software). The only people who are likely to greatly care about this are the people trying to make money off of open source software.

If this were another era.... This book did wonders for me -- http://www.commodore.ca/manuals/c64_programmers_reference/c64-programmers_reference.htm

I guess everyone is missing the part that we haven't actually confirmed the composition of the atmosphere and whether it corresponds to one of their simulated atmospheres to such a degree that their results are applicable *or* that the simulated atmosphere is actually usable by life of any kind.

For all we know, it has an atmosphere made entirely of nitrogen or one that doesn't have sufficient carbon dioxide to sustain a greenhouse effect and has substantially frozen out.

This is purely hype of a simulation based on mostly made up stuff to determine what compositions *could* work to sustain a temperature-habitable environment. Mars is nearly temperature-habitable but no one would ever claim that it is 'habitable'. The only really interesting bit is the ability to, in the future, spectroscopically analyze the atmosphere and plug the values into their simulation to get results based in reality.

1) If you're being blocked then you're hosting your mail server on IP space that Comcast and Verizon have designated as dynamic. Don't do that. Either get them to properly classify your block as non-dynamic _or_ make sure that you're really on non-dynamic space.

2) Ensure that you have proper reverse DNS configured for your server. If you have business class service, they should be completely understanding of your need to change PTR names for the IP's you use.

3) If you really are running on dynamic IP space and have no way around that (that's not painful to you), you always have the option of smarthosting your mail through the Comcast or Verizon mail servers. That's what they're there for.

DCC does something very similar, and has been in use for years.

SysRQ can be extremely useful in figuring out why a machine has locked up or become unresponsive...

http://www.kernel.org/doc/Documentation/sysrq.txt

'Only two Gmail accounts appear to have been accessed, and that activity was limited to account information (such as the date the account was created) and subject line, rather than the content of emails themselves,' said David Drummond in that blog update. That does sound like it perhaps could be a result of insecure HTTP traffic being intercepted in transit between the users and Gmail's servers.

No, if that were the case they would have been able to see *everything* the user received as part of the data response, including message bodies.

That's a pretty long-winded. Why didn't you just say "...theories remain: either the gas is created as a by-product of reactions between volcanic rock and water". Oh, right, the clip and story already did. :P

Upvotes for --
    Rendezvous With Rama
    War of the Worlds
    The Cold Equations
    I, Robot - Asimov long story
    NightFall - Asimov short story
    Lord of the Rings/The Hobbit - I still have my 1970's paperbacks.

I remember this one clearly as well. I'll never stow-away aboard a spaceship as long as I live!