Yes you are correct on the format of the matcher. I was doing it from memory…
Is the matcher near the beginning of the mailetcontainer.xml? It needs to be in the right place in the message processing flow that the message to trigger gets processed before going to the main processor. You can always put in some LogMessage calls to write debug the process flow and make sure you’re trigger message is being processed in the right sequence. > On Feb 20, 2019, at 9:00 AM, Marans.Jeffrey <jeffrey.mar...@cic.gc.ca> wrote: > > Hi Craig. > > I think the match line you suggest below should read <mailet > match="RecipientIs=trig...@ircc.caa" class="FromRepository"> > > > > James starts without error and when I send message to > trig...@ircc.caa<mailto:trig...@ircc.caa> it’s delivered as you see below, > but the error directory isn’t reprocessed. I’ve tried using the absolute and > relative paths to the error directory. > > > > I can’t find anything in the docs regarding resetting the “reader pointer in > the FromRepository”. > > > > Jeff. > > > > > > -----Original Message----- > From: Craig Cudmore [mailto:cr...@cudmore.ca] > Sent: Tuesday, February 19, 2019 1:38 PM > To: James Users List <server-user@james.apache.org> > Subject: Re: how to resubmit failed messages > > > > 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 For additional commands, e-mail: server-user-h...@james.apache.org
