-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, 18 Mar 2013, Steffen Kaiser wrote:
I create a profile manually, import our self-signed root CA cert,& copy
the cert8.db to \defaults\profile\cert8.db . For
notebooks and workstations, that are not administrated centrally, there is
are instal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 13 Mar 2013, Stan Hoeppner wrote:
You simply can't do account auto
configuration with a self signed cert, at least not with a vanilla TB
setup. The only possible solution I can think of would be to preload
the user profile with the certific
On 18/03/2013 03:10, Alex wrote:
https://www.rapidsslonline.com/
less than $20/year, takes literally 15 minutes from start to having
a certificate. Well, maybe 30 minutes the first time when you need
to read everything.
There are probably dozens of other sites offering similar services;
I've us
>> https://www.rapidsslonline.com/
>> less than $20/year, takes literally 15 minutes from start to having
>> a certificate. Well, maybe 30 minutes the first time when you need
>> to read everything.
>>
>> There are probably dozens of other sites offering similar services;
>> I've used this one sev
On 14/03/2013 03:36, Noel wrote:
https://www.rapidsslonline.com/
less than $20/year, takes literally 15 minutes from start to having
a certificate. Well, maybe 30 minutes the first time when you need
to read everything.
There are probably dozens of other sites offering similar services;
I've u
On 3/13/2013 10:23 PM, Alex wrote:
> Hi,
>
>>> Can someone else confirm that restarting Thunderbird is a way around
>>> having to manually import the certs or change them later through the
>>> account settings menu?
>>>
>>> Does anyone have any experience with configuring Outlook to use
>>> self-si
Hi,
>> Can someone else confirm that restarting Thunderbird is a way around
>> having to manually import the certs or change them later through the
>> account settings menu?
>>
>> Does anyone have any experience with configuring Outlook to use
>> self-signed certs?
>
>
> This sounds like you're wo
On 3/13/2013 9:38 PM, Alex wrote:
> Hi guys,
>
It's relatively easy. On first starting TB with no account, cancel the
wizard. The use "Edit" -> "Preferences" or "≡" -> "Options..." ->
"Options..." to get to TB's configuration pages. There, use "Advanced"
-> "Certificates" ->
On 14 Mar 2013 03:38, "Alex" wrote:
>
> Hi guys,
>
> >>> It's relatively easy. On first starting TB with no account, cancel
the
> >>> wizard. The use "Edit" -> "Preferences" or "≡" -> "Options..." ->
> >>> "Options..." to get to TB's configuration pages. There, use
"Advanced"
> >>> -> "Certific
Hi guys,
>>> It's relatively easy. On first starting TB with no account, cancel the
>>> wizard. The use "Edit" -> "Preferences" or "≡" -> "Options..." ->
>>> "Options..." to get to TB's configuration pages. There, use "Advanced"
>>> -> "Certificates" -> "View Certificates" -> "Servers" and fina
Hi guys,
>> It's relatively easy. On first starting TB with no account, cancel the
>> wizard. The use "Edit" -> "Preferences" or "≡" -> "Options..." ->
>> "Options..." to get to TB's configuration pages. There, use "Advanced"
>> -> "Certificates" -> "View Certificates" -> "Servers" and finally
On 3/13/2013 8:01 AM, Phil Turmel wrote:
> On 03/13/2013 01:51 AM, Stan Hoeppner wrote:
>> On 3/13/2013 12:00 AM, Alex wrote:
>
>> I just verified that TB (17.0.4) won't do STARTTLS on TCP 143 without
>> first accepting the self signed cert.
>>
>>> I'm really hoping someone can help me to clarify
On 03/13/2013 01:51 AM, Stan Hoeppner wrote:
> On 3/13/2013 12:00 AM, Alex wrote:
> I just verified that TB (17.0.4) won't do STARTTLS on TCP 143 without
> first accepting the self signed cert.
>
>> I'm really hoping someone can help me to clarify more specifically
>> what's going on here.
>
> Y
Interesting, thanks Prof.
Looks like I have some experimenting to do to see what about:config
options this sets, so I can add them to my list.
On 2013-03-13 2:31 AM, Professa Dementia wrote:
I just verified that TB (17.0.4) won't do STARTTLS on TCP 143 without
first accepting the self sign
On 2013-03-13 12:37 AM, Alex wrote:
Is it conventional to use port 143 for encrypted IMAP connections
these days, and not just 993?
Port 143 uses STARTTLS, port 993 uses SSL/TLS... been that way for a
long time, and yes there is a (slight) difference.
STARTTLS *begins* as an unencrypted sessi
I just verified that TB (17.0.4) won't do STARTTLS on TCP 143 without
first accepting the self signed cert.
I'm really hoping someone can help me to clarify more specifically
what's going on here.
You've already clarified it. You simply can't do account auto
configuration with a self signed
On 3/13/2013 12:00 AM, Alex wrote:
> Hi,
Hi "Alex"
>> I have an fc18 system with postfix and dovecot-2.1.13 and have
>> configured them to use sasl for SMTP Auth and Maildir with imaps.
>>
>> The system is running now, so I'm trying to set up thunderbird to
>> autodetect all settings during the i
Hi,
> I have an fc18 system with postfix and dovecot-2.1.13 and have
> configured them to use sasl for SMTP Auth and Maildir with imaps.
>
> The system is running now, so I'm trying to set up thunderbird to
> autodetect all settings during the initial account setup. However, it
> seems to want to
Hi,
I have an fc18 system with postfix and dovecot-2.1.13 and have
configured them to use sasl for SMTP Auth and Maildir with imaps.
The system is running now, so I'm trying to set up thunderbird to
autodetect all settings during the initial account setup. However, it
seems to want to use port 14
19 matches
Mail list logo