[jira] [Closed] (JAMES-3647) adoptopenjdk docker images lagacy
[
https://issues.apache.org/jira/browse/JAMES-3647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benoit Tellier closed JAMES-3647.
-
Fix Version/s: 3.7.0
Resolution: Fixed
> adoptopenjdk docker images lagacy
> -
>
> Key: JAMES-3647
> URL: https://issues.apache.org/jira/browse/JAMES-3647
> Project: James Server
> Issue Type: Improvement
> Components: docker
>Affects Versions: 3.6.0
>Reporter: Benoit Tellier
>Priority: Major
> Fix For: 3.7.0
>
> Time Spent: 2h
> Remaining Estimate: 0h
>
> https://hub.docker.com/_/adoptopenjdk?tab=description&page=1&ordering=last_updated&name=11
> {code:java}
> DEPRECATION NOTICE
> This image is officially deprecated in favor of the eclipse-temurin image,
> and will receive no further updates after 2021-08-01 (Aug 01, 2021). Please
> adjust your usage accordingly.
> {code}
> DOD adopt eclipse-temurin image.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Closed] (JAMES-3297) Publish the number of items currently in the mailet pipeline as a metric
[ https://issues.apache.org/jira/browse/JAMES-3297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benoit Tellier closed JAMES-3297. - Resolution: Fixed https://github.com/apache/james-project/pull/650 contributed this > Publish the number of items currently in the mailet pipeline as a metric > > > Key: JAMES-3297 > URL: https://issues.apache.org/jira/browse/JAMES-3297 > Project: James Server > Issue Type: Improvement >Reporter: Matthieu Baechler >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > Some MailQueue implementations have a limit on the number of elements that > can be dequeued but not yet ack (RabbitMQ has that feature). > In some cases it can prevent new mails to being dequeued and it's not easy to > diagnose. > By exposing that number as a metric and/or issuing a warning when this number > reach the limit, we could help the operator to understand what's going wrong. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Closed] (JAMES-2968) Move "Time Spent in IMAP-*" Log Entry from INFO to DEBUG
[ https://issues.apache.org/jira/browse/JAMES-2968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benoit Tellier closed JAMES-2968. - Resolution: Fixed https://github.com/apache/james-project/pull/649 fixed this > Move "Time Spent in IMAP-*" Log Entry from INFO to DEBUG > > > Key: JAMES-2968 > URL: https://issues.apache.org/jira/browse/JAMES-2968 > Project: James Server > Issue Type: Improvement > Components: IMAPServer >Affects Versions: 3.3.0 >Reporter: Jerry Malcolm >Priority: Trivial > Fix For: 3.3.0 > > Time Spent: 10m > Remaining Estimate: 0h > > At logging INFO level the logs have a tremendous number of imap metrics lines: > org.apache.james.metrics.logger.DefaultMetricFactory | Time spent in > IMAP-FETCH: 53 ms. > To me this seems more like a DEBUG level log entry. Obviously a matter of > opinion. But I like to think of INFO level as more 'one-time' entries rather > than multiple repetitive heartbeat-type log entries. > Simply recommending changing the log level on that entry from INFO to DEBUG. > I can make the change and submit a pull request if no objections. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-3298) Update information for DOAP file - is outdated
[ https://issues.apache.org/jira/browse/JAMES-3298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17413831#comment-17413831 ] Benoit Tellier commented on JAMES-3298: --- https://github.com/apache/james-site/pull/17 is merged. Please review, improve... > Update information for DOAP file - is outdated > -- > > Key: JAMES-3298 > URL: https://issues.apache.org/jira/browse/JAMES-3298 > Project: James Server > Issue Type: Sub-task >Reporter: Ioan Eugen Stan >Priority: Trivial > Time Spent: 20m > Remaining Estimate: 0h > > The information here [https://projects.apache.org/project.html?james] ,is > managed by the DOAP (Description of a project) file > [https://github.com/apache/james-site/blob/master/doap_JAMES.rdf] . > > We should updated it to reflect current status (maybe generate it ?!) . -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Closed] (JAMES-3645) RemoteDelivery sslEnable parameter have no effect
[
https://issues.apache.org/jira/browse/JAMES-3645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benoit Tellier closed JAMES-3645.
-
Fix Version/s: 3.7.0
Resolution: Fixed
https://github.com/apache/james-project/pull/632 fixed this.
> RemoteDelivery sslEnable parameter have no effect
> -
>
> Key: JAMES-3645
> URL: https://issues.apache.org/jira/browse/JAMES-3645
> Project: James Server
> Issue Type: Improvement
>Reporter: Benoit Tellier
>Priority: Major
> Fix For: 3.7.0
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> h3. Description
> As an administrator I wish to secure my outgoing emails using SSL (SMTPS on
> port 465), and default to SMTP on port 25 (where STARTTLS can be used
> opportunistically).
> This need is a recurring one for Gitter users (often asked, known for years
> to be buggy).
> h3. Setting up test James servers
> I did write a simple docker-compose.yml file to experiment this:
> {code:java}
> version: '3'
> services:
> james1:
> image: apache/james:memory-latest
> container_name: james1
> hostname: james1
> volumes:
> - $PWD/keystore:/root/conf/keystore
> james2:
> image: apache/james:memory-latest
> container_name: james2
> hostname: james2
> volumes:
> - $PWD/keystore:/root/conf/keystore
> {code}
> I do embed two RcptHooks to diagnose where remoteDelivery connects on james2:
> {code:java}
> package org.apache.james;
> import org.apache.james.core.MailAddress;
> import org.apache.james.core.MaybeSender;
> import org.apache.james.protocols.smtp.SMTPSession;
> import org.apache.james.protocols.smtp.hook.HookResult;
> import org.apache.james.protocols.smtp.hook.RcptHook;
> public class SoutRcptHook implements RcptHook {
> @Override
> public HookResult doRcpt(SMTPSession session, MaybeSender sender,
> MailAddress rcpt) {
> System.out.println(" <---> SSL activated: " +
> sender.asPrettyString() + " sends a message securely to " + rcpt.asString());
> return HookResult.DECLINED;
> }
> {code}
> And
> {code:java}
> package org.apache.james;
> import org.apache.james.core.MailAddress;
> import org.apache.james.core.MaybeSender;
> import org.apache.james.protocols.smtp.SMTPSession;
> import org.apache.james.protocols.smtp.hook.HookResult;
> import org.apache.james.protocols.smtp.hook.RcptHook;
> public class NoSSLRcptHook implements RcptHook {
> @Override
> public HookResult doRcpt(SMTPSession session, MaybeSender sender,
> MailAddress rcpt) {
> System.out.println(" <---> NO SSL: " + sender.asPrettyString() + "
> sends a message securely to " + rcpt.asString());
> return HookResult.DECLINED;
> }
> }
> {code}
> Which then ellows configuring the SMTP server:
> {code:java}
>
>
> smtpserver-global
> 0.0.0.0:25
>
> file://conf/keystore
> james72laBalle
>
> org.bouncycastle.jce.provider.BouncyCastleProvider
> SunX509
>
> Apache JAMES awesome SMTP Server
>
> class="org.apache.james.smtpserver.CoreCmdHandlerLoader"/>
>
>
>
>
> smtpserver-TLS
> 0.0.0.0:465
>
> file://conf/keystore
> james72laBalle
>
> org.bouncycastle.jce.provider.BouncyCastleProvider
> SunX509
>
> Apache JAMES awesome SMTP Server
>
> class="org.apache.james.smtpserver.CoreCmdHandlerLoader"/>
>
>
>
>
> {code}
> We then can review logs to know which port was eventually used to receive
> emails (smtp logs also tells us if STARTTLS is used).
> I expect `sslEnable` parameter to govern this opportunistic SSL connection.
> Thus RemoteDelivery configuration looks like this:
> {code:java}
>
>
> outgoing
> bounces
> true
> *
> true
> true
>
>
> {code}
> We then can create some test data and send a mail from james1 to james2:
> {code:java}
> docker-compose up -d
> docker exec james1 james-cli adddomain james1
> docker exec james2 james-cli adddomain james2
> docker exec james1 james-cli adduser bob@james1 123456
> docker exec james2 james-cli adduser bob@james2 123456
> docker inspect james1
> telnet [james1] 25
> auth login
> Ym9iQGphbWVzMQ==
> MTIzNDU2
> ehlo james1
> mail from:
> rcpt to:
> data
> Subject: rueooerwbwerb
> veriobwerobwerbr
> rwebeberber
> .
> {code}
> Will generate james1 to remote-deliver a mail to james2, and we can in the
> process diagnose the remote delivery behaviour between the two.
> h3. Actual behaviour
> james1 attepts an SSL connection on port 25:
> {code:ja
[jira] [Commented] (JAMES-3639) Allow to configure SSL from PEM keys (without a keystore)
[
https://issues.apache.org/jira/browse/JAMES-3639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17413833#comment-17413833
]
Benoit Tellier commented on JAMES-3639:
---
https://github.com/apache/james-project/pull/626 solved this
> Allow to configure SSL from PEM keys (without a keystore)
> -
>
> Key: JAMES-3639
> URL: https://issues.apache.org/jira/browse/JAMES-3639
> Project: James Server
> Issue Type: Improvement
> Components: IMAPServer, JMAP, POP3Server, SMTPServer
>Reporter: Benoit Tellier
>Assignee: Antoine Duprat
>Priority: Major
> Time Spent: 2h 20m
> Remaining Estimate: 0h
>
> This gives the opportunity to inter-operate directly with OpenSSL formats and
> avoids some potentially tricky configuration steps (importing the keys in a
> keystore).
> Read related thread on the mailing list:
> https://www.mail-archive.com/server-dev@james.apache.org/msg70772.html
> How this looks like:
> {code:java}
>
> file://conf/private.nopass.key
> file://conf/certs.self-signed.csr
>
> {code}
> Tested manually with self signed certificates:
> {code:java}
> # Generating your private key
> openssl genrsa -des3 -out private.key 2048
> # Creating your certificates
> openssl req -new -key private.key -out certs.csr
> # Signing the certificate yourself
> openssl x509 -req -days 365 -in certs.csr -signkey private.key -out
> certs.self-signed.csr
> # Removing the password from the private key
> # Not necessary if you supply the secret in the configuration
> openssl rsa -in private.key -out private.nopass.key
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Closed] (JAMES-3639) Allow to configure SSL from PEM keys (without a keystore)
[
https://issues.apache.org/jira/browse/JAMES-3639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benoit Tellier closed JAMES-3639.
-
Fix Version/s: 3.7.0
Resolution: Fixed
> Allow to configure SSL from PEM keys (without a keystore)
> -
>
> Key: JAMES-3639
> URL: https://issues.apache.org/jira/browse/JAMES-3639
> Project: James Server
> Issue Type: Improvement
> Components: IMAPServer, JMAP, POP3Server, SMTPServer
>Reporter: Benoit Tellier
>Assignee: Antoine Duprat
>Priority: Major
> Fix For: 3.7.0
>
> Time Spent: 2h 20m
> Remaining Estimate: 0h
>
> This gives the opportunity to inter-operate directly with OpenSSL formats and
> avoids some potentially tricky configuration steps (importing the keys in a
> keystore).
> Read related thread on the mailing list:
> https://www.mail-archive.com/server-dev@james.apache.org/msg70772.html
> How this looks like:
> {code:java}
>
> file://conf/private.nopass.key
> file://conf/certs.self-signed.csr
>
> {code}
> Tested manually with self signed certificates:
> {code:java}
> # Generating your private key
> openssl genrsa -des3 -out private.key 2048
> # Creating your certificates
> openssl req -new -key private.key -out certs.csr
> # Signing the certificate yourself
> openssl x509 -req -days 365 -in certs.csr -signkey private.key -out
> certs.self-signed.csr
> # Removing the password from the private key
> # Not necessary if you supply the secret in the configuration
> openssl rsa -in private.key -out private.nopass.key
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
[BUILD-FAILURE]: Job 'james/ApacheJames/master [master] [262]'
BUILD-FAILURE: Job 'james/ApacheJames/master [master] [262]': Check console output at "https://ci-builds.apache.org/job/james/job/ApacheJames/job/master/262/";>james/ApacheJames/master [master] [262]" - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Updated] (JAMES-3644) Better document outgoing email setup
[ https://issues.apache.org/jira/browse/JAMES-3644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benoit Tellier updated JAMES-3644: -- Description: Because outgoing smtp setup is a very generic question from our users, then we should have at hand docs to hand them and ease things up! This page dedicated to **SPF** should become `Outgoing email setup`: https://james.apache.org/howTo/spf.html - [x] https://www.mail-tester.com/ usage to debug stuff - [x] **PTR** records - [x] **SPF** record - [x] DKIM - How to create the keys? - How the DKIM record looks like? - Configuring the DKIMSign mailet before RemoteDelivery Link on Github: https://github.com/apache/james-project/blob/master/src/homepage/howTo/spf.html was: Because outgoing smtp setup is a very generic question from our users, then we should have at hand docs to hand them and ease things up! This page dedicated to **SPF** should become `Outgoing email setup`: https://james.apache.org/howTo/spf.html - [ ] https://www.mail-tester.com/ usage to debug stuff - [ ] **PTR** records - [x] **SPF** record - [ ] DKIM - How to create the keys? - How the DKIM record looks like? - Configuring the DKIMSign mailet before RemoteDelivery Link on Github: https://github.com/apache/james-project/blob/master/src/homepage/howTo/spf.html > Better document outgoing email setup > > > Key: JAMES-3644 > URL: https://issues.apache.org/jira/browse/JAMES-3644 > Project: James Server > Issue Type: Improvement > Components: Documentation >Reporter: Benoit Tellier >Priority: Major > Time Spent: 1h 10m > Remaining Estimate: 0h > > Because outgoing smtp setup is a very generic question from our users, then > we should have at hand docs to hand them and ease things up! > This page dedicated to **SPF** should become `Outgoing email setup`: > https://james.apache.org/howTo/spf.html > - [x] https://www.mail-tester.com/ usage to debug stuff > - [x] **PTR** records > - [x] **SPF** record > - [x] DKIM > - How to create the keys? > - How the DKIM record looks like? > - Configuring the DKIMSign mailet before RemoteDelivery > Link on Github: > https://github.com/apache/james-project/blob/master/src/homepage/howTo/spf.html -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
