Ok, at the end, I found what my problem was. I'm ashamed to admit, the
problem was between the keyboard and the chair, thus me.
This are the gotchas:
- I created the folder process under inbox, but with the command
copyTo=process I'm actually referring to a folder at the root of the email
folder
Hi Claus,
thanks for the info! But it looks like the problem is somewhere else.
I tried to:
- create a class that implements
org.apache.camel.component.mail.MailBoxPostProcessAction but that interface
is not existent, so the compiler says
org.apache.camel.component.mail.MailBoxPostProcessAction
Oh Claus,
I see!!! I'm very sorry I didn't notice the release is different!!!
Ok, so never mind about the postProcessAction issue, when the 2.15 camel
release will be available on maven I'll consider upgrading.
What remains open is why the copyTo parameter doesn't work in my route.
Thanks a
Hi
See this unit test
https://github.com/apache/camel/blob/master/components/camel-mail/src/test/java/org/apache/camel/component/mail/MailPostProcessActionTest.java
On Tue, Jan 6, 2015 at 10:40 AM, A-Light angelo.leg...@outlook.com wrote:
Hi Claus,
thanks for the info! But it looks like the
Hi
I added an unit test of the copyTo function
https://github.com/apache/camel/commit/5a4d715a1b065a3598ad0ef85b98da81f438c0b5
Not sure why it fails for you. Maybe its some permission issue or the
copyTo folder does not exists, and cannot be created or something.
Your best chance is to run with
Hi
btw for postProcessAction=myPostProcess you should use
postProcessAction=#myPostProcess.
See referring beans from uris section at
http://camel.apache.org/how-do-i-configure-endpoints.html
On Fri, Nov 28, 2014 at 6:36 PM, A-Light angelo.leg...@outlook.com wrote:
Hi all,
I'm using a route
Hi,
is there any update on this issue? Is there something I can do to help
understand why this method is not invoked or in general on how to make this
feature work?
(reposted with the right account)
Thanks,
A.
--
View this message in context:
Hi
I suggest if you can do a new test where you dont mark an existing
mail back as unseen, but try with an actual new mail.
Also as camel-mail dont have an unit test for that option, it would be
good to add one. And see if indeed there is a bug, though the option
has been around for years. So
Hi Claus,
thank you for your answer.
I enabled the trace both by adding the debugMode=true in the uri
parameters and by placing trace=true in the context but in the log I
didn't see any row containing folder.copyMessages.
What I saw in the log that seems related to the process folder is:
I refer to the logging configuration, eg if using log4j then its the
log4j.properties or its .xml file you set the logging levels. Then set
the level to TRACE for org.apache.camel.component.mail
On Mon, Dec 1, 2014 at 12:00 PM, A-Light angelo.leg...@outlook.com wrote:
Hi Claus,
thank you for
Oh ok, I got it wrong, sorry :)
I enabled the log and in fact I can see the following lines at each mailbox
polling:
2014-12-01 11:36:05,628 (Camel (mail-test) thread #20 -
imap://mailserver:143) DEBUG [org.apache.camel.component.mail.MailConsumer]
Polling mailbox folder: imap://mailserver:143,
You can enable TRACE logging on the camel-mail component and it should
log that it copies the message.
folder.copyMessages(new Message[]{mail}, destFolder);
LOG.trace(IMAP message {} copied to {}, mail, copyTo);
Can you see if you can see that?
On Fri, Nov 28, 2014 at 6:36
12 matches
Mail list logo
