On 30 Sep 2010, at 18:51, Eric Charles wrote:

You can use a custom mailet (you need to develop it) to encrypt incoming mails before they arrive in the mail repository.

For the decryption part when a user consults his mailbox via pop3/ imap4, there is no mailet equivalent... For James 3, you could overwrite (develop your own) org.apache.james.pop3server.core.CoreCmdHandlerLoader defined in pop3server.xml, and org.apache.james.imap.processor.main.DefaultImapProcessorFactory defined in spring-beans.xml. I'm not sure how to do it in James 2.3, except hacking James internals.

Thank you, I thought this would be one option. ATM we've been working with 2.3.

On 30 Sep 2010, at 19:43, Norman Maurer wrote:

You would need to
implement your own mailbox store. If you just start up I would suggest
you to have a look at latest mailbox-api / mailbox-store for this.

Another possibility too.

On 30 Sep 2010, at 20:45, Ranjib Dey wrote:

but from your email it seems you want to store
the mails encrypted only in the server, in such case even file system
encryption should suffice (which is supported by any modern file system).

I don't want the server that the files are stored on to have access to the mail. I'm looking at an architecture where we use one externally- managed database on SAN storage for mail for very high availability, uptime, scalability and redundancy, but multiple secure mail servers feeding it.

Is there such a thing as an encrypting JDBC (meta)connector? Such a thing might be configured in config.xml and simply encrypt data going through it to another JDBC connection (probably quite hard as only certain columns could be encrypted, otherwise a WHERE clause won't work). This would have the advantage of potentially being usable for encrypting other data, e.g. the user database. The only stuff I can find is about encrypting the link to the database - not so much of an issue for me.

Can Jasypt be applied by configuration? or would it require a re-write of the mailstore access code? As you can tell, I haven't waded into the code that accesses the mailstore yet.

many thanks,

Michael


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to