>> - For whatever reason there are mail servers that demand the whole
>> email address as the login ID. java.net.URI is incapable of handling
>> things like
>>
>> imap://b...@dummy.com@dummy.com?password=test
>> imap://dummy.com?password=test&username=b...@dummy.com
>>
>> You can probably direct-p
Hi Donald
On Wed, Apr 27, 2011 at 12:37 AM, Donald Whytock wrote:
> Trying with a different mail server, it consistently deletes with IMAP
> and consistently fails to delete with POP3. Long as it's consistent,
> I'm good. Thanks.
>
Thanks for reporting back.
Yeah that's in line what people h
Trying with a different mail server, it consistently deletes with IMAP
and consistently fails to delete with POP3. Long as it's consistent,
I'm good. Thanks.
A couple issues that came up...
- I got a FolderNotOpen error when the component was trying to set the
DELETED flag. So to the beginning
Using Apache James at the moment. The current stable version of that
(2.3.2) doesn't support IMAP. ("A backport to James Server 2.3.2 would
require a volunteer.")
I have another localhost server I can try. Might work better anyway.
Ideally, the production app won't be running on a localhost emai
Hi
Ah try using imap instead of pop3. pop3 is very limited and it may not
work setting those flags. I think we have seen this in the past
setting the flags to SEEN or DELETED etc.
We have a little tip about use imap instead of pop3 at the wiki page
http://camel.apache.org/mail.html
On Fri, Apr
At the moment my route is very short:
from("pop3://bot@localhost?password=test")
.process(message1)
.process(peeker)
.choice()
.when(property("chatterbot.email").isNotNull())
.to("seda:mailtester");
from("seda:mailtester")
.routeId("listener.test")
.process(mes
On Thu, Apr 21, 2011 at 8:50 PM, Donald Whytock wrote:
> Okay, it's not ROUTE_STOP, or not necessarily. I've been getting
> mixed results with email deletion. In all cases I see the message
> "Exchange processed, so flagging message as DELETED" coming from
> MailConsumer.processCommit() as the e
Okay, it's not ROUTE_STOP, or not necessarily. I've been getting
mixed results with email deletion. In all cases I see the message
"Exchange processed, so flagging message as DELETED" coming from
MailConsumer.processCommit() as the exchange's onCompletion is run,
but in some cases the email doesn
But if I do filter on the pipeline it'll determine whether the entire
pipeline is or isn't performed, right? So to break out of the
pipeline I'd have to put the filter on each pipelined item, such as
from X
filter when Y
to A
filter when Y
to B
end // filter
to C // do something after f
On Wed, Apr 20, 2011 at 12:42 AM, Donald Whytock wrote:
> I ask because it appears to, in my application where I'm using
> ROUTE_STOP to break out of a pipeline.
>
> Perhaps there should be some mechanism for breaking out of a pipeline
> without killing the whole route? A PIPELINE_STOP property,
I ask because it appears to, in my application where I'm using
ROUTE_STOP to break out of a pipeline.
Perhaps there should be some mechanism for breaking out of a pipeline
without killing the whole route? A PIPELINE_STOP property, or maybe
ROUTE_STOP could contain the ID of the route to be broken
Hi all...
Does using ROUTE_STOP on an email exchange prevent the message from
being deleted from the POP3 server?
Don
12 matches
Mail list logo
