Hi, There is no binding for Spring (and thus default James server) for webadmin. In order to use webadmin one need to rely on Guice products.
Best regards On 2/20/19 9:20 PM, Raphael OUAZANA wrote: > Hi Jeffrey, > > You are trying to contact James on port 25, which is for SMTP. > > Webadmin is listening by default on port 8000. > > Regards, > Raphaël. > > Le 2019-02-20 13:59, Marans.Jeffrey a écrit : >> Hi Raphael. >> >> I’m using james-server-app-3.2.0. >> >> Path is /opt/cibids/james-server-app-3.2.0 and I wonder if I’m missing >> some syntax. >> >> >> >> curl -XPATCH >> http://172.16.251.133:25/mailRepositories/var%2Fmail%2Ferror%2F/mails?action=reprocess >> >> >> >> >> 220 irc JAMES SMTP Server Server (JAMES SMTP Server ) ready >> >> 500 5.5.1 Command PATCH unrecognized. >> >> 500 5.5.1 Command USER-AGENT: unrecognized. >> >> 500 5.5.1 Command HOST: unrecognized. >> >> 500 5.5.1 Command ACCEPT: unrecognized. >> >> 500 5.5.1 Command unrecognized. >> >> >> >> >> >> Jeffrey Marans >> >> >> >> >> >> >> >> -----Original Message----- >> From: Raphael OUAZANA [mailto:raphael.ouaz...@linagora.com] >> Sent: Tuesday, February 19, 2019 3:47 PM >> To: James Users List <server-user@james.apache.org> >> Cc: Craig Cudmore <cr...@cudmore.ca> >> Subject: Re: how to resubmit failed messages >> >> >> >> Hi, >> >> >> >> Nice trick, but there is now a simpler way to achieve this. >> >> >> >> We tend to prefer webadmin now than cli for new features (cli will >> probably be replaced by webadmin in a future version). So with >> webadmin you can easily reprocess a mail repository, see here: >> >> http://james.apache.org/server/manage-webadmin.html#Reprocessing_mails_from_a_mail_repository >> >> >> >> >> Regards, >> >> Raphaël. >> >> >> >> Le 2019-02-19 19:37, Craig Cudmore a écrit : >> >>> Here's a high-level list of steps you need to re-process rejected >> >>> message: >> >>> 1) Configure your mailetcontainer.xml to have a mailet like: >> >>> <mailet >>> match=:"RecientIs=trig...@mail.com<mailto:RecientIs=trig...@mail.com>" >>> class="FromRepository"> >>> >> >>> >>> <repositoryPath>file://var/mail/error</repositoryPath<file:///\\var\mail\error%3c\repositoryPath>> >>> >> >>> <processor>process</processor> >> >>> <delete>true</delete> >> >>> </mailet> >> >>> >> >>> This mailet will look for mails that are being sent from >> >>> trig...@mail.com<mailto:trig...@mail.com> and if it finds one, it >>> will throw away the trigger >> >>> message and tell James to grab any messages in the /var/mail/error >> >>> queue to re-process. >> >>> >> >>> 2) Restart James. The reader pointer in the FromRepository needs to be >> >>> reset back to the beginning of the error queue. If you're using a >> >>> database for your repository you likely won't need this step. >> >>> >> >>> 3) Send a message to james to >>> "trig...@mail.com<mailto:trig...@mail.com>". >> >>> >> >>> Then James should reprocess any messages in the error queue. >> >>> >> >>> On Tue, Feb 19, 2019 at 1:24 PM cryptearth >>> <cryptea...@cryptearth.de<mailto:cryptea...@cryptearth.de>> >> >>> wrote: >> >>> >> >>>> Hey Jeffrey, >> >>>> >> >>>> this awnser could be wrong as I don't now for sure, but I guess once >> >>>> a mail is filtered into one of the error-directories - it's out of >> >>>> the queue. But I could be wrong because the mails stored as >> >>>> serialized java objects - wich also should be able to be read in back >> >>>> again for further processing. But as re-processing would need some >> >>>> action by the user or an admin - there's no command to reprocess >> >>>> filtered-out messages - at least it doesn't show up for james-cli.sh. >> >>>> >> >>>> Matt >> >>>> >> >>>> Am 19.02.2019 um 19:17 schrieb Marans.Jeffrey: >> >>>> > I'm setting up a proof of concept mail system using apache james >> >>>> > 3.2 >> >>>> with minimal mods. >> >>>> > I have a Postal load test server that sends to a james relay which >> >>>> forwards the email to a second james server. The latter persists the >> >>>> messages into a MySQL database. >> >>>> > During testing I turn off various components, and I've found >> >>>> undeliverable messages accumulating in the second server >> >>>> james/var/mail/error directory when the db server is off-line. >> >>>> > How do I get james to reprocess the messages? >> >>>> > >> >>>> > Regards, >> >>>> > Jeffrey Marans. >> >>>> > >> >>>> > >> >>>> >> >>>> >> >>>> --------------------------------------------------------------------- >> >>>> To unsubscribe, e-mail: >>>> server-user-unsubscr...@james.apache.org<mailto:server-user-unsubscr...@james.apache.org> >>>> >> >>>> For additional commands, e-mail: >>>> server-user-h...@james.apache.org<mailto:server-user-h...@james.apache.org> >>>> >> >>>> >> >>>> >> >> >> >> --------------------------------------------------------------------- >> >> To unsubscribe, e-mail: >> server-user-unsubscr...@james.apache.org<mailto:server-user-unsubscr...@james.apache.org> >> >> >> For additional commands, e-mail: >> server-user-h...@james.apache.org<mailto:server-user-h...@james.apache.org> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org > For additional commands, e-mail: server-user-h...@james.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org For additional commands, e-mail: server-user-h...@james.apache.org
