When storing mail, the target account and folder are passed in to one of
the three mail-store mailets. If the folder doesn't exist on the target
account, it makes sense that this folder be created automatically. I
don't have a problem with that. However, if the target account doesn't
exist,
My previous post explains a problem when there are capitalization
inconsistencies between the target acct name and the user name. I've
traced through the code and see how this is happening:
The "To" and "Sender" fields can be any case: je...@xyz.com.
usersRepository.getUser(sender) lowercases
How is RRT supposed to work with the sender side? I understand that RRT
stands for "Recipient..". But the translations still need to work
on outbound as well for storing in the 'sent' folder. I don't see
anywhere in the code that sender rrt is processed. And I confirmed
that ToSenderFo
+1
On 24/10/2019 21:43, Matthieu Baechler wrote:
Hi,
I would like to propose the migration to Java 11 as a runtime.
I opened an ADR here: https://github.com/apache/james-project/pull/174
Here is the content of this ADR:
---
# 9.
Hi Mark,
Yes good guess for the first issue, you need indeed now Java 11 to
compile the project.
The documentation that you are pointing to is completely outdated I'm
afraid, sorry for that.
If you want to pass the tests with maven, you can add this option in
your maven command line "-Dski
+1
Thanks for the proposal.
On 24/10/2019 21:43, Matthieu Baechler wrote:
> Hi,
>
> I would like to propose the migration to Java 11 as a runtime.
>
> I opened an ADR here: https://github.com/apache/james-project/pull/174
>
> Here is the content of this ADR:
>
> --
René Cordier created JAMES-2933:
---
Summary: Update Build from source documentation page
Key: JAMES-2933
URL: https://issues.apache.org/jira/browse/JAMES-2933
Project: James Server
Issue Type: Bu
On 26/10/2019 09:27, Garry Hurley wrote:
> -1
>
> While I agree it is good to support Java 11, forcing a move to Java 11 will
> hamstring some users of James. First of all, government agencies are slow
> to adopt new versions, mainly because they have few actual employees
> well-versed enough to