Hey all, I have observed enough of these Corrupt Content Alerts to formulate a hypothesis as to their origin. In many cases, I receive the same email message via two separate routes, one through the sourceforge and one directly. I am invariably able to read the message which arrives via the direct route. Reading the message which went to the list is only possible some of the time. This tends to point the finger at the sourceforge list server.
While I can respect the desire of people to use localized character encodings in their email, people should be aware that doing so causes your message to be dropped by sourceforge. Worse, anyone who gets your email via the direct route, then responds to it, also gets their message dropped by sourceforge. (This is supported by the observation that when I quote the "direct version" of a Corrupt email, my own message comes back to me "Corrupt".) At this point, it is worse than a private email conversation, because everyone else on the list is informed when you're saying something, but is not allowed to read what you said. An example: (I'm going to pick on Martin, but I don't mean to be mean. :) ) There's something in the way Martin quotes email which sets off the Sourceforge mail gremlin. Original messages from martin are usually OK. But looking at the archives of Corrupt Content email has caused me to hypothesize that the <?> symbol in Martin's quote line might have caused the mail to be dropped. Martin is far from unique in this respect, he just talks the most. :) Now my hypothesis might be wrong, so the first thing is: does anyone have data to disprove the Sourceforge hypothesis? Failing that, can I ask that regular users of the list start reading the version that is sent out by sourceforge (you can set up your account to receive email that you send)? If you notice that the version distributed to the list has been replaced by a corrupt content alert, could you please experiment with your mailer to ensure that you send something that subscribers to the list will receive? I do not know if there is an administrative solution to this problem, other than migrating the maling list(s) to a different server. Are there people in either the GeoAPI or GeoTools projects who have the ability/responsibility to interface with Sourceforge to address issues like this? Bryce ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ Geotools-devel mailing list Geotools-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel