Delivery reports about your email

[The Post Office]

This is a collection of reports about email delivery
process concerning a message you originated:

<smtp ipebio15.ise.pw.edu.pl [EMAIL PROTECTED] 1284>: ...\
        expired after 3 days, problem was:
        smtp; 500 (connect to ipebio15.ise.pw.edu.pl 
[194.29.161.106|25|194.29.160.2|60912]: Connection timed out)

Following is a copy of MESSAGE/DELIVERY-STATUS format section below.
It is copied here in case your email client is unable to show it to you.
The information here below is in  Internet Standard  format designed to
assist automatic, and accurate presentation and usage of said information.
In case you need human assistance from the Postmaster(s) of the system which
sent you this report, please include this information in your question!

        Virtually Yours,
                Automatic Email delivery Software

Reporting-MTA: dns; elektron.elka.pw.edu.pl
Arrival-Date: Thu, 19 Jul 2001 11:10:00 +0200

Original-Recipient: rfc822;[EMAIL PROTECTED]
Final-Recipient: RFC822;[EMAIL PROTECTED]
Action: failed
Status: 5.4.1 (TCP/IP-connection failure)
Diagnostic-Code: smtp; 500 (connect to ipebio15.ise.pw.edu.pl 
[194.29.161.106|25|194.29.160.2|60912]: Connection timed out)
Remote-MTA: dns; ipebio15.ise.pw.edu.pl (194.29.161.106|25|194.29.160.2|60912)
Last-Attempt-Date: Mon, 23 Jul 2001 04:18:35 +0200


Reporting-MTA: dns; elektron.elka.pw.edu.pl
Arrival-Date: Thu, 19 Jul 2001 11:10:00 +0200

Original-Recipient: rfc822;[EMAIL PROTECTED]
Final-Recipient: RFC822;[EMAIL PROTECTED]
Action: failed
Status: 5.4.1 (TCP/IP-connection failure)
Diagnostic-Code: smtp; 500 (connect to ipebio15.ise.pw.edu.pl [194.29.161.106|25|194.29.160.2|60912]: Connection timed out)
Remote-MTA: dns; ipebio15.ise.pw.edu.pl (194.29.161.106|25|194.29.160.2|60912)
Last-Attempt-Date: Mon, 23 Jul 2001 04:18:35 +0200

---

The private key format for IIS4 is different. Use this to convert it

 

openssl rsa -in holly.pem -out holly.net.key -outform NET

 

You'll be prompted for a password. In the case of IIS you can use one as I think it is stored in the SAM database (no doubt someone will correct me). Please note that IIS4 must run with administrator privileges to support SSL (yuk!).

 

Also, if you are using a "wildcard" certificate, it appears that IIS4 won't use it if it is self-signed. (Once I get our new certificate, I'll be able to verify this).

-
John Airey
Internet Systems Support Officer, ITCSD, Royal National Institute for the Blind,
Bakewell Road, Peterborough PE2 6XU,
Tel.: +44 (0) 1733 375299 Fax: +44 (0) 1733 370848 [EMAIL PROTECTED]

-----Original Message-----
From: David [mailto:[EMAIL PROTECTED]]
Sent: 19 July 2001 09:12
To: [EMAIL PROTECTED]
Subject: OpenSSL and IIS4

Hey,

I am trying to setup https on IIS4 by using OpenSSL, I follow steps:
1. Create private key
    openssl genrsa -des3 > holly.pem
2.Generate a CSR from your key
    openssl req -new -key holly.pem  > holly.csr
3. Generate a self-signed certificate
    openssl req -x509 -key holly.pem  -in holly.csr > holly.crt
4. From IIS4 key Manager select import key file: holly.pem and cert file:holly.crt.
I got error: wrong password.

I am sure that I use exactly the same password, so what  real problem is?
anyone has this experience.

Thanks
 

---