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|59421]: 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:07:39 +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|59421]: Connection timed out)
Remote-MTA: dns; ipebio15.ise.pw.edu.pl (194.29.161.106|25|194.29.160.2|59421)
Last-Attempt-Date: Mon, 23 Jul 2001 04:15:35 +0200
Reporting-MTA: dns; elektron.elka.pw.edu.pl Arrival-Date: Thu, 19 Jul 2001 11:07:39 +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|59421]: Connection timed out) Remote-MTA: dns; ipebio15.ise.pw.edu.pl (194.29.161.106|25|194.29.160.2|59421) Last-Attempt-Date: Mon, 23 Jul 2001 04:15:35 +0200
Slamou alycom,Verify that IIS 4 use keys with lenght higher than 512 bits, if not upgrade your version of IIS.
Haikel MEJRI
David a écrit :
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
