Hi Mark.
We fixed this configuration issue as part of upcoming 3.5 release.
Note that configuration shiped serves as an example and needs to be
adapted to your needs.
Thanks for the report.
Benoit
On 28/10/2019 22:27, Mark Gordon wrote:
> in the conf/mailetcontainer.xml file there is a new
Hi gordon,
You can achieve this by a simple address rewrite:
- Have the RecipientRewriteTable configured in mailetcontainer.xml
- Use the CLI to rewrite mails for m...@yahoo.com to m...@hotmail.com
The default conbfiguration should do this out of the box, and you will
end up with a more
Hello David,
- 1. Does the `cassandra` DNS entry within the James container resolves
to Cassandra? (this can be achieved with links or network).
- 2. A restarting Cassandra (with many data in the commitlog) might
reject clients. Monitor Cassandra logs to check if this happens.
I also noticed
I looked into this some more. It appears that the Rewrite mailet may do
what I need. I am having some trouble figuring out how to make it work.
I have tried adding the xml below in the root processor after the
PostmasterAlias and also i the transport processor before RemoteDelivery
I added
One of the reasons I choose Apache James was because of the mailet api.
Looks like a powerful way to process email.
With that said, I am wondering if there is an existing maillet that will
do the first thing I am trying to do.
If an email comes in for b...@mail.bob.com i would like to not relay
in the conf/mailetcontainer.xml file there is a new maillet WithPriority.
I don't know what this does. One can assume it as something to do with
email PRIORITYI used my powerful deductive reasoning skills to figure
that out. In the release from sept 2019 the setting priority is missing
and
Thx. I got the two smtp servers running. I noticed you can run the same
server on multiple ports.
if you want to bind to multiple ports us command delimited list:
0.0.0.0:465,0.0.0.0:587
I just change the tls both to false.
A quick FYI for people who don't know much about email...
What I found was that the type of store was causing my problem. I noticed
that using the bouncy castle provider was causing the problem.
The store I had created worked fine on 3.3. When I added the bouncy castle
jars to 3.3 (to get DKIM going) I started getting the same "incorrect
password"
Hello Mark,
Was http://james.apache.org/server/config-ssl-tls.html to answer your
concerns?
Please contribute to [1] if you think you can enhance it!
[1]
https://github.com/apache/james-project/blob/master/src/site/xdoc/server/config-ssl-tls.xml
Regards,
Benoit
On 28/10/2019 00:41, Mark
Hi!
I am sure the problem is due to my inexperience with Docker and Cassandra, and
even more so networking between multiple Docker containers… but I have tried
everything I can think of and would like to ask for some help.
I am getting this error:
[root@e5cc3846b51c apache-james-3.3.0]#
10 matches
Mail list logo