Ok, so after looking through the files and logs and repos - I found the
issue:
https://repo.maven.apache.org/maven2/org/apache/james/james-server-util-java8/
error: there isn't a pack for current 3.1.0 of james - so I guess that's
why a wrong artifact gets downloaded into local repo and
Hey Benoit,
thanks for your reply.
Here're my current build specs:
host: win7 ulti sp1 x64
vm: virtualbox 5.1.26r117224
vm-os: opensuse tumbleweed x64 - snapshot 20171203
jdk: openjdk 1.8.0_151 x64
maven: 3.5.2 - additional repo at
cool thx.
On Mon, Dec 4, 2017 at 1:25 AM, Benoit Tellier
wrote:
> Hi Mark.
>
> What do you mean?
>
> What packaging are you using? You simply need to use James newest Jars
> with your old conf.
>
> If you are using spring packaging the newest version of these jar is in
>
Hi,
You can implement reverse DNS checks upon EHLO commands with
ReverseEqualsEhloHeloHandler will perform an equality check
ResolvableEhloHeloHandler will check PTR record exists.
Read more about this technique:
https://blog.zensoftware.co.uk/2015/04/28/using-reverse-lookups-to-reduce-spam/
You are right.
Using an AUTHENTICATE / LOGIN command on an unsecure connection should
not be permitted. Or at the very least as an admin I should be able to
disable it.
I am not aware of such mechanism.
As I think this is important, I will introduce a ticket about it.
Cheers,
Benoit
Le
Hi Guofeng Zhang,
First sorry for the late answer.
You can check the email was well received by connecting to James server
using IMAP, for instance.
This looks like a bit weird, could you:
- ensure both recipients have a local domain (handled by your James
server?)
- Could you try to collect
Hi Mark, sorry for the late answer.
To get a more personalized mail post processing, you will have to edit
**mailetcontainer.xml** file.
Bounce is returned to the sender address advertized in the SMTP
envelope. You will need to detect "fake" incoming SMTP connections.
Several mechanisms exists
Hi Matt.
- DskipTests skips tests execution, not test compilation. If you used
that option then your failure is not normal.
By the way, such "non compilable/non runnable" tests seems really weird
to me. Could you:
- Give me your environment settings: OS/OS version/ Java JDK +
version/maven
Hi Mark.
What do you mean?
What packaging are you using? You simply need to use James newest Jars
with your old conf.
If you are using spring packaging the newest version of these jar is in
the 3.0.1 downloadable ZIP.
Cheers,
Benoit
Le 02/12/2017 à 10:01, Mark Gordon a écrit :
> What is the