#Powermail webmail how to
#Powermail webmail update
#Powermail webmail upgrade
#Powermail webmail full
#Powermail webmail registration

If you have a certificate generated through the LIR Portal or elsewhere, you will need this certificate in a file for use with OpenSSL. If the mail client that you use regularly does not support S/MIME, you can use OpenSSL to seperately handle signatures and encryption.

#Powermail webmail how to

If you need the certificate in a file to import into the mail client's certificate store see Appendix A1.2 for instructions on how to do this. If you need to generate a new certificate see Appendix A1.1 for instructions on how to do this. No plans found for S/MIME features in the near future. Could not handle an opaque signed then encrypted message Multiple signed messages received also failed. Fails if the encryption is done before the signing. On receiving, only works if the message is signed before encrypting.

#Powermail webmail upgrade

Looks like S/MIME is supported if you upgrade to OS X Panther (No free/demo version available for us to test.) However, when it sends signed or encrypted mail it encodes the message.Ĥ.3 Table of Apple Mac Mail Clients MAIL CLIENT Multiple signed messages received also failed.Īll tests successful, even multiple signings. However on ve-vcs-vcs Outlook reported it as having an invalid digital signature.

Can not handle messages encrypted before signing or double signed messages.įailed to handle received messages signed twice.Ĭould read all valid combinations on receiving. It is not at all clear if the last text line relates to the message you are currently looking at or a previous one. Text appears, and sometimes remains, in a scrolling status bar at the bottom of the screen. There seems to be no clear indication of when messages are signed and/or encrypted, valid or not. Probably the most difficult mail client we tested for clarity. It appears it was supported in past versions but none are available for the current version. However we were unable to find any plugin that support S/MIME. Work in progress, but no timelines.Ĥ.2 Table of Windows Mail Clients MAIL CLIENTĮudora has a plug-in architecture which can support S/MIME.

Requires patching and S/MIME support is very rudimentry. Could not handle an opaque signed then encrypted message.įailed to get the system installed.

(This last point is fixed in later versions of Mozilla) Does not always recognise a valid signature and shows message as NOT signed. The three tables below show the results of the tests for the three platforms used.Ĥ.1 Table of Linux Mail Clients MAIL CLIENTįailed to handle received messages signed twice. All the tests were completed using a certificate generated with the 2048 (High Grade) option. These messages were saved to files and verified using OpenSSL. The second stage involved sending a signed message and an encrypted message from the mail client. The messages were composed using OpenSSL to sign and encrypt them. These messages used clear and opaque signing and encrypting in various combinations. The first stage involved sending a set of precomposed mail messages to the client using sendmail on Linux. This process is described for each mail client in Section 5.

The tested mail client list is shown in Section 7.Īfter installing a mail client, various options and preferences had to be set in order to use S/MIME. We then selected a number of the most commonly used mail clients from the lists across three operating systems, Linux, Windows XP and Apple Mac.

#Powermail webmail full

The two lists can be seen in full in Appendix B1.

#Powermail webmail update

We then did the same analysis on the RIPE Database update logs for the same period. We did not spend a large amount of time trying to exactly match up all variations of some of the more obscure clients. We extracted the information from the X-Mailer: lines and produced an almost unique list with counts of mail clients.

#Powermail webmail registration

This includes messages to Registration Services and the Database Administration. We examined all the messages received by our ticketing system for the period 1 January 2003 to 30 June 2003. The RIPE NCC Software Engineering Department has undertaken a study to evaluate the use of S/MIME by mail clients. A question was raised by some members about how widespread is the compliance of S/MIME within mail clients. This implementation uses the X.509 certificates. At the RIPE 45 Meeting a proposal was presented to implement an additional form of strong authentication for protecting objects in the RIPE Database and to allow for secure communication by e-mail with the RIPE NCC.