Re: Force user to use outlook and custom organizational form

From: hint (legend_hint_at_yahoo.com)
Date: 02/20/04


Date: 20 Feb 2004 02:55:30 -0800


"Siegfried Weber" <siegfriedcw@notmail.com> wrote in message news:<u0mGRQ09DHA.1052@TK2MSFTNGP12.phx.gbl>...
> Ken Slovak - [MVP - Outlook] wrote:
> >
> > You have the answer already. Encrypted messages using custom forms are
> > not compatible with mail clients other than Outlook. You either have
> > to send them not encrypted or signed, or change the items to standard
> > IPM.Note messages before you sign or encrypt them.

Problem #1: user is sending an email addressed to both external users
and internal users. Internal users need to see the custom user
properties (need to send using custom form), while external users
cannot have winmail.dat attached (must use plain text). ... headache
>_<

>
> Setting the mesage class back to IPM.Note will cause the message to loose
> the signed/encryped info too (because it is part of the message class). A
> better approach would be to set the recipient address flag to be in plain
> text and not RTF.

Tried that, doesn't work for signed emails sent with custom form. :(

Thanks,
Zhen
>
> --
> Cheers,
>
> Siegfried Weber
>
> If you want a smart answer, ask a smart question
> http://catb.org/~esr/faqs/smart-questions.html
>
> Why tables are bad: http://www.hotdesign.com/seybold/
>
> Note: Please do not send any e-mail to sweber@cdolive.com because I am
> no longer connected with this organization. The current owner does not
> return NDRs (non delivery reports - aka bounce messages) hence you will
> not get any confirmation what happened to the e-mail.



Relevant Pages

  • Re: WSE 3.0 Policy and Encrypting Custom Headers (XML Encryption S
    ... We made a custom assertion, which encrypts custom headers using X509 ... >>> easier to encrypt custom soap headers to conform to the Xml Encryption ...
    (microsoft.public.dotnet.framework.webservices.enhancements)
  • Re: Force user to use outlook and custom organizational form
    ... Encrypted messages using custom forms are ... not compatible with mail clients other than Outlook. ... IPM.Note messages before you sign or encrypt them. ...
    (microsoft.public.exchange.development)
  • Re: WSE 3.0 Policy and Encrypting Custom Headers (XML Encryption S
    ... >> easier to encrypt custom soap headers to conform to the Xml Encryption ... >> localization header, etc). ... WSE 2.0 does allow the body and username ...
    (microsoft.public.dotnet.framework.webservices.enhancements)
  • Re: Please Help me- Creating Custom tokens
    ... But i guess that deals with the client sending a custom token obtained ... from a token issuer and using that to encrypt and sign the requests.. ... >> encrypted token from the server to the client. ...
    (microsoft.public.dotnet.framework.webservices.enhancements)
  • Re: Force user to use outlook and custom organizational form
    ... > not compatible with mail clients other than Outlook. ... > IPM.Note messages before you sign or encrypt them. ... Setting the mesage class back to IPM.Note will cause the message to loose ... If you want a smart answer, ask a smart question ...
    (microsoft.public.exchange.development)