.conf files, strange, this should be .xml files...

Which exact snapshot are you trying?

On 06/10/2014 07:49 PM, Marc Chamberlin wrote:
> I decided to start over and reinstall James from scratch and do a
> minimal amount of configuration before starting James, so for the moment
> ignore my previous email requesting help. Seems I now have a different
> problem to resolve first. That said, I downloaded this version of James
> (I had to guess that it is the latest snapshot  ) from the repository at
> 
>  
> https://repository.apache.org/content/repositories/snapshots/org/apache/james/apache-james/3.0-beta5-SNAPSHOT/
> 
> 
> and the version I downloaded was -
> 
> apache-james-3.0-beta5-20121229.091821-854-app.tar.gz
> <http://repository.apache.org/content/repositories/snapshots/org/apache/james/apache-james/3.0-beta5-SNAPSHOT/apache-james-3.0-beta5-20121229.091821-854-app.tar.gz>
> 
> 
> Next, I simply renamed 3 of the configuration template files for
> imapserver, pop3server, and smtpserver .conf files so as to remove the
> "-template" part from their names. Started up James, and I get the
> following error message in wrapper.log -
> 
> INFO   | jvm 1    | 2014/06/10 09:25:01 | ERROR 09:25:01,679 |
> james.mailprocessor | Unable to init matcher All:
> org.apache.mailet.MailetException: Could not load matcher (All)
> (java.lang.ClassNotFoundException: org.apache.james.transport.matchers.All)
> INFO   | jvm 1    | 2014/06/10 09:25:01 |
> org.apache.mailet.MailetException: Could not load matcher (All)
> (java.lang.ClassNotFoundException: org.apache.james.transport.matchers.All)
> INFO   | jvm 1    | 2014/06/10 09:25:01 |     at
> org.apache.james.container.spring.bean.factory.mailetcontainer.AbstractLoaderBeanFactory.loadFailed(AbstractLoaderBeanFactory.java:60)
> 
> INFO   | jvm 1    | 2014/06/10 09:25:01 |     at
> org.apache.james.container.spring.bean.factory.mailetcontainer.MatcherLoaderBeanFactory.getMatcher(MatcherLoaderBeanFactory.java:55)
> 
> INFO   | jvm 1    | 2014/06/10 09:25:01 |     at
> org.apache.james.mailetcontainer.lib.AbstractStateMailetProcessor.parseConfiguration(AbstractStateMailetProcessor.java:346)
> 
> INFO   | jvm 1    | 2014/06/10 09:25:01 |     at
> org.apache.james.mailetcontainer.lib.AbstractStateMailetProcessor.init(AbstractStateMailetProcessor.java:119)
> 
> INFO   | jvm 1    | 2014/06/10 09:25:01 |     at
> org.apache.james.mailetcontainer.impl.camel.CamelMailetProcessor.init(CamelMailetProcessor.java:101)
> 
> INFO   | jvm 1    | 2014/06/10 09:25:01 |     at
> org.apache.james.mailetcontainer.impl.camel.CamelCompositeProcessor.createMailProcessor(CamelCompositeProcessor.java:103)
> 
> INFO   | jvm 1    | 2014/06/10 09:25:01 |     at
> org.apache.james.mailetcontainer.lib.AbstractStateCompositeProcessor.init(AbstractStateCompositeProcessor.java:181)
> 
> INFO   | jvm 1    | 2014/06/10 09:25:01 |     at
> org.apache.james.mailetcontainer.impl.camel.CamelCompositeProcessor.init(CamelCompositeProcessor.java:66)
> 
> INFO   | jvm 1    | 2014/06/10 09:25:01 |     at
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> INFO   | jvm 1    | 2014/06/10 09:25:01 |     at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> 
> 
> 
> I did some Googling on this error and found it had been reported about a
> year ago, but the apparent solution was to download the latest version
> of James (at that time) and use it. Well, I think I have downloaded the
> latest version, since we are now a year later than when this error was
> initially reported, so now what do I do? Thanks for any help offered, in
> advance...
> 
>      Marc...
> 
> 
> 
> 
> On 06/09/2014 04:37 PM, Marc Chamberlin wrote:
>> Hello -
>>
>> I am trying to get the latest beta version of James running on an
>> openSuSE13.1 x64 system and running into some troubles. Wonder if some
>> kind guru can translate this into plain English for me. I suspect it
>> may have something to do with my domainlist.conf file but I have tried
>> all kinds of permutations with no joy so far... Anywise on startup I
>> am getting the following messages in the wrapper.log file, and going
>> on the assumption that the first error message is the best place to
>> start resolving the problem, I will only include the initial messages
>> and not the whole file. (unless someone asks me for it...)
>>
>>
> 
> 

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

Reply via email to