Stainless Steel Rat writes: > * Dmitry Yaitskov on Tue, 30 Mar 1999 > > | Where (rfc#) does it say so? Note, the pop3 server (or rather, 3 > | different pop servers that I tested) did not become confused. It was > | the local mail client (gnus) that got confused. > > Then the bug is in Gnus. QED. Indeed SSR, if POP requires you not to mangle the message and you intend to put it in a mbox format you're going to have to pick one standard or the other to violate. Picking the mbox format to violate means generating a broken mbox, so that's right out. Basically if you want to use an mbox spool to transport the mail then you have a design limitation that precludes you following the POP spec in certain circumstances. I know it turns out your code wasn't involved, but it sounds like you seem convinced you should be trusting on network data to preserve the integrity of Gnus's spool. If that's the case you're asking for all kidns of trouble. Security principles dictate that under no condition should data from the network be trusted such that invalid data would break the client. greg