[continued from previous message]   
      
   >all participants in your WME network to the list along with the corresponding   
   key   
   >and - if it's a private key of your own - the passphrase. Based on this list,   
   if   
   >WME is active, all mails, whether sent normally or by one of your nyms, are   
   >examined for the presence of corresponding encryption keys. If OmniMix finds   
   keys   
   >for all 'To:' and 'Cc:' recipients and there are no 'Bcc:' recipients (who   
   would   
   >be uncovered by an encryption using their keys), the mail gets encrypted and   
   only   
   >header data mandatory for delivery are left outside the protected block. At   
   >request the sender's signature is added in the course of the encryption to   
   prove   
   >the authenticity of the sent mail.   
   >Finally you have to tell OmniMix, who's allowed to use the single private key   
   /   
   >password combinations to sign outgoing and decrypt incoming WME mails.   
   Therefore   
   >go to the 'User' tab and mark for every user the 'WME' mail addresses that   
   belong   
   >to that account.   
   >Now you've finished. All outgoing mails are processed dependent on the WME   
   mode   
   >('WME' tab, 'disabled' / 'enabled' / 'required'). If a message has to depart   
   from   
   >that rule, then use the according header directive. 'O-WmeSend-Mode: required'   
   >e.g. rejects a message that can't be WME encrypted, with 'O-WmeSend-Mode:   
   >disabled' you would even be allowed to send a usual anonymous mail to someone   
   >whose key is present at the WME keys list. The 'Sign' setting within the WME   
   >participants list is binding in any case. Therefore, if signatures are   
   requested,   
   >the WME encryption has to fail as long as the password isn't properly set for   
   the   
   >WME key or the WME item isn't assigned to the user account.   
   [end quoted plain text]   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)