-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

This might be slightly off topic, but it's a question to which I'd be  
interested to hear the views of those on this list.

I'm experimenting with PGP signing and encrypting emails (as I hope  
you'll be able to see!). The commercial PGP application works by  
sitting as a proxy on the client machine - intercepting traffic  
between both the email client and the IMAP server, and the email  
client and the SMTP server. The PGP engine will encrypt/decrypt/sign/ 
authenticate as required "invisibly".

I'm sure there are many views both for and against the way that PGP  
have chosen to implement their technology. However, it's raised a  
question for me. That is, when my email client sends an email using  
SMTP, that email gets intercepted and modified before being sent to  
the recipient. However, my email client will use IMAP to keep a copy  
of that email in my sent items folder. So, the items in the sent  
folder are therefore not exactly what was actually sent.

I'm looking to use PGP as much as a tool for an authenticated audit  
trail as anything else. So, there's a problem I think. My "sent items"  
never include my PGP signature. I can see that this would also happen  
whenever a setup is configured to add to an email - for example, those  
disclaimers many organistations append to messages.

So, what's the view on this? Can I get around it? The only way I can  
think is to BCC myself on every message, but that seems a bit clunky.

Thanks in advance

Simon

[EMAIL PROTECTED]



-----BEGIN PGP SIGNATURE-----
Version: PGP Desktop 9.9.0 (Build 397)
Charset: US-ASCII

wj8DBQFJLSqPVZXZp4J8rUERAiRoAJ9vbV1ScyfFqDeEEJZjt8x+Z6xi9ACgq1Ba
sFL1z4INX2RwITfngr+EmJU=
=Z6gi
-----END PGP SIGNATURE-----
_______________________________________________
Imap-uw mailing list
Imap-uw@u.washington.edu
http://mailman2.u.washington.edu/mailman/listinfo/imap-uw

Reply via email to