Re: Release james-server into 3.0.0-beta5

2016-11-02 Thread Shawn Fu Sheng
+1

Thanks and Regards,
Shawn

On 2 Nov 2016, at 8:46 PM, Benoit Tellier  wrote:

Hello every one,

I'm very happy to announce the vote for the upcoming 3.0.0-beta5 version
of our beloved james server.

You can access sources on github

https://github.com/apache/james-project/releases

Nexus artifact to be released can be found here :
https://repository.apache.org/#stagingRepositories

It is number #1010

Moreover I uploaded compiled zip, along with md5 and sha1 sums, all signed.

http://www.apache.org/dist/james/server/james-server-app-3.0.0-beta5-SNAPSHOT-app.zip
http://www.apache.org/dist/james/server/james-server-app-3.0.0-beta5-SNAPSHOT-app.zip.asc
http://www.apache.org/dist/james/server/james-server-app-3.0.0-beta5-SNAPSHOT-app.zip.md5
http://www.apache.org/dist/james/server/james-server-app-3.0.0-beta5-SNAPSHOT-app.zip.md5.asc
http://www.apache.org/dist/james/server/james-server-app-3.0.0-beta5-SNAPSHOT-app.zip.sha1
http://www.apache.org/dist/james/server/james-server-app-3.0.0-beta5-SNAPSHOT-app.zip.sha1.asc

According to Release policy, we need a majority vote :
- At least 3 PMC
- A majority of voters
- This release can't be vetoed

Follow http://www.apache.org/dev/release.html for more details.

To vote, you can reply to this email with

+1

   If you accept the release

-1

   If you reject the release

Votes will close on Saturday 5th November 2016, 2pm CET.

Regards,

Benoit Tellier

Developer at Linagora


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


Re: Release org.apache.james:apache-jspf-project into 1.0.1

2016-10-11 Thread Shawn Fu Sheng
+1

Thanks and Regards,
Shawn

On 11 Oct 2016, at 10:04 PM, Benoit Tellier  wrote:


Hello every one,

As you may know, we want to release James 3.0.0-beta5. This release
demands us to remove every SNAPSHOT dependency, including the one to JSPF.

You can access sources on github.

Nexus artifact to be released can be found here :
https://repository.apache.org/#stagingRepositories

It is number #1006

According to Release policy, we need a majority vote :
- At least 3 PMC
- A majority of voters
- This release can't be vetoed

Follow http://www.apache.org/dev/release.html for more details.

To vote, you can reply to this email with

+1

   If you accept the release

-1

   If you reject the release

Votes will close on friday 14th October 2016, 4pm CEST.

Regards,

Benoit Tellier

Developer at Linagora


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


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


Re: Apache James Server 3.0-beta5-SNAPSHOT : Unable receive email from outside domains using SSL [unsigned]

2016-09-27 Thread Shawn Fu Sheng
Hi Bernd,

thank you for your prompt reply. After created another  and 
modified accordingly, now both receiving(25) and sending(465) are working 
perfectly! thank you so much again for your great support!!!  :p :p :p 

Thanks and Regards,
Shawn

On Sep 28, 2016, at 1:31 AM, Bernd Waibel <bwai...@intarsys.de> wrote:

Hello Shawn,

you are not disturbing anyone, you're just welcome.

The standard port for mail handling is 25. This normally is not SSL encrypted.

There is a protocol extension which is called STARTTLS, also on Port 25.
If STARTTLS is used, the sending SMTP servers connect to port 25, sends a (not 
encrypted) STARTTLS command, and after that the communication will be SSL 
encrypted. All over port 25. This is supported by James3 (not by James2).
So it starts without encryption, and then changes to encryption on-the-fly.

The SSL encrypted SMTP (called SSMTP or SMTPS) is on another port, normally 
465, but this is not used by standard mail handling.
That is: every mail server does use port 25, because there is no other way to 
find out another port like 465.
The SSL Port is just for direct server-to-server connections, or user-to-server 
connections.
So the sender (server or user) need to know that this is SSL encrypted.
And these "pure-SSL" connections have to be configured inside the sending mail 
server or sending mail client directly.
So it is normally used only for user-to-server connections.

