On Tuesday 18 March 2003 18:25, Peter Donald wrote: > On Tue, 18 Mar 2003 20:52, Niclas Hedhman wrote: > > At the moment, I'm handling > > > > * Multiple destinations (TO, CC and BCC) > > * Single layered Text or Binary Attachments, i.e. no MultiPart > > Multiparts. * Convinience interfaces for sending simple text messages. > > > > This Block will be made available to Avaloners later (somehow). > > kool. > > > I would like to enquiry if anyone has any wishlist of features they would > > like to have in the initial release. > > How abstract is the transport layer? ie Could I configure something to be > delivered to local mail stores?
Well, as the codebase currently IS (3-4 years old), it relies entirely on the Java Mail API for Transport. Java Mail API allows for pluggable Transports, but I think only SMTP is available at the moment. A search on the net could reveal otherwise. OTOH, it is fairly easy in Java Mail API to "send" a message to any OutputStream, and MY MailTransporter is interface/impl separated, and I have just made it an Avalon component. The Mailer (another component) uses the MailTransporter for the sending of the mail itself. The Mailer can be changed to dynamically lookup a MailTransporter, according to configuration. Niclas --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
