On Tue, Nov 11, 2008 at 11:47:34AM -0500, Carlos Williams wrote:
> On Mon, Nov 10, 2008 at 9:20 PM, Victor Duchovni
> <[EMAIL PROTECTED]> wrote:
> >> On Mon, Nov 10, 2008 at 5:26 PM, Noel Jones <[EMAIL PROTECTED]> wrote:
> >> > If your existing verisign certificate is a "server" type certificate w
On Mon, Nov 10, 2008 at 9:20 PM, Victor Duchovni
<[EMAIL PROTECTED]> wrote:
>> On Mon, Nov 10, 2008 at 5:26 PM, Noel Jones <[EMAIL PROTECTED]> wrote:
>> > If your existing verisign certificate is a "server" type certificate with
>> > the right FQDN, you should be able to use it with postfix.
I bel
On Mon, Nov 10, 2008 at 06:36:53PM -0500, Carlos Williams wrote:
> On Mon, Nov 10, 2008 at 5:26 PM, Noel Jones <[EMAIL PROTECTED]> wrote:
> > Yes, the FQDN of the server is encoded in the certificate. If you rename
> > the server, you must get a new certificate (or generate a new one if
> > self-
On Mon, Nov 10, 2008 at 5:26 PM, Noel Jones <[EMAIL PROTECTED]> wrote:
> Yes, the FQDN of the server is encoded in the certificate. If you rename
> the server, you must get a new certificate (or generate a new one if
> self-signed).
>
> If your existing verisign certificate is a "server" type cert
Carlos Williams wrote:
It appears that my postfix server is using invalid TLS certs from
/etc/postfix/main.cf. When I set up my client to use TLS, I get an
invalid certificate error from Outlook that tells me the hostname and
domain of the server which are wrong. I renamed the FQDN at some point
It appears that my postfix server is using invalid TLS certs from
/etc/postfix/main.cf. When I set up my client to use TLS, I get an
invalid certificate error from Outlook that tells me the hostname and
domain of the server which are wrong. I renamed the FQDN at some point
however I must have re-us
