Error: Domain not found

[Christian Fischer]

Hey there,
I have a problem while sending an Email with this error-Message:
What dam I doing wrong ?
Thanks in advantage!

I have already tried to add a domain via cli /doaminlist.
I am using version 3.0 beta 4

DEBUG 20:32:48,083 | james.domainlist | No domain found
javax.persistence.NoResultException: Query "SELECT domain FROM JamesDomain
domain WHERE domain.name=:name" selected no result, but expected unique
result.
at
org.apache.openjpa.persistence.QueryImpl.getSingleResult(QueryImpl.java:345)
at
org.apache.james.domainlist.jpa.JPADomainList.containsDomain(JPADomainList.java:100)
at
org.apache.james.mailetcontainer.impl.JamesMailetContext.isLocalServer(JamesMailetContext.java:341)
at
org.apache.james.transport.matchers.HostIsLocal.matchRecipient(HostIsLocal.java:38)
at
org.apache.mailet.base.GenericRecipientMatcher.match(GenericRecipientMatcher.java:54)
at
org.apache.james.mailetcontainer.impl.camel.MatcherSplitter.split(MatcherSplitter.java:87)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.apache.camel.component.bean.MethodInfo.invoke(MethodInfo.java:322)
at
org.apache.camel.component.bean.MethodInfo$1.proceed(MethodInfo.java:224)
at
org.apache.camel.component.bean.BeanProcessor.process(BeanProcessor.java:159)
at
org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:91)
at
org.apache.camel.component.bean.BeanProcessor.process(BeanProcessor.java:74)
at
org.apache.camel.language.bean.BeanExpression$InvokeProcessor.process(BeanExpression.java:136)
at
org.apache.camel.language.bean.BeanExpression.evaluate(BeanExpression.java:92)
at
org.apache.camel.language.bean.BeanExpression.evaluate(BeanExpression.java:101)
at
org.apache.camel.processor.Splitter.createProcessorExchangePairs(Splitter.java:99)
at
org.apache.camel.processor.MulticastProcessor.process(MulticastProcessor.java:181)
at org.apache.camel.processor.Splitter.process(Splitter.java:94)
at
org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:70)
at
org.apache.camel.processor.DelegateAsyncProcessor.processNext(DelegateAsyncProcessor.java:98)
at
org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:89)
at
org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:68)
at
org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:70)
at
org.apache.camel.processor.DelegateAsyncProcessor.processNext(DelegateAsyncProcessor.java:98)
at
org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:89)
at
org.apache.camel.processor.interceptor.TraceInterceptor.process(TraceInterceptor.java:99)
at
org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:70)
at
org.apache.camel.processor.RedeliveryErrorHandler.processErrorHandler(RedeliveryErrorHandler.java:299)
at
org.apache.camel.processor.RedeliveryErrorHandler.process(RedeliveryErrorHandler.java:208)
at
org.apache.camel.processor.DefaultChannel.process(DefaultChannel.java:256)
at
org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:70)
at org.apache.camel.processor.Pipeline.process(Pipeline.java:143)
at org.apache.camel.processor.Pipeline.process(Pipeline.java:78)
at
org.apache.camel.processor.UnitOfWorkProcessor.process(UnitOfWorkProcessor.java:113)
at
org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:70)
at
org.apache.camel.processor.DelegateAsyncProcessor.processNext(DelegateAsyncProcessor.java:98)
at
org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:89)
at
org.apache.camel.management.InstrumentationProcessor.process(InstrumentationProcessor.java:68)
at
org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:70)
at
org.apache.camel.component.direct.DirectProducer.process(DirectProducer.java:61)
at
org.apache.camel.processor.UnitOfWorkProcessor.process(UnitOfWorkProcessor.java:99)
at
org.apache.camel.util.AsyncProcessorHelper.process(AsyncProcessorHelper.java:91)
at
org.apache.camel.processor.DelegateAsyncProcessor.process(DelegateAsyncProcessor.java:85)
at
org.apache.camel.processor.UnitOfWorkProducer.process(UnitOfWorkProducer.java:63)
at
org.apache.camel.impl.ProducerCache$1.doInProducer(ProducerCache.java:333)
at
org.apache.camel.impl.ProducerCache$1.doInProducer(ProducerCache.java:303)
at

Re: Problems building James/Cassandra backend

[Matthieu Baechler]

Hi Marc,


On 10/23/2016 03:19 AM, Marc Chamberlin wrote:

[... problem with James docker-compose]

Hi - I haven't heard back from Matthieu about this problem, if he 
still around? If not, does anyone got an idea on how to solve this issue?


