Apache Log4j 2 vulnerability (CVE-2021-44228)

2021-12-13 Thread Amlan Sengupta
Hello, Considering the following CVE @ https://www.ncsc.gov.uk/news/apache-log4j-vulnerability /deployments/james-server-app-3.6.0/conf/log4j2.xml /deployments/james-server-app-3.6.0/lib/log4j-api-2.14.0.jar /deployments/james-server-app-3.6.0/lib/log4j-core-2.14.0.jar

Re: Apache James MTA 3.6.0 spawning additional connections.

2021-07-13 Thread Amlan Sengupta
to be sponsored to contribute it. Cheers, Benoit On 13/07/2021 16:18, Amlan Sengupta wrote: > Hello, > > We are seeing something very strange with Apache James MTA. > > Keeping the flow below in context, we have a client which only uses 1 connection ad re

Apache James MTA 3.6.0 spawning additional connections.

2021-07-13 Thread Amlan Sengupta
Hello, We are seeing something very strange with Apache James MTA. Keeping the flow below in context, we have a client which only uses 1 connection ad reuses it send emails to Apache James. We have confirmed this through connection tracking. We are seeing Apache James spawning up to 60

Re: Apache James : Purely MX record based smtp.

2021-07-02 Thread Amlan Sengupta
TEWAY_PORT} ${env:JAMES_REMOTE_DELIVERY_USERNAME} ${env:JAMES_REMOTE_DELIVERY_PASSWORD} Cheers, Benoit On 30/06/2021 22:56, Amlan Sengupta wrote: > Hello, > > To be honest I was not expecting it to need anything else b

Re: Apache James : Purely MX record based smtp.

2021-07-01 Thread Amlan Sengupta
bounces ${env:JAMES_REMOTE_DELIVERY_GATEWAY} ${env:JAMES_REMOTE_DELIVERY_GATEWAY_PORT} ${env:JAMES_REMOTE_DELIVERY_USERNAME} ${env:JAMES_REMOTE_DELIVERY_PASSWORD} Cheers, Benoit On 30/06/2021 22:56, Amlan Sengupta wrote: > Hello, > > To be honest

Re: Apache James : Purely MX record based smtp.

2021-06-30 Thread Amlan Sengupta
Hello, To be honest I was not expecting it to need anything else besides a MX Record. The java exception on the other hand states the following : jvm 1 | 30-Jun-2021 10:20:30.654 ERROR [RemoteDelivery-2] org.apache.james.dnsservice.library.MXHostAddressIterator.:79 - Couldn't resolve IP

Apache James : Purely MX record based smtp.

2021-06-30 Thread Amlan Sengupta
Hello, I am a bit unclear based on Apache James 3.5.0 docs whether it is able to connect to smtp service provider purely based on MX Records. I have gone through the mailing list historically . I have set the gateway and gatewayPort to published MX Record. Logs say the following which seem to

Re: James 3.5.0 startTLS="true"

2021-06-28 Thread Amlan Sengupta
some point. On Mon, Jun 28, 2021 at 9:23 AM Amlan Sengupta wrote: > Hello, > > I am running into a weird problem with James 3.5.0. I am trying to enable > the following but it fails to load the cacerts-test. I have confirmed the > file exist and the

James 3.5.0 startTLS="true"

2021-06-28 Thread Amlan Sengupta
Hello, I am running into a weird problem with James 3.5.0. I am trying to enable the following but it fails to load the cacerts-test. I have confirmed the file exist and the secret is correct. I also hardcoded the values of the secret but startTLS="true"> to no vail.

Rate limiting

2021-03-29 Thread Amlan Sengupta
Hello, Apache James : 3.5.0 I have a non functional requirement which I am trying to implement through Apache James which is “ A maximum of ( very low number ) emails per hour is allowed ”. I am currently using the default FileMailQueue approach while trying to adhere to ( very low number )