[/quote]

It isn't part of memory pool selection rules in bitcoind.  Most (all?) major pools use custom software but AFAIK unless it has changed recently no pool does "forward looking of fees". 

The OP has two solutions:
The first solution is to delete the offending transactions locally (requires some wallet.dat surgery).  Other nodes including miners will "forget" about the unconfirmed transactions in time (I believe 24 hours?).  This would allow creating a replacement transaction with an appropriate fee to ensure timely inclusion.

The second solution is to contact a pool operator directly, provide them the transaction hash(es) and for a manually paid bounty (fee) they may be willing to manually add the offending transactions to the pool's next block.  IIRC Luke has done this in the past.

If both of those solutions sound like they suck, well that is the point.  The mandatory fee rules exist to protect the network from a denial of service attack.  If one could create 600 outputs using 22KB for a mere 0.0005 BTC (about 1.2 cents) then one could also create transactions totaling ~30,000 transactions and 1 MB for about $0.50.  For less than minimum wage an attacker could denial of service attack the largest computing network in the world and add roughly about 4GB of spam to the blockchain per month.

Simple version:  DON'T BYPASS MANDATORY ANTI-SPAM RULES.  They exist to protect the network.  When you bypass them the network teats the transaction like a threat and the "immune system" which consists of dropping and delaying high-cost low-value transactions kicks in.
[/quote]

would his work for my situation, link to thread https://bitcointalk.org/index.php?topic=143266.0;all