This is an automated email from the ASF dual-hosted git repository. aduprat pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/james-project.git
commit 488a5e03025d4d69e510de53f08aa9d535d8dd67 Author: Benoit Tellier <[email protected]> AuthorDate: Wed Feb 13 11:22:27 2019 +0700 3.3.0 Release: Mail processing howto should refer James 3.3.0 --- src/homepage/howTo/mail-processing.html | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/src/homepage/howTo/mail-processing.html b/src/homepage/howTo/mail-processing.html index 83678c5..1f10887 100644 --- a/src/homepage/howTo/mail-processing.html +++ b/src/homepage/howTo/mail-processing.html @@ -72,7 +72,7 @@ layout: default Hence, we can arrange James standard components listed <a href="/server/dev-provided-mailets.html">here</a> to achieve basic logic. But what if our goals are more complex? What if we need our own processing components?</p> - <p>This page will propose a 'hands on practice' how-to using James 3.2.0. We will implement a custom mailet and a custom matcher, + <p>This page will propose a 'hands on practice' how-to using James 3.3.0. We will implement a custom mailet and a custom matcher, then deploy it in a James server.</p> <p>We need to choose our use case. We will, when a mail is delayed over one day, write a mail to the original sender @@ -224,8 +224,8 @@ layout: default <pre><code>docker run -p "25:25" -p "143:143" \ -v "$PWD/src/main/resources/mailetcontainer.xml:/root/conf/mailetcontainer.xml" \ - -v "$PWD/target/custom-mailets-3.2.0-SNAPSHOT.jar:/root/extensions-jars/custom-mailets.jar" \ - linagora/james-jpa-sample:3.2.0</code></pre> + -v "$PWD/target/custom-mailets-3.3.0-SNAPSHOT.jar:/root/extensions-jars/custom-mailets.jar" \ + linagora/james-jpa-sample:3.3.0</code></pre> </div> <footer class="major"> --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
