Every so often a bug comes along that seems to defy logical sense. In these cases, the mindset we adopt determines whether we're able to solve the problem, or whether we run screaming into the night. Sometimes it's necessary to momentarily suspect disbelief and just go with the flow, probing for clues where we're sure they shouldn't exist or be significant.

Consider being presented with the claim that a given system can't send email more than 500 miles. Sounds nutty, right? Then read this story. There's no Perl content, but it's worth the read just as a reminder of how nutty life can get in tech, and how crazy sounding bugs reports don't always mean crazy users.

(Credit for the link goes to the 0xdeadbeef mailing list, viaBoingBoing)

Update: In the event the story gets slashdotted, there's always the google cache. Arrg. Not working. rinceWind provides this link, which works at the moment, and RMGir provides this link.

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.