Hi Philip, This was the same problem that we encountered. I didn't know about TurbineMailService so went the Screen (java) -> Javamail route. For velocity stuff a facade object on a Message seems to work, it makes the templating alot easier to do, but maybe this is what you wanted to avoid doing ( custom objects). Will you be using SSL for secure access to mail servers? That seemed a little tricky to get working. Regards, Malcolm Kendall
-----Original Message----- From: Philip S. Wachtel [mailto:[EMAIL PROTECTED] Sent: 08 July 2003 19:02 To: Turbine Users List Subject: Turbine Architecture Question Hi there, I'm trying to find an answer to a design question. I would like to build a web interface to an IMAP/SMTP server. Think hotmail. At first, I thought it would make sense to create a mail service the screens could use to access the IMAP and SMTP server. Now, however, I'm losing confidence in that idea because I can't find a way to really hide the workings of Javamail, which is what I'm using. My layers, as I saw it, were: Screen (vm) --> Screen (java) -- > TurbineMailService --> Javamail -(IMAP/SMTP proto)-> Mail Server But, the problem is that the TurbineMailService would wind up having to convert Javamail objects to custom objects for the screens. This just doesn't make sense to me. So, the bottom line questions is, what would be a better approach to this? I could just use the Javamail tools directly in the screens? Seems messy, but more straight forward. Thanks for your suggestions. Regards, Philip
