Hi. I don't have something to add to this thread specifically, but I would like to point out that:
GIven the discussion around the specific topics I think we are getting our documentation. All we need to do now is copy paste it, curate it and edited in asciidoc format. I'll even put in the links to he mailing list archive / thread as reference. @David: If you can do just that: ask questions and compile the answers it would be a huge win for us. You don't even have to be very creative about it: it's good material. Once I'm done with the automation I would like for us to 'get together' in a (virtual) party and migrate the old website and get the new one out the door. Also, I'll try to find some time in the next days to work together on some specific tasks I believe it will be better than alone :). Regards, La 08.07.2020 11:49, Tellier Benoit a scris: > Le 08/07/2020 à 15:33, David Leangen a écrit : >> Thanks. >> >> I love this James adventure. It is not boring. Every time I scratch the >> surface, a new concept pops out. 😀 >> >> Ok, so digging in… > :-) >>> Also as Matthieu said, RemoteDelivery is a side effect of the current >>> Processing chain. >> I looked at org.apache.james.transport.mailets.RemoteDelivery, with the >> assumption that it is the correct Mailet. > Correct >> First, the javadoc says: >>> The RemoteDelivery mailet delivers messages to a remote SMTP server able to >>> deliver or forward messages to their final destination. >> That is consistent with what you wrote. So I looked at the code to try to >> get a sense of *how* it does this. > Ouch. Complex and old code relying on javax.mail is waiting you ^^ >> What I could gather is that the magic is actually done with >> org.apache.james.queue.api.MailQueue. All RemoteDelivery does is enqueue the >> Mail, then it’s done. > It do start DeliveryRunnable that consume the outgoing queue. Relaying > happens there. >> So the queue-api seems now quite important. > I confirm it is. >> I also gather that it is the same queue that accepts mails from the incoming >> SMTP Service in the figure. However, by looking at the api code and the >> sparse javadocs that come with it, I am getting few clues as to what it does >> or how it works. >> >> I can only guess that the actual heavy lifting is done with an >> implementation that gets wired with Guice. > It is guice agnostic. Look inside RemoteDelivery::init... >> I will investigate further, but in the meantime, can somebody please point >> me in the right direction to help speed up my journey? >> > Did I just do that or you need more information? > > Cheers, > > Benoit > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org > For additional commands, e-mail: server-dev-h...@james.apache.org > -- Eugen Stan +40720 898 747 / netdava.com
<<attachment: eugen_stan.vcf>>
signature.asc
Description: OpenPGP digital signature
