Slashdot Mirror


GMail and Sourceforge E-mail Bouncing Saga

An anonymous reader writes "All e-mail going back and forth from Sourceforge and Gmail is being bounced. This leaves many Open Source projects with helpless mailing lists. Fortunately, Sourceforge blames Google and Google is blaming SourceForge for this. The Sourceforge support site is clogged with support requests for a resolution to this problem. Google's response to this bouncing has been automated e-mails saying it is probably at the other end of mail delivery. This is something that the community needs to know about since it has been going on for a week already with no end in sight." Worth noting that Sourceforge and Slashdot are both part of OSTG. Update 20:07 GMT by SM: According to SourceForge support staff this issue is now resolved. Apparently a few days ago the sender-verify to gmail started resulting in 450 errors. Google has since either corrected this issue or whitelisted SourceForge and several tests of the system have resulted in correct delivery.

2 of 242 comments (clear)

  1. Why is the email bouncing? by Anonymous Coward · · Score: 5, Insightful

    The summary was useless, there's only a few things I want to know about this spat. Who sends the first DSN, why and why was it rejected by the other party?

  2. Re:Probably Sourceforge? by srussell · · Score: 4, Insightful
    Unless anyone else is having trouble with gmail, I'm tempted to just lay all of the blame at sourceforge.
    Hear, hear. Considering all of the problems I've (personally) encountered with SourceForge (broken databases, unresponsive, utterly down) and how few problems I've seen with Google (as in, none), I'd be inclined to think the problem is on SourceForge's end. Google has a reputation for reliability and quality. SourceForge, on the other hand...

    --- SER