Slashdot Mirror


Some Anti-Spam Vendors Blocking and Slowing Gmail

fiorenza writes "Google's Gmail (and corporate mail) are being throttled and sometimes blocked by some anti-spam services, including MessageLabs and Antigen. Ars Technica reports that the blocking is a result of the Google CAPTCHA crack, which has allowed a deluge of spam from Gmail's clusters. Most users won't get blocked mail, but Ars confirmed with MessageLabs that Gmail delivery delays are to be expected."

163 comments

  1. Re:It's ok though... by New_Age_Reform_Act · · Score: 3, Insightful

    With the current state of the world economy, no one will be willing to pay for something that they get used for free.

    --
    "The New Age. The New Beginning."
  2. Re:It's ok though... by TheMeuge · · Score: 5, Insightful

    Umm... I have used a number of commercial email systems (in-house for major companies and institutions) and none of them could provide a service that was even remotely close to what Gmail does for free.

  3. Gmail and others blocking legit domains, so hey by gnuman99 · · Score: 3, Insightful

    There were number of times where my emails are silently deleted from Hotmail or even gmail, so hey. Welcome to the world of screwed up SMTP protocol. And all thanks to spammers.

    Today email is less reliable message delivery medium than regular mail which is quite sad considering all transactions in SMTP were considered to be, well, transactions. An acceptance of email by destination means it is delivered, not going to /dev/null. Want to filter spam? Reply with 5xx codes instead - not accept with 2xx and then bin it (unless mailing list headers found in mail, there you can drop spam)

    1. Re:Gmail and others blocking legit domains, so hey by imemyself · · Score: 4, Interesting

      I definitely agree with you, if a mail server accepts my mail with a 200 code, then the mail *should* be delivered. Even if its put in someone's spam folder, the message should get there. That's one of my pet peeves. That being said, from my experiences when setting up my mail server, Gmail was probably one of the best about not blocking legit mail (I've had an SPF record since the beginning though). I had lots of problems with Hotmail, and I think my mail was usually marked as spam by Yahoo until I enabled DKIM signing. With SPF records and DKIM, I don't think I have any major problems (though my mail server handles a pitifully small amount of mail, so its not like we're going to get marked as a bulk sender).

      --
      Every time you post an article on Slashdot, I kill a server. Think of the servers!
    2. Re:Gmail and others blocking legit domains, so hey by gnuman99 · · Score: 3, Interesting

      Just to add something, the problem with 5xx replies is filter is *before* queue so some mail may be delayed and servers need to be contacted a few times before they get a delivery slot. For example, say gmail can filter 1 million messages at a time. That means 1 million open connections. So, if you are connection 1,000,040 you get 4xx response - temporary failure due to no available resources. So try again later.

      This is not a problem, really. You can wait a few days until you can deliver the message as long as it is *delivered* eventually. /dev/nulling spam while accepting it with 2xx code is like burning unopened envelope at post office because it was typed instead of handwritten indicating possible spam.

      Pre-queue filter with only 1 unique IP connection at a time to mail server. Problem solved.

      Huge email servers get reasonably constant and predictable amount of mail per day and per hour and even per minute. They can plan pre-queue filtering with some margin for any spikes. And if there is a huge bomb and your mail doesn't get there for 7 days and your server gives up, hey, at least you get a "Could not deliver the message because destination was not available". Much better than "err, never got any mail from you" from the destination party.

    3. Re:Gmail and others blocking legit domains, so hey by moderatorrater · · Score: 1

      Today email is less reliable message delivery medium than regular mail Depends on where you receive your regular mail and how you do email. I've has less than 10% of my emails not get where they were going, and if you take out the former company domain that was spamming people, it's 0%. Where I live now, there's a good 30% chance that my mail won't get to me.
    4. Re:Gmail and others blocking legit domains, so hey by BagOBones · · Score: 5, Insightful

      Really? Do you have any idea the resources this would take for some organizations?

      Based on stats from my frontend SPAM filters 80 - 90% of ALL mail receive in a day is SPAM.

      On my reports some individual users are targeted with between 1500 and 2000 SPAM messages a day. There storage quotas would probably be exceeded over night from SPAM alone.

      I would need to increase my storage capacity immensely if I allowed every spam message to get to the users Junk folder. Not to mention the extra bandwidth of allowing all those mail delivery connections to complete OR to send NDRs to forged senders that are going to bounce back at my system and cause even more load.

      --
      EA David Gardner -"... but the consumers have proven that actually what they want is fun."
    5. Re:Gmail and others blocking legit domains, so hey by freedumb2000 · · Score: 4, Insightful

      True, and it is really not necessary to pass all mail. In my experience weeding out mal-configured mail servers (i use postfix rules and greylisting) takes care of over 90% of spam. The rest gets caught by an RBL or tagged by spamassassin and sent to the users spam folder. Things may change any day though depending on future strtegies by spam senders, but at the moment it works quite nicely.

    6. Re:Gmail and others blocking legit domains, so hey by Anonymous Coward · · Score: 0

      OT: Mass-mailings is spelled 'spam' in lowercase, not uppercase. It is not an abbreviation, nor is it a trademarked canned food product, but a regular noun.

    7. Re:Gmail and others blocking legit domains, so hey by imemyself · · Score: 1

      OK, then use DNS/IP blacklists have your mail server's not accept the mail and report a 500-something error to the SMTP client that's trying to send it. That would block a substantial amount of the spam. Then the rest could be put in the user's spam folders based on content filtering, which can be very unreliable. I just noticed a legitimate message that spam assassin marked as an 8.1 (I've tuned it to put it in my spam folder at 3.3). If need be, the spam folder could be deleted every week. There's no need to send NDR's if you didn't accept the mail in the first place, and the blacklists would be applied before the actual message was sent, so it wouldn't be taking a massive amount of bandwidth. And if you're currently accepting the mail from the client and then just sending it to /dev/null, you're already using more bandwidth by accepting the mail.

      I'm not saying that your mail server should accept and deliver every email it receives, but if your server claims to have accepted it w/ a 200 code, then I think its reasonable to expect that your server is going to attempt to deliver it. The different SMTP error codes are there for a reason.

      My opinion on spam is this: ten pieces of spam getting through is a (relatively) minor annoyance; one legitimate email being sent to /dev/null (especially if the sender has no way of knowing that it was blocked) could be a disaster depending on the situation.

      --
      Every time you post an article on Slashdot, I kill a server. Think of the servers!
    8. Re:Gmail and others blocking legit domains, so hey by kesuki · · Score: 1

      Most of the spam mail is identical, and goes to multiple accounts. if you have millions of users, then you can save space by making messages with identical md5 sums all take only one slot of disk storage space.

      then you run into the problem that not all e-mails produce unique md5 sums (something only an e-mail provider with millions and billions of test cases would ever notice...) and well the occasional bit of mail gets lost because it produced an identical md5 some by chance as a spam message.

    9. Re:Gmail and others blocking legit domains, so hey by Asm-Coder · · Score: 1

      Ok, so if your filters are picking up mail as spam, drop it, and reply with a 500 error. The original sender will receive a message saying "The message could not be delivered." A legitimate contact will ask whoever they were emailing by some other means, and will ask them to create a rule to allow their mail through. A spammer can't because all they have is an email, and won't be bothered to find out 10 million phone numbers and call them all.

      You could even give the recipient a short message saying, "xyz@abc.com sent you a message that was marked as spam. Do you know this person and want to accept messages from them in the future?"

      This isn't rocket science people. It's not hard to fix. The rules were set up with the potential for spammers in mind, and it has a built-in system for handling it. However, people who break the rules make it difficult for the system to work.

    10. Re:Gmail and others blocking legit domains, so hey by Hyppy · · Score: 1

      It's a noun, it's a verb, it's an adjective! It's a floor wax, it's a dessert topping it's... oh, wait...

    11. Re:Gmail and others blocking legit domains, so hey by Spazmania · · Score: 2, Informative

      if a mail server accepts my mail with a 200 code, then the mail *should* be delivered.

      That's not actually the rule. The rule is: if a mail server accepts my mail with a 200 code, then the mail should be delivered *OR* a non-deliverable message should be constructed and returned to the envelope from address.

      When you actually follow that rule, it's quite amazing how many folks get bent out of shape by the undeliverables returned when someone forges their address, even though they haven't bothered to use SPF to protect themselves.

      --
      Moderating "-1, Disagree" is simple censorship. Have the guts to post your opinion.
    12. Re:Gmail and others blocking legit domains, so hey by Spazmania · · Score: 1

      Pre-queue filter with only 1 unique IP connection at a time to mail server. Problem solved.

      Botnet.

      --
      Moderating "-1, Disagree" is simple censorship. Have the guts to post your opinion.
    13. Re:Gmail and others blocking legit domains, so hey by Anonymous Coward · · Score: 0

      I would need to increase my storage capacity immensely if I allowed every spam message to get to the users Junk folder.

      He didn't say that. Read it again:

      if a mail server accepts my mail with a 200 code, then the mail *should* be delivered.

      A 200 response is the mail server's way of saying "yes I accept this mail". To silently discard it after that is simply broken behaviour. If you aren't going to accept the mail, don't tell clients that you have.

      Yes, spam far outnumbers legitimate mail. But a lot of that spam can be rejected while the client is still connected, meaning you don't have to store it all.

    14. Re:Gmail and others blocking legit domains, so hey by Teflon_Jeff · · Score: 1

      I wonder if Comcast has anything to do with this...

      What? They've been behind most of the other internet throttling schemes lately. It's at least plausible to ask.

      "And they would have gotten away with it too, if it hadn't been for those meddling Nerds."

      --
      "Teach a man to build a fire, and he's warm for a day. Set a man on fire and he's warm for the rest of his life."
    15. Re:Gmail and others blocking legit domains, so hey by value_added · · Score: 1

      I had lots of problems with Hotmail, and I think my mail was usually marked as spam by Yahoo until I enabled DKIM signing. With SPF records and DKIM, I don't think I have any major problems ...

      Yahoo allows you to request your server be whitelisted, so you could have saved yourself the trouble with DKIM and friends. I did exactly that, and my DSL-based servers send and receive email all day long without issue.

      As a side note, I use Spamhaus RBLs, so my spam (predominantly from the cable dynamic IP crowd) is essentially zero. By contrast, my Yahoo accounts' bulk folders were always filled with that kind of spam, when it wasn't filled with the legitimate emails from the many mailings lists I subscribe to. Yahoo has since (a month or two ago) made changes, and from what I can see, they no longer accept email from cable users.

      If there's an irony in all this it's that doing things yourself is a bit more work, but infinitely more satisfying. To say nothing of the fact that it probably works better in almost all cases.

      With SPF records and DKIM, I don't think I have any major problems (though my mail server handles a pitifully small amount of mail, so its not like we're going to get marked as a bulk sender).

      You don't have to be a bulk sender to end up tagged with Yahoo's X-YahooFilteredBulk, for example. It can be your very first and only mail.

    16. Re:Gmail and others blocking legit domains, so hey by chromatic · · Score: 1

      You could even give the recipient a short message saying, "xyz@abc.com sent you a message that was marked as spam. Do you know this person and want to accept messages from them in the future?"

      This isn't rocket science people.

      Your idea is better than backscatter, but how do you know xyz@abc.com really sent that message?

    17. Re:Gmail and others blocking legit domains, so hey by Sorthum · · Score: 1

      SPF has severe implementations flaws. Generating an NDR for a message you've accepted, back to a purported sender is contributing to the backscatter problem, and is NOT a viable solution.

    18. Re:Gmail and others blocking legit domains, so hey by rabbit994 · · Score: 1

      Use a decent SMTP Proxy like ASSP or other commercial systems where if it's marked as spam, the sending SMTP Server is given 5xx notice so if it's legit, user gets a bounceback and if it's spambot, it just disappears.

    19. Re:Gmail and others blocking legit domains, so hey by Dan541 · · Score: 1

      You could even give the recipient a short message saying, "xyz@abc.com sent you a message that was marked as spam. Do you know this person and want to accept messages from them in the future?"
        So instead of 10thousand spams I get 10thousand short messages?

      I can't say I'm optomistic
      --
      An SQL query goes to a bar, walks up to a table and asks, "Mind if I join you?"
    20. Re:Gmail and others blocking legit domains, so hey by Anonymous Coward · · Score: 0

      How is prevented DDoS on current architecture?? Firewall problem hosts out. Problem solved. Spoofed packets? Forward to mail server *after* connection was established and confirmed.

    21. Re:Gmail and others blocking legit domains, so hey by gnuman99 · · Score: 4, Informative

      Here's what happens. On SMTP level. << is for what server sends. Rest is what is sent to server.

      << This is your great SMTP server. Yo!
      << 220 super.server.net ESMTP
      HELO srv.my_super_subnet.server.net
      << 250 srv.my_super_subnet.server.net
      MAIL FROM: <handle@server.net>
      << 250 2.1.0 Ok
      RCPT TO: <handle2@server.net>
      << 250 2.1.5 Ok
      DATA
      << End data with <CR><LF>.<CR><LF>
      Subject: Yo
      From: Bob Superman <handle@server.net>
      To: My Buddy <handle2@server.net>

      Want some viagra?

      .
      << 554 5.7.1 Rejected, id=sdsada - SPAM
      QUIT
      << 221 2.0.0 Bye

      See?? No backscatter. The pre-queue filter runs *before* the message is accepted after the . is on the new line indicated end of message.

      What happens now is they get,

      << 250 2.6.0 Ok, id=fsffs FROM blah Ok: queued as foo

      or similar response. Then the filter runs and junks the mail! *That* runs email. I send out email, and it get junked. It gets delivered 50% of the time because some wise guy runs some new magic filter - no spam gets through, and 50% real messages get binned. Then people that should get mail complain that they never get mail (and not just from me).

      If you reply to message from a post queue filter you get backscatter. This is wrong way of doing things. If you reject mail in pre-queue, there is NO backscatter.

      The *only* reason to run after queue and drop silently is for mail marked as Bulk, like mailing list software marks mail as Bulk precedence. Any other mail should be treated as a *no* mail lost priority. Otherwise we may just abandon SMTP altogether.

    22. Re:Gmail and others blocking legit domains, so hey by gnuman99 · · Score: 1

      I think I was replying to someone else in the other reply! :) Sorry about that.

      Regarding validation of email, that is not really the issue here. There are many ways for people to validate if the source is who they say they are. These include SPF or DomainKeys or even GPG/PGP in the message body. Thankfully forgeries are still not really the bulk of the problem.

      The most critical issue is lost mail. I know it is the simplest solution to just drop mail, but it is not an acceptable solution. I believe it is better to shut down SMPT all together than use /dev/null with 2xx codes.

    23. Re:Gmail and others blocking legit domains, so hey by chromatic · · Score: 1

      Thankfully forgeries are still not really the bulk of the problem.

      I'm not so sure. Every piece of spam that makes it through my filters has a forged From address.

    24. Re:Gmail and others blocking legit domains, so hey by Anonymous Coward · · Score: 0

      all thanks to spammers

      I believe it is the anti-spam vendors blocking email, not the spammers.

    25. Re:Gmail and others blocking legit domains, so hey by Anonymous Coward · · Score: 0

      He did not write that servers should accept all incoming email, he wrote all email acknowledged as received should be stored. If I send someone an email, and I do not receive an error message, I want that message to be delivered; otherwise, I want an error message so I know there was a problem.

    26. Re:Gmail and others blocking legit domains, so hey by Antique+Geekmeister · · Score: 1

      For your external mail servers, put SPF and blacklist filtering *first*. Both are very lightweight filtering and easy to use, and tremendously reduce the load of spam that needs to be checked by other means.

      Unfortunately, the Gmail spam recently passes both of those, because it's going through Gmail's legitimate servers with falsely registered, but registered nonetheless accounts. So such IP based filtering does not help. And I'm afraid they need to really rethink their CAPTCHA approach.

    27. Re:Gmail and others blocking legit domains, so hey by Spazmania · · Score: 1

      NOT a viable solution.

      And yet it is the published rule per RFC 2821 section 3.7:

      'If an SMTP server has accepted the task of relaying the mail and later finds that the destination is incorrect or that the mail cannot be delivered for some other reason, then it MUST construct an "undeliverable mail" notification message and send it to the originator of the undeliverable mail (as indicated by the reverse-path).'

      You can't complain about others breaking the rules and then cherry pick which ones you're going to follow. Well, you can I suppose, but it would make you a hypocrite.

      --
      Moderating "-1, Disagree" is simple censorship. Have the guts to post your opinion.
    28. Re:Gmail and others blocking legit domains, so hey by RazzleDazzle · · Score: 1

      Yes, having a spam filter in front of your internal mail system makes perfect sense in most cases today. Having a third party anti-spam service is awesome because they front all of the bandwidth, smtp connections, general administration of the anti-spam system, and they usually have a spam quarantine of some sort for your IT or end users to peruse and search.

      --
      ZERO ZERO ONE ZERO ONE ZERO ONE ONE! Just brushing up for my next big invention: Ethernet over Voice (EoV)
    29. Re:Gmail and others blocking legit domains, so hey by SCHecklerX · · Score: 1

      I think you'd find that if you would reject on obvious stupid things, and implement greylisting, that the amount of stuff you would actually have to process would go waaaaay down.

      My company (and my home server) reject (mail does not get delivered, but an error is sent back to the originating server) on the following:

      - not using a FQDN (i just look for a '.' fer cryin' out loud) in a helo greeting
      - claiming to be my server in a helo greeting
      - using an rfc1918 address in a helo greeting
      - claiming to be a from address from my domains
      - rcpt throttling against dictionary attacks
      - greet pause. If they start spewing before they've been acknowledged, Bzzt!
      - their server is on the spamhaus zen list
      - not in the whitelist for greylisting. Tempfail here, not reject. Spam zombies tend to not queue and try again.

      that gets rid of 80+ % of the crap, with minimal processing (reject before they even start to send the message itself...hooray mimedefang!). The rest then goes through filtering and is flagged if spammy by spamassassin.

    30. Re:Gmail and others blocking legit domains, so hey by Phroggy · · Score: 1

      I would need to increase my storage capacity immensely if I allowed every spam message to get to the users Junk folder. Not to mention the extra bandwidth of allowing all those mail delivery connections to complete OR to send NDRs to forged senders that are going to bounce back at my system and cause even more load. On top of that, if you send all spam to the Junk folder, it completely negates the usefulness of the Junk folder. I send spam with a SpamAssassin score between 5 and 10 to a Quarantine folder, but anything above 10, users never see. I look through my own Quarantine folder every few days, checking for false positives, and every now and then, I find one. This is useful. If everything scored above 10 were in there too, there's no way I'd have time to look at it.

      The system-wide quarantine (with all messages scored above 10) exists only so that if a user complains of a specific message they didn't get, I can verify whether it was incorrectly filtered, but that almost never happens. On my tiny little server with not very many users, the system-wide quarantine only gets about 200 messages a day, but that's definitely more than I'm willing to look at.
      --
      $x='S24;r)>63/* h@<5+oZ)32"5cz';$me='phroggy'x$];
      $x=~y+ -xz+\0-Tx+;print$_^chop$me for split'',$x;
  4. Crack down by Midnight+Thunder · · Score: 2, Insightful

    I am not sure what Google can do to crack down on this abuse, but they really need to. Have there been any improvement to their Captcha system since it was compromised? Are they closing down suspect accounts?

    --
    Jumpstart the tartan drive.
    1. Re:Crack down by Dachannien · · Score: 1

      Maybe they could try filtering their outgoing messages? Just a thought.

    2. Re:Crack down by Thelasko · · Score: 5, Interesting

      I think the safest thing they can do right now is return to their invitation only registration in an effort to close the breach. Then they have to start deleting spam accounts quickly before the spammers adapt to inviting themselves. If they are lucky they will be able to delete spam accounts faster than they multiply.

      --
      One of our competitors trademarked the term "hypothesis". From now on, we will call them "boneheaded ideas".
    3. Re:Crack down by Normal+Dan · · Score: 1

      Then they have to start deleting spam accounts quickly before the spammers adapt to inviting themselves.

      One of the great things about the invitation only registration is google can delete an entire block of accounts and follow the chain up to the offender.

      The down side is, people who live alone with no friends on or off line will be unable to get a gmail account. At first glance this may seem fine since they would have no one to email anyway, however, some porn sites require email registration.
      --
      A unique way to learn a language: http://languageloom.com
    4. Re:Crack down by Anonymous Coward · · Score: 0

      This is actually an excellent idea. I remember when Gmail had invitations, but everyone and their dog had them coming out of their ears. At the time, it seemed pointless, but it all makes sense if you think about it. Invitations add traceability. If some spammers can be identified, then the person who gave a given spammer their invite could be silently scored. If multiple spammers are invited by one account, their score increases. Eventually, people with high scores have their invites taken away and/or lose privileges, or are kicked off, etc.

      Ultimately, if someone can crack a relatively complex image captcha, then someone will be able to defeat any similar system that is invented, eventually. It is interesting to note that some of those bots that are able to hit ~30% accuracy are at least as accurate as humans. :-)

    5. Re:Crack down by Anonymous Coward · · Score: 0

      Evidence seems to suggest that the CAPTCHA wasn't cracked.

      Instead, it looks like someone with plenty of financial resources set up a system where a robot grabs a Google CAPTCHA and sends it to the 3rd world, in real time. People there are paid a fee for successfully typing in the values of CAPTCHA images.

      It's looking like a real paper trail is necessary.

    6. Re:Crack down by Iamthecheese · · Score: 1

      I.Q tests as CAPTCHAs. Seriously. The argument against this is discrimination against the disabled, but that is obviously the first bump in the mountain that is strong AI. As AI gets better, the overlap between the abilities of computers and the severly disabled will grow. Next will be the moderately disabled, then AIs will equal the capacities of your average joe. Ther eis no solution to this: If its ability your testing, the efinition of "human" will continue to blur.

      There are a few things that a person can do much better than a robot, and since captchas no longer represent significant-enough strengths for people, we should change to things that do.

      Things that people do better than people:
      -Generalize. Why is a finger like a can of soup?
      Socialize. Tommy hit Billy. Will that make Tommy love Billy?
      -Think about the future. Would it be good to give everyone in the world their own nuclear power plant?
      Dream. Tommy wears a cowboy hat. What does Tommy want to be when he grows up?

      --
      If video games influenced behavior the Pac Man generation would be eating pills and running away from their problems.
    7. Re:Crack down by Phroggy · · Score: 1

      Generalize. Why is a finger like a can of soup? I can't immediately think of a good answer to that question. Certainly there isn't a single "correct" answer coming to mind. That doesn't mean I'm not human.

      Socialize. Tommy hit Billy. Will that make Tommy love Billy?
      Think about the future. Would it be good to give everyone in the world their own nuclear power plant?
      Dream. Tommy wears a cowboy hat. What does Tommy want to be when he grows up? You've definitely got the right idea. Unfortunately, while computers are terrible at answering these kinds of questions, computers are also terrible at asking these kinds of questions. Let's take the dream example - you'd have to give the computer a list of behaviors (wearing a cowboy hat) and the corresponding dreams (wanting to be a cowboy, or perhaps wanting to be a country music singer). The computer picks something from the list, forms it into a sentence, and checks to see if the answer matches what's on the list. Simple enough.

      However, your list is of a finite size. You had to come up with the whole list by yourself, because computers are terrible at these kinds of questions. That means, it won't take a spammer long to reverse-engineer your list, and program a computer to be able to respond to your questions. Sure it will take awhile, but eventually you'll run out of questions that the spammer's computer hasn't been taught the answers to.

      A much better idea is to combine multiple elements in infinite possible combinations, and ask questions about the way these elements are combined. Here's an example:

      Tommy wears a cowboy hat, Suzy is tall, ants crawl around the picnic basket, the sun is shining brightly, Billy likes pastrami, and Jane loves bugs.
      1) What does the vegetarian boy want to be when he grows up?
      2) What is the short girl looking at?


      This sort of thing shouldn't be difficult for a computer to generate. We still have to build lists of data (e.g. vegetarians don't like pastrami), interests (ants crawling around a picnic basket would attract the interest of someone who loves bugs), dreams (someone who wants to be a cowboy would wear a cowboy hat), etc., but now we have a ton of possible combinations, irrelevant data thrown in (the sun is shining), and no direct link between the question and the pieces of data needed to answer the question (it's not obvious why pastrami is important).
      --
      $x='S24;r)>63/* h@<5+oZ)32"5cz';$me='phroggy'x$];
      $x=~y+ -xz+\0-Tx+;print$_^chop$me for split'',$x;
  5. Re:It's ok though... by anotherone · · Score: 3, Funny

    Did you seriously just post an unsolicited commercial message in a thread about how unsolicited commercial messages are watering down legitimate communication mediums?

    --
    Username taken, please choose another one.
  6. Re:It's ok though... by Anonymous Coward · · Score: 0

    Oh, I see, if by "higher-quality email service" you mean a service that won't let most legitimate mail get through, while blocking a minuscule amount of spam, I guess you're right.

  7. Google wins by mfh · · Score: 5, Insightful

    The missing part of this story really is that Google`s Gmail client has very effective anti-spam filtering. I can see why companies who earn their keep protecting typical client-side email systems, would want to make Gmail obsolete or ineffective. Spammers might use Gmail as a tool to spam, but with good filtering it really doesn`t cost that much compared to the loss of time spent weeding out ham from spam.

    --
    The dangers of knowledge trigger emotional distress in human beings.
  8. Re:It's ok though... by Stochastism · · Score: 3, Insightful

    This is to be expected from free mail providers. If you want quality service, including people that police spammers and watch their systems, then you obviously pay for the higher-quality email service. I suspect Yahoo, Hotmail and Gmail between them have more "police" than most other commercial providers put together.

    I don't necessarily believe these free services are inherently low quality. What is true is that they are a massive target for spammers. Spammers get something from these services they don't get by sending mail directly by SMTP: DKIM and SPF authentication from (relatively) high reputation IPs.

    Yes, they all go around blocking each other sometimes, but this is not new. I vaguely remember complaints about Gmail being blocked by Yahoo (or was it the other way around) a couple of years ago.
  9. Re:It's ok though... by teknopurge · · Score: 4, Funny

    Then you haven't used Exchange, etc.

    Exchange trumps Gmail easily. No Contest.

    Regards,

  10. Re:It's ok though... by teknopurge · · Score: 1, Funny

    Commercial?! Psft - it was a viral-green-eco-friendly-lovein message, man!

  11. Re:It's ok though... by teknopurge · · Score: 2, Insightful

    Q: How do you keep the majority of the spammers away?

    A: Attach a price-tag.

    Regards,

  12. Re:It's ok though... by flyingfsck · · Score: 2, Interesting

    and you certainly haven't used Citadel, which trumps Exchange by a wide margin.

    --
    Excuse me, but please get off my Pennisetum Clandestinum, eh!
  13. Re:It's ok though... by kris.montpetit · · Score: 3, Informative

    This is to be expected from free mail providers. If you want quality service, including people that police spammers and watch their systems, then you obviously pay for the higher-quality email service. Regards,

    What can i say, Google gives me 7 gigs of space for my account, the most popular local ISP gives 100 megs, and this crappy service. Actually gmail is the only email client i've dealt with recently that isn't hell and a half to support. the anti spam service has been near perfect until now as well on all 3 of my accounts. :D

    And saying thats its a budget service is just plain uneducated. its funded (quite generously, I might add) by the discreet, context sensitive ads you will find on the side of the page, as opposed to part of your internet subscription.

  14. Re:It's ok though... by CowboyNealOption · · Score: 5, Funny

    I have yet to see Exchange work well in any environment over a few dozen people; certainly not without investing large amounts of money on duplicate servers and hardware. Included is my favourite Exchange analogy: If the same method that exchange/outlook uses to store email were used in the real world as a paper filing system: Every document is translated into Greek, and the original is burned. Then they are all glued together into one solid block and stuffed into a magic box with a tiny slot, through which you can talk to a little gnome who somehow gets each message for you as needed. Sometimes the gnome gets confused and it takes hours (sometimes days) for him to sort things out; meanwhile he can't find your documents until he is totally finished becoming unconfused again. As an added bonus the gnome costs several thousand dollars and when he dies every few years you need to buy a new gnome. Oh and if the first box gets (arbitrarily) full you have to buy another special gnomebox, which of course costs $$$

  15. Re:It's ok though... by Anonymous Coward · · Score: 0

    Aaargh. I know this is petty and small but stop signing everything with regards. It shouldn't but it is really annoying me.

  16. Re:It's ok though... by Ucklak · · Score: 2, Funny

    and you certainly haven't used Lotus Notes, which trumps Citadel and Exchange by a wider margin.

    --
    if you steal from one source, that is plagiarism, if you steal from many, well, that's just research.
  17. They will, eventually, be cracked again. by khasim · · Score: 2, Interesting

    What they need to do is have a process for detecting when an account is spamming.

    Now, you and I would just say "when an account is sending 10,000 messages a day" and that would be correct for about 99.9% of the cases.

    I'd also recommend Google "seeding" the spammers databases with "spamtraps" (not tied to Gmail or Google in any way). If an account sends email to a spamtrap, that account is frozen.

    And so forth.

    1. Re:They will, eventually, be cracked again. by timeOday · · Score: 5, Insightful

      What they need to do is have a process for detecting when an account is spamming. Now, you and I would just say "when an account is sending 10,000 messages a day" and that would be correct for about 99.9% of the cases.
      No, that's the whole point of defeating captcha. Instead of sending 10,000 messages from 1 account, send 10 messages each from 1000 accounts.
    2. Re:They will, eventually, be cracked again. by timeOday · · Score: 1

      PS, that also defeats the spam trap addresses. If you're only sending a few (or 1) spam from each account, killing an account because it sent email to a fake user doesn't help much.

    3. Re:They will, eventually, be cracked again. by kesuki · · Score: 3, Interesting

      welcome to spamtrap@donotreply.com (just kidding, but donotreply.com gets a lot of interesting e-mail, I just wondered what they'd do if they started getting 'spamtrap' addressed mail)

      well, making special spamtrap e-mail addresses and putting them in the clear on usenet, message boards, or even on social networking sites owned by google, and making sure the content is boring drivel no one would e-mail that person about. well, i mean how could you decide how to make boring drivel that would still put their address out on sites? 'first post' messages?

      wouldn't someone notice that google got 'first post' every time on 123 consecutive front page articles? wouldn't they? though and e-mail them a congratulation and get spam busted?

      i mean i know i can post boring irrelevant information, but i can't guarantee that if an e-mail is tied to that identity that someone won't e-mail me....

      so spam traps are harder to implement than one would think, unless they're in 'hidden' code. EG: you go to a website, the e-mail is in the html, but never shows on the page... and if you do that, then they might make a scanner that nullifies those addresses... once the realize what's happening.

    4. Re:They will, eventually, be cracked again. by rtb61 · · Score: 1
      The problem will eventually resolve itself. With the switch to IPv6, dirt cheap appliance servers and free open source software, everyone will be running their own email server. The net result of that is, the default will be to block all free web mail messages and only allow known ones in.

      Until then ISP's are going to have real problems with free web mail services, for the end user of course the solution is simply block them, and wait for an alternate form of communication to let you know an address to allow in.

      --
      Chaos - everything, everywhere, everywhen
    5. Re:They will, eventually, be cracked again. by textstring · · Score: 1

      they obviously know what spam looks like judging by my mail box and they could probably get away with running their spam filter on outgoing mail, but then it could become a privacy and usability issue. personally, i think keeping their domain name as far away from SPAM as possible is the best move google could make.
      your spamtrap idea is great, if i could stand to read another letter of it i'd be more interested

    6. Re:They will, eventually, be cracked again. by An+anonymous+Frank · · Score: 1

      What they need to do is have a process for detecting when an account is spamming. They do.

      When I tried using Gmail loader to transfer old mail from Apple Mail and Lotus Domino to Gmail, it took some trial and error to get it right; I quickly found myself blocked for a couple of hours for "sending too many undeliverable messages with external recipients", and this, for merely several hundred messages at a time.
    7. Re:They will, eventually, be cracked again. by Phroggy · · Score: 1

      The problem will eventually resolve itself. With the switch to IPv6, dirt cheap appliance servers and free open source software, everyone will be running their own email server. The net result of that is, the default will be to block all free web mail messages and only allow known ones in.

      Until then ISP's are going to have real problems with free web mail services, for the end user of course the solution is simply block them, and wait for an alternate form of communication to let you know an address to allow in.

      You're just talking about whitelisting, which makes e-mail nearly useless because people can't get on your whitelist until they've gotten on your whitelist so they can let you know they want to send you mail. IPv6 is completely irrelevant to this discussion; most people don't want to run their own mail server and I sure as hell don't want them to try. It takes a lot of work for me to maintain my own mail server, and I know what I'm doing; normal users shouldn't have to deal with that responsibility.

      No, the solution to the problem of free web mail services is not to make everyone run their own mail server. If you follow the problem back to its logical source, it's not even free web mail services that are the problem here - they're only a problem because it's easy for spammers to create thousands of accounts, so shutting down a single account has no measurable effect. The only reason they're able to sign up for multiple accounts without the web mail service figuring out that they're all for one spammer is that the spammer is using a botnet to distribute the requests, so they're all coming from unique IPs and look like individual people instead of a single spammer. Get rid of the botnets, and the web mail problem will sort itself out.

      So how do we get rid of the botnets? Well, I thought enabling the software firewall by default in Windows XP Service Pack 2 would help; obviously it didn't. Users can be tricked into running just about anything, and once that happens, any security software on their PC can be assumed to have been compromised.

      I think ISPs are going to have to step up to the plate here and become a little less customer-friendly, for the sake of the rest of the Internet. That means ISPs are going to have to start shutting off accounts when they find out their customers are part of a botnet. Block all outgoing traffic, and redirect port 80 to a site that explains what's going on and offers download links for free software to clean up the problem (it can be commercial software that the ISP pays for, but it has to be "free" to the customer).

      That's going to piss people off, and cause cancellations. People don't like being accused of being spammers. People don't like being accused of being dumb enough to let their PC become compromised. Tough. It's the only way to clean up the Internet.
      --
      $x='S24;r)>63/* h@<5+oZ)32"5cz';$me='phroggy'x$];
      $x=~y+ -xz+\0-Tx+;print$_^chop$me for split'',$x;
  18. Re:It's ok though... by teknopurge · · Score: 2, Interesting

    I'm forced to use Notes every day.

    Exchange is -years- ahead of notes.

  19. We use messagelabs by DaveOne · · Score: 2, Interesting

    Our company uses Messagelabs. Just tried a quick message from my Gmail account. Almost immediately received the message. No delay for my account, at any rate.

    1. Re:We use messagelabs by call-me-kenneth · · Score: 1

      Same here - mail between my Gmail account and my work account, which gets Messagelabs spam/malware filtering, works fine in both directions. Sounds like a badly-sourced story to me...

    2. Re:We use messagelabs by freedumb2000 · · Score: 1

      Maybe they really meant greylisting when they said delay. That would explain why your mail went through without wait.

  20. Re:It's ok though... by cleatsupkeep · · Score: 5, Funny

    And YOU definitely haven't used Gmail, which trumps Lotus Notes by a large margin... Oh, wait...

  21. Re:It's ok though... by imemyself · · Score: 4, Insightful

    Wow, if you're having that many problems with Exchange, your sysadmins need to do a better job. Exchange is generally a pretty good mail/groupware server for corporate environments. If you throw an Exchange server together in five minutes, then yeah, you might have some problems, but as long as you think it through beforehand (and like with anything computer related, have a good backup strategy) it should work pretty well unless you have some really unusual requirements.

    --
    Every time you post an article on Slashdot, I kill a server. Think of the servers!
  22. Re:It's ok though... by toadlife · · Score: 1

    I have yet to see Exchange work well in any environment over a few dozen people; certainly not without investing large amounts of money on duplicate servers and hardware. I have.
    --
    I don't always use unix-like operating systems; but when I do, I prefer FreeBSD.
  23. Re:It's ok though... by kesuki · · Score: 2, Interesting

    I remember reading a post about one poor hapless admin, who had come across an exchange server that was eating 10 GB of HD space a day, couldn't figure out what was causing the massive use of disk space, his company was in the middle of their most critical time of year, and he had 3 days left before the server crashed again and he'd be out of a job if he lost 12 of so days (since the last backup of that servers files) of e-mail.. it was an old post, and the people who had ideas were ideas the admin had already tried.

    I'm fairly sure that the shit hit the fan and he took the blame, and i can't imagine a single reason why anything other than poorly designed malware, or a really rare hard to reproduce bug could be eating 10 GB of disc space a day...

    If it had been recent i would have suggested he find a tool to let him add an external raid array for the OS to keep eating the 10GB a day until he had the problem locked down... but, it was too late for my advice...

  24. Re:It's ok though... by LoadWB · · Score: 1

    That *is* funny. Though I have never had this experience with Exchange 2003 at any site I've managed over the past five plus years. In fact, our Exchange 2003 installations have remained rock-solid and stable. These installations range from five people to over 50. Very happy with the performance and stability.

    That is not to say that I have not seen Exchange 2003 tank. It happened recently to a colleague running on Windows 2000 Server. Lost his mail store.

    But there are arguments on both ways of doing things: separate databases or files for mailboxes, or one monolithic mail store. I have seen uw-imap and QPopper eat mailboxes -- stuff happens sometimes. ::shrugs::

    But that is why we are administrators, because the technology is not flawless.

  25. Gmail should go back to cell phone authentication by Animats · · Score: 3, Insightful

    Gmail should go back to their old scheme, where you had to have a cell phone to receive your password, and you could only have one gmail account per phone. That would slow the spammers down.

    If you don't have a phone, you're probably not a good candidate for an advertiser-supported service anyway.

  26. Re:It's ok though... by ubrgeek · · Score: 2, Informative

    Notes is a bitch to admin and has a serious learning-curve but it's absolutely bulletproof. It's also used in some places as a tie-in/point of connection to DMS. Like I said, I'd hate to admin it, but I love know it's going to be reliable (and I mean C&C reliable) when it's administered right.

    --
    Bark less. Wag more.
  27. Re:It's ok though... by CowboyNealOption · · Score: 1

    I will admit that Exchange 2003 seems better than 2000 (which I have had eat an entire mail directory; adios email until a restore is done, and you lose everything that came in since the last backup). The latest issue with Exchange 2003 required it to rebuild the mail store, which took over 24 hours to complete (granted the hardware wasn't super fast, but still we were only talking about less than 2 gigabytes of email here). The same setup, using a linux mail server storing email in maildir format would have taken minutes to recover from, rather than hours. And as an added bonus, everyone except the impacted mailbox (and most likely, the single email message that was corrupted) would have continued functioning just fine.

  28. Re:Gmail should go back to cell phone authenticati by Vegeta99 · · Score: 1

    What? I've never seen an ad in my gmail when i use my phone.

    Of course, the phone runs Windows Mobile so I don't use the gmail program, I just have it check IMAP every 10 mins, but who's counting?

  29. Exchange is unusable, period. by HisMother · · Score: 0

    One word: majordomo.

    --
    Cantankerous old coot since 1957.
  30. Serves gmail right by Indy1 · · Score: 0

    for the past 6 months or so, the amount of gmail spam hitting my server has been insane. I've thrown up a pile of filters and what not, but sometimes the only solution is to firewall gmail off for a few weeks until the spam wave dies off.

    If they want to treat their network like a sewer, then I have no problem doing the same, and dumping their ip ranges into the firewall with the rest of the spam sewers.

    --
    Lawyers, MBA's, RIAA? A jedi fears not these things!
  31. Whoa.. so what you're saying is... by Animaether · · Score: 2, Insightful

    ...to be safe from spammers using Google Mail... people should just -get- Google Mail themselves?

    I don't know whether to just blink or to think that you discovered a Google strategy here; getting even more people over to Google Mail because there's less spam there; nevermind the fact that a portion of that spam is sent from their own servers(!) I suppose there wouldn't be a heck of a lot of incentive to do something about the spam accounts, then.

    =====

    Or maybe you're saying that Google should apply their spam filters for incoming mail to all outbound mail as well. That sounds a lot more sane anyway.
    If a legit message is flagged as possible spam, ask for user input (make sure this can't be automated too easily) on whether it's actually legit or not.
    Regardless of that response, if N messages in t time are flagged, have an engineer (okay, school kid) check it out and disable the account if necessary

  32. Re:It's ok though... by kitsunewarlock · · Score: 5, Funny

    And you certainly haven't used a telegraph. I only get spam about once every month or so, and I can usually ignore it by about the 15th beep or so.

    --
    Ginga no Rekshiya Mata Each page.
  33. 1 AND !1 = 1 ??? by billcopc · · Score: 1

    Most users won't get blocked mail

    Okay, so business as usual. If users did receive blocked mail, they would be whining now wouldn't they ?

    So Google's captcha got smashed, ho-hum! Happens all the time to others, and it is certainly NOT a good reason to blacklist Gmail, unless you also block all Yahoo and Hotmail.

    If this causes your spam solution to slow down due to overload, the fault is not Google's, it's your fault for running an underpowered mail queue. Spam is everyone's problem, and we have to work together to clean it up. Pointing fingers doesn't solve shit!

    --
    -Billco, Fnarg.com
    1. Re:1 AND !1 = 1 ??? by Dan541 · · Score: 1

      If this causes your spam solution to slow down due to overload, the fault is not Google's, How is it not google's fault?

      They did fuck all about it!
      I was still able to register with gmail after they knew the captcha had been cracked.
      --
      An SQL query goes to a bar, walks up to a table and asks, "Mind if I join you?"
    2. Re:1 AND !1 = 1 ??? by billcopc · · Score: 1

      They did not fail to provide you with free email, and nowhere in their TOS do they offer any guarantees for spam filtering or even privacy. They are not at fault for anything here. You're certainly allowed to be dissatisfied, but Google hasn't done anything wrong or illegal.

      Things get cracked, it's inevitable and people just deal with it. If your email needs are not met by Google's offerings, you're free to try someone else's email solution.

      Me, I run my own mail server: problem solved! If I'm not happy with my email, the only person I need to bitch at is myself, and I'm fully empowered to fix it at whim.

      --
      -Billco, Fnarg.com
    3. Re:1 AND !1 = 1 ??? by Dan541 · · Score: 1

      I don't use gmail but I still get their shit as a result.

      --
      An SQL query goes to a bar, walks up to a table and asks, "Mind if I join you?"
    4. Re:1 AND !1 = 1 ??? by billcopc · · Score: 1

      Okay, now what if I were spamming you, but (through some perversion of reality) there were a few of your friends using mailboxes in my domain... would you block them to dodge the spam, or would you simply tighten up your spam filter ?

      Same shit, different domain name.

      --
      -Billco, Fnarg.com
    5. Re:1 AND !1 = 1 ??? by Dan541 · · Score: 1

      Blacklist that mail server tightening the spam filter only increases a chance of false positive.

      --
      An SQL query goes to a bar, walks up to a table and asks, "Mind if I join you?"
  34. Re:It's ok though... by Anonymous Coward · · Score: 0

    You mean they don't have adverts automatically inserted?

  35. Mod parent up!!! by Anonymous Coward · · Score: 0

    Wish I had mod points....

  36. Don't blame the spammers by kitsunewarlock · · Score: 3, Insightful

    Blame the companies that allowed the idiots who buy from spammers to get internet in the first place. I know: everyone makes mistakes. At 2 AM, even I've clicked on a banner once or twice to find something (although I can never recall joining a site due to advertisement via mass mailing).

    But, sadly, statistics still prove that if you try to hit 1,000,000 people without any true risk of getting caught, your bound to hit a sucker eventually. There's one born every minute, after all. Not to use colloquial phrases as my source, of course.

    Personally I'm disheartened that American spam has lowered so. It makes it much harder to track down the parent company and call them and ask them why they sent you their e-mail in the first place...

    --
    Ginga no Rekshiya Mata Each page.
  37. Re:It's ok though... by Anonymous Coward · · Score: 0

    I have to agree with the other poster. If you absolutely must put "Regards," at the end of every post, at least put it in your signature. That's what it's for.

    Also, "price tag" is not hyphenated.

  38. That's so very very sad. by CFD339 · · Score: 1

    You must be in some crappy shop running a years out of date version administered by buffoons then.

    --
    The problem with quotes on the internet, is that nobody bothers to check their veracity. -- Abraham Lincoln
  39. Re:It's ok though... by CowboyNealOption · · Score: 2, Informative

    The really nice thing is if you don't buy the superdupermondo version, you can add disk space until you turn blue and it won't matter: the mail stores in the standard exchange 2003 version are limited to 2GB, you can only have one, so be prepared to fork over more money for a version that is identical, except it doesn't have the limit. As an added bonus, feel happy that you could have bought a really nice linux server for the cost of the exchange software alone.

  40. Re:It's ok though... by Bryansix · · Score: 3, Insightful

    It's funny how a good backup strategy involves NOT using anything from Microsoft to backup exchange. I mean seriously, how long has been exchange been out and Microsoft can't make a backup program that can backup and restore individual mailboxes? WTF! Oh, and I don't want to take the store offline to do it.

  41. Re:It's ok though... by rabbit994 · · Score: 1, Interesting

    Wait? Exchange 2003/2007 Recovery Storage Group? Maybe it's time your Exchange got an upgrade.

    Since Exchange 2003 SP2 I haven't seen Exchange Database corrupt itself and I deal with servers running 100-200 users on single servers. These servers have had RAID drives fail, Power pulled from them and users do some really idiotic stuff. Databases always came back ok.

    You could have really nice LInux server for Exchange money, but you would also have something with a bunch of half baked software that didn't have nice Desktop Client, didn't support your blackberry like it should and is asking to break when you update one piece of software.

  42. Re:It's ok though... by rubah · · Score: 1

    Our on-line signatures are not so much signatures as rubberstamps. Sometimes people like to go for the more personal effect.

  43. Re:It's ok though... by imemyself · · Score: 5, Insightful

    That is *completely* incorrect. In Exchange 2003 prior to SP2, the limit for the mailbox store was 16 GB. In SP2 they upped that limit to 75 GB, which really is probably enough for most of the small organizations that probably just have a single server running Exchange Standard.

    Here is a document about it, scroll down to the part where it says Licensed Database Size Limit. http://technet.microsoft.com/en-us/library/aa998066.aspx

    In Exchange 2007, Standard Edition can have up to five mailbox stores in each of five storage groups. And there is no limit on size. http://www.msexchange.org/tutorials/Exchange-2007-Store-Related-Changes-Improvements.html

    Its also mentioned on the Microsoft Exchange page on wikipedia.

    I'm not saying that Exchange is a perfect mailserver for (or worth the cost in) every situation, or denying that Microsoft does some really annoying things, but please try to get your facts straight before you complain about a piece of software.

    --
    Every time you post an article on Slashdot, I kill a server. Think of the servers!
  44. might aswell block yahoo too by Anonymous Coward · · Score: 0

    usenet if flooded with chinese spam from gmail my mailbox filled with spam from yahoo. blocking both seems like a great idea. read somewhere that the captcha really hasn't been cracked, spammers have just hired cheap labour to solve them.

    1. Re:might aswell block yahoo too by Bronster · · Score: 1

      Specifically yahoo.co.uk is sending thousands of spams per day via their SMTP service, because the UK service provides SMTP for free accounts.

      Seriously, it's a trickle of a couple per second to every one of our mx servers, all day every day. Quite impressive.

      (and no, I don't have any answers. Outbound spam scanning is good though)

  45. Get rid of Captchas! by zymano · · Score: 1

    And go after the IP number and the individuals doing this shit.

    Go after their ISP's and take the idiots to court.

    Cat and mouse games are stupid.

    1. Re:Get rid of Captchas! by Skapare · · Score: 2, Interesting

      The IPs doing this shit are the end user addresses for home and office computers that are no different than all the other end users that use Gmail. They could block an IP, but eventually that IP will be used by someone else who is a legitimate and secure Gmail user. They are better off closing accounts that send spam. But Google isn't doing that (based on having seen spam from the very same user I reported to them as a spammer 2 weeks prior). If they do decide to pursue the user of the IP, once they get past the legal roadblocks of getting the identity out of the ISP (while doing this for 100,000 such IPs at the same time), all they get is some stupid loser who has an infected Windows box being used as part of the botnet. They can get this machine cleaned up, but they aren't anywhere near the real culprits.

      What Google needs to do is segregate all users that are new since the crack (they know when it was, because they can see a spike in new user signups from random end user IP addresses). In the mean time, close down direct signups and fallback to the invite system only allowing the old users to send invitations. Re-engineer the CAPTCHA system to at least temporarily thwart the signups before bringing that back online. For all new users, run all their outgoing mail through the same filters that are used for incoming mail. Mail that can't be sent, put it in a new folder type for "blocked outgoing". The user has to pass a new CAPTCHA per each message to do a re-deliver around the filtering (or just rephrase and send a new one). And limit the number of these to 3 per day (although this may not do much good since the botnet may only be doing this much or less over a million accounts).

      --
      now we need to go OSS in diesel cars
    2. Re:Get rid of Captchas! by Dan541 · · Score: 1

      And go after the IP number and the individuals doing this shit.

      Go after their ISP's and take the idiots to court.

      Cat and mouse games are stupid. You think we woulden't take spammers to court if we could?

      --
      An SQL query goes to a bar, walks up to a table and asks, "Mind if I join you?"
    3. Re:Get rid of Captchas! by zymano · · Score: 1

      We don't take it seriously.

    4. Re:Get rid of Captchas! by zymano · · Score: 1

      interesting.

      I hate Captchas. This all revolves around lack of control.

      ISP's forcing users to use tracking software would help.

      We can do this but don't. It's perceived is a wild jungle so we don't do anything.

  46. Re:It's ok though... by Sleepy · · Score: 3, Insightful

    >Exchange trumps Gmail easily. No Contest.

    As a source for spam, and a plague of server-generated 'automated' notices, Exchange beats EVERYTHING.

    Exchange is fine if you keep it where it belongs: inside a workgroup or protected by a SMTP-protocol filter (which is not running on the same box).

    Recently I had to defend a customer who was the target of a DDOS... 80% of which were "bounces" from Exchange (forged From: undeliverables, permanent Out Of Office, DSNs, Mailbox full emails, etc). Exchange is pathetic in terms of controlling what gets "onto" the server.

    By comparison, Google mail is a VERY good Internet citizen. They may have had Captcha compromised, but they'll plug it up. I'll them over their competition anyday.

  47. Re:It's ok though... by Anonymous Coward · · Score: 0

    Those are easy to shut off in Exchange, but it still requires somebody to actually be aware that it needs shutting off. Exchange may have stupid defaults, but every product is susceptible to that at some point or another. I'm sure whoever set up that machine and paid *such* close attention to it would create an equally bad sendmail box.

  48. Re:It's ok though... by Techman83 · · Score: 1

    I would have to disagree, it's only ok if you don't know any better. I describe our exchange box as a 2 year old screaming child. It requires regular maintenance that cannot be done live.I cannot believe that large orgs use this as it is really only manageble in a small org, in which case there are plenty of easily setup foss software with far better support!

    --
    # cat /dev/mem | strings | grep -i cat
    Damn, my RAM is full of cats. MEOW!!
  49. Re:It's ok though... by xmas2003 · · Score: 1

    Then you certainly haven't used /usr/ucb/mail, which trumps Lotus Notes, Citadel, Exchange, and Gmail combined!

    --
    Hulk SMASH Celiac Disease
  50. Re:It's ok though... by kesuki · · Score: 1, Informative

    um the problem i mentioned the disc usage wasn't directly tied to exchange, it was tied to a 'feature' of windows, where it was endlessly consuming more and more gigs of space, at a rate of 10 GB a day. just wanted to be clear here, this was due to a 'feature' of windows not exchange server.

    It just happened to be happening on a mission critical exchange server..

  51. Re:It's ok though... by Com2Kid · · Score: 1

    A good admin would have fired up Sysinternal's Process Monitor and found out who in the hell was writing to disk. Looking at IO by process would have pointed to the culprit pretty quickly. Of course you won't find step by step instructions on doing that by Googling, one would have to show some initiative, but a good sysadmin has a virtual swiss army knife of tools that they use to keep things taped together.

    Hell, if the emergencies didn't pop up at the worst possible moment, what fun would be left to have?

    I've worked both in the server room keeping things patched up and out front with the people who write the stuff that breaks. The server room is almost always more fun, every day is a new emergency, but that is what you sign up for!

    (Besides, sysadmins with systems which never break may find themselves out of a job! )

  52. Re:It's ok though... by EvolutionsPeak · · Score: 1

    Interesting that your "real world" scenario involves gnomes and magic.

  53. Re:Gmail should go back to cell phone authenticati by Oriumpor · · Score: 3, Interesting

    Expect to see a technological solution, this isn't a company full of middle managers or people who are used to losing technical battles.

    If I were a betting man I'd say Google will either A) release a new authentication/authorization scheme for creating new accounts, or B) they'll evolve their current system to be resistant to delivering false negatives on bot provided responses.

    Because honestly, isn't this just graphical/visual acuity based Turing test that needs to be treated as "passed" by the industry? The reasoning being: the equivalent of Alicebot now exists for the graphical world, so the test needs to be re-engineered to test another (currently) unpassed Turing style evaluation.

    Based on that realization: the whole reason capcha's are stupid is that if you keep the existing design but try and make it "harder" to break, the designer of the Bot need only account for that change and not an entire redesign.

    All this sounds like a great technical challenge: think up a new Turing test... When in reality those posting go back to invite only are absolutely right but it's likely we won't see that come out of Google.

  54. Re:Gmail should go back to cell phone authenticati by Animats · · Score: 1

    What? I've never seen an ad in my gmail when i use my phone.

    In the early days of Gmail, you had to supply a cell phone number, and your initial password was sent to your cell phone via SMS. One Gmail account per cell phone number. This puts a dent in spamming; you have to keep buying new phone numbers as your old accounts are terminated.

    Some free dating sites now do this. I've been bugging the Craigslist people to try it.

  55. Re:It's ok though... by Dan541 · · Score: 0

    What on earth do you need 7Gigs for?!

    Unless your going to email a movie!

    I agree 10meg is living in the stone age but 7gigs just seems overkill.

    ~Dan

    --
    An SQL query goes to a bar, walks up to a table and asks, "Mind if I join you?"
  56. Re:It's ok though... by urbanriot · · Score: 1
    I couldn't agree more. Our company builds Exchange servers (single and clusters) for clients ranging from small business to large corporations, and after initial install we rarely have any post installation administration requests. We build our servers, install them, and they happily run for years.

    I have no idea what that analogy you're jabbering on about has to do with anything, but you should try to find someone with experience to build your servers rather than whatever paper MCSE you have running the show.

    While I'd love to see a good open source alternative that can do everything Exchange can do, as well as it does it, but I've found Exchange a treat to work with since 5.5.

    Wow, if you're having that many problems with Exchange, your sysadmins need to do a better job.
  57. Re:Gmail should go back to cell phone authenticati by waded · · Score: 1

    Yes, and it also increases cost to acquire customer, decreases the number of potential customers at the same time(to those who have cell phones.) That would be an idiotic thing to do, when really all Google has to do is balance well-done features against poorly-done features well enough to acquire and keep you from switching away (switching costs on email can be kind of high with "unlimited storage" in play these days.) Ad impressions are ad impressions, even ones taken when composing an email that'll never make it to its destination. Bo hoo.

    The old scheme was likely more relevant for early testing, although perhaps putting those spammers-without-cell-phones in the mix earlier on might have been a good idea.

  58. Re:It's ok though... by Kalriath · · Score: 1

    It's to draw attention to his signature, which is an advertisement. Stop being so surprised.

    --
    For a site about things like basic rights, Slashdot users sure do like to censor "dissent".
  59. CAPTCHA Replacement Idea by KnowledgeEngine · · Score: 2, Interesting

    My 2 Cents... Show the user 5 images. Your job is to 1) Select the one image that is out of place with a radio button 2)Solve the captcha that is one of the 5 images 3) Choose which word best describes the remaining 3 images from a drop down/combo.
    How this would work
    ..1....2......3.......4......5 (Captcha image)
    Cat Cat Money Cat "Peaches"
    Drop down choices (Housewive, Gutter, Salsa, Fruit, Cat)
    Answer: 1-(Image3-Money) 2-(Peaches) 3-(Cat)
    Of course this would only be reasonable for something one time only like signing up for gmail.

    1. Re:CAPTCHA Replacement Idea by electrictroy · · Score: 0, Troll

      Or just use Spamcop.net email which requires a credit card to use.

      --
      The government is not your daddy. Its purpose is not to raid middle-class neighbors' wallets and give it to you.
    2. Re:CAPTCHA Replacement Idea by Cramer · · Score: 1

      Like getting credit card numbers is difficult? That's laughable to any high volume spammers. Any 5yo can use Google to find hundreds of CC numbers.

  60. Re:Gmail should go back to cell phone authenticati by whereiswaldo · · Score: 3, Insightful

    Gmail should go back to their old scheme, where you had to have a cell phone to receive your password... If you don't have a phone, you're probably not a good candidate for an advertiser-supported service anyway.

    Since when does cell phone == phone? Tons of people don't have cell phones, and most of them are consumers of various goods just like people who do have cell phones. It's amazing how the 'net culture makes it easy to write off huge swaths of the population just because they don't have or want the latest gadgets.

  61. Re:It's ok though... by Anonymous Coward · · Score: 3, Insightful

    While the 2GB size was erroneous, it is true that 2003 Standard is limited to a single mail store (see the article you linked to; it says as much). So prior to SP2 you were stuck with 16GB total size.

    I find it typical that you start mentioning Exchange 2007; pretty much every Microsoft person recommended we upgrade to the newest software when we started having trouble with our Exchange server. Luckily we decided to get off the Microsoft upgrade treadmill; it was a pretty easy sell when we saw how much just the software alone cost.

  62. Re:It's ok though... by BountyX · · Score: 1

    Open XChange trumps Citadel by a wide margin.

    --
    Trying to install linux on my microwave, but keep getting a kernel panic...
  63. Re:Gmail should go back to cell phone authenticati by Anonymous Coward · · Score: 0

    Obviously gmail can't simply strip millions of us of the ability to use our accounts. If they didn't want those of us who are largely stationary, use a POP client and don't own cell phones, then they shouldn't have started offering POP access.

  64. Re:It's ok though... by acoustix · · Score: 1

    I've been running Exchange for ~5 years without any major incidents. My latest install is Exchange 2003 running in an active/passive cluster for ~250 mailboxes. In the 20 months that it has been running I only have a total of 2-3 minutes of downtime - and that's only from the 5-10 seconds that it takes to failover when I apply updates.

    I would say that it has been extremely reliable for me.

    -Nick

    --
    "A plan fiendishly clever in its intricacies"- Homer Simpson
  65. Re:It's ok though... by kasperd · · Score: 1

    In Exchange 2003 prior to SP2, the limit for the mailbox store was 16 GB. In SP2 they upped that limit to 75 GB
    16GB per mailbox should be enough for most users for a few years to come, what is all the fuss about?
    --

    Do you care about the security of your wireless mouse?
  66. Oh please, spare me. by MacDork · · Score: 1

    On my reports some individual users are targeted with between 1500 and 2000 SPAM messages a day. There storage quotas would probably be exceeded over night from SPAM alone.

    Yeah, because 2000 email messages is what? 4 MB of text, maybe. A 1TB hard drive will set you back about $250 at Target. $250 to hold a quarter million users' spam. OH GAWD, that's Sofa King expensive. A tenth of a penny per user. Wow. Where will your organization ever come up with that kind of cash!?!

    In the meantime, I have three different email accounts that people have to CC to in order for me to get all my email. They practically need a fscking template to send email because a$$hole admins keep blocking their messages or mine enroute. Good job jerks. You've ruined email.

    1. Re:Oh please, spare me. by Pegasus · · Score: 1

      You obviously never ever set up a mail server with moderate traffic. TBs are cheap, but IOPS are not. Today I can get same 100 IOPS from 1TB disk as I can get from 10 year old 2GB disk. While 100 IOPS per 2GB of disk space was bad but somehow manageable, 100 IOPS per 1TB of disk space is utterly worthless, unless you (as an end user) are willing to put up with up to 30s of wait to retrieve a single mail.

    2. Re:Oh please, spare me. by MacDork · · Score: 1

      unless you (as an end user) are willing to put up with up to 30s of wait to retrieve a single mail

      Given that I have to check three email accounts to get my messages, I can safely say 30 seconds would be a fantasy paradise.

  67. .Free Anti spam webinar, Why Todayâ(TM)s Spam by antispam24 · · Score: 0, Offtopic

    Spam isnâ(TM)t just a big nuisance; itâ(TM)s big business as well. So why is spam persisting? Ferris Research estimates that spam will cost $140 billion worldwide in 2008, of which $42 billion will be in the United States alone. If you compare these numbers with Ferrisâ(TM)s 2007 estimates of $100 billion and $35 billion, youâ(TM)ll see that the cost of spam has increased substantially over 12 months. Register for a complimentary Webinar conducted by Abaca and Ferris research to know more about how you can stop this nuisance. To register please click the link below: http://www.surveymonkey.com/s.aspx?sm=LPFKkdkFwOYltiQZtM_2bttw_3d_3d

  68. Re:It's ok though... by n3tcat · · Score: 1

    . -. .-..
    Hmm...
    .- .-. --.
    This could be interesting
    . / -.-- ---

    Ah goddammit!

  69. Re:It's ok though... by Kugrian · · Score: 1

    Best analogy ever. Can you do car ones as well?

  70. Re:Gmail should go back to cell phone authenticati by Ravadill · · Score: 1

    The CIA world fact book says as of 2006 there were 233 million cell phones in use in the US for a population of just over 300 million... that's a vast majority of the population with access to a mobile, especially when you consider the number of internet users savvy enough to want to sign onto gmail in the first place with cell phones is most likely an even higher percentage.

  71. Re:It's ok though... by hostyle · · Score: 2, Funny

    I couldn't agree more. Our company builds Exchange servers (single and clusters) for clients ranging from small business to large corporations, and after initial install we rarely have any post installation administration requests. We build our servers, install them, and they happily run for years.

    Perhaps the emails they have sent to report problems / issues are not getting through ... :P

    --
    Caesar si viveret, ad remum dareris.
  72. Re:It's ok though... by Anonymous Coward · · Score: 0

    I'm not saying that Exchange is a perfect mailserver for (or worth the cost in) every situation, or denying that Microsoft does some really annoying things For a mail system that is still decades behind real technology, makes its users look bad with respect to established email standards and has a difficult time interoperating with anything other than itself (in defiance of internet tradition), you sure are defensive.
  73. Re:It's ok though... by electrictroy · · Score: 1

    Alright.

    What's so special about Gmail? I signed-up for it a few years ago when everyone was talking about it, and I didn't see anything that made me go "wow" with delight. To this day I continue using my yahoo account, since everybody knows that's where I'm located (since 1997), and the Gmail sits idle. I couldn't find a compelling reason to switch.

    --
    The government is not your daddy. Its purpose is not to raid middle-class neighbors' wallets and give it to you.
  74. I wish people would stop advocating SPF etc. by Anonymous+Brave+Guy · · Score: 1

    Please, people, SPF is broken, and so are all the other similar technologies.

    For one thing, they are not standardised but in competition. That means most people don't use them. That means they are practically begging for a high proportion of false positives.

    For another, the technical approach they tend to take is impractical. It's all very well saying big business should set up its DNS entries using this or that little hack, but most of us (yes, the vast majority of domains registered) are not running on dedicated hardware with full-time sysadmin staff who are paid to mess around with this stuff. It would be completely impractical for me, as the lone, volunteer-in-my-spare-time sysadmin of a small, local non-profit, to keep track of the dozen or more people who may legitimately send mail using our domain name and all the mail relays used by all the ISPs they use, and then to update our domain information accordingly every few days when something changes. Life's just too short for that kind of idiocy, which is presumably why of the small proportion of domains that do have SPF entries, a high proportion only say "allow from all", which pretty much defeats the point.

    Don't get me wrong: I hate spam as much as the next guy. I set up some simple spam filtering on our incoming mail, using nothing but the standard issue tools our mail hosting service provides, and it blocks 95+% of our incoming spam with no false positives observed in more than two years of use. It's using one of common score-based systems that considers many indicators but will only block mail when the combination of factors is sufficiently strong to be very confident it really is just spam. It doesn't rely on any SPF or SendID or DomainKeys rubbish, and we do just fine.

    Basically, the only people SPF is really hurting are those using poorly configured mail services that outright block incoming messages from sources without SPF because some know-it-all sysadmin bought the snake oil. Oh, and those of us who admin non-SPF'd systems, who get grief from these other people when mails they asked for don't arrive and after asking their know-it-all sysadmins they blame us.

    --
    If you disagree, post your argument. (-1, Overrated) isn't your personal censorship tool for views you don't like.
  75. Re:It's ok though... by jsfetzik · · Score: 3, Informative

    In Exchange 2003 prior to SP2, the limit for the mailbox store was 16 GB. In SP2 they upped that limit to 75 GB
    16GB per mailbox should be enough for most users for a few years to come, what is all the fuss about? No 16GB to for the mailbox store, which houses ALL of the mail boxes, IIRC. Thus, the reason for having 10M-20M limits on peoples inbox.
  76. Re:It's ok though... by Nullav · · Score: 1

    I know exactly what you mean. Those slashes hurt my ears. :(

    --
    I just read Slashdot for the articles.
  77. Re:It's ok though... by p$iCLOne · · Score: 1

    Heh, with Gmail you don't need an admin and it hasn't failed me once in many years, whereas Exchange has been woefully oversold [sticks tongue out]

  78. Re:It's ok though... by p$iCLOne · · Score: 1

    How does this make the case for Exchange on the user end? How does ensuring sysadmins having a job correlate to a more effective system? Perhaps look for a cash cow in some other...ehem...[smart] way?

  79. Re:It's ok though... by ssstraub · · Score: 1

    How about the fact you can't easily switch (and by "switch" I mean never visit mail.yahoo.com again) from your Yahoo account for free even if you wanted to?

    With Gmail, you can forward your mail to an external address for life, for free. No lock-in! With Yahoo you get the annoyance of checking that original account "just in case" someone sent mail there instead of your new account, since you cannot forward from Yahoo without paying for it.

    I'd recommend Gmail over anything else just for that reason, but throw in absolutely free POP3 and IMAP support and suddenly no other provider is even competing on the same level.

  80. Re:It's ok though... by imemyself · · Score: 1

    That may be true, but personally I like having control over the server (and the ability to easily do backups/restores if I accidentally were to delete a message or something). Also, AFAIK, I can't have Gmail push mail to my Windows Mobile phone (I can w/ direct push in Exchange 2003 SP2), or sync my contacts/calendar/tasks from Outlook, and from my phone. I have no doubt whatsoever that Gmail would be more than sufficient for most individuals (I have a Gmail account that I use for subscribing to stuff so I don't get annoying newsletters that I don't read on my real email account), but for a business environment, something along the lines of Exchange (or Groupwise, or Zimbra, or Notes if you must) is many times a better solution. Because they do more than just email.

    --
    Every time you post an article on Slashdot, I kill a server. Think of the servers!
  81. Re:It's ok though... by SpookyTech · · Score: 1

    guys you are invited to try out www.sawoutlook.com . A cool tool. Cheers.

  82. Re:It's ok though... by Wavebreak · · Score: 1

    Of course you don't need it, in fact I'd assume that's the very reason they can actually offer it, but that's not the point. The point is you have essentially unlimited storage for the foreseeable future, meaning you never have to worry about deleting mail you might just miss at some point to save space.

    --
    Nobody expects the British Columbia Human Rights Tribunal.
  83. Re:It's ok though... by teknopurge · · Score: 1

    Our on-line signatures are not so much signatures as rubberstamps. Sometimes people like to go for the more personal effect. Bingo. :)

    Sorry to the other grammer nazi. I will do better...

    Regards, ;)

  84. Re:It's ok though... by Com2Kid · · Score: 1

    A server of any OS has the potential for sporadically breaking out into inanity from time to time, especially if it is under constant heavy load. Not to say that you can't get a server up and running stable for 10 years that gets dry walled in to place, but the majority of servers (and software) is not that reliable.

    It is up to Sysadmins to know how to fix the machine when the sh!t does hit the fan, because sooner or later it indeed will.

  85. Re:It's ok though... by Thundersnatch · · Score: 2, Insightful

    What a bunch of incompetents. 12 day old backups for one, and a complete inability to open task manager to discover which process was doing all the disk writes.

    If it was exchange itself, a mail loop was probably the cause. Older Exchange versions didn't totally prevent users from creating ping-pong forwarding rules with certain external mail systems. Again, a few minutes with simple tools like perfmon would have diagnosed the issue.

    Give the same "admins" a Linux box and the same amount of training they had for Windows/Exchange, and the damage would inevitably be just as bad.

    Management is the key in any IT system - we run Exchange and other Windows-based stuff with four-nines reliability. It is possible, and not even that hard with good controls and processes. The same can be said of just about any modern OS, and even most application stacks (although there is some truly horrible, unworkable crap out there in the vertical markets).

  86. Re:It's ok though... by Thundersnatch · · Score: 1

    You don't want to backup or restore individual mailboxes. That's what the deleted items/mailbox retention feature and recovery storage groups are for. Using those features, you don't need to restore individual mailboxes unless you need to roll back by many months.

    Backing up individual mailboxes is horribly inefficient because it breaks single-instance storage, and requires an index seek for each item being backed up. We did a test once, and our 60 GB exchange databases exploded to >200 GB with a mailbox-level backup, and took 6 times longer, hammering the crap out of the disk and CPU in the Exchange box in the process.

    Think of it this way... would you back up each row in a SQL database table separately with individual queries? No. But that's what you're asking Exchange to do with mailbox-level backups.

  87. Re:It's ok though... by KevReedUK · · Score: 1

    That's mailbox store, NOT mailbox... One mailbox store can hold many mailboxes!

    --
    Just my $0.03 (At current exchange rates, my £0.02 is worth more than your $0.02)
  88. Re:It's ok though... by operagost · · Score: 1

    I believe the limit for both 2000 and 2003 is 16 GB. Besides, SP2 added the ability to resize it up to 75 GB for no additional charge.

    --

    Gamingmuseum.com: Give your 3D accelerator a rest.
  89. Re:It's ok though... by operagost · · Score: 1

    None of those items you mentioned are in any way inherent to the design of Exchange.

    --

    Gamingmuseum.com: Give your 3D accelerator a rest.
  90. Re:It's ok though... by Bryansix · · Score: 1

    Symantec Backup Exec does this though? I've used it. If the need arose I could recover email from months back or yesterday for a single mailbox. Users are dumb or malicious all the time. There are many reasons to want this.

  91. Re:It's ok though... by kris.montpetit · · Score: 1

    I dont need 7 gigs-although you can use it as an online backup area. I just have 7 gigs because it was free :P

  92. Re:It's ok though... by Sleepy · · Score: 1

    >Those are easy to shut off in Exchange, but it still requires somebody to actually be aware that it needs shutting off. Exchange may have stupid defaults, but every product is susceptible to that at some point or another. I'm sure whoever set up that machine and paid *such* close attention to it would create an equally bad sendmail box.

    Apples and oranges though:

    Sendmail: free updates, free security updates, free major revision upgrades

    Exchange: Several thousands of dollars to upgrade, security updates are sunset for "old" versions -- thus people too "cheap" to upgrade Exchange end up running insecure setups. Actually, "cheap" isn't fair.. I've seen Exchange shops where IT was incapable of attempting a +1.0 version upgrade on Exchange.

    So 2 points against Exchange in terms of staying secure and up to date. This of course demonstrates itself in the real world... there are tens of thousands of Exchange 2000 (and even Exchange 5.5) systems out there spewing Delivery Status notices, Out of Office, blindly accepting email wildcarded for their domain (no SMTP rejection possible upon a bad RCPT TO mailbox), etc.

    Perhaps Exchange 2007 is better in this respect by default, but that's not my point... the installation base is a tiny fraction of Exchange 2K and 2K3, and will be for years to come. If Microsoft ever decided to spare the Internet, they would time-bomb their servers or lease their servers as a subscription service. They make it hard for their mistakes to disappear.

  93. Re:It's ok though... by Sleepy · · Score: 1

    >None of those items you mentioned are in any way inherent to the design of Exchange.

    Weasel wording or useless semantics.

    Perhaps Exchange was not DESIGNED (ie, intended) to be that way, but it IS. You are simply unaware of this real world fact, or find the truth inconvenient. *shrugs*

  94. Re:It's ok though... by Thundersnatch · · Score: 1

    In a properly managed Exchange system, there's almost no reason to want mailbox-level backup. Deleted items and deleted mailbox retention cover almost all of the situations where you would want a mailbox-level backup, without requiring any type of restore or 3rd party software. In the very infrequent case of needing really old data not covered by deleted items retention, you can restore a whole database using a recovery storage group and move items indiviudally from there.

    Yes, many tools do mailbox-level backups, but they are really inefficient, and quite brittle and buggy. Have you tested a restore this way?

    Also, there is no way to do reliable incremental backups with per-mailbox tools. There is no Microsoft API for individual mailbox backup, so these tools impersonate an Outlook client (using MAPI) to suck down messages. Finally, a real exchange backup does a check of all database pages for corruption during the backup. You don't get that very important feature with mailbox-levelbackups.

    See this link for some more details.

  95. Re:It's ok though... by Bryansix · · Score: 1

    But that misses the point entirely. I don't have the hard drive space to have deleted item retention set to that length of time.

  96. Re:It's ok though... by Thundersnatch · · Score: 1

    Then you don't have the hard drive space to completely restore your backups either!

    When you restore from a mailbox-level backup, single-instance-stoage (SiS) is broken. Every message you restore is inserted into the Exchange database separately. At my site, our SIS ratio (which can be seen using perfmon) is 5.6, meaning each email message is sent to 4.6 people on average (plus one copy in sent items), but only stored once.

    Assuming your site's ratio is similar, if you had to restore all of your mailboxes using a mailbox-level backup, you would need 5.6 times as much disk space as you currently use for Exchgange databases!

    Have you ever done a full test restore? If not, you're in for some rude surprises.

    Disk space is CHEAP. Data loss and down time are not. We use a deleted items retention period of 180 days, and it only increases our Exchange database sizes by about 30%

  97. Re:It's ok though... by Bryansix · · Score: 1

    I don't want mailbox level backups to restore all of them at the same time. I want them to restore one mailbox.

  98. Re:It's ok though... by electrictroy · · Score: 1

    (1) If I never abandon Yahoo, why would it I need to forward my emails someplace else?

    (2) Yahoo has POP3 and IMAP support (it's how I read my pop.psu.edu account).

    Like I said, I just don't see any reason to abandon yahoomail and switch to googlemail. (Of course, I also still use a Commodore=64 and Amiga 500, so maybe I just like to cling to old things.) (shrug)

    --
    The government is not your daddy. Its purpose is not to raid middle-class neighbors' wallets and give it to you.
  99. Re:It's ok though... by Thundersnatch · · Score: 1

    So you're doing regular full database backups as well as mailbox-level backups? That's fine, I suppose, so long as you have the backup window and tape/disk media space to spare.

    I still suggest testing a full restore of Exchange regularly, as well as mailbox-level test restores.

  100. My anti-spam solution! by coleedwards · · Score: 1

    Hi guys! Just wanted to say a few words about my way to deal with spam - I use Gafana.com - that'sin my opinion the best anti-spam solution ever! Has anyone of you tried it?

  101. Re:Gmail should go back to cell phone authenticati by Vegeta99 · · Score: 1

    Yeah, I knew that, but what does having a cell phone have to do with using their ad-supported service?

    I only ever see ads on their website, I don't get SMS spam from them (or anyone else for that matter) or in my phone's inbox.