Hi David,
well, I wouldn't go as far as to say "it wasn't tested" - but rather "no
one took the effort to build it local it give it a try" - as if this
would had been done at least someone should had noticed that the way the
mailetcontainer.xml was at this point just doesn't work. So, I guess the
only "tests" done were the automatic checks on commit - and these might
were not been able to correctly check the messed up config.
As for why we can't exactly re-produce each others result: I just clone
it from github and build it myself - do you the same or do you use some
pre-compiled/-packaged archive provided from somewhere else? Although it
should not make any difference it's quite possible that the packaged
version actually does differ from what you get if you build it from
source on your own.
As for your failing JVM start up: that looks really odd - only got this
very error on php when the default mysql socket changed path. Give it a
try to just launch the VM itself: $>java -version
If this fails then there's something wrong with the jre in the folder
you designated. Also check the file and directory permissions (as that's
what once got me into trouble as I'm still not really understand the
difference between the read and the execute permission). If you google
about this issue it's always something with a wrapper and a messed up
path - so this might could be the reason also for you (wild guess)?
Anyway, I joined for a question about mailing lists and something no
longer part of james - it was just a coincidence I noticed your
(including Ahmet and Joe) issue about James 3.4 - strange none of the
devs yet replied. So I guess as my question remains unanswered and your
issue is caused by a broken release I guess we can agree on just use 3.3
instead. From what I can see the important changes are not that big so
unless someone really relies on DKIM built into james instead of once
external james-dkim or some changes to the webadmin (I never got it to
work as I just don't know how) I guess it shouldn't be an issue to just
use 3.3.
So, I wish you luck. Maybe I'll rejoin later - for now I'm out.
Matt
Am 06.03.2020 um 10:22 schrieb [email protected]:
hi Matt
Confusing that we don't duplicate each others problems, but I do agree that
3.4.0 is not usable. It seems to have been released without much testing.
I set it up on a cloud VM with email known to be fully working with exim4 and
dovecot running - which of course I stopped first so james can listen on ports
143 and 25.
I created a domain in james that actually has A and MX records pointing to the
VM and a james user in that domain. I configured maildir storage and commented
out the offending mailet as has been proscribed.
A test mail from another fully functioning mail server is spooled in the logs,
but not seen in the INBOX - just as with the tests I carried out on my home
laptop. A test mail in the other direction (ie from James) gets the same
treatment - successfully spooled locally, but never received by the remote host.
There was other bizarreness that I didn't get on the laptop - although I got
james up and running with the run.sh script it would no go with the james
command (neither james console nor james start) - errors below .
I may look at version 3.3, but I'm finish trying to get 3.4 to do anything. For
the record. I've been testing on linux (fedora laptop and debian VM) with java
8.
startup error below this
(root@badwolf:/opt/james-server-app-3.4.0/bin# echo $JAVA_HOME
/opt/jre1.8.0_241)
===============================================================================
root@badwolf:/opt/james-server-app-3.4.0/bin# ./james console
Running Apache James :: Server :: App...
wrapper | --> Wrapper Started as Console
wrapper | Launching a JVM...
wrapper | JVM exited while loading the application.
jvm 1 | wrapper | Unable to start JVM: No such file or directory (2)
wrapper | Launching a JVM...
wrapper | JVM exited while loading the application.
jvm 2 | wrapper | Unable to start JVM: No such file or directory (2)
wrapper | Launching a JVM...
wrapper | JVM exited while loading the application.
jvm 3 | wrapper | Unable to start JVM: No such file or directory (2)
wrapper | Launching a JVM...
wrapper | JVM exited while loading the application.
jvm 4 | wrapper | Unable to start JVM: No such file or directory (2)
wrapper | Launching a JVM...
wrapper | JVM exited while loading the application.
jvm 5 | wrapper | Unable to start JVM: No such file or directory (2)
wrapper | There were 5 failed launches in a row, each lasting less than 300
seconds. Giving up.
wrapper | There may be a configuration problem: please check the logs.
wrapper | <-- Wrapper Stopped
--
David Matthews
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
