-----BEGIN PGP SIGNED MESSAGE----- Wasn't it claimed that 2.53 was safe -- only earlier versions (alpha/beta?) were at risk? Seems like they should just release another version to lessen the confusion. Scott -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBOSwjblpGPE+AF6qBAQEiZwQAvICxK3K0VPNxX4v7agjf5owZ6ZtDPC9r 3egzkz30iQDHNSTNskPC8IQlVV4PBgthIjY7rJvFQBzE9zgRevF0MVvQ4+WdAeyM YLLl72l3pqr0y70qWfD72+6EyRwscb2yBaIvNK6Vk3/t58i8anL0iQO0aeIQYrvL cbNH+O6S74w= =ZbNr -----END PGP SIGNATURE-----
- Qpopper 2.53 remote problem, ... John Gonzalez/netMDC admin
- Re: Qpopper 2.53 remote problem,... Scott D. Yelich
- Re: Qpopper 2.53 remote prob... John Gonzalez/netMDC admin
- Re: Qpopper 2.53 remote ... Russ Allbery
- Re: Qpopper 2.53 rem... listy-dyskusyjne Krzysztof Dabrowski
- Re: Qpopper 2.5... John Gonzalez/netMDC admin
- Hmmm. TLS p... Magnus Naeslund
- Re: Hmm... Magnus Bodin
- Re: Hmm... A.L.
- Re: Qpopper... Russ Allbery
- Re: Qpo... John Gonzalez/netMDC admin