I am still around (:

We updated the docker documentation last week, now it should be as 
simple as :


$ wget 
https://raw.githubusercontent.com/apache/james-project/master/dockerfiles/run/docker-compose.yml


$ docker-compose up


Let us know if it works.

You will be able to play with the configuration by mounting a conf 
directory into James container. But let's start with the simplest use case.


Cheers,

--
Matthieu Baechler

-
To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org
For additional commands, e-mail: server-user-h...@james.apache.org

Re: Mockup proposal for a promoting James website

[Matthieu Baechler]

Hi Marc,


On 10/23/2016 05:09 PM, Marc Chamberlin wrote:
Hi Benoit -  (I will follow your precedent of top posting.) 


Please don't !

No, the trouble with the current organization of the James website is 
that the only way to navigate it is to use the hierarchical tree 
structured table of contents that is found on the left hand side of 
the pages. This can make it difficult to discover where a particular 
topic is addressed, especially if/when that topic is found in a 
location that the developer thought was appropriate, but not intuitive 
in the mind of a user.  For example, I wanted to discover what mailets 
are provided with James. My initial guess was to navigate to the "User 
Manual" > Configure James >  Mailet Container  and almost missed the 
tiny link provided/embedded at the bottom of the page to the list of 
mailets.  Then and only then did I discover that this list was located 
in a surprising location under "Developers Corner" which I had assumed 
would be topics strictly of interest to James developers, not to 
users.  (I am NOT criticizing this particular layout, just using it as 
an example of how using a tree hierarchy must be navigated, sometimes 
through many many branches, in order to discover where a particular 
topic is documented.)


Using search engines can further complicate matters, especially on 
sites such as James where multiple versions of documents are stored. 
One can easily and inadvertently land on a document that is 
inappropriate for the version of the James that he/she is using, and 
waste a lot of time chasing a wrong answer. (I know, I have done it 
myself)


What a site map is/does is to flatten the presentation of an entire 
website into a single page which contains links to EVERY web page 
associated with that website. (including orphaned web pages which 
sometimes crop up) That both makes it easy to see a high level view of 
the entire website, all at once, and provides a lot of additional 
clues as to the organizational model and where one may find documents 
on a particular subject. One measure of the ease of use of a website 
is to ask how many clicks does it take, to discover the answer to a 
question or reach a goal on that website. A site map can reduce this 
to a single click. Site maps are often used on large complex web sites 
and I am sure you can find many examples. Also I have seen tools that 
develop a site map automatically, some do it externally by chasing 
links, others do it internally on the servers by chasing documents and 
directories also, although these tools do have their limitations and 
shortcomings especially if/when a web site serves dynamic content.


I am not asking that James use a site map in lieu of the hierarchical 
table of contents it now has, just in addition to it.

I understand your point but I think the main problem is that :

1. none of us has experience into site map
2. we use a generated static site with old technologies
3. we are going the mix that with yet another static site technology

If you think you can tackle this challenge, you are more than welcome, 
we'll try to help us on that.


Anyway, keep sending us your comments, they are very valuable.

Cheers,

--
Matthieu Baechler

-
To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org
For additional commands, e-mail: server-user-h...@james.apache.org

AW: Remote delivery via SSL [unsigned]

[Bernd Waibel]

Hi Rudi,

I think it is the same question as here:
http://www.mail-archive.com/server-dev@james.apache.org/msg48897.html

Port 465 is only for directly configured connections.
The SMTP Standard always uses Port 25 (and may use STARTTLS as described).

Best regards
Bernd Waibel
-Ursprüngliche Nachricht-
Von: James List [mailto:james-l...@olmeca.nl] 
Gesendet: Sonntag, 23. Oktober 2016 21:07
An: server-user@james.apache.org
Betreff: Remote delivery via SSL

Hi, I’m trying to setup James to only use SSL when connecting to other SMTP 
servers. To this end I have added the following configuration to the 
mailetconfiguration of the RemoteDelivery mailet.


  true
  465
  true
  
javax.net.ssl.SSLSocketFactory

But when attempting remote delivery the server uses port 25. I am puzzled. Any 
clues anyone?
(PS. my server has an SSL certificate installed).

INFO  00:09:08,197 | james.mailetcontext | Attempting delivery of 
Mail1476623937182-626a1d36-e920-47be-88ee-2c7c8ece79ad-to-me.com 
 to 
host mx5.mail.icloud.com . at 17.172.34.68 from 
r...@yplein.nl  for addresses [olm...@me.com 
]
ERROR 00:10:08,256 | james.mailetcontext | Could not connect to SMTP host: 
17.172.34.68, port: 25
java.net.SocketTimeoutException: connect timed out


Rudi

-
To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org
For additional commands, e-mail: server-user-h...@james.apache.org

Re: James 3.0 roadmap

[Benoit Tellier]

Hi Marc,

That sounds like a good idea.

We do not plan to work any further on these progress bars. However, if
you want to do some related contributions, you are more than welcome!

Regards,

Benoit

Le 23/10/2016 à 17:18, Marc Chamberlin a écrit :
> Hi Benoit -  (I will follow your precedent of top posting.)  I didn't
> mean to imply that the tasks associated with the completion of the James
> project weren't documented somewhere, I kinda assumed they were. If you
> were to present the chart showing progress, with each task being a link
> to where that task is documented, it just makes it a lot easier for a
> user/viewer to discover and read more about what that particular task
> involves.
> 
>  Marc...
> 
> On 10/22/2016 11:01 PM, Benoit Tellier wrote:
>> Most tasks already have issues on the Jira. If not, we create it as soon
>> as we start working on it.
>>
>> Note that some tasks are not related to the Apache project, but we still
>> want to do it before the release. Hence we do not introduce issues
>> about it.
>>
>> For things that are related with Gatling, we started a new project :
>> https://github.com/linagora/james-gatling . You can have a look to the
>> issues of this project.
>>
>>
>> Regards,
>>
>> Benoit
>>
>> Le 22/10/2016 à 16:32, Marc Chamberlin a écrit :
>>> On 10/21/2016 6:31 AM, Benoit Tellier wrote:
 Hi everyone,


 As part of our work on James 3.0, we introduced a graph showing our
 advancement.

 You can consult it here :

 https://rawgit.com/linagora/james-project/master/james3-roadmap-progress/index.html



 We will update this graph after each of our Kanban review (~ every 2
 weeks).

 Regards,

 Benoit Tellier


 -
 To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org
 For additional commands, e-mail: server-user-h...@james.apache.org


>>> Could you make each of the tasks shown into a link pointing to a more
>>> detailed description of what that particular task is about?
>>>
>>>  Marc
>>>
>> -
>> To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org
>> For additional commands, e-mail: server-user-h...@james.apache.org
>>
>>
> 
> 

-
To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org
For additional commands, e-mail: server-user-h...@james.apache.org