[jira] [Resolved] (JAMES-2033) RemoteDelivery raising error on JMAP sent emails
[
https://issues.apache.org/jira/browse/JAMES-2033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tellier Benoit resolved JAMES-2033.
---
Resolution: Fixed
Merged
> RemoteDelivery raising error on JMAP sent emails
>
>
> Key: JAMES-2033
> URL: https://issues.apache.org/jira/browse/JAMES-2033
> Project: James Server
> Issue Type: Bug
>Reporter: Quynh Nguyen
>
> Here is the stack trace:
> {code}
> 01:35:42.905 [ERROR] o.a.j.m.i.JamesMailetContext - Exception caught in
> RemoteDelivery.run()
> org.apache.james.jmap.send.exception.MailShouldBeInOutboxException: Message
> with Id CassandraMessageId{uuid=245689c0-35ea-11e7-8564-ddd22b16a7b9} can't
> be found in outbox
> at
> org.apache.james.jmap.send.PostDequeueDecorator.assertMessageBelongsToOutbox(PostDequeueDecorator.java:123)
> at
> org.apache.james.jmap.send.PostDequeueDecorator.moveFromOutboxToSent(PostDequeueDecorator.java:111)
> at
> org.apache.james.jmap.send.PostDequeueDecorator.done(PostDequeueDecorator.java:79)
> at
> org.apache.james.transport.mailets.remoteDelivery.DeliveryRunnable.runStep(DeliveryRunnable.java:112)
> at
> org.apache.james.transport.mailets.remoteDelivery.DeliveryRunnable.run(DeliveryRunnable.java:87)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> What happen is very simple:
> - User sends a mail
> - mail is getting processed and is being processed by REmoteDelivery
> - RemoteDelivery copies the email and enqueue it it a dedicated MailQueue
> - JamesMailSpooler execute the dequeue decorator and moves the mail out of
> outbox
> - RemoteDelivery threads dequeue the email, send it
> - As the mail is dequeued a second time the DequeueDecorator is executed a
> second time. But the mail no more is in the Outbox. It then raise this error!
> Workaround : Add an attribute to the mail to not try to move it two time
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Closed] (JAMES-2033) RemoteDelivery raising error on JMAP sent emails
[
https://issues.apache.org/jira/browse/JAMES-2033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tellier Benoit closed JAMES-2033.
-
> RemoteDelivery raising error on JMAP sent emails
>
>
> Key: JAMES-2033
> URL: https://issues.apache.org/jira/browse/JAMES-2033
> Project: James Server
> Issue Type: Bug
>Reporter: Quynh Nguyen
>
> Here is the stack trace:
> {code}
> 01:35:42.905 [ERROR] o.a.j.m.i.JamesMailetContext - Exception caught in
> RemoteDelivery.run()
> org.apache.james.jmap.send.exception.MailShouldBeInOutboxException: Message
> with Id CassandraMessageId{uuid=245689c0-35ea-11e7-8564-ddd22b16a7b9} can't
> be found in outbox
> at
> org.apache.james.jmap.send.PostDequeueDecorator.assertMessageBelongsToOutbox(PostDequeueDecorator.java:123)
> at
> org.apache.james.jmap.send.PostDequeueDecorator.moveFromOutboxToSent(PostDequeueDecorator.java:111)
> at
> org.apache.james.jmap.send.PostDequeueDecorator.done(PostDequeueDecorator.java:79)
> at
> org.apache.james.transport.mailets.remoteDelivery.DeliveryRunnable.runStep(DeliveryRunnable.java:112)
> at
> org.apache.james.transport.mailets.remoteDelivery.DeliveryRunnable.run(DeliveryRunnable.java:87)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> What happen is very simple:
> - User sends a mail
> - mail is getting processed and is being processed by REmoteDelivery
> - RemoteDelivery copies the email and enqueue it it a dedicated MailQueue
> - JamesMailSpooler execute the dequeue decorator and moves the mail out of
> outbox
> - RemoteDelivery threads dequeue the email, send it
> - As the mail is dequeued a second time the DequeueDecorator is executed a
> second time. But the mail no more is in the Outbox. It then raise this error!
> Workaround : Add an attribute to the mail to not try to move it two time
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
james-project git commit: JAMES-2033 RemoteDelivery raising error on JMAP sent emails
Repository: james-project
Updated Branches:
refs/heads/master 50aacfe7f -> ed06af090
JAMES-2033 RemoteDelivery raising error on JMAP sent emails
Project: http://git-wip-us.apache.org/repos/asf/james-project/repo
Commit: http://git-wip-us.apache.org/repos/asf/james-project/commit/ed06af09
Tree: http://git-wip-us.apache.org/repos/asf/james-project/tree/ed06af09
Diff: http://git-wip-us.apache.org/repos/asf/james-project/diff/ed06af09
Branch: refs/heads/master
Commit: ed06af0906b85bd612ccc1576c516d743bb07f64
Parents: 50aacfe
Author: quynhn
Authored: Mon May 22 14:24:45 2017 +0700
Committer: quynhn
Committed: Mon May 22 14:26:54 2017 +0700
--
.../james/jmap/send/PostDequeueDecorator.java | 14 +---
.../jmap/send/PostDequeueDecoratorTest.java | 36
2 files changed, 45 insertions(+), 5 deletions(-)
--
http://git-wip-us.apache.org/repos/asf/james-project/blob/ed06af09/server/protocols/jmap/src/main/java/org/apache/james/jmap/send/PostDequeueDecorator.java
--
diff --git
a/server/protocols/jmap/src/main/java/org/apache/james/jmap/send/PostDequeueDecorator.java
b/server/protocols/jmap/src/main/java/org/apache/james/jmap/send/PostDequeueDecorator.java
index 8a122db..41add56 100644
---
a/server/protocols/jmap/src/main/java/org/apache/james/jmap/send/PostDequeueDecorator.java
+++
b/server/protocols/jmap/src/main/java/org/apache/james/jmap/send/PostDequeueDecorator.java
@@ -45,6 +45,7 @@ import com.google.common.collect.ImmutableList;
public class PostDequeueDecorator extends MailQueueItemDecorator {
private static final Logger LOG =
LoggerFactory.getLogger(PostDequeueDecorator.class);
+private static final String IS_DELIVERED = "DELIVERED";
private final MailboxManager mailboxManager;
private final Factory messageIdFactory;
@@ -74,11 +75,14 @@ public class PostDequeueDecorator extends
MailQueueItemDecorator {
if (success && mandatoryJmapMetaDataIsPresent()) {
MessageId messageId = messageIdFactory.fromString((String)
getMail().getAttribute(MailMetadata.MAIL_METADATA_MESSAGE_ID_ATTRIBUTE));
String username = (String)
getMail().getAttribute(MailMetadata.MAIL_METADATA_USERNAME_ATTRIBUTE);
-try {
-MailboxSession mailboxSession =
mailboxManager.createSystemSession(username, LOG);
-moveFromOutboxToSent(messageId, mailboxSession);
-} catch (MailboxException e) {
-throw new MailQueueException(e.getMessage(), e);
+if (getMail().getAttribute(IS_DELIVERED) == null) {
+try {
+MailboxSession mailboxSession =
mailboxManager.createSystemSession(username, LOG);
+moveFromOutboxToSent(messageId, mailboxSession);
+getMail().setAttribute(IS_DELIVERED, IS_DELIVERED);
+} catch (MailboxException e) {
+throw new MailQueueException(e.getMessage(), e);
+}
}
}
}
http://git-wip-us.apache.org/repos/asf/james-project/blob/ed06af09/server/protocols/jmap/src/test/java/org/apache/james/jmap/send/PostDequeueDecoratorTest.java
--
diff --git
a/server/protocols/jmap/src/test/java/org/apache/james/jmap/send/PostDequeueDecoratorTest.java
b/server/protocols/jmap/src/test/java/org/apache/james/jmap/send/PostDequeueDecoratorTest.java
index 32c75d8..568aac9 100644
---
a/server/protocols/jmap/src/test/java/org/apache/james/jmap/send/PostDequeueDecoratorTest.java
+++
b/server/protocols/jmap/src/test/java/org/apache/james/jmap/send/PostDequeueDecoratorTest.java
@@ -19,8 +19,12 @@
package org.apache.james.jmap.send;
import static org.assertj.core.api.Assertions.assertThat;
+import static org.mockito.Matchers.any;
+import static org.mockito.Matchers.eq;
import static org.mockito.Mockito.mock;
+import static org.mockito.Mockito.times;
import static org.mockito.Mockito.verify;
+import static org.mockito.Mockito.verifyNoMoreInteractions;
import static org.mockito.Mockito.when;
import java.io.ByteArrayInputStream;
@@ -34,6 +38,7 @@ import
org.apache.james.jmap.send.exception.MailShouldBeInOutboxException;
import org.apache.james.jmap.utils.SystemMailboxesProviderImpl;
import org.apache.james.mailbox.MailboxManager;
import org.apache.james.mailbox.MailboxSession;
+import org.apache.james.mailbox.MessageIdManager;
import org.apache.james.mailbox.MessageManager;
import org.apache.james.mailbox.MessageUid;
import org.apache.james.mailbox.acl.GroupMembershipResolver;
@@ -42,12 +47,16 @@ import
org.apache.james.mailbox.inmemory.manager.InMemoryIntegrationResources;
import org.apache.james.mailbox.model.ComposedMessageId;
import org.apache
[jira] [Commented] (MAILBOX-297) Cassandra setFlags operation speed improvment for ranges
[
https://issues.apache.org/jira/browse/MAILBOX-297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16020622#comment-16020622
]
Tellier Benoit commented on MAILBOX-297:
Pull request link: https://github.com/linagora/james-project/pull/806
> Cassandra setFlags operation speed improvment for ranges
>
>
> Key: MAILBOX-297
> URL: https://issues.apache.org/jira/browse/MAILBOX-297
> Project: James Mailbox
> Issue Type: Bug
> Components: cassandra
>Affects Versions: master
>Reporter: Tellier Benoit
> Fix For: master
>
>
> We observed that flags updates are very slow on large ranges for Cassandra
> implementation.
> A quick audit shows that:
> - We read full messages, and not just specific metadata. Thus we endup
> performing a "join" on James side, which is costly and not needed
> - We generate a new modseq on every message, paying much synchronisation
> costs.
> - We process the given flags sequentially.
> This is the proposed algorithm changes:
> {code:java}
> 1. Generate MODSEQ
> 2. Read messages metadata to be updated
> 3. Update each message, with condition that MODSEQ should not change
> since read (Compulsory to not mess up conditional requests):
>- If OK, compute UpdatedFlags
>- If not OK, add UID to failed list
> 4. Restart from 1 and try to update the failed list. several time.
> Step 3 can be done in a parallel fashion.
> My answer continues to try to do the update with the failed list.
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
Re: Release james-server into 3.0.0-RC1
+1 On 10/05/17 20:25, aduprat wrote: Hello every one, I'm very happy to announce the vote for the upcoming 3.0.0-RC1 version of our beloved james server. You can access sources on github https://github.com/apache/james-project/releases Nexus artifact to be released can be found here : https://repository.apache.org/#stagingRepositories It is number #1012 Moreover I uploaded compiled zip, along with md5 and sha1 sums, all signed. http://www.apache.org/dist/james/server/james-server-app-3.0.0-RC1-app.zip http://www.apache.org/dist/james/server/james-server-app-3.0.0-RC1-app.zip.asc http://www.apache.org/dist/james/server/james-server-app-3.0.0-RC1-app.zip.md5 http://www.apache.org/dist/james/server/james-server-app-3.0.0-RC1-app.zip.md5.asc http://www.apache.org/dist/james/server/james-server-app-3.0.0-RC1-app.zip.sha1 http://www.apache.org/dist/james/server/james-server-app-3.0.0-RC1-app.zip.sha1.asc According to Release policy, we need a majority vote : - At least 3 PMC - A majority of voters - This release can't be vetoed Followhttp://www.apache.org/dev/release.html for more details. To vote, you can reply to this email with +1 If you accept the release -1 If you reject the release Votes will close on Monday 15th May 2017, 8am CET. Regards, Antoine Duprat - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (MAILBOX-297) Cassandra setFlags operation speed improvment for ranges
[
https://issues.apache.org/jira/browse/MAILBOX-297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16020616#comment-16020616
]
Tellier Benoit commented on MAILBOX-297:
I used https://github.com/linagora/gatling-imap/pull/24 to run benchs on the
proposed code changes.
Bench description: Set custom flags on 5000 messages at once.
Before: mean time : 28s
Reading only metadata: mean time : 12.5s
Generate modseq only once: 1.750s
Parallelised: mean time: 0.678s
Which is a x42 improvment.
Pull request will follow soon.
> Cassandra setFlags operation speed improvment for ranges
>
>
> Key: MAILBOX-297
> URL: https://issues.apache.org/jira/browse/MAILBOX-297
> Project: James Mailbox
> Issue Type: Bug
> Components: cassandra
>Affects Versions: master
>Reporter: Tellier Benoit
> Fix For: master
>
>
> We observed that flags updates are very slow on large ranges for Cassandra
> implementation.
> A quick audit shows that:
> - We read full messages, and not just specific metadata. Thus we endup
> performing a "join" on James side, which is costly and not needed
> - We generate a new modseq on every message, paying much synchronisation
> costs.
> - We process the given flags sequentially.
> This is the proposed algorithm changes:
> {code:java}
> 1. Generate MODSEQ
> 2. Read messages metadata to be updated
> 3. Update each message, with condition that MODSEQ should not change
> since read (Compulsory to not mess up conditional requests):
>- If OK, compute UpdatedFlags
>- If not OK, add UID to failed list
> 4. Restart from 1 and try to update the failed list. several time.
> Step 3 can be done in a parallel fashion.
> My answer continues to try to do the update with the failed list.
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (MAILBOX-297) Cassandra setFlags operation speed improvment for ranges
Tellier Benoit created MAILBOX-297:
--
Summary: Cassandra setFlags operation speed improvment for ranges
Key: MAILBOX-297
URL: https://issues.apache.org/jira/browse/MAILBOX-297
Project: James Mailbox
Issue Type: Bug
Components: cassandra
Affects Versions: master
Reporter: Tellier Benoit
Fix For: master
We observed that flags updates are very slow on large ranges for Cassandra
implementation.
A quick audit shows that:
- We read full messages, and not just specific metadata. Thus we endup
performing a "join" on James side, which is costly and not needed
- We generate a new modseq on every message, paying much synchronisation costs.
- We process the given flags sequentially.
This is the proposed algorithm changes:
{code:java}
1. Generate MODSEQ
2. Read messages metadata to be updated
3. Update each message, with condition that MODSEQ should not change since
read (Compulsory to not mess up conditional requests):
- If OK, compute UpdatedFlags
- If not OK, add UID to failed list
4. Restart from 1 and try to update the failed list. several time.
Step 3 can be done in a parallel fashion.
My answer continues to try to do the update with the failed list.
{code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Updated] (JAMES-2033) RemoteDelivery raising error on JMAP sent emails
[
https://issues.apache.org/jira/browse/JAMES-2033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tellier Benoit updated JAMES-2033:
--
Description:
Here is the stack trace:
{code}
01:35:42.905 [ERROR] o.a.j.m.i.JamesMailetContext - Exception caught in
RemoteDelivery.run()
org.apache.james.jmap.send.exception.MailShouldBeInOutboxException: Message
with Id CassandraMessageId{uuid=245689c0-35ea-11e7-8564-ddd22b16a7b9} can't be
found in outbox
at
org.apache.james.jmap.send.PostDequeueDecorator.assertMessageBelongsToOutbox(PostDequeueDecorator.java:123)
at
org.apache.james.jmap.send.PostDequeueDecorator.moveFromOutboxToSent(PostDequeueDecorator.java:111)
at
org.apache.james.jmap.send.PostDequeueDecorator.done(PostDequeueDecorator.java:79)
at
org.apache.james.transport.mailets.remoteDelivery.DeliveryRunnable.runStep(DeliveryRunnable.java:112)
at
org.apache.james.transport.mailets.remoteDelivery.DeliveryRunnable.run(DeliveryRunnable.java:87)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
{code}
What happen is very simple:
- User sends a mail
- mail is getting processed and is being processed by REmoteDelivery
- RemoteDelivery copies the email and enqueue it it a dedicated MailQueue
- JamesMailSpooler execute the dequeue decorator and moves the mail out of
outbox
- RemoteDelivery threads dequeue the email, send it
- As the mail is dequeued a second time the DequeueDecorator is executed a
second time. But the mail no more is in the Outbox. It then raise this error!
Workaround : Add an attribute to the mail to not try to move it two time
was:
What happen is very simple:
User sends a mail
mail is getting processed and is being processed by REmoteDelivery
RemoteDelivery copies the email and enqueue it it a dedicated MailQueue
JamesMailSpooler execute the dequeue decorator and moves the mail out of
outbox
RemoteDelivery threads dequeue the email, send it
As the mail is dequeued a second time the DequeueDecorator is executed a
second time. But the mail no more is in the Outbox. It then raise this error!
> RemoteDelivery raising error on JMAP sent emails
>
>
> Key: JAMES-2033
> URL: https://issues.apache.org/jira/browse/JAMES-2033
> Project: James Server
> Issue Type: Bug
>Reporter: Quynh Nguyen
>
> Here is the stack trace:
> {code}
> 01:35:42.905 [ERROR] o.a.j.m.i.JamesMailetContext - Exception caught in
> RemoteDelivery.run()
> org.apache.james.jmap.send.exception.MailShouldBeInOutboxException: Message
> with Id CassandraMessageId{uuid=245689c0-35ea-11e7-8564-ddd22b16a7b9} can't
> be found in outbox
> at
> org.apache.james.jmap.send.PostDequeueDecorator.assertMessageBelongsToOutbox(PostDequeueDecorator.java:123)
> at
> org.apache.james.jmap.send.PostDequeueDecorator.moveFromOutboxToSent(PostDequeueDecorator.java:111)
> at
> org.apache.james.jmap.send.PostDequeueDecorator.done(PostDequeueDecorator.java:79)
> at
> org.apache.james.transport.mailets.remoteDelivery.DeliveryRunnable.runStep(DeliveryRunnable.java:112)
> at
> org.apache.james.transport.mailets.remoteDelivery.DeliveryRunnable.run(DeliveryRunnable.java:87)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> What happen is very simple:
> - User sends a mail
> - mail is getting processed and is being processed by REmoteDelivery
> - RemoteDelivery copies the email and enqueue it it a dedicated MailQueue
> - JamesMailSpooler execute the dequeue decorator and moves the mail out of
> outbox
> - RemoteDelivery threads dequeue the email, send it
> - As the mail is dequeued a second time the DequeueDecorator is executed a
> second time. But the mail no more is in the Outbox. It then raise this error!
> Workaround : Add an attribute to the mail to not try to move it two time
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Reopened] (JAMES-2033) RemoteDelivery raising error on JMAP sent emails
[ https://issues.apache.org/jira/browse/JAMES-2033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tellier Benoit reopened JAMES-2033: --- > RemoteDelivery raising error on JMAP sent emails > > > Key: JAMES-2033 > URL: https://issues.apache.org/jira/browse/JAMES-2033 > Project: James Server > Issue Type: Bug >Reporter: Quynh Nguyen > > What happen is very simple: > User sends a mail > mail is getting processed and is being processed by REmoteDelivery > RemoteDelivery copies the email and enqueue it it a dedicated MailQueue > JamesMailSpooler execute the dequeue decorator and moves the mail out of > outbox > RemoteDelivery threads dequeue the email, send it > As the mail is dequeued a second time the DequeueDecorator is executed a > second time. But the mail no more is in the Outbox. It then raise this error! -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-2033) RemoteDelivery raising error on JMAP sent emails
[ https://issues.apache.org/jira/browse/JAMES-2033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16020607#comment-16020607 ] Quynh Nguyen commented on JAMES-2033: - It's done by: https://github.com/linagora/james-project/pull/805 > RemoteDelivery raising error on JMAP sent emails > > > Key: JAMES-2033 > URL: https://issues.apache.org/jira/browse/JAMES-2033 > Project: James Server > Issue Type: Bug >Reporter: Quynh Nguyen > > What happen is very simple: > User sends a mail > mail is getting processed and is being processed by REmoteDelivery > RemoteDelivery copies the email and enqueue it it a dedicated MailQueue > JamesMailSpooler execute the dequeue decorator and moves the mail out of > outbox > RemoteDelivery threads dequeue the email, send it > As the mail is dequeued a second time the DequeueDecorator is executed a > second time. But the mail no more is in the Outbox. It then raise this error! -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Closed] (JAMES-2033) RemoteDelivery raising error on JMAP sent emails
[ https://issues.apache.org/jira/browse/JAMES-2033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Quynh Nguyen closed JAMES-2033. --- > RemoteDelivery raising error on JMAP sent emails > > > Key: JAMES-2033 > URL: https://issues.apache.org/jira/browse/JAMES-2033 > Project: James Server > Issue Type: Bug >Reporter: Quynh Nguyen > > What happen is very simple: > User sends a mail > mail is getting processed and is being processed by REmoteDelivery > RemoteDelivery copies the email and enqueue it it a dedicated MailQueue > JamesMailSpooler execute the dequeue decorator and moves the mail out of > outbox > RemoteDelivery threads dequeue the email, send it > As the mail is dequeued a second time the DequeueDecorator is executed a > second time. But the mail no more is in the Outbox. It then raise this error! -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Resolved] (JAMES-2033) RemoteDelivery raising error on JMAP sent emails
[ https://issues.apache.org/jira/browse/JAMES-2033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Quynh Nguyen resolved JAMES-2033. - Resolution: Done > RemoteDelivery raising error on JMAP sent emails > > > Key: JAMES-2033 > URL: https://issues.apache.org/jira/browse/JAMES-2033 > Project: James Server > Issue Type: Bug >Reporter: Quynh Nguyen > > What happen is very simple: > User sends a mail > mail is getting processed and is being processed by REmoteDelivery > RemoteDelivery copies the email and enqueue it it a dedicated MailQueue > JamesMailSpooler execute the dequeue decorator and moves the mail out of > outbox > RemoteDelivery threads dequeue the email, send it > As the mail is dequeued a second time the DequeueDecorator is executed a > second time. But the mail no more is in the Outbox. It then raise this error! -- This message was sent by Atlassian JIRA (v6.3.15#6346) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
