[
https://issues.apache.org/jira/browse/JAMES-2086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benoit Tellier closed JAMES-2086.
-
Resolution: Fixed
> IMAP quota error handl
] has been addressing this
and has been merged
> Heathcheck for IMAP
> ---
>
> Key: JAMES-4069
> URL: https://issues.apache.org/jira/browse/JAMES-4069
> Project: James Server
> Issue Type: Improvement
>
hung created JAMES-4069:
---
Summary: Heathcheck for IMAP
Key: JAMES-4069
URL: https://issues.apache.org/jira/browse/JAMES-4069
Project: James Server
Issue Type: Improvement
Reporter: hung
duction I guess it's good for others too.
> IMAP UID <-> MSN mapping occupies too much memory
> -
>
> Key: JAMES-3740
> URL: https://issues.apache.org/jira/browse/JAMES-3740
>
ated memory leaks fixed
... compact uid <=> MSN m,appings implemented
This is less of a concern IMO. I run a 10.000 user platform with less than 350
MB footprint all james servers combined...
Yet we could experiment alternative UID -> MSN mappings.
> IMAP UID <-> MSN mapping oc
are solved, I close the ticket.
Feel free to open a new one might you experience any other issue.
Best regards,
Benoit
> Errors during connect or sync through IMAP
> --
>
> Key: JAMES-4037
> URL: https://is
[
https://issues.apache.org/jira/browse/JAMES-4020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benoit Tellier closed JAMES-4020.
-
Resolution: Fixed
> Fully comply with IMAP FE
[
https://issues.apache.org/jira/browse/JAMES-4041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benoit Tellier closed JAMES-4041.
-
Fix Version/s: 3.8.3
Resolution: Fixed
> OOM upon IMAP c
[
https://issues.apache.org/jira/browse/JAMES-4041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benoit Tellier updated JAMES-4041:
--
Attachment: Screenshot from 2024-05-29 15-34-44.png
> OOM upon IMAP c
Benoit Tellier created JAMES-4041:
-
Summary: OOM upon IMAP copy
Key: JAMES-4041
URL: https://issues.apache.org/jira/browse/JAMES-4041
Project: James Server
Issue Type: Bug
t it, can i ask any contacts for
questions about rabbitmq activemq pulsar configs?
> Errors during connect or sync through IMAP
> --
>
> Key: JAMES-4037
> URL: https://issues.apache.org/jira/browse/JAMES-4037
&g
pull chibenwa/james-jpa:JAMES-4037-2
{code}
> Errors during connect or sync through IMAP
> --
>
> Key: JAMES-4037
> URL: https://issues.apache.org/jira/browse/JAMES-4037
> Project: James Server
>
ask!
Regards,
Benoit
> Errors during connect or sync through IMAP
> --
>
> Key: JAMES-4037
> URL: https://issues.apache.org/jira/browse/JAMES-4037
> Project: James Server
> Issue Type:
rror.
The test suite exercising these extension is written with MPT. Current MPT
tests mostly exercise IMAP and storage logic but hard code the wiring and fake
the network layer thus failed catching the issue,
> Errors during connect or sync throu
ENDLIMIT)
* STATUS "INBOX" (APPENDLIMIT NIL)
a1 OK STATUS completed.
{code}
Thanks for the report. I will fix that tomorrow.
As of today you can work around those bugs by specifying the disabedCaps IMAP
configuration setting to "hide" those buggy capabilities to your
d.
{code}
Thanks for the report. I will fix that tomorrow.
As of today you can work around those bugs by specifying the disabedCaps IMAP
configuration setting to "hide" those buggy capabilities to your clients.
CF
https://github.com/apache/james-project/blob/32d09f9ec590f5bbde46aff634f
4:47:01.169 [ERROR] o.a.j.i.p.AbstractMailboxProcessor - Unexpected error
during IMAP processing
java.lang.NullPointerException: null
at
org.apache.james.imap.processor.StatusProcessor.appendLimit(StatusProcessor.java:211)
at
org.apache.james.imap.processor.StatusProcessor.la
n do that cuz i am more just user than
it spec.
for now i can tell that looks like only eM Client doing this error
Outlook 2016, 2019, Mozilla Thunderbird and Google Gmail doing that error
14:43:05.646 [WARN ] o.a.j.i.n.ImapChannelUpstreamHandler - Error while
processing imap req
hand.
Do you have a way to have the exact IMAP exchange between client and server.
1. give the exact james log trace that was generated connecting outlook to
james jpa 3.8.1?
2. if you have a way to wireshark and bypass the TLS encryption I take it!
3. And if not then exact command details shal
rate-keystone
Then add domain and user after that connect from outlook and em client try sync
for new mails and got same errors
> Errors during connect or sync through IMAP
> --
>
> Key: JAMES-4037
> URL: https://iss
) "" "*"
* LIST (\HasNoChildren \Archive) "." "Archive"
* LIST (\HasNoChildren \Drafts) "." "Drafts"
* LIST (\HasNoChildren \Sent) "." "Sent"
* LIST (\HasNoChildren \Junk) "." "Spam&
bout same error in logs when doing same
thing
> Errors during connect or sync through IMAP
> --
>
> Key: JAMES-4037
> URL: https://issues.apache.org/jira/browse/JAMES-4037
> Project: James Server
.com/apache/james-project/pull/2255
> Errors during connect or sync through IMAP
> --
>
> Key: JAMES-4037
> URL: https://issues.apache.org/jira/browse/JAMES-4037
> Project: James Server
>
.com/apache/james-project/pull/2254
Apparently mailboxTyper was badly wired with the Spring packaging and a null
reference was passed to it.
Thus when the mail user agent tries to use IMAP special use with the LIST
command it failed.
I fixed the wiring for Spring in the above PR.
Thanks for the re
ilya terskov created JAMES-4037:
---
Summary: Errors during connect or sync through IMAP
Key: JAMES-4037
URL: https://issues.apache.org/jira/browse/JAMES-4037
Project: James Server
Issue Type
> Fix inconsistency IMAP - JMAP keyword issue for JMAP RFC-8621
> -
>
> Key: JAMES-4026
> URL: https://issues.apache.org/jira/browse/JAMES-4026
> Project: James Server
>
René Cordier created JAMES-4026:
---
Summary: Fix inconsistency IMAP - JMAP keyword issue for JMAP
RFC-8621
Key: JAMES-4026
URL: https://issues.apache.org/jira/browse/JAMES-4026
Project: James Server
/apache/james-project/pull/2165
> JMAP email keywords in mixed JMAP/IMAP usage
>
>
> Key: JAMES-4016
> URL: https://issues.apache.org/jira/browse/JAMES-4016
> Project: James Server
>
well do the PR:
https://github.com/apache/james-project/pull/2165
It implements strategy b).
Feel free to give it a review.
Best regards and thanks for the report!
> JMAP email keywords in mixed JMAP/IMAP usage
>
>
>
ttle experience in Scala development (as in no
experience at all)
> JMAP email keywords in mixed JMAP/IMAP usage
>
>
> Key: JAMES-4016
> URL: https://issues.apache.org/jira/browse/JAMES-4016
>
adapt
in consequences
This means that big IMAP FETCH would have an overhead of a few messages.
Which likely is acceptable.
If everyone agrees with this, I would carry on with this approach.
Best regards,
Benoit TELLIER
On 20/03/2024 16:40, Benoit TELLIER wrote:
Hello all,
Today I did put
Hello all,
Today I did put together a POC where the following IMAP command
a0 FETCH 1:* (BODY[])
would directly stream content from the S3 storage without storing the
full input in a byte array.
I did test it a bit manually on top of the S3 AES implementation.
Link: https://github.com
Hello all,
As I had already been writing here, I did encounter significant issues
during a recent deployment [1]
[1] https://www.mail-archive.com/server-dev@james.apache.org/msg73848.html
This did lead to [2] implementing backpressure for IMAP FETCH. Which had
been mitigating the issue
urces/cucumber/ImapKeywordsConsistency.feature
Somehow, sadly it did not make it into the main JMAP specification.
We should definitly plan to adopt a similar behaviour onto the RFC-8621
implementation ASAP.
Would this be something you would be interested to contribute?
> JMAP email keywords in mixe
Benoit Tellier created JAMES-4020:
-
Summary: Fully comply with IMAP FETCH
Key: JAMES-4020
URL: https://issues.apache.org/jira/browse/JAMES-4020
Project: James Server
Issue Type: Bug
Jacopo Tessera created JAMES-4016:
-
Summary: JMAP email keywords in mixed JMAP/IMAP usage
Key: JAMES-4016
URL: https://issues.apache.org/jira/browse/JAMES-4016
Project: James Server
Issue
[
https://issues.apache.org/jira/browse/JAMES-4007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benoit Tellier closed JAMES-4007.
-
Resolution: Fixed
> Some IMAP litterals were not cleaned
feels motivated.
> Netty backpressure for IMAP Fetch
> -
>
> Key: JAMES-3997
> URL: https://issues.apache.org/jira/browse/JAMES-3997
> Project: James Server
> Issue Type: Improvement
>
and solved real issues on prod!
I'll keep this around to have a few days feedback before merging.
> Netty backpressure for IMAP Fetch
> -
>
> Key: JAMES-3997
> URL: https://issues.apache.org/jira/browse/JAMES-39
merged
> Empty password for IMAP login should not lead to worrying error log
> ---
>
> Key: JAMES-3998
> URL: https://issues.apache.org/jira/browse/JAMES-3998
> Pro
the APPEND is throttled thus not executed.
Another related issue:
{code:java}
reactor.core.Exceptions$ErrorCallbackNotImplemented:
com.github.fge.lambdas.ThrownByLambdaException:
java.nio.file.NoSuchFileException: /tmp/imap-literal2808491105678124450.tmp
Cause
Benoit Tellier created JAMES-4007:
-
Summary: Some IMAP litterals were not cleaned up
Key: JAMES-4007
URL: https://issues.apache.org/jira/browse/JAMES-4007
Project: James Server
Issue Type
r.me/presentations/2014-twitter-meetup-netty/slides.html#9.0
> Netty backpressure for IMAP Fetch
> -
>
> Key: JAMES-3997
> URL: https://issues.apache.org/jira/browse/JAMES-3997
> Project: James Server
René Cordier created JAMES-3998:
---
Summary: Empty password for IMAP login should not lead to worrying
error log
Key: JAMES-3998
URL: https://issues.apache.org/jira/browse/JAMES-3998
Project: James
René Cordier created JAMES-3997:
---
Summary: Netty backpressure for IMAP Fetch
Key: JAMES-3997
URL: https://issues.apache.org/jira/browse/JAMES-3997
Project: James Server
Issue Type: Improvement
ies.
>
> That's a classic trick to have optional mavven dependencies and address
> several architectures at once ;-)
>
> Thoughts Quan?
>
> Best regards,
>
> On 08/12/2023 11:09, Quan tran hong wrote:
> > Hello Andre Borie,
> >
> > Your PoC work is very c
ick to have optional mavven dependencies and address
several architectures at once ;-)
Thoughts Quan?
Best regards,
On 08/12/2023 11:09, Quan tran hong wrote:
Hello Andre Borie,
Your PoC work is very cool. I am happy that someone out there succeeded in
using our IMAP command extensio
Hello Andre Borie,
Your PoC work is very cool. I am happy that someone out there succeeded in
using our IMAP command extension mechanism.
> however I have a question as to which pattern the storage & APNS
long-lived client should conform to. The IMAP extension & mailbox listeners
(
to
develop their own solutions:
* https://github.com/freswa/dovecot-xaps-plugin
*
https://github.com/cyrusimap/cyrus-imapd/commit/a4470bf0f79de49030b3d66d2b385a1345c1a040
> we added exactly one year ago support for IMAP extension
As you saw previously I am already doing this in my proof-of-c
IMAP extension:
implementing support for XAPPLEPUSHSERVICE can thus always be done in an
extension. Here is an example of how to do so:
https://github.com/apache/james-project/tree/master/examples/custom-imap
I speak for myself - this is not something I would contribute by myself
for pleasure
like your help as to how best to
implement Apple Push notification support.
For a bit of context, Apple iOS does not use IMAP IDLE - instead it uses a proprietary IMAP command
"XAPPLEPUSHSERVICE" combined with Apple's hosted push notifications service
"APNS".
When an
Hello and hope everyone is well. I would like your help as to how best to
implement Apple Push notification support.
For a bit of context, Apple iOS does not use IMAP IDLE - instead it uses a
proprietary IMAP command "XAPPLEPUSHSERVICE" combined with Apple's hosted push
notifi
[
https://issues.apache.org/jira/browse/JAMES-3954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benoit Tellier closed JAMES-3954.
-
Resolution: Fixed
> Implement RFC-9394 IMAP PARTIAL Extension for Paged SEARCH and FE
Benoit Tellier created JAMES-3954:
-
Summary: Implement RFC-9394 IMAP PARTIAL Extension for Paged
SEARCH and FETCH
Key: JAMES-3954
URL: https://issues.apache.org/jira/browse/JAMES-3954
Project: James
[
https://issues.apache.org/jira/browse/JAMES-3938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benoit Tellier closed JAMES-3938.
-
Fix Version/s: 3.8.0
Resolution: Fixed
> IMAP MOVE should not fail on empty mail
Benoit Tellier created JAMES-3938:
-
Summary: IMAP MOVE should not fail on empty mailbox
Key: JAMES-3938
URL: https://issues.apache.org/jira/browse/JAMES-3938
Project: James Server
Issue Type
://github.com/apache/james-project/pull/1476
> Automatically provision default (IMAP) mailboxes
>
>
> Key: JAMES-3895
> URL: https://issues.apache.org/jira/browse/JAMES-3895
> Pro
[
https://issues.apache.org/jira/browse/JAMES-3895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wojtek updated JAMES-3895:
--
Description:
While accessing James via IMAP, only default INBOX mailbox is present. Some
e-mail applications
Wojtek created JAMES-3895:
-
Summary: Automatically provision default (IMAP) mailboxes
Key: JAMES-3895
URL: https://issues.apache.org/jira/browse/JAMES-3895
Project: James Server
Issue Type: New
.@linagora.com
Tel: (0033) 6 77 25 04 58 (WhatsApp, Signal)
On 10/03/2023 05:32, Wojtek wrote:
Hi,
While accessing James via IMAP, only default INBOX mailbox is present.
Some e-mail applications do create them on demand (Apple mail.app, but
it's not quite strict when it comes to nami
Hi,
While accessing James via IMAP, only default INBOX mailbox is present.
Some e-mail applications do create them on demand (Apple mail.app, but
it's not quite strict when it comes to naming so other app's don't
understand it), others like Thunderbird simply shows an error
[
https://issues.apache.org/jira/browse/JAMES-3888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benoit Tellier closed JAMES-3888.
-
Resolution: Fixed
> Enforce sequetial ordering of IMAP requests for each chann
[
https://issues.apache.org/jira/browse/JAMES-3888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benoit Tellier updated JAMES-3888:
--
Affects Version/s: master
> Enforce sequetial ordering of IMAP requests for each chann
[
https://issues.apache.org/jira/browse/JAMES-3888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benoit Tellier updated JAMES-3888:
--
Fix Version/s: 3.8.0
> Enforce sequetial ordering of IMAP requests for each chann
Benoit Tellier created JAMES-3888:
-
Summary: Enforce sequetial ordering of IMAP requests for each
channels
Key: JAMES-3888
URL: https://issues.apache.org/jira/browse/JAMES-3888
Project: James Server
[
https://issues.apache.org/jira/browse/JAMES-3884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benoit Tellier closed JAMES-3884.
-
Resolution: Fixed
> Latest IMAP configuration is applied for all process
Benoit Tellier created JAMES-3884:
-
Summary: Latest IMAP configuration is applied for all processors
Key: JAMES-3884
URL: https://issues.apache.org/jira/browse/JAMES-3884
Project: James Server
[
https://issues.apache.org/jira/browse/JAMES-3870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benoit Tellier closed JAMES-3870.
-
Resolution: Fixed
> Each IMAP response line is a distinct TCP pac
[
https://issues.apache.org/jira/browse/JAMES-3867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benoit Tellier closed JAMES-3867.
-
Resolution: Fixed
> Make IMAP modular
> -
>
> Key
[
https://issues.apache.org/jira/browse/JAMES-3868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benoit Tellier closed JAMES-3868.
-
Fix Version/s: 3.8.0
Resolution: Fixed
> Cannot handle IMAP PLAIN login with passw
Benoit Tellier created JAMES-3870:
-
Summary: Each IMAP response line is a distinct TCP packet
Key: JAMES-3870
URL: https://issues.apache.org/jira/browse/JAMES-3870
Project: James Server
-flush.png
> Each IMAP response line is a distinct TCP packet
>
>
> Key: JAMES-3870
> URL: https://issues.apache.org/jira/browse/JAMES-3870
> Project: James Server
> Is
Niko Usai created JAMES-3868:
Summary: Cannot handle IMAP PLAIN login with password longer than
255 char
Key: JAMES-3868
URL: https://issues.apache.org/jira/browse/JAMES-3868
Project: James Server
Benoit Tellier created JAMES-3867:
-
Summary: Make IMAP modular
Key: JAMES-3867
URL: https://issues.apache.org/jira/browse/JAMES-3867
Project: James Server
Issue Type: Improvement
[
https://issues.apache.org/jira/browse/JAMES-3853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benoit Tellier closed JAMES-3853.
-
Resolution: Fixed
> Support IMAP XLIST
> --
>
> Key
[
https://issues.apache.org/jira/browse/JAMES-3854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benoit Tellier closed JAMES-3854.
-
Resolution: Fixed
> Support RFC-8438 IMAP STATUS=S
[
https://issues.apache.org/jira/browse/JAMES-3855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benoit Tellier closed JAMES-3855.
-
Resolution: Fixed
> Supports IMAP UNAUTHENTICATE (RFC-8
[
https://issues.apache.org/jira/browse/JAMES-3857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benoit Tellier closed JAMES-3857.
-
Resolution: Fixed
> Implement RFC-7889 IMAP APPENDLI
[
https://issues.apache.org/jira/browse/JAMES-3858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benoit Tellier closed JAMES-3858.
-
Resolution: Fixed
> Implement RFC-8474 IMAP OBJECTID extens
[
https://issues.apache.org/jira/browse/JAMES-3856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benoit Tellier closed JAMES-3856.
-
Resolution: Fixed
> Implement RFC-9208 IMAP QUOTA Extens
Benoit Tellier created JAMES-3858:
-
Summary: Implement RFC-8474 IMAP OBJECTID extension
Key: JAMES-3858
URL: https://issues.apache.org/jira/browse/JAMES-3858
Project: James Server
Issue Type
Benoit Tellier created JAMES-3857:
-
Summary: Implement RFC-7889 IMAP APPENDLIMIT
Key: JAMES-3857
URL: https://issues.apache.org/jira/browse/JAMES-3857
Project: James Server
Issue Type
Benoit Tellier created JAMES-3856:
-
Summary: Implement RFC-9208 IMAP QUOTA Extension
Key: JAMES-3856
URL: https://issues.apache.org/jira/browse/JAMES-3856
Project: James Server
Issue Type
Benoit Tellier created JAMES-3855:
-
Summary: Supports IMAP UNAUTHENTICATE (RFC-8437)
Key: JAMES-3855
URL: https://issues.apache.org/jira/browse/JAMES-3855
Project: James Server
Issue Type
[
https://issues.apache.org/jira/browse/JAMES-3854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benoit Tellier updated JAMES-3854:
--
Summary: Support RFC-8438 IMAP STATUS=SIZE (was: Support RFC-8438IMAP
STATUS=SIZE)
> Supp
Benoit Tellier created JAMES-3853:
-
Summary: Support IMAP XLIST
Key: JAMES-3853
URL: https://issues.apache.org/jira/browse/JAMES-3853
Project: James Server
Issue Type: Improvement
[
https://issues.apache.org/jira/browse/JAMES-3811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benoit Tellier closed JAMES-3811.
-
Resolution: Fixed
https://github.com/apache/james-project/pull/1267
> Ability to cancel I
[
https://issues.apache.org/jira/browse/JAMES-3757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benoit Tellier closed JAMES-3757.
-
Resolution: Fixed
> IMAP/SMTP OIDC extensions should support impersonnat
[
https://issues.apache.org/jira/browse/JAMES-3737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benoit Tellier closed JAMES-3737.
-
Resolution: Fixed
Most of the work had been done on this topic
> Reactive IMAP implementat
[
https://issues.apache.org/jira/browse/JAMES-3816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benoit Tellier closed JAMES-3816.
-
Resolution: Fixed
> Limit IMAP concurrent reque
Hello all,
I think it is a best practice to announce ADRs on the mailing list so
here I go...
As I was traveling by plane, I had a bunch of free time, off-line. As
such I decided to catch up on ADRs for recent architecture changes
(sorry for not opening the ADRs in the first place).
The PR
Benoit Tellier created JAMES-3816:
-
Summary: Limit IMAP concurrent requests
Key: JAMES-3816
URL: https://issues.apache.org/jira/browse/JAMES-3816
Project: James Server
Issue Type
Benoit Tellier created JAMES-3811:
-
Summary: Ability to cancel IMAP request execution
Key: JAMES-3811
URL: https://issues.apache.org/jira/browse/JAMES-3811
Project: James Server
Issue Type
[
https://issues.apache.org/jira/browse/JAMES-3755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benoit Tellier closed JAMES-3755.
-
Resolution: Fixed
Contributed
> IMAP OIDC: optional configuration of a token_instrospect
[
https://issues.apache.org/jira/browse/JAMES-3765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
René Cordier closed JAMES-3765.
---
Fix Version/s: 3.8.0
Resolution: Fixed
> Massive operations on some IMAP command are s
[
https://issues.apache.org/jira/browse/JAMES-3755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tung TRAN updated JAMES-3755:
-
Attachment: IntrospectionToken.mp4
> IMAP OIDC: optional configuration of a token_instrospect
Tran Hong Quan created JAMES-3765:
-
Summary: Massive operations on some IMAP command are slow
Key: JAMES-3765
URL: https://issues.apache.org/jira/browse/JAMES-3765
Project: James Server
:
68747470733a2f2f696d616765732e7a656e68756275736572636f6e74656e742e636f6d2f3566376665336238623637613735366537633633643138312f31366361643337322d666133662d343731372d396438632d373437653336363163336361.png
> Massive operations on some IMAP command are slow
>
>
> Key: JAMES-3765
>
[
https://issues.apache.org/jira/browse/IMAP-215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benoit Tellier closed IMAP-215.
---
Resolution: Duplicate
See https://issues.apache.org/jira/browse/JAMES-3735
> Refactor Processors
[
https://issues.apache.org/jira/browse/JAMES-3735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benoit Tellier closed JAMES-3735.
-
Resolution: Fixed
> Kill IMAP processing ch
1 - 100 of 1002 matches
Mail list logo
