james-server-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Eric Charles <e...@apache.org>
Subject Re: SMTP server multiple port configuration -- suggested change to example
Date Tue, 14 Jun 2011 12:01:31 GMT
Hi,
Tks for the fix.
It is now committed in the smtp-ssl.xml example
Eric

On 14/06/11 13:51, Dwayne Nelson wrote:
> So I haven't looked into how to use jira yet, but I think I found an
> update for the configuration supporting multiport SMTP as it appears on
> the following repository file:
>
> https://svn.apache.org/repos/asf/james/server/trunk/container-spring/src/main/config/examples/smtpserver-ssl.xml
>
>
> When I tried adding the block to james-server-context.xml, I was having
> the same problem with james exiting. Setting spring log to debug, I
> noticed the following lines shortly before the exit:
>
> DEBUG 02:44:58,519 |
> org.springframework.beans.factory.support.DefaultListableBeanFactory |
> Finished creating instance of bean
> 'smtpserver-ssl:org.apache.james.smtpserver.CoreCmdHandlerLoader'
> DEBUG 02:44:58,534 |
> org.springframework.beans.factory.support.DefaultListableBeanFactory |
> Creating shared instance of singleton bean 'smtpserver-ssl:null'
>
> so I updated james-server-context.xml to the following (adding the smtp
> jmx handler for the ssl block):
>
> <property name="jmxHandlersPackage"
> value="org.apache.james.smtpserver.jmx.JMXHandlersLoader"/>
>
> here it is in context:
>
> <!--
> SMTP Server SSL
> -->
> <bean id="smtpserver-ssl"
> class="org.apache.james.smtpserver.netty.SMTPServer">
> <property name="protocolHandlerChain" ref="smtpProtocolHandlerChain-ssl"/>
> </bean>
>
> <bean id="smtpProtocolHandlerChain-ssl"
> class="org.apache.james.container.spring.bean.postprocessor.ProtocolHandlerChainPostProcessor">
>
> <property name="coreHandlersPackage"
> value="org.apache.james.smtpserver.CoreCmdHandlerLoader"/>
> <property name="jmxHandlersPackage"
> value="org.apache.james.smtpserver.jmx.JMXHandlersLoader"/>
> <property name="beanName" value="smtpserver-ssl"/>
> </bean>
>
> With this change, my multiport (25, 465) smtp configuration started
> working. I added a line in log4j.properties to turn logging on for the
> new smtpserver-ssl and now see that everything is working fine.
>
> -Dwayne
>
> On 06/10/2011 05:56 AM, Eric Charles wrote:
>> Don't hesitate to open jira with contributions on documentation.
>> The web site in SVN is a bit more complete (especially on
>> configuration level) now than the one on-line.
>> The new version will be deployed for server 3.0-beta1.
>>
>> Tks,
>> - Eric
>>
>> On 09/06/11 20:26, Dwayne Nelson wrote:
>>> I definitely had the feeling that the features and stability were good
>>> enough. My bigger concern with 3.0 is that the documentation wont be as
>>> complete so how to use certain features may not be as obvious to someone
>>> like myself who is new to the code. As I become more familiar with
>>> James, I will certainly be willing to help with the documentation effort
>>> myself. For now, though, I have more questions than answers.
>>>
>>> Thanks,
>>> -Dwayne
>>>
>>> On 6/9/2011 01:57 AM, Norman Maurer wrote:
>>>> Am 08.06.2011 13:39, schrieb Dwayne Nelson:
>>>>> I'm trying to get a feel for when James version 3 will be complete
>>>>> (weeks vs months?). The project that I'm working on doesn't require
>>>>> absolute stability (yet) but does rely on either detailed
>>>>> documentation or an active community. I know the James team is busy
>>>>> developing version 3 and I would really like to use it as it
>>>>> represents the future but I am wondering if I might be better using
>>>>> the 2.x version of James for now. A project roadmap would make this
>>>>> decision easier but I wasn't able to find one. Is there a publicly
>>>>> available James 3.0 roadmap?
>>>>
>>>> Hi there,
>>>>
>>>> to be honest there isn't any "real" roadmap. But I will try to push
>>>> the beta release this evening or tommorrow.
>>>> If I would start a new project I would definitly use 3.0. A few of us
>>>> already use it in production.
>>>>
>>>> Bye,
>>>> Norman
>>>>
>>>>
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
>>>> For additional commands, e-mail: server-user-help@james.apache.org
>>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
>>> For additional commands, e-mail: server-user-help@james.apache.org
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
>> For additional commands, e-mail: server-user-help@james.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
> For additional commands, e-mail: server-user-help@james.apache.org
>


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


Mime
View raw message