> As Quan did not succeed to send a mail to this list (...) I'm forwarding it
> for him!
> Let me introduce myself first. My name is Tran Hong Quan. I am from Vietnam
> and studying fourth-year at Hanoi university of science and technology.
Welcome, Quan!
Hi Matthieu,
My apologies for be absence. I expect to continue to be absent for the next
couple of weeks, but I wanted to respond to your email.
> I'm not sure which message to answer in the thread so I start a new
> thread to summarize my thoughts on the various topics discussed.
No problem.
Hi Benoit,
Ok, cool. I think we are making progress.
> Would it answer some of your concerns?
Let me answer this first: yes. Thank you for patiently tolerating my
persistence.
> Well from what I recall, we had a nice community meeting answering that
> very question.
>
> - We will
>> From my point of view the most important point is to describe what
>> James does now.
>
> +1
Yes, I agree.
Again, I do not disagree that this is “most important”. Let me use a more
concrete example to illustrate why it is not the **only** concern.
When I first looked into James, there
Hi Raphaël,
> First thank you very much for your involvement into the community, I hope
> you'll be able to continue to do so.
Well, thanks to you for your support.
> From my point of view the most important point is to describe what James does
> now. It is what is more helpful to users
Hi Rene,
>> I have observed a few different types of approaches to OSS:
>> * Haphazard “me” approach.
> I think you are correct, I would say that now it is more later approach as
> well. Well at least since I started working on the project (might have been
> different before).
Thank you
Hi Rene,
Thanks for your reply. Sorry I just sent out my last email without having seen
yours. My comments inline.
>> To continue with the documentation (at least on the path I have taken so
>> far) I need to better understand the vision. That will allow me to resolve
>> and clarify the
Hi Benoit,
> I think I did answer in that thread already.
Yes, you did. And thank you.
>> To continue with the documentation (at least on the path I have taken so
>> far) I need to better understand the vision. That will allow me to resolve
>> and clarify the topics previously raised
[
https://issues.apache.org/jira/browse/JAMES-3187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17185106#comment-17185106
]
David Leangen commented on JAMES-3187:
--
{quote}[https://github.com/apache/james-project/pull/243
Hello,
I am still trying to get a sense of the community’s vision, and it’s thoughts
relating to how to treat users. Unfortunately I have not heard too many
comments so far on this topic. Trying to read between the lines, I could think
of 4 potential conclusions:
1. People are still on
[
https://issues.apache.org/jira/browse/JAMES-3360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17180895#comment-17180895
]
David Leangen commented on JAMES-3360:
--
Thank you for the clarification.
{quote}bq. UserRepository
[
https://issues.apache.org/jira/browse/JAMES-3360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17180464#comment-17180464
]
David Leangen commented on JAMES-3360:
--
Thank you for commenting. I think your comment is kinda
David Leangen created JAMES-3360:
Summary: Change "User Repository" to "User Directory"
Key: JAMES-3360
URL: https://issues.apache.org/jira/browse/JAMES-3360
Project: James Server
> I do think we might want to leverage this opportunity to close
> low-traffic unused mailing lists. This includes:
My 2 cents:
From the user perspective, I think it would be desirable to trim down the
number of mailing lists.
Hi Benoit,
Thank you for responding.
>> I wanted to tie together a few ongoing threads and make a proposal for the
>> road to a 4.0 release.
>
> I'm uncomfortable with the 4.0 release switch. It gives the impression
> that "much" needs to change whilewhat we need is to re-brand, and better
>
Hello!
I wanted to tie together a few ongoing threads and make a proposal for the road
to a 4.0 release. My assumption is that there currently is not roadmap to 4.0.
If I am mistaken, please do let me know and I will adapt.
I think by now it is clear that, although a great project with TONS
[
https://issues.apache.org/jira/browse/JAMES-3260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17170764#comment-17170764
]
David Leangen commented on JAMES-3260:
--
Hi [~ieugen]. The gradle build is awesome! Thanks so much
> Migrating is not sexy work but is easier than writing new documentation.
Conditional on the structure and content being in a desirable state, I would
agree with this generalization. In this case, though, I don’t feel the
condition is me, so I think we’ll have to agree to disagree.
> I've
> I've decided to add docs stubs to all repositories.
> I'm going to start migrating the documentation for the popular libraries and
> then decide what to do with the others (start the retiring process most
> likely).
Awesome! Nice initiative. Thanks!!
> Anyone up for a documentation
[
https://issues.apache.org/jira/browse/JAMES-3226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17168309#comment-17168309
]
David Leangen commented on JAMES-3226:
--
Good point to re-evaluate the module naming.
"main&
[
https://issues.apache.org/jira/browse/JAMES-3226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17168302#comment-17168302
]
David Leangen edited comment on JAMES-3226 at 7/30/20, 11:38 PM:
-
Should
[
https://issues.apache.org/jira/browse/JAMES-3226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17168302#comment-17168302
]
David Leangen commented on JAMES-3226:
--
Should there be a kind of "top" page with a top-
[
https://issues.apache.org/jira/browse/JAMES-3226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17168301#comment-17168301
]
David Leangen commented on JAMES-3226:
--
Nice! That is exactly what I had in mind with the modules
[
https://issues.apache.org/jira/browse/JAMES-3348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17166419#comment-17166419
]
David Leangen commented on JAMES-3348:
--
However, I still don't have permissions in JIRA, so I can't
[
https://issues.apache.org/jira/browse/JAMES-3348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17166418#comment-17166418
]
David Leangen commented on JAMES-3348:
--
I confirm that with this fix, the problem is resolved
l.JPASieveQuota &
> org.apache.james.sieve.jpa.model.JPASieveScript are not registered as
> persistant class hence the failure.
>
> I opened https://issues.apache.org/jira/browse/JAMES-3348 & a fix for
> this here: https://github.com/apache/james-project/pull/242.
>
> Cheers,
>
> Benoit
Problem solved.
It appears that the problem was due to a bad volume configuration. That makes
sense, since the problem only popped up when I started using Docker.
Cheers,
=David
> On Jul 28, 2020, at 15:57, David Leangen wrote:
>
>
> Hi!
>
> Any ideas why I would ge
Hi!
Any ideas why I would get this error in my client? (attached image)
I was running locally without an issue. This error popped up when I tried
running with Docker.
Thanks!
=David
[
https://issues.apache.org/jira/browse/JAMES-3346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Leangen updated JAMES-3346:
-
Summary: Configure Elasticsearch (was: Configure Lucene)
> Configure Elasticsea
[
https://issues.apache.org/jira/browse/JAMES-3346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17166178#comment-17166178
]
David Leangen commented on JAMES-3346:
--
There is [an explanation on the
website|https
[
https://issues.apache.org/jira/browse/JAMES-3346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17166175#comment-17166175
]
David Leangen commented on JAMES-3346:
--
I found what I think is a [default elasticsearch config
Hello,
I am having trouble figuring out the origin of this problem:
14:30:10.458 [INFO ] o.a.j.s.SendMailHandler - Successfully spooled mail
Mail1595914206122-99a764fb-1097-4614-a1c2-022d0b331bee from
MaybeSender{mailAddress=Optional[user01@test.local]} on
localhost/0:0:0:0:0:0:0:1 for
David Leangen created JAMES-3346:
Summary: Configure Lucene
Key: JAMES-3346
URL: https://issues.apache.org/jira/browse/JAMES-3346
Project: James Server
Issue Type: Sub-task
[
https://issues.apache.org/jira/browse/JAMES-3345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17166093#comment-17166093
]
David Leangen commented on JAMES-3345:
--
The property [appears to
be|http://db.apache.org/derby/docs
David Leangen created JAMES-3345:
Summary: Cannot control location of derby.log file
Key: JAMES-3345
URL: https://issues.apache.org/jira/browse/JAMES-3345
Project: James Server
Issue Type
[
https://issues.apache.org/jira/browse/JAMES-3246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17166087#comment-17166087
]
David Leangen commented on JAMES-3246:
--
Regardless of how we move forward, there is a derby.log file
[
https://issues.apache.org/jira/browse/JAMES-3245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Leangen closed JAMES-3245.
> Clarify Sieve Configuration (managesieveserver.
[
https://issues.apache.org/jira/browse/JAMES-3243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Leangen closed JAMES-3243.
> Clarify HealthCheck Configuration (healthcheck.propert
[
https://issues.apache.org/jira/browse/JAMES-3244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Leangen closed JAMES-3244.
> Clarify Listeners Configuration (listeners.
[
https://issues.apache.org/jira/browse/JAMES-3239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Leangen closed JAMES-3239.
> Clarify Logging Configuration (logback.xml & log4j.pro
[
https://issues.apache.org/jira/browse/JAMES-3241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Leangen closed JAMES-3241.
> Clarify Extension Configuration (extensions.propert
[
https://issues.apache.org/jira/browse/JAMES-3242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Leangen closed JAMES-3242.
> Clarify JWT Configuration (jwt_public
[
https://issues.apache.org/jira/browse/JAMES-3235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Leangen closed JAMES-3235.
> Clarify Recipient Rewrite Table Configuration (recipientrewritetable.
[
https://issues.apache.org/jira/browse/JAMES-3237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Leangen closed JAMES-3237.
> Clarify Users Configuration (usersrepository.
[
https://issues.apache.org/jira/browse/JAMES-3234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Leangen closed JAMES-3234.
> Clarify POP3 Configuration (pop3server.
[
https://issues.apache.org/jira/browse/JAMES-3233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Leangen reopened JAMES-3233:
--
As discussed in this issue, the configuration is probably needed, but ought to
be simplified
[
https://issues.apache.org/jira/browse/JAMES-3233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Leangen updated JAMES-3233:
-
Summary: Simplify Mailet Container Configuration (mailetcontainer.xml)
(was: Clarify Mailet
[
https://issues.apache.org/jira/browse/JAMES-3232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Leangen closed JAMES-3232.
> Clarify Mail Repository Stores Configuration (mailrepositorystore.
[
https://issues.apache.org/jira/browse/JAMES-3231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Leangen closed JAMES-3231.
> Clarify LMTP Configuration (lmtpserver.
[
https://issues.apache.org/jira/browse/JAMES-3230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Leangen closed JAMES-3230.
> Clarify JMAP Configuration (jmap.propert
[
https://issues.apache.org/jira/browse/JAMES-3215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Leangen reopened JAMES-3215:
--
The original issue was "Remove SSL support in James", which we agreed not to
d
[
https://issues.apache.org/jira/browse/JAMES-3215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Leangen updated JAMES-3215:
-
Summary: Update SSL support in James (was: Remove SSL support in James)
> Update SSL supp
David Leangen created JAMES-3341:
Summary: Clarify DB Configuration (james-database.properties)
Key: JAMES-3341
URL: https://issues.apache.org/jira/browse/JAMES-3341
Project: James Server
David Leangen created JAMES-3340:
Summary: Clarify Sieve Configuration (managesieveserver.xml)
Key: JAMES-3340
URL: https://issues.apache.org/jira/browse/JAMES-3340
Project: James Server
David Leangen created JAMES-3339:
Summary: Clarify Listeners Configuration (listeners.xml)
Key: JAMES-3339
URL: https://issues.apache.org/jira/browse/JAMES-3339
Project: James Server
Issue
David Leangen created JAMES-3337:
Summary: Clarify JWT Configuration (jwt_publickey)
Key: JAMES-3337
URL: https://issues.apache.org/jira/browse/JAMES-3337
Project: James Server
Issue Type
David Leangen created JAMES-3338:
Summary: Clarify HealthCheck Configuration (healthcheck.properties)
Key: JAMES-3338
URL: https://issues.apache.org/jira/browse/JAMES-3338
Project: James Server
David Leangen created JAMES-3336:
Summary: Clarify Extension Configuration (extensions.properties)
Key: JAMES-3336
URL: https://issues.apache.org/jira/browse/JAMES-3336
Project: James Server
David Leangen created JAMES-3334:
Summary: Clarify Logging Configuration (logback.xml &
log4j.properties)
Key: JAMES-3334
URL: https://issues.apache.org/jira/browse/JAMES-3334
Project: James Se
David Leangen created JAMES-3335:
Summary: Clarify JMX Configuration (jmx.properties)
Key: JAMES-3335
URL: https://issues.apache.org/jira/browse/JAMES-3335
Project: James Server
Issue Type
David Leangen created JAMES-:
Summary: Clarify WebAdmin Configuration (webadmin.properties)
Key: JAMES-
URL: https://issues.apache.org/jira/browse/JAMES-
Project: James Server
David Leangen created JAMES-3331:
Summary: Clarify SMTP Configuration (smtpserver.xml)
Key: JAMES-3331
URL: https://issues.apache.org/jira/browse/JAMES-3331
Project: James Server
Issue Type
David Leangen created JAMES-3332:
Summary: Clarify Users Configuration (usersrepository.xml)
Key: JAMES-3332
URL: https://issues.apache.org/jira/browse/JAMES-3332
Project: James Server
Issue
David Leangen created JAMES-3330:
Summary: Clarify Recipient Rewrite Table Configuration
(recipientrewritetable.xml)
Key: JAMES-3330
URL: https://issues.apache.org/jira/browse/JAMES-3330
Project
David Leangen created JAMES-3329:
Summary: Clarify POP3 Configuration (pop3server.xml)
Key: JAMES-3329
URL: https://issues.apache.org/jira/browse/JAMES-3329
Project: James Server
Issue Type
David Leangen created JAMES-3328:
Summary: Clarify Mailet Container Configuration
(mailetcontainer.xml)
Key: JAMES-3328
URL: https://issues.apache.org/jira/browse/JAMES-3328
Project: James Server
David Leangen created JAMES-3327:
Summary: Clarify Mail Repository Stores Configuration
(mailrepositorystore.xml)
Key: JAMES-3327
URL: https://issues.apache.org/jira/browse/JAMES-3327
Project: James
David Leangen created JAMES-3326:
Summary: Clarify LMTP Configuration (lmtpserver.xml)
Key: JAMES-3326
URL: https://issues.apache.org/jira/browse/JAMES-3326
Project: James Server
Issue Type
David Leangen created JAMES-3325:
Summary: Clarify JMAP Configuration (jmap.properties)
Key: JAMES-3325
URL: https://issues.apache.org/jira/browse/JAMES-3325
Project: James Server
Issue Type
David Leangen created JAMES-3324:
Summary: Clarify IMAP Configuration (imapserver.xml)
Key: JAMES-3324
URL: https://issues.apache.org/jira/browse/JAMES-3324
Project: James Server
Issue Type
David Leangen created JAMES-3323:
Summary: Clarify DomainList Configuration (domainlist.xml)
Key: JAMES-3323
URL: https://issues.apache.org/jira/browse/JAMES-3323
Project: James Server
Issue
David Leangen created JAMES-3322:
Summary: Clarify DNS configuration (dnsservice.xml)
Key: JAMES-3322
URL: https://issues.apache.org/jira/browse/JAMES-3322
Project: James Server
Issue Type
[
https://issues.apache.org/jira/browse/JAMES-3321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Leangen updated JAMES-3321:
-
Description:
The "James Extendable Server" is currently described as:
h2. James
David Leangen created JAMES-3321:
Summary: Makes James Extendable Server easier to use
Key: JAMES-3321
URL: https://issues.apache.org/jira/browse/JAMES-3321
Project: James Server
Issue Type
[
https://issues.apache.org/jira/browse/JAMES-3220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Leangen closed JAMES-3220.
> Clarify DomainList Configuration (domainlist.
[
https://issues.apache.org/jira/browse/JAMES-3219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Leangen closed JAMES-3219.
> Clarify DNS configuration (dnsservice.
[
https://issues.apache.org/jira/browse/JAMES-3218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Leangen closed JAMES-3218.
> Specify "User" and "Use&
> Some of the topics in the last few days:
> - how to run the SMTP server
> - how to process the emails
> - how to configure James
I think if we stick to the concept of Basic Server and Extendable Server, those
use cases will naturally be taken care of. I explain more below.
> I prefer
> It's great to see progress on this.
Yes indeed!
> Do you think it's possible to push for a website ready for review by 1st
> august?
For me at least, this is too ambitious. Perhaps a few more (say, weekly?)
milestones and a final review by the end of August?
At least from my perspective,
>> I will need a bit more time.
> Take it :-)
I will reply directly in the code by means of a PR (either by making changes to
the code that we can revise before merging or by adding comments).
Cheers,
=David
-
To unsubscribe,
> For Mailet/Matchers, I would port existing documentation from javadoc to
> antora (and use includes to not duplicate the sources).
Do you mean transform from Javadoc format to asciidoc format (either manually
or with a conversation tool)?
Or do you mean build a tool to extract the Javadoc
>>> Cool! I will try to take some time today to comment more thoroughly, likely
>>> in the form of a PR.
>> There is quite a lot of text there and a lot of concepts, so it will take me
>> a while to go through it. :-)
> Maybe more importantly than going through the entire text, the important
>
> Cool! I will try to take some time today to comment more thoroughly, likely
> in the form of a PR.
There is quite a lot of text there and a lot of concepts, so it will take me a
while to go through it. :-)
-
To
Hi Benoit,
Thank you for giving this so much thought.
(By the way, I am very sorry that I have been less available these days, and
will continue to be so for the next few weeks, but I will still try to
contribute to this as much as possible.)
> I am making good progress on Antora
>> While working on the documentation website
I have been distracted by other work the past 2 weeks. I hope to get back to
this project within this week.
Thanks for helping to push it forward!
-
To unsubscribe, e-mail:
> I would like to propose a new vote 3.5.0 release of the Apache James server.
+1
-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
Hi,
>> If no objections are received in the next 3 days I'll move forward with
>> the change.
Thanks for all your efforts. Sorry that I have not moved forward much in the
past days. I have been preoccupied with other things.
I am having trouble imagining what you are referring to exactly in
[
https://issues.apache.org/jira/browse/JAMES-3226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17156414#comment-17156414
]
David Leangen commented on JAMES-3226:
--
Hi [~ieugen], do you think we could discuss the site
David Leangen created JAMES-3304:
Summary: No diagnostics for failed authorization
Key: JAMES-3304
URL: https://issues.apache.org/jira/browse/JAMES-3304
Project: James Server
Issue Type: Bug
David Leangen created JAMES-3303:
Summary: Can add domain even when virtualhosting disabled
Key: JAMES-3303
URL: https://issues.apache.org/jira/browse/JAMES-3303
Project: James Server
Issue
[
https://issues.apache.org/jira/browse/JAMES-3301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17155013#comment-17155013
]
David Leangen commented on JAMES-3301:
--
Very nice to have the inventory. Thanks!
IMO, I think
[
https://issues.apache.org/jira/browse/JAMES-3302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17155012#comment-17155012
]
David Leangen commented on JAMES-3302:
--
Personally, I wouldn't spend too much time on this. It does
Hi Eugen,
Thank you very much for all your efforts. The community is fortunate that you
are able to dedicate so much concentrated effort.
> I've given up on building the old site since I failed several times.
I think that’s ok, though. Honestly, I don’t see a viable path forward in terms
of
[
https://issues.apache.org/jira/browse/JAMES-3236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17154212#comment-17154212
]
David Leangen commented on JAMES-3236:
--
[~btellier], if you have the time, can you (or anybody) help
Hi Eugen,
Thanks for your support.
> GIven the discussion around the specific topics I think we are getting
> our documentation.
> @David: If you can do just that: ask questions and compile the answers
> it would be a huge win for us.
Thanks, that is indeed the intent since the beginning. The
Thanks.
I love this James adventure. It is not boring. Every time I scratch the
surface, a new concept pops out.
Ok, so digging in…
> Also as Matthieu said, RemoteDelivery is a side effect of the current
> Processing chain.
I looked at org.apache.james.transport.mailets.RemoteDelivery,
> The only wrong thing about this picture is the SMTP Service before "Outgoing".
Ok, thank you Matthieu.
> As weird as it is, the delivery of messages to a remote server is done by a
> Mailet called RemoteDelivery and it's not handled by the SMTP Service.
> As far as I know, a lot of people
Sorry, I do have one more question in response to your email…
You wrote:
> In my opinions we should document "How to write hooks with the
> protocols/smtp library", "How to plug such hooks into a running James
> server"
>
> Then "How to write commands for the protocols/smtp library" (and how
Still on the topic of SMTP relay and the original image I posted at the
beginning of this thread:
—> https://james.apache.org/images/james-smtp-relay.png
Would the attached (lousy) image be a reasonable representation of the general
concept of an SMTP Relay?
signature.asc
Description:
> I gonna try my best, given my time constraints :-)
Thank you!
This is all very good information, which allows me to peel one more layer of
the onion.
Likely my next batch of questions will be in a separate email thread, as I
think we have exhausted the concept of “James SMTP Model”.
In
1 - 100 of 487 matches
Mail list logo
