Another quick update on this, it looks like the bug was introduced in version 2.5.8-2 built Mar 30 2005, 11:04:33, revision 1.611 version 2.5.8-1 built Mar 21 2005, 17:28:54, revision 1.592 does not exhibit the behavior. Matt