On Sun, Sep 11, 2011 at 6:44 PM, Norman Maurer <[email protected]> wrote: > Hi there, > > I think its time to finally get rid of javamail for sending emails via > SMTP / SMTPS and use something more performant / better suited for > heavy usage. javamail just sucks in many ways for SMTP Delivery in a > way that a real server need it. It just don't expose all the needed > stuff that we need. Like proper de-decting of 5xx code in the greeting > etc.
+1 :-) > So I started to work on a nio based SMTP / SMTPS client, which is > build on top of netty. I think its now ready for a first review: > https://github.com/normanmaurer/niosmtp I'd be happy to see client code for email protocols added to James. (I still find myself using the IMAP client in mailbox-integration-tester. I should really tidy it up...) > It still lacks a few things that we need (also unit tests). Like SMTP > AUTH and STARTTLS but I'm working on it (and I love contributions ;)). > I really want to get it complete and use it as a replacement of > javamail in our "RemoteDelivery" code. I also thing that we should > move the RemoteDelivery code out of the Mailets and use a "real > service" for it. This will make it easier to extend it and also expose > stats etc. So I propose to start to work on a replacement as an > experimental code base atm. We would still ship the old code till we > dedicide that the new one is ready for primetime. +1 :-) > For the new code I plan to allow to hook in custom > "DelayCalculationPolicy" and also add support for notifiers which get > called after each delivery. This will allow us todo smarter things in > the future... > > WDYT ? Sounds good but be careful about pulling into your code base from derivative works Robert --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
