> > I tried to communicate many times with the lynx-dev mailing list
> > and did not get any answers. So, I've decided to send some notes to the
I can't find any trace of your articles in my personal archive, but also
note that I've failed to get an article onto the list from my office
account, and my office ISP is on the ORBS open relay black list (they
supplied a firewall system and advised that we didn't do MX delivery
of mail but used their smart host, because the firewall fakes a good
response to the first MX address, even if it turns out to be bad, then
only tries to deliver to that address). (We are not the open relay,
but any customer with an open relay and using the smart host, is enough
to get it blacklisted.)
My guess is that sig.net is using the ORBS list and failing to bounce
rejected messages properly, but I haven't done controlled tests.
> > I tried to communicate many times with the lynx-dev mailing list
> > about SSL (which does not work for me). Any idea about where the Email went
The licence on Lynx is incompatible with the inclusion of patented software
for which royalties are payable by some users; therefore it is not possible
to legally distribute SSL binaries; you must compile them yourself, using
the RSAREF library for the patentend bit (not pure SSLeay/OpenSSL) for
non-commercial use, and royalty paid commercial versions of the RSA libraries
for commercial use.
Note that there is a CERT buffer overrun alert on RSAREF v2.
There are also issues to do with export control, although these have been
considerably relaxed over the last 12 months.
