On 10-Sep-2006 8:32, [EMAIL PROTECTED] wrote:
> Any chance of adding support for 3.1.5? (Currently fails with "dns:
> query failed: 5.1.3.saupdates.openprotect.*com* => NXDOMAIN".)
We've already added txt record for the 3.1.5 release and it should work now.
Thanks. Indeed, it works fine n
Hi,
> gpg --armor
--export KEYID
>
> the man page is amazingly helpful ;-)
Thanks, that was helpful. The instructions have been updated to use
this technique instead of copying the entire public key ring of root.
cheers,
skar.
--
OpenProtect - The email virus/spam filter
http://openprotec
Hi,
> Any chance
of adding support for 3.1.5? (Currently fails with "dns:
> query failed: 5.1.3.saupdates.openprotect.com
=> NXDOMAIN".)
We've already added txt record for the 3.1.5 release and it should
work now.
cheers,
skar.
--
OpenProtect - The email virus/spam filter
http://openpr
Hi,
On 24-Aug-2006 0:16, [EMAIL PROTECTED] wrote:
This is to notify you about another SARE channel with the most used
rules available as a single channel. If you're not the type to try every
single rule in SARE and manually select them, you can instead use this
single channel instead.
(sn
On Aug 24, 2006, at 7:26 AM, [EMAIL PROTECTED] wrote:
Yes, downloading the gpg and using "sa-update import" doesn't have
that problem though. So, how to extract this public key alone from
the public key ring to copy over to the sa-update public key ring?
Any idea on this is welcome :)
gp
Justin Mason wrote:
hey, btw, it might be better to extract the gpg public key from "gpg",
instead of copying over the entire public key ring -- since that will (a)
overwrite any existing SA-update keys, including the system ones,
and (b) will trust any existing GPG correspondents to publish SA
