I've looked at 3.3 vs 3.4 sending test emails on the same server. Version 3.3 has 'spooler' threads delivering the messages:
01-Apr-2020 11:29:10.182 INFO [spooler-6] org.apache.james.transport.mailets.jsieve.delivery.SieveExecutor.sieveMessage:127 - Can not locate SIEVE script for user <[email protected]> 01-Apr-2020 11:29:10.318 INFO [spooler-3] org.apache.james.transport.mailets.delivery.SimpleMailStore.storeMail:98 - Local delivered mail Mail1585765747386-5acd8b26-a879-4788-9af2-80d93f3b96e3 successfully from root@localhost to <[email protected]> in folder INBOX with composedMessageId ComposedMessageId{mailboxId=2, messageId=DefaultMessageId{}, uid=MessageUid{uid=3}} 01-Apr-2020 11:29:10.371 ERROR [spooler-7] org.apache.james.transport.mailets.ToSenderFolder.doService:88 - Local delivery with ToSenderFolder mailet for mail Mail1585765748298-b3bc33aa-e270-4ffe-846d-c559c3132a7c with sender root@localhost in folder Sent In version 3.4, I don't see any log entry for 'spooler' thread even though you can see them created in org.apache.james.mailetcontainer.impl.JamesMailSpooler.init @PostConstruct public void init() { LOGGER.info("init..."); queue = queueFactory.createQueue(MailQueueFactory.SPOOL); spooler = Schedulers.fromExecutor(Executors.newFixedThreadPool(numThreads, NamedThreadFactory.withName("spooler"))); LOGGER.info("uses {} Thread(s)", numThreads); run(); } On Mon, Mar 16, 2020 at 1:40 PM joe <[email protected]> wrote: > I have taken same route. unable to get 3.4.0 to do anything, so > > I have fallen back to 3.3.0 > > On 3/16/20 11:52 AM, [email protected] wrote: > >> Hi Joe, this is weird, which product did you use? (distributed James, > >> Spring James, ...) ? > > This looks like the same problem that I and another couple of people > mentioned here. I was using > > > > > https://downloads.apache.org/james/server/3.4.0/james-server-app-3.4.0-app.zip > > > >> Are you sending or receiving message? Could you put some logs, even they > >> are debugs, looking at the mailet processing pipeline might give us some > >> ideas > >> > > What I found was that if you sent a mail the logs reported it as being > spooled, but it was never delivered to the inbox. No error message and the > same failure if mail was sent from a local or remote user. I now have > version 3.3.0 running and mail is sent and delivered reliably. > > > > -- > > David Matthews > > [email protected] > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
