[Enigmail] Enigmail on TB 3.0b1 not functional

[John Clizbe]

Valery Kondakoff wrote:
> On 28.12.2008 22:17, Robert J. Hansen wrote:
> 
>> To get key 0xFEAF8109, try:
>> http://pool.sks-keyservers.net/pks/lookup?op=get&search=0xFEAF8109
> 
> Got the idea. Here is the right URL:
> http://pool.sks-keyservers.net:11371/pks/lookup?op=get&search=0xFEAF8109

Depends, sort of.

Rob's URL is correct for an increasing number of keyservers which also listen on
port 80 as well as HKP's default port of 11371. At last count, this was 15 out
of 38 as surveyed at Peter Pramberger's SKS Network Status page:
http://www.pramberger.at/peter/services/keyserver/network/

It's best to always specify port 11371 with a wildcard DNS aggregate such as
pool.sks-keyservers.net. (The network survey routine at sks-keyservers.net
_only_ checks availability of port 11371.)

The port may be safely omitted if one is specifying a single keyserver by name
or using a smaller DNS round-robin in which all servers also are known to listen
on port 80.

-- 
John P. Clizbe                      Inet:John (a) Mozilla-Enigmail.org
You can't spell fiasco without SCO. hkp://keyserver.gingerbear.net  or
     mailto:pgp-public-keys at gingerbear.net?subject=HELP

Q:"Just how do the residents of Haiku, Hawai'i hold conversations?"
A:"An odd melody / island voices on the winds / surplus of vowels"

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 680 bytes
Desc: OpenPGP digital signature
URL: <http://www.mozdev.org/pipermail/enigmail/attachments/20081228/04209752/attachment.bin>