See here: https://en.wikipedia.org/wiki/Opportunistic_TLS
And here: https://en.wikipedia.org/wiki/SMTPS

So: 
For Server-to-server you need a Port 25 (which should support STARTTLS, but do 
not need to).
For Client-to-server you need a Port 465 with "SSL only" connections.
So you have one instance, with two ports, same database.

In smptserver.xml you define one .
This one you bind to port 25.
Also you set up TLS (which is just the private key and certificate to use for 
STARTTLS).
Here you set .
If you want to support STARTTLS, which is recommended.

Then you set up (copy all) another  in the same file.
This one you bind to port 465.
You should use , if you want user-to-server connection, and if 
the user should supply username and password for sending mails through this 
service. Very recommened.
Also you set up TLS (which is just the private key and certificate to use for 
SSL/TLS).
Here you set .

Btw. I did not do that till now, but this is the way it should work.

Best regards
Bernd Waibel

-Ursprüngliche Nachricht-
Von: Shawn Fu Sheng [mailto:sh...@victz.com] 
Gesendet: Dienstag, 27. September 2016 18:13
An: server-dev@james.apache.org
Betreff: Apache James Server 3.0-beta5-SNAPSHOT : Unable receive email from 
outside domains using SSL

Dear All,

sorry to disturb. i am new to James and i built 
james-server-app-3.0.0-beta5-SNAPSHOT-app.zip from latest source code (22 Sep 
2016) on GIT. It was working perfectly before i setup SSL. After i open SMTP 
SSL i am unable receive email from outside domains.

Learnt that in order to receive email from outside domains, there must have 
SMTP instance listening 25 without encryption. but if i want my user to use SSL 
to connect my email service, should i have to set up multiple SMTP instances 
using same database? is this the correct approach? or is there already have any 
setting to handle this scenario? 

Appreciate your advice, please. thank you very much in advance.

Thanks and Regards,
Shawn


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



Apache James Server 3.0-beta5-SNAPSHOT : Unable receive email from outside domains using SSL

2016-09-27 Thread Shawn Fu Sheng
Dear All,

sorry to disturb. i am new to James and i built 
james-server-app-3.0.0-beta5-SNAPSHOT-app.zip from latest source code (22 Sep 
2016) on GIT. It was working perfectly before i setup SSL. After i open SMTP 
SSL i am unable receive email from outside domains.

Learnt that in order to receive email from outside domains, there must have 
SMTP instance listening 25 without encryption. but if i want my user to use SSL 
to connect my email service, should i have to set up multiple SMTP instances 
using same database? is this the correct approach? or is there already have any 
setting to handle this scenario? 

Appreciate your advice, please. thank you very much in advance.

Thanks and Regards,
Shawn



Re: James logo – the Vote is Open

2016-09-26 Thread Shawn Fu Sheng

Hi,

maybe the last one, looks better...

* VOTE FOR LOGO NUMBER: 10


Thanks and Regards,
Shawn

On Sep 26, 2016, at 10:04 PM, Laura Royet  wrote:

Hi everyone,

This emails opens the *single vote ballot* for *James log**o*.
Below are the detailed explanation.

**Who ca**n vote :* all the recipients of this email.
Deadline :Monday, 3 October 2016 at 18:00 UTC*.

*How to vo**te :
**You have two options : **choosing**one of the **proposals between the 10 
submitted *on : http://james.apache.org/#tabs-4 or *give a blank vote*.

*So please complete the appropriate field below **:*
* VOTE FOR LOGO NUMBER:
* AGAINST PROPOSED LOGOS, WAIT MORE TIME FOR NEW CHOICES :



The proposal collecting the most votes will become James new logo!

Thank you in advance for participating.

Regards,

Laura