Hallo

thanks so lot

> -----Original Message-----
> From: pficabdyi-mxhgu42kq73w.ml@delegate.org [mailto:pficabdyi-mxhgu42kq73w.ml@delegate.org]
> Sent: Tuesday, December 16, 2003 12:14 AM
> To: pficabdyi-mxhgu42kq73w.ml@delegate.org
> Cc: pxueqbdyi-mxhgu42kq73w.ml@delegate.org
> Subject: Re: [DeleGate-En] RPC over SSL to http - - http to 
> RPC over SSL
> 
> 
> On 12/16/03(00:01) you "Lepczynski, Bernd" 
> <pxueqbdyi-mxhgu42kq73w.ml@delegate.org> wrote
> in <_A2503@delegate-en.ML_>
>  |Thanks for that hint you gave me before.
>  |
>  |Now RPC seems to be working , but another http error:
>  |
>  |12/15 15:47:11.06 [1296] 2+1: HTTP error status: 503 RPC Error: 6BA
> ...
>  |We had checked the staus error 503. This means that the 
> process is closed
>  |because of an Error in header.
> 
> As long as I know, the error code 503 means that the server 
> is not available.


I'll check this 503 Error today again.


> [RFC2616 HTTP/1.1]
> 
> I don't understand why you use two DeleGates just to relay 
> HTTPS to HTTPS.
> It can be done simply, without concering with SSL nor HTTP, like this:
> delegated -P443 
> SERVER=tcprelay://rpc-over-https-server:443 ADMIN=xxx
> 
The answer: 
at the mailclient we have to start with SSL+(RPC_over_HTTP)--> Outlook 2003.
So we present an certifikate made only for the incomming connection.
In the middle (like man in the middle) we have to check the email (and Stuff
comming over WebDAV)
for virus and attachments.
At the End we have to connect to the RPC-over_HTTP_Server with SSL --> IIS 6
and we accept the certificate from that server.
There seems to be no way out. We have to start with SSL an End at SSL, but
in the middle we have to check the email directly .

Best regards

Bernd