-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Pollywog wrote: > > Mine says this, but I applied the 3 in 1 patch that I learned about in this > thread: > > > sending: 'User: anonymous\nTime: 1134325707\nSig: > 177d0df77c0b91197da93b41c85c4f5f3d9b823b\n\nOp: ping\nThread: 31207\nPV: > 2.0\n\n' > received: 'Thread: 31207\nCode: 200\nDiag: OK\nPV: 2.0\n\n' > 66.250.40.33:24441 (200, 'OK') > > > 8)
In the time of our lil' conversation pyzor got back from dead and it's functioning properly now. The thing I ment was that the pyzor suddenly died few days ago, and finnaly got back this afternoon; applying a patch has nothing to do with the server response by itself, the patch is for some "unusual" strings that can be found in the email (and that caused the error message) in process of making a digest of it before checking for matches with the pyzor server. - -- Regards, SickBoy <sickboy at blupill dot com> # Encrypted/Signed Mail Preferred. # Public Key ID: 0x2C6FC5FE (Available on key servers) # 61A4 EE81 CDA3 52AB 04F3 3F4A CB3B B6D5 2C6F C5FE -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (MingW32) iD8DBQFDnHQXyzu21Sxvxf4RAq6eAJ0b/MlEv1iIFnIGTlryF7eykjOAZgCfYRNn rzeo8QSM6kAlrbXqeHQQ6L0= =Dw4S -----END PGP SIGNATURE-----
