I would say that more likely then not the transaction was a mistake and that the sender meant to pay a 0.0001BTC transaction fee and send 291.2409BTC to the address that ended up receiving 0.0001BTC.

It is possible that the sender had some kind of agreement with the mining pool that included the transaction in their block, in that the sender would send a transaction that has a very large tx fee that the pool would confirm and then the pool would subsequently send an equivalent amount of btc (minus some fee) to the address of the sender's choice. This would allow the sender to have increased privacy and for the pool to have some extra income. There would be the risk of the transaction being public once the block is found and that the found block getting orphaned, potentially causing another mining pool to collect those tx fees. Regardless I do not believe that this is the case here because blockchain.info's node appears to have seen the transaction ~2 minutes before it was confirmed into a block, meaning that it was "luck" that this particular pool included this transaction into their block.