You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-user@james.apache.org by Eric Charles <er...@apache.org> on 2010/11/02 19:30:56 UTC
Re: 3.0-M1 default configuration
Hi Gerry, Norman and All,
Remote delivery is activated, but you can not really use it if you don't
send from localhost because it "authRequired" still needs to be set to
true in smtpserver.xml.
I enabled it on my config and now I can use james as relay to external
mail servers and james is not detected as "potential open relay".
If OK to everyone, I will activate the authRequired by default for the
next release.
Tks,
Eric
On 21/10/2010 09:44, Norman wrote:
> +1
>
> Norman
>
> Am 21.10.2010 09:33, schrieb Eric Charles:
>> Hi Gerry,
>>
>> It seems that qmail, postifx,... have virtual hosting disabled by
>> default.
>> So probably James should be delivered as such, with a clear
>> indication on how to enable it via a simple config file (the
>> mailserver.xml atm).
>>
>> For remote delivery, it is already enabled now, so that's fine.
>>
>> Tks,
>>
>> Eric
>>
>>
>> On 14/10/2010 18:03, Gerry Matte wrote:
>>> I am one of those awaiting true virtual hosting.
>>> I agree that you should enable virtual hosting by default even if
>>> only one example virtual host is configured in the default config set.
>>> I also agree that the default config should have remote delivery
>>> enabled.
>>> Gerry Matte
>>> --------------------------------------------------
>>> From: "Eric Charles" <er...@apache.org>
>>> Sent: Thursday, October 14, 2010 12:17 AM
>>> To: "James Users List" <se...@james.apache.org>; "James
>>> Developers List" <se...@james.apache.org>
>>> Subject: 3.0-M1 default configuration
>>>
>>>> Hi All,
>>>>
>>>> We are preparing the 3.0-M1 release and need to define the default
>>>> configuration.
>>>>
>>>> Currently, when you download James 3 snapshot, you have
>>>> virtualHosting: disabled
>>>> mailbox: jpa
>>>> user: jpa
>>>> virtualuser: jpa
>>>> domainlist: xml
>>>> ValidRcptHandler handler: enabled
>>>> jmx: disabled
>>>> remote delivery: disabled
>>>>
>>>> I was thinking to enable virtualHosting to be able to manage more
>>>> than one domain at once (this was a long-time waited feature, so
>>>> let's provide it by default).
>>>> This would lead to implement domainlist with jpa.
>>>>
>>>> I was wondering what to do with remote delivery. I can imagine if
>>>> we leave it as such to have many users downloading and thinking
>>>> that james does not do the expected job: send mails...
>>>>
>>>> What do you think of?
>>>> Have you got any other requirement we should meet?
>>>>
>>>> Tks for your feedbacks,
>>>>
>>>> Eric
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> 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
Re: 3.0-M1 default configuration
Posted by Eric Charles <er...@apache.org>.
authRequired is now enable in trunk. will be available in M2 (for the
second vote).
tks,
Eric
On 2/11/2010 19:30, Eric Charles wrote:
> Hi Gerry, Norman and All,
>
> Remote delivery is activated, but you can not really use it if you
> don't send from localhost because it "authRequired" still needs to be
> set to true in smtpserver.xml.
> I enabled it on my config and now I can use james as relay to external
> mail servers and james is not detected as "potential open relay".
>
> If OK to everyone, I will activate the authRequired by default for the
> next release.
>
> Tks,
>
> Eric
>
> On 21/10/2010 09:44, Norman wrote:
>> +1
>>
>> Norman
>>
>> Am 21.10.2010 09:33, schrieb Eric Charles:
>>> Hi Gerry,
>>>
>>> It seems that qmail, postifx,... have virtual hosting disabled by
>>> default.
>>> So probably James should be delivered as such, with a clear
>>> indication on how to enable it via a simple config file (the
>>> mailserver.xml atm).
>>>
>>> For remote delivery, it is already enabled now, so that's fine.
>>>
>>> Tks,
>>>
>>> Eric
>>>
>>>
>>> On 14/10/2010 18:03, Gerry Matte wrote:
>>>> I am one of those awaiting true virtual hosting.
>>>> I agree that you should enable virtual hosting by default even if
>>>> only one example virtual host is configured in the default config set.
>>>> I also agree that the default config should have remote delivery
>>>> enabled.
>>>> Gerry Matte
>>>> --------------------------------------------------
>>>> From: "Eric Charles" <er...@apache.org>
>>>> Sent: Thursday, October 14, 2010 12:17 AM
>>>> To: "James Users List" <se...@james.apache.org>; "James
>>>> Developers List" <se...@james.apache.org>
>>>> Subject: 3.0-M1 default configuration
>>>>
>>>>> Hi All,
>>>>>
>>>>> We are preparing the 3.0-M1 release and need to define the default
>>>>> configuration.
>>>>>
>>>>> Currently, when you download James 3 snapshot, you have
>>>>> virtualHosting: disabled
>>>>> mailbox: jpa
>>>>> user: jpa
>>>>> virtualuser: jpa
>>>>> domainlist: xml
>>>>> ValidRcptHandler handler: enabled
>>>>> jmx: disabled
>>>>> remote delivery: disabled
>>>>>
>>>>> I was thinking to enable virtualHosting to be able to manage more
>>>>> than one domain at once (this was a long-time waited feature, so
>>>>> let's provide it by default).
>>>>> This would lead to implement domainlist with jpa.
>>>>>
>>>>> I was wondering what to do with remote delivery. I can imagine if
>>>>> we leave it as such to have many users downloading and thinking
>>>>> that james does not do the expected job: send mails...
>>>>>
>>>>> What do you think of?
>>>>> Have you got any other requirement we should meet?
>>>>>
>>>>> Tks for your feedbacks,
>>>>>
>>>>> Eric
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> 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
>
---------------------------------------------------------------------
To unsubscribe, e-mail: server-user-unsubscribe@james.apache.org
For additional commands, e-mail: server-user-help@james.apache.org