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|47692]: 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: Fri, 20 Jul 2001 02:59:44 +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|47692]: Connection timed out)
Remote-MTA: dns; ipebio15.ise.pw.edu.pl (194.29.161.106|25|194.29.160.2|47692)
Last-Attempt-Date: Mon, 23 Jul 2001 10:09:42 +0200


Reporting-MTA: dns; elektron.elka.pw.edu.pl
Arrival-Date: Fri, 20 Jul 2001 02:59:44 +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|47692]: Connection timed out)
Remote-MTA: dns; ipebio15.ise.pw.edu.pl (194.29.161.106|25|194.29.160.2|47692)
Last-Attempt-Date: Mon, 23 Jul 2001 10:09:42 +0200

---

 
Now I am able to install key generated by OpenSSL from IIS key manager
by converting format to IIS format. (Thanks Lisle and John)

Then I did  follow steps.
1. Add my ip(203.1.1.1) and port(443) to keymanager and save changes.
2. Select a virtul directory (download) and update properties with
    Select  'Require Secure Channel'  and 'Do not accept certificates' option
3. Restart IIS.

Then when I try URL:
http://203.76.4.111/download
Error: it tell me not authorized
*why? I did not select require client cert option.

try another
https://203.76.4.111/download
Error: The page cannot be displayed
*why? I already add my ip and port to key manager.

I change option to 'Require Client Certificates' then try URL again,
It still give me same error instead of popup a requre cert window.
If I use this option, do I need to install the same cert into my browser in order to access my secure directory?

What am I doing wrong here?

Thanks.
David

David wrote:

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
 

---