yikes, sorry again about this... I just switched back the domain sent to the clients to one that google sees as clean (dl.getdropbox.com). if you have links that are generating warnings, simply change 'files.getdropbox.com' to 'dl.getdropbox.com'
after the first incident, we came up with a way to prevent the single malicious user causing all these problems from republishing malicious content. we also registered with the google webmaster tools system in order to get notification of any malicious content detected. unfortunately, their site didn't let us know of any malicious content on the domain before banning us again as it should have . we've requested a review, but it does look like we're going to have to do one of two things to prevent another banning:
1) implement custom URLs for users i.e. dl.getdropbox.com/arash (apparently google will treat these as separate domains)
2) outright ban serving content as text/html (i.e. no hotlinking to html docs). this would unfortunately kill a pretty neat use case for dropbox, but solve all the malware issues.
I'll report back soon on what we decide to do, but appreciate any feedback.
re. #1,
unfortunately, what google does is choose the most specific path or most specific subdomain that catches all the malware. this means that if we were to give out custom display names and do something like dl.getdropbox.com/arash, we actually could have the same problem. if {dl.getdropbox.com/badperson1 dl.getdropbox.com/badperson2.... dl.getdropbox.com/badperson1000} existed, that'd be enough for them to ban dl.getdropbox.com as a whole because there are too many unique bad sites.
we try to keep malware labels as specific as possible based on our data. If we can see that it's limited to a specific subdomain, we'll do that. If we can recognize that it's limited to a specific subdirectory, even better. The general problem is that it's often not trivial to find the most specific part of a site that is affected by malware - and with CMSs as they are there's often no clear folder-type structure that we can work with.
the same problem would likely exist if we offered subdomains. if there are enough bad subdomains, (i.e. badperson1.getdropbox.com, badperson2.getdropbox.com... etc.), then the entire getdropbox.com domain would be banned.
in today's case, google decided to ban everything that starts with dl.getdropbox.com/u. it looks to me that while they could have banned dl.getdropbox.com/u/badpersonid, they decided that there were enough unique occurrences to conclude it'd be more effective to just ban everything with the /u prefix. that's bad news, because it means that any subdomain/custom display name solution would likely result in an identical ban.
in summary, I'm afraid #2 may be the only solution that can work in the long run .
Posted 3 hours ago #
hi all,
sorry if amidst all this discussion, the solution wasn't made obvious. simply adjust your links that say 'files.getdropbox.com' to 'dl.getdropbox.com' and the warnings will go away. the google warnings on 'files.getdropbox.com' should be removed in the next few hours.
Posted 3 hours ago #
Posts
This issue was previously addressed, seemed it was one malicious user.
Option's their considering for handling it, since it's popped up again.
Edit: Seems you have to be a user to see their forums... Snip's posted.
Source: http://forums.getdropbox.com/topic.php?page=3&id=10019&replies=73#post-72642