svn commit: r1291645 - /james/app/trunk/src/main/resources/META-INF/org/apache/james/spring-server.xml
Author: eric
Date: Tue Feb 21 08:14:00 2012
New Revision: 1291645
URL: http://svn.apache.org/viewvc?rev=1291645view=rev
Log:
impact spring-server.xml with james-database.properties name and place
(MAILBOX-166)
Modified:
james/app/trunk/src/main/resources/META-INF/org/apache/james/spring-server.xml
Modified:
james/app/trunk/src/main/resources/META-INF/org/apache/james/spring-server.xml
URL:
http://svn.apache.org/viewvc/james/app/trunk/src/main/resources/META-INF/org/apache/james/spring-server.xml?rev=1291645r1=1291644r2=1291645view=diff
==
---
james/app/trunk/src/main/resources/META-INF/org/apache/james/spring-server.xml
(original)
+++
james/app/trunk/src/main/resources/META-INF/org/apache/james/spring-server.xml
Tue Feb 21 08:14:00 2012
@@ -320,7 +320,7 @@
bean
class=org.springframework.beans.factory.config.PropertyPlaceholderConfigurer
property name=ignoreUnresolvablePlaceholders value=true/
-property name =location
value=classpath:META-INF/org/apache/james/database.properties/
+property name =location
value=classpath:james-database.properties/
/bean
bean id=datasource class=org.apache.commons.dbcp.BasicDataSource
destroy-method=close
property name=driverClassName value=${database.driverClassName} /
-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
svn commit: r1291646 - /james/app/trunk/src/main/resources/META-INF/persistence.xml
Author: eric Date: Tue Feb 21 08:19:08 2012 New Revision: 1291646 URL: http://svn.apache.org/viewvc?rev=1291646view=rev Log: Readd the persistence.xml in app, we need the additional domain and user classes (MAILBOX-166) Added: james/app/trunk/src/main/resources/META-INF/persistence.xml Added: james/app/trunk/src/main/resources/META-INF/persistence.xml URL: http://svn.apache.org/viewvc/james/app/trunk/src/main/resources/META-INF/persistence.xml?rev=1291646view=auto == --- james/app/trunk/src/main/resources/META-INF/persistence.xml (added) +++ james/app/trunk/src/main/resources/META-INF/persistence.xml Tue Feb 21 08:19:08 2012 @@ -0,0 +1,48 @@ +?xml version=1.0 encoding=UTF-8? +!-- + Licensed to the Apache Software Foundation (ASF) under one + or more contributor license agreements. See the NOTICE file + distributed with this work for additional information + regarding copyright ownership. The ASF licenses this file + to you under the Apache License, Version 2.0 (the + License); you may not use this file except in compliance + with the License. You may obtain a copy of the License at + +http://www.apache.org/licenses/LICENSE-2.0 + + Unless required by applicable law or agreed to in writing, + software distributed under the License is distributed on an + AS IS BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY + KIND, either express or implied. See the License for the + specific language governing permissions and limitations + under the License. +-- + +persistence xmlns=http://java.sun.com/xml/ns/persistence; +xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; +xsi:schemaLocation=http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_2_0.xsd; +version=2.0 + +persistence-unit name=James transaction-type=RESOURCE_LOCAL +!-- Mailbox stuff-- +classorg.apache.james.mailbox.jpa.mail.model.JPAMailbox/class +classorg.apache.james.mailbox.jpa.mail.model.JPAUserFlag/class + classorg.apache.james.mailbox.jpa.mail.model.openjpa.AbstractJPAMessage/class + classorg.apache.james.mailbox.jpa.mail.model.openjpa.JPAMessage/class + classorg.apache.james.mailbox.jpa.mail.model.openjpa.JPAMessage/class +classorg.apache.james.mailbox.jpa.mail.model.JPAProperty/class +classorg.apache.james.mailbox.jpa.user.model.JPASubscription/class +classorg.apache.james.domainlist.jpa.model.JPADomain/class +classorg.apache.james.user.jpa.model.JPAUser/class +classorg.apache.james.rrt.jpa.model.JPARecipientRewrite/class + +properties +property name=openjpa.jdbc.SynchronizeMappings value=buildSchema(ForeignKeys=true)/ +property name=openjpa.jdbc.MappingDefaults value=ForeignKeyDeleteAction=cascade, JoinForeignKeyDeleteAction=cascade/ +property name=openjpa.jdbc.SchemaFactory value=native(ForeignKeys=true)/ +property name=openjpa.jdbc.QuerySQLCache value=false/ +/properties + +/persistence-unit + +/persistence - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (JAMES-1378) LocalDelivery Mailet should not use deprecated UsersRepositoryAliasingForwarding mailet
LocalDelivery Mailet should not use deprecated UsersRepositoryAliasingForwarding mailet --- Key: JAMES-1378 URL: https://issues.apache.org/jira/browse/JAMES-1378 Project: JAMES Server Issue Type: Improvement Reporter: Eric Charles -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
svn commit: r1291652 - /james/server/trunk/mailets/src/main/java/org/apache/james/transport/mailets/LocalDelivery.java
Author: eric
Date: Tue Feb 21 08:30:43 2012
New Revision: 1291652
URL: http://svn.apache.org/viewvc?rev=1291652view=rev
Log:
LocalDelivery Mailet should not use deprecated
UsersRepositoryAliasingForwarding mailet + code format (JAMES-1378)
Modified:
james/server/trunk/mailets/src/main/java/org/apache/james/transport/mailets/LocalDelivery.java
Modified:
james/server/trunk/mailets/src/main/java/org/apache/james/transport/mailets/LocalDelivery.java
URL:
http://svn.apache.org/viewvc/james/server/trunk/mailets/src/main/java/org/apache/james/transport/mailets/LocalDelivery.java?rev=1291652r1=1291651r2=1291652view=diff
==
---
james/server/trunk/mailets/src/main/java/org/apache/james/transport/mailets/LocalDelivery.java
(original)
+++
james/server/trunk/mailets/src/main/java/org/apache/james/transport/mailets/LocalDelivery.java
Tue Feb 21 08:30:43 2012
@@ -27,6 +27,7 @@ import javax.annotation.Resource;
import javax.mail.MessagingException;
import org.apache.commons.collections.iterators.IteratorChain;
+import org.apache.james.domainlist.api.DomainList;
import org.apache.james.filesystem.api.FileSystem;
import org.apache.james.mailbox.MailboxManager;
import org.apache.james.user.api.UsersRepository;
@@ -36,29 +37,20 @@ import org.apache.mailet.MailetContext;
import org.apache.mailet.base.GenericMailet;
/**
- * Receives a Mail from JamesSpoolManager and takes care of delivery of the
+ * Receives a Mail from the Queue and takes care of delivery of the
* message to local inboxes.
*
- * Since James 2.3.0 this mailet is a composition of
- * UserRepositoryAliasingForwarding and ToMultiRepository configurated to mimic
- * the old LocalDelivery behaviour.
+ * This mailet is a composition of RecipientRewriteTable, SieveMailet
+ * and MailboxManager configured to mimic the old LocalDelivery
+ * James 2.3 behavior.
*/
public class LocalDelivery extends GenericMailet {
-
-/**
- * Mailet that apply aliasing and forwarding
- */
-private UsersRepositoryAliasingForwarding aliasingMailet;
-
-/**
- * Mailet that actually store the message
- */
-private SieveMailet sieveMailet;
-
+private RecipientRewriteTable recipientRewriteTable; // Mailet that
applies RecipientRewriteTable
+private SieveMailet sieveMailet; // Mailet that actually stores the
message
private UsersRepository usersRepository;
-
+private org.apache.james.rrt.api.RecipientRewriteTable rrt;
private MailboxManager mailboxManager;
-
+private DomainList domainList;
private FileSystem fileSystem;
@Resource(name = usersrepository)
@@ -66,6 +58,11 @@ public class LocalDelivery extends Gener
this.usersRepository = usersRepository;
}
+@Resource(name = domainlist)
+public void setDomainList(DomainList domainList) {
+this.domainList = domainList;
+}
+
@Resource(name = mailboxmanager)
public void setMailboxManager(MailboxManager mailboxManager) {
this.mailboxManager = mailboxManager;
@@ -76,17 +73,20 @@ public class LocalDelivery extends Gener
this.fileSystem = fileSystem;
}
+@Resource(name = recipientrewritetable)
+public final void
setRecipientRewriteTable(org.apache.james.rrt.api.RecipientRewriteTable rrt) {
+this.rrt = rrt;
+}
+
/**
* Delivers a mail to a local mailbox.
*
- * @param mail
- *the mail being processed
+ * @param mail the mail being processed
*
- * @throws MessagingException
- * if an error occurs while storing the mail
+ * @throws MessagingException if an error occurs while storing the mail
*/
public void service(Mail mail) throws MessagingException {
-aliasingMailet.service(mail);
+recipientRewriteTable.service(mail);
if (mail.getState() != Mail.GHOST) {
sieveMailet.service(mail);
}
@@ -105,15 +105,20 @@ public class LocalDelivery extends Gener
* @see org.apache.mailet.base.GenericMailet#init()
*/
public void init() throws MessagingException {
+
super.init();
-aliasingMailet = new UsersRepositoryAliasingForwarding();
-aliasingMailet.setUsersRepository(usersRepository);
-aliasingMailet.init(getMailetConfig());
+recipientRewriteTable = new RecipientRewriteTable();
+recipientRewriteTable.setDomainList(domainList);
+recipientRewriteTable.setRecipientRewriteTable(rrt);
+recipientRewriteTable.init(getMailetConfig());
+
sieveMailet = new SieveMailet();
-MailetConfig m = new MailetConfig() {
-
-/**
+sieveMailet.setUsersRepository(usersRepository);
+sieveMailet.setMailboxManager(mailboxManager);
+sieveMailet.setFileSystem(fileSystem);
+sieveMailet.init(new MailetConfig() {
+/*
* @see
[jira] [Closed] (JAMES-1378) LocalDelivery Mailet should not use deprecated UsersRepositoryAliasingForwarding mailet
[ https://issues.apache.org/jira/browse/JAMES-1378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Charles closed JAMES-1378. --- Resolution: Fixed Fix Version/s: 3.0-beta4 Assignee: Eric Charles Done LocalDelivery Mailet should not use deprecated UsersRepositoryAliasingForwarding mailet --- Key: JAMES-1378 URL: https://issues.apache.org/jira/browse/JAMES-1378 Project: JAMES Server Issue Type: Improvement Reporter: Eric Charles Assignee: Eric Charles Fix For: 3.0-beta4 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (JAMES-1379) Default mailet configuration should not apply RecipientRewriteTable
Default mailet configuration should not apply RecipientRewriteTable --- Key: JAMES-1379 URL: https://issues.apache.org/jira/browse/JAMES-1379 Project: JAMES Server Issue Type: Improvement Reporter: Eric Charles Assignee: Eric Charles -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Updated] (JAMES-1379) Default mailet configuration should not apply RecipientRewriteTable nor RecipientToLowerCase
[ https://issues.apache.org/jira/browse/JAMES-1379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Charles updated JAMES-1379: Summary: Default mailet configuration should not apply RecipientRewriteTable nor RecipientToLowerCase (was: Default mailet configuration should not apply RecipientRewriteTable) Default mailet configuration should not apply RecipientRewriteTable nor RecipientToLowerCase Key: JAMES-1379 URL: https://issues.apache.org/jira/browse/JAMES-1379 Project: JAMES Server Issue Type: Improvement Reporter: Eric Charles Assignee: Eric Charles -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
Re: [VOTE] Release Apache James jSieve 0.5
[X] +1 Please release - Manolo On Tue, Feb 21, 2012 at 5:50 AM, Felix Knecht fe...@otego.com wrote: [X] +1 Please release Regards Felix --**--**- To unsubscribe, e-mail: server-dev-unsubscribe@james.**apache.orgserver-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-help@james.apache.**orgserver-dev-h...@james.apache.org
[jira] [Commented] (JAMES-1379) Default mailet configuration should not apply RecipientRewriteTable nor RecipientToLowerCase
[ https://issues.apache.org/jira/browse/JAMES-1379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13212459#comment-13212459 ] Eric Charles commented on JAMES-1379: - The recipientrewritetable is already applied in the localdelivery mailet. The RecipientToLowerCase is not more useful, as we now lowercase all (user+domain part of email, see JAMES-1369). Default mailet configuration should not apply RecipientRewriteTable nor RecipientToLowerCase Key: JAMES-1379 URL: https://issues.apache.org/jira/browse/JAMES-1379 Project: JAMES Server Issue Type: Improvement Reporter: Eric Charles Assignee: Eric Charles -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
svn commit: r1291656 - /james/server/trunk/mailetcontainer-api/src/main/resources/mailetcontainer.conf
Author: eric Date: Tue Feb 21 08:38:20 2012 New Revision: 1291656 URL: http://svn.apache.org/viewvc?rev=1291656view=rev Log: Default mailet configuration should not apply RecipientRewriteTable nor RecipientToLowerCase (JAMES-1379) Modified: james/server/trunk/mailetcontainer-api/src/main/resources/mailetcontainer.conf Modified: james/server/trunk/mailetcontainer-api/src/main/resources/mailetcontainer.conf URL: http://svn.apache.org/viewvc/james/server/trunk/mailetcontainer-api/src/main/resources/mailetcontainer.conf?rev=1291656r1=1291655r2=1291656view=diff == --- james/server/trunk/mailetcontainer-api/src/main/resources/mailetcontainer.conf (original) +++ james/server/trunk/mailetcontainer-api/src/main/resources/mailetcontainer.conf Tue Feb 21 08:38:20 2012 @@ -27,7 +27,7 @@ /context spooler -threads 20 /threads +threads20/threads /spooler processors @@ -39,7 +39,7 @@ /mailet mailet match=InSpammerBlacklist=dnsbl.njabl.org. class=ToProcessor processorspam/processor -notice550 Requested action not taken: rejected - see http://njabl.org/ /notice +notice550 Requested action not taken: rejected - see http://njabl.org//notice /mailet mailet match=All class=ToProcessor processortransport/processor @@ -51,12 +51,6 @@ nameX-UserIsAuth/name valuetrue/value /mailet - mailet match=All class=RecipientRewriteTable - recipientrewritetableDefaultRecipientRewriteTable/recipientrewritetable - /mailet - !-- Disable this if you want to have case-sensitive local-parts of the recipients -- - mailet match=RecipientIsLocal class=RecipientToLowerCase/ - mailet match=RecipientIsLocal class=LocalDelivery/ mailet match=HostIsLocal class=ToProcessor processorlocal-address-error/processor @@ -108,4 +102,5 @@ /mailet /processor /processors + /mailetcontainer - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
Build failed in Jenkins: james-app-trunk #621
See https://builds.apache.org/job/james-app-trunk/621/changes Changes: [eric] Readd the persistence.xml in app, we need the additional domain and user classes (MAILBOX-166) [eric] impact spring-server.xml with james-database.properties name and place (MAILBOX-166) -- [...truncated 618 lines...] [INFO] Installing /home/jenkins/.m2/repository/org/apache/james/apache-james-mailbox-api/0.4-SNAPSHOT/apache-james-mailbox-api-0.4-SNAPSHOT.jar to https://builds.apache.org/job/james-app-trunk/ws/trunk/target/appassembler/lib/apache-james-mailbox-api-0.4-20120221.044209-355.jar [INFO] Installing /home/jenkins/.m2/repository/org/apache/james/apache-james-mailbox-tool/0.4-SNAPSHOT/apache-james-mailbox-tool-0.4-SNAPSHOT.jar to https://builds.apache.org/job/james-app-trunk/ws/trunk/target/appassembler/lib/apache-james-mailbox-tool-0.4-20120221.044739-272.jar [INFO] Installing /home/jenkins/.m2/repository/org/apache/geronimo/specs/geronimo-annotation_1.0_spec/1.1.1/geronimo-annotation_1.0_spec-1.1.1.jar to https://builds.apache.org/job/james-app-trunk/ws/trunk/target/appassembler/lib/geronimo-annotation_1.0_spec-1.1.1.jar [INFO] Installing /home/jenkins/.m2/repository/org/apache/james/protocols/protocols-api/1.6.2/protocols-api-1.6.2.jar to https://builds.apache.org/job/james-app-trunk/ws/trunk/target/appassembler/lib/protocols-api-1.6.2.jar [INFO] Installing /home/jenkins/.m2/repository/org/apache/james/apache-mailet/2.4/apache-mailet-2.4.jar to https://builds.apache.org/job/james-app-trunk/ws/trunk/target/appassembler/lib/apache-mailet-2.4.jar [INFO] Installing /home/jenkins/.m2/repository/org/springframework/spring-core/3.1.0.RELEASE/spring-core-3.1.0.RELEASE.jar to https://builds.apache.org/job/james-app-trunk/ws/trunk/target/appassembler/lib/spring-core-3.1.0.RELEASE.jar [INFO] Installing /home/jenkins/.m2/repository/org/springframework/spring-asm/3.1.0.RELEASE/spring-asm-3.1.0.RELEASE.jar to https://builds.apache.org/job/james-app-trunk/ws/trunk/target/appassembler/lib/spring-asm-3.1.0.RELEASE.jar [INFO] Installing /home/jenkins/.m2/repository/org/springframework/spring-beans/3.1.0.RELEASE/spring-beans-3.1.0.RELEASE.jar to https://builds.apache.org/job/james-app-trunk/ws/trunk/target/appassembler/lib/spring-beans-3.1.0.RELEASE.jar [INFO] Installing /home/jenkins/.m2/repository/org/springframework/spring-context/3.1.0.RELEASE/spring-context-3.1.0.RELEASE.jar to https://builds.apache.org/job/james-app-trunk/ws/trunk/target/appassembler/lib/spring-context-3.1.0.RELEASE.jar [INFO] Installing /home/jenkins/.m2/repository/org/springframework/spring-expression/3.1.0.RELEASE/spring-expression-3.1.0.RELEASE.jar to https://builds.apache.org/job/james-app-trunk/ws/trunk/target/appassembler/lib/spring-expression-3.1.0.RELEASE.jar [INFO] Installing /home/jenkins/.m2/repository/org/springframework/spring-web/3.1.0.RELEASE/spring-web-3.1.0.RELEASE.jar to https://builds.apache.org/job/james-app-trunk/ws/trunk/target/appassembler/lib/spring-web-3.1.0.RELEASE.jar [INFO] Installing /home/jenkins/.m2/repository/commons-configuration/commons-configuration/1.6/commons-configuration-1.6.jar to https://builds.apache.org/job/james-app-trunk/ws/trunk/target/appassembler/lib/commons-configuration-1.6.jar [INFO] Installing /home/jenkins/.m2/repository/commons-lang/commons-lang/2.6/commons-lang-2.6.jar to https://builds.apache.org/job/james-app-trunk/ws/trunk/target/appassembler/lib/commons-lang-2.6.jar [INFO] Installing /home/jenkins/.m2/repository/javax/mail/mail/1.4.4/mail-1.4.4.jar to https://builds.apache.org/job/james-app-trunk/ws/trunk/target/appassembler/lib/mail-1.4.4.jar [INFO] Installing /home/jenkins/.m2/repository/log4j/log4j/1.2.16/log4j-1.2.16.jar to https://builds.apache.org/job/james-app-trunk/ws/trunk/target/appassembler/lib/log4j-1.2.16.jar [INFO] Installing /home/jenkins/.m2/repository/org/apache/james/james-server-lifecycle-spring/3.0-beta4-SNAPSHOT/james-server-lifecycle-spring-3.0-beta4-SNAPSHOT.jar to https://builds.apache.org/job/james-app-trunk/ws/trunk/target/appassembler/lib/james-server-lifecycle-spring-3.0-beta4-20120220.155201-749.jar [INFO] Installing /home/jenkins/.m2/repository/org/apache/geronimo/specs/geronimo-annotation_1.1_spec/1.0.1/geronimo-annotation_1.1_spec-1.0.1.jar to https://builds.apache.org/job/james-app-trunk/ws/trunk/target/appassembler/lib/geronimo-annotation_1.1_spec-1.0.1.jar [INFO] Installing /home/jenkins/.m2/repository/org/apache/geronimo/specs/geronimo-jpa_2.0_spec/1.0/geronimo-jpa_2.0_spec-1.0.jar to https://builds.apache.org/job/james-app-trunk/ws/trunk/target/appassembler/lib/geronimo-jpa_2.0_spec-1.0.jar [INFO] Installing /home/jenkins/.m2/repository/org/apache/james/james-server-cli/3.0-beta4-SNAPSHOT/james-server-cli-3.0-beta4-SNAPSHOT.jar to https://builds.apache.org/job/james-app-trunk/ws/trunk/target/appassembler/lib/james-server-cli-3.0-beta4-20120220.155938-604.jar [INFO]
svn commit: r1291660 - /james/app/trunk/src/main/resources/mailetcontainer-template.conf
Author: eric Date: Tue Feb 21 08:46:33 2012 New Revision: 1291660 URL: http://svn.apache.org/viewvc?rev=1291660view=rev Log: RecipientRewriteTable mailet is not configurable, update this in the mailetcontainer-template Modified: james/app/trunk/src/main/resources/mailetcontainer-template.conf Modified: james/app/trunk/src/main/resources/mailetcontainer-template.conf URL: http://svn.apache.org/viewvc/james/app/trunk/src/main/resources/mailetcontainer-template.conf?rev=1291660r1=1291659r2=1291660view=diff == --- james/app/trunk/src/main/resources/mailetcontainer-template.conf (original) +++ james/app/trunk/src/main/resources/mailetcontainer-template.conf Tue Feb 21 08:46:33 2012 @@ -17,8 +17,11 @@ specific language governing permissions and limitations under the License. -- + !-- This block is responsible for processing messages on the spool. -- + mailetcontainer + !-- MailAddress used for PostMaster -- postmasterPostmaster@localhost/postmaster @@ -27,7 +30,6 @@ !-- expose JMX MBeans -- enableJmxtrue/enableJmx - !-- The root processor is a required processor - James routes all mail on the spool -- !-- through this processor first. -- @@ -402,10 +404,8 @@ Regards, Postmaster XXX.YYY /mailet -- - !-- The RecipientRewriteTable will use the definitions found in recipientrewritetable-store.xml -- - mailet match=All class=RecipientRewriteTable - recipientrewritetableDefaultRecipientRewriteTable/recipientrewritetable - /mailet + !-- The RecipientRewriteTable will use the definitions found in recipientrewritetablexml -- + mailet match=All class=RecipientRewriteTable / !-- Is the recipient is for a local account, deliver it locally -- mailet match=RecipientIsLocal class=LocalDelivery/ - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Resolved] (JAMES-1379) Default mailet configuration should not apply RecipientRewriteTable nor RecipientToLowerCase
[ https://issues.apache.org/jira/browse/JAMES-1379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Charles resolved JAMES-1379. - Resolution: Fixed Fix Version/s: 3.0-beta4 Done. Default mailet configuration should not apply RecipientRewriteTable nor RecipientToLowerCase Key: JAMES-1379 URL: https://issues.apache.org/jira/browse/JAMES-1379 Project: JAMES Server Issue Type: Improvement Reporter: Eric Charles Assignee: Eric Charles Fix For: 3.0-beta4 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
svn commit: r1291664 - /james/app/trunk/src/debian/control/conffiles
Author: eric
Date: Tue Feb 21 08:54:49 2012
New Revision: 1291664
URL: http://svn.apache.org/viewvc?rev=1291664view=rev
Log:
update the debian conffile futher to configuration files renames
Modified:
james/app/trunk/src/debian/control/conffiles
Modified: james/app/trunk/src/debian/control/conffiles
URL:
http://svn.apache.org/viewvc/james/app/trunk/src/debian/control/conffiles?rev=1291664r1=1291663r2=1291664view=diff
==
--- james/app/trunk/src/debian/control/conffiles (original)
+++ james/app/trunk/src/debian/control/conffiles Tue Feb 21 08:54:49 2012
@@ -3,7 +3,8 @@
/etc/${project.artifactId}/fetchmail.conf
/etc/${project.artifactId}/hbase-site.conf
/etc/${project.artifactId}/imapserver.conf
-/etc/${project.artifactId}/jcr-repository.conf
+/etc/${project.artifactId}/james-database.properties
+/etc/${project.artifactId}/jcr-repository.xml
/etc/${project.artifactId}/jmx.properties
/etc/${project.artifactId}/lmtpserver.conf
/etc/${project.artifactId}/log4j.properties
-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (JAMES-1380) Default mailet configuration should not apply InSpammerBlacklist
Default mailet configuration should not apply InSpammerBlacklist Key: JAMES-1380 URL: https://issues.apache.org/jira/browse/JAMES-1380 Project: JAMES Server Issue Type: Improvement Reporter: Eric Charles InSpammerBlacklist is configured by default in the mailetcontainer.xml mailet match=InSpammerBlacklist=dnsbl.njabl.org. class=ToProcessor processorspam/processor notice550 Requested action not taken: rejected - see http://njabl.org//notice /mailet This gives a safer default configuration but slows down the spooling. This configuration will still be present in the -template, and thus can be applied by any administrator before starting the server. I propose to get rid of it. If I don't hear anything against, I will to it tomorrow. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
Build failed in Jenkins: james-app-trunk #622
See https://builds.apache.org/job/james-app-trunk/622/changes Changes: [eric] update the debian conffile futher to configuration files renames [eric] RecipientRewriteTable mailet is not configurable, update this in the mailetcontainer-template -- [...truncated 378 lines...] [INFO] Installing /home/jenkins/.m2/repository/org/apache/james/apache-james-mailbox-api/0.4-SNAPSHOT/apache-james-mailbox-api-0.4-SNAPSHOT.jar to https://builds.apache.org/job/james-app-trunk/ws/trunk/target/appassembler/lib/apache-james-mailbox-api-0.4-20120221.044209-355.jar [INFO] Installing /home/jenkins/.m2/repository/org/apache/james/apache-james-mailbox-tool/0.4-SNAPSHOT/apache-james-mailbox-tool-0.4-SNAPSHOT.jar to https://builds.apache.org/job/james-app-trunk/ws/trunk/target/appassembler/lib/apache-james-mailbox-tool-0.4-20120221.044739-272.jar [INFO] Installing /home/jenkins/.m2/repository/org/apache/geronimo/specs/geronimo-annotation_1.0_spec/1.1.1/geronimo-annotation_1.0_spec-1.1.1.jar to https://builds.apache.org/job/james-app-trunk/ws/trunk/target/appassembler/lib/geronimo-annotation_1.0_spec-1.1.1.jar [INFO] Installing /home/jenkins/.m2/repository/org/apache/james/protocols/protocols-api/1.6.2/protocols-api-1.6.2.jar to https://builds.apache.org/job/james-app-trunk/ws/trunk/target/appassembler/lib/protocols-api-1.6.2.jar [INFO] Installing /home/jenkins/.m2/repository/org/apache/james/apache-mailet/2.4/apache-mailet-2.4.jar to https://builds.apache.org/job/james-app-trunk/ws/trunk/target/appassembler/lib/apache-mailet-2.4.jar [INFO] Installing /home/jenkins/.m2/repository/org/springframework/spring-core/3.1.0.RELEASE/spring-core-3.1.0.RELEASE.jar to https://builds.apache.org/job/james-app-trunk/ws/trunk/target/appassembler/lib/spring-core-3.1.0.RELEASE.jar [INFO] Installing /home/jenkins/.m2/repository/org/springframework/spring-asm/3.1.0.RELEASE/spring-asm-3.1.0.RELEASE.jar to https://builds.apache.org/job/james-app-trunk/ws/trunk/target/appassembler/lib/spring-asm-3.1.0.RELEASE.jar [INFO] Installing /home/jenkins/.m2/repository/org/springframework/spring-beans/3.1.0.RELEASE/spring-beans-3.1.0.RELEASE.jar to https://builds.apache.org/job/james-app-trunk/ws/trunk/target/appassembler/lib/spring-beans-3.1.0.RELEASE.jar [INFO] Installing /home/jenkins/.m2/repository/org/springframework/spring-context/3.1.0.RELEASE/spring-context-3.1.0.RELEASE.jar to https://builds.apache.org/job/james-app-trunk/ws/trunk/target/appassembler/lib/spring-context-3.1.0.RELEASE.jar [INFO] Installing /home/jenkins/.m2/repository/org/springframework/spring-expression/3.1.0.RELEASE/spring-expression-3.1.0.RELEASE.jar to https://builds.apache.org/job/james-app-trunk/ws/trunk/target/appassembler/lib/spring-expression-3.1.0.RELEASE.jar [INFO] Installing /home/jenkins/.m2/repository/org/springframework/spring-web/3.1.0.RELEASE/spring-web-3.1.0.RELEASE.jar to https://builds.apache.org/job/james-app-trunk/ws/trunk/target/appassembler/lib/spring-web-3.1.0.RELEASE.jar [INFO] Installing /home/jenkins/.m2/repository/commons-configuration/commons-configuration/1.6/commons-configuration-1.6.jar to https://builds.apache.org/job/james-app-trunk/ws/trunk/target/appassembler/lib/commons-configuration-1.6.jar [INFO] Installing /home/jenkins/.m2/repository/commons-lang/commons-lang/2.6/commons-lang-2.6.jar to https://builds.apache.org/job/james-app-trunk/ws/trunk/target/appassembler/lib/commons-lang-2.6.jar [INFO] Installing /home/jenkins/.m2/repository/javax/mail/mail/1.4.4/mail-1.4.4.jar to https://builds.apache.org/job/james-app-trunk/ws/trunk/target/appassembler/lib/mail-1.4.4.jar [INFO] Installing /home/jenkins/.m2/repository/log4j/log4j/1.2.16/log4j-1.2.16.jar to https://builds.apache.org/job/james-app-trunk/ws/trunk/target/appassembler/lib/log4j-1.2.16.jar [INFO] Installing /home/jenkins/.m2/repository/org/apache/james/james-server-lifecycle-spring/3.0-beta4-SNAPSHOT/james-server-lifecycle-spring-3.0-beta4-SNAPSHOT.jar to https://builds.apache.org/job/james-app-trunk/ws/trunk/target/appassembler/lib/james-server-lifecycle-spring-3.0-beta4-20120220.155201-749.jar [INFO] Installing /home/jenkins/.m2/repository/org/apache/geronimo/specs/geronimo-annotation_1.1_spec/1.0.1/geronimo-annotation_1.1_spec-1.0.1.jar to https://builds.apache.org/job/james-app-trunk/ws/trunk/target/appassembler/lib/geronimo-annotation_1.1_spec-1.0.1.jar [INFO] Installing /home/jenkins/.m2/repository/org/apache/geronimo/specs/geronimo-jpa_2.0_spec/1.0/geronimo-jpa_2.0_spec-1.0.jar to https://builds.apache.org/job/james-app-trunk/ws/trunk/target/appassembler/lib/geronimo-jpa_2.0_spec-1.0.jar [INFO] Installing /home/jenkins/.m2/repository/org/apache/james/james-server-cli/3.0-beta4-SNAPSHOT/james-server-cli-3.0-beta4-SNAPSHOT.jar to https://builds.apache.org/job/james-app-trunk/ws/trunk/target/appassembler/lib/james-server-cli-3.0-beta4-20120220.155938-604.jar [INFO] Installing
[jira] [Commented] (JAMES-1379) Default mailet configuration should not apply RecipientRewriteTable nor RecipientToLowerCase
[ https://issues.apache.org/jira/browse/JAMES-1379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13212488#comment-13212488 ] Eric Charles commented on JAMES-1379: - RecipientToLowerCase is still needed to cover recipient with upper cases.. Readding it. Default mailet configuration should not apply RecipientRewriteTable nor RecipientToLowerCase Key: JAMES-1379 URL: https://issues.apache.org/jira/browse/JAMES-1379 Project: JAMES Server Issue Type: Improvement Reporter: Eric Charles Assignee: Eric Charles Fix For: 3.0-beta4 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
svn commit: r1291682 - /james/server/trunk/mailetcontainer-api/src/main/resources/mailetcontainer.conf
Author: eric Date: Tue Feb 21 10:06:29 2012 New Revision: 1291682 URL: http://svn.apache.org/viewvc?rev=1291682view=rev Log: Readd the RecipientToLowerCase mailet (JAMES-1379) Modified: james/server/trunk/mailetcontainer-api/src/main/resources/mailetcontainer.conf Modified: james/server/trunk/mailetcontainer-api/src/main/resources/mailetcontainer.conf URL: http://svn.apache.org/viewvc/james/server/trunk/mailetcontainer-api/src/main/resources/mailetcontainer.conf?rev=1291682r1=1291681r2=1291682view=diff == --- james/server/trunk/mailetcontainer-api/src/main/resources/mailetcontainer.conf (original) +++ james/server/trunk/mailetcontainer-api/src/main/resources/mailetcontainer.conf Tue Feb 21 10:06:29 2012 @@ -51,6 +51,7 @@ nameX-UserIsAuth/name valuetrue/value /mailet + mailet match=RecipientIsLocal class=RecipientToLowerCase/ mailet match=RecipientIsLocal class=LocalDelivery/ mailet match=HostIsLocal class=ToProcessor processorlocal-address-error/processor - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Updated] (JAMES-1379) Default mailet configuration should not apply RecipientRewriteTable
[ https://issues.apache.org/jira/browse/JAMES-1379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Charles updated JAMES-1379: Summary: Default mailet configuration should not apply RecipientRewriteTable (was: Default mailet configuration should not apply RecipientRewriteTable nor RecipientToLowerCase) Default mailet configuration should not apply RecipientRewriteTable --- Key: JAMES-1379 URL: https://issues.apache.org/jira/browse/JAMES-1379 Project: JAMES Server Issue Type: Improvement Reporter: Eric Charles Assignee: Eric Charles Fix For: 3.0-beta4 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
Re: [VOTE] Release Apache James jSieve 0.5
2012/2/20 Eric Charles e...@apache.org: Hi there, In preparation of James server 3.0b4 release, we have have to release jSieve 0.5. This release uses the latest mime4j 0.7.2. which makes it compatible with server. The manager module is not taken in this release as it depends on a server snapshot. If manager depends on server then it cannot be included in the jsieve tree as server already depends on jsieve and we don't want bidirectional dependency (or we'll be hit by this at each release cycle) You can see the list of changes on https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10412version=12314991 So please cast your VOTE: https://repository.apache.org/content/repositories/orgapachejames-003 [X] -1 Something is wrong I can't find the source package for this release (AFAIK we can't vote binaries). It was available in the 0.4 package (http://apache.fastbull.org/james/apache-jsieve/0.4/apache-james-jsieve-0.4-src.zip) , so maybe something gone wrong with the latest pom changes or with the release process. Stefano - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
Re: How to build James from trunk
Gentlemen, I still have problems to understand what is normal and what is not normal with maven and James. (1) From what goes on on this mailing list I have understood that James Components live their lives quite independently from each other. So, it is normal that in some development phases component1 has version 0.2 in its pom.xml but in other modules' poms component1 version 0.1 is still referenced. (Am I right so far?) Note that in this example the referenced version 0.1 is lover than the trunk version 0.2. There are two principal kinds of references in Maven poms: (i) dependency and (ii) parent. As for dependencies, it is perfectly reasonable for me that component2 depends on component1 version 0.1, whereby there is already the version 0.2 of component1 in the trunk. But as for parent references I am asking myself what can be the reason for distinct versions in the parent's project.version and its child's project.parent.version? Here is an example from the current trunk: apache-jsieve has version 0.6-SNAPSHOT in its pom, but 0.5-SNAPSHOT is referenced in apache-jsieve-assemble's pom as its parent. Both m2e and mvn install complain about that. When I replace 0.5-SNAPSHOT in apache-jsieve-assemble's pom with 0.6-SNAPSHOT it works. Is it a bug? apache-james-mailbox referencing james-project 1.8.1-SNAPSHOT as its parent is another example. Why does it not reference james-project 1.8.2-SNAPSHOT? Generally, which are there situations in which parent reference version lower than parent trunk version make sense? (2) In (1) I spoke about the case when referenced version is lover than the trunk version. Here I am asking about the opposite: hupa-parent references james-project 1.9-SNAPSHOT as its parent but the version of james-project in the trunk is 1.8.2-SNAPSHOT. This cannot be OK, can it? hupa-parent should be fixed to reference james-project 1.8.2-SNAPSHOT as its parent, should it not? (3) Generally, is the following sequence always expected to work and if it does not, is it a reason to file a bug in Jira? rm -Rf $HOME/.m2/repository cd james/current svn update mvn clean install -DskipTests Best, gazda On Fri, Jan 13, 2012 at 10:23 AM, Jochen Gazda gazdahims...@gmail.com wrote: Thanks for the tips, Eric and Ioan. Maven seems to work as expected now. Gazda On Thu, Jan 12, 2012 at 8:13 AM, Ioan Eugen Stan stan.ieu...@gmail.com wrote: Pe 11.01.2012 21:40, Eric Charles a scris: Hi Jochen, Your settings.xml seems ok. 'mvn package' (or even compile) from a toplevel should take the snapshots from your sources even if not installed. I usually invoke 'mvn clean install' in case of weird behaviour. Can you now compile? Thx, Eric Also, sometimes, it helps to delete all downloaded files from your maven local repository. -- Ioan Eugen Stan http://ieugen.blogspot.com - 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
Limit Mail Box Size
Hi, Good morning. Is there a way we can limit the mail box size for each user? Thanks, Sai.
Re: How to build James from trunk
2012/2/21 Jochen Gazda gazdahims...@gmail.com: (1) [] But as for parent references I am asking myself what can be the reason for distinct versions in the parent's project.version and its child's project.parent.version? Here is an example from the current trunk: apache-jsieve has version 0.6-SNAPSHOT in its pom, but 0.5-SNAPSHOT is referenced in apache-jsieve-assemble's pom as its parent. Both m2e and mvn install complain about that. When I replace 0.5-SNAPSHOT in apache-jsieve-assemble's pom with 0.6-SNAPSHOT it works. Is it a bug? IMO ti does not make sense and it is a bug. I guess the issue is related to the use of parent module in a subfolder pattern, that is much more difficult to deal with. apache-james-mailbox referencing james-project 1.8.1-SNAPSHOT as its parent is another example. Why does it not reference james-project 1.8.2-SNAPSHOT? Maybe simply because the last time we worked on mailbox we only had 1.8.1-SNAPSHOT and the parent moved forward in the mean time. This is not a big issue, but you can move mailvox to 1.8.1 final or to 1.8.2-SNAPSHOT if it helps. Generally, which are there situations in which parent reference version lower than parent trunk version make sense? It simply happens because we don't start upgrading every project pom when we move the parent forward but we only upgrade them when we need a release. Otherwise we should always try to build with the latest available released parent (not even a snapshot). (2) In (1) I spoke about the case when referenced version is lover than the trunk version. Here I am asking about the opposite: hupa-parent references james-project 1.9-SNAPSHOT as its parent but the version of james-project in the trunk is 1.8.2-SNAPSHOT. This cannot be OK, can it? Well, when you work with snapshot everything can be right or wrong. If you release 1.8 then you automatically create 1.9-SNAPSHOT.. after a while you decide to release 1.9-SNAPSHOT as 1.8.1 and this will move you to 1.8.2-SNAPSHOT. As they are snapshots it is not so bad. hupa-parent should be fixed to reference james-project 1.8.2-SNAPSHOT as its parent, should it not? BTW, it would be better to point to 1.8.1 because it probably doesn't need anymore to point to a snapshot for the parent. (3) Generally, is the following sequence always expected to work and if it does not, is it a reason to file a bug in Jira? rm -Rf $HOME/.m2/repository cd james/current svn update mvn clean install -DskipTests I often found problematic to run a single pass mvn clean install but runinng the mvn clean package mvn install for each project (in the right order, so to not depend on only snapshot repositories) is expected to work and if it doesn't work we should probably fix something. Stefano - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (JSIEVE-86) Potential bidirectional dependency between jsieve manager and server
Potential bidirectional dependency between jsieve manager and server Key: JSIEVE-86 URL: https://issues.apache.org/jira/browse/JSIEVE-86 Project: JAMES jSieve Issue Type: New Feature Reporter: Eric Charles sieve manager is aimed to be used in server james-server-filesystem-api is the one to talk about... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (JSIEVE-87) james-jsieve artifact should not produce -src.zip/tar.gz, just -sources.jar
james-jsieve artifact should not produce -src.zip/tar.gz, just -sources.jar Key: JSIEVE-87 URL: https://issues.apache.org/jira/browse/JSIEVE-87 Project: JAMES jSieve Issue Type: Improvement Reporter: Eric Charles -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
svn commit: r1291885 - /james/jsieve/trunk/assemble/pom.xml
Author: eric Date: Tue Feb 21 16:02:07 2012 New Revision: 1291885 URL: http://svn.apache.org/viewvc?rev=1291885view=rev Log: Set parent as 0.6-SNAPSHOT and define jsieve-core dependency to make it compile Modified: james/jsieve/trunk/assemble/pom.xml Modified: james/jsieve/trunk/assemble/pom.xml URL: http://svn.apache.org/viewvc/james/jsieve/trunk/assemble/pom.xml?rev=1291885r1=1291884r2=1291885view=diff == --- james/jsieve/trunk/assemble/pom.xml (original) +++ james/jsieve/trunk/assemble/pom.xml Tue Feb 21 16:02:07 2012 @@ -23,7 +23,7 @@ parent groupIdorg.apache.james/groupId artifactIdapache-jsieve/artifactId -version0.5-SNAPSHOT/version +version0.6-SNAPSHOT/version relativePath../relativePath /parent @@ -42,7 +42,7 @@ dependencies dependency groupIdorg.apache.james/groupId -artifactIdapache-jsieve/artifactId +artifactIdapache-jsieve-core/artifactId /dependency dependency - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Resolved] (HUPA-84) Make web.xml dtd compliant
[ https://issues.apache.org/jira/browse/HUPA-84?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jochen Gazda resolved HUPA-84. -- Resolution: Fixed Make web.xml dtd compliant -- Key: HUPA-84 URL: https://issues.apache.org/jira/browse/HUPA-84 Project: JAMES Hupa Issue Type: Bug Components: client Reporter: Jochen Gazda Assignee: Norman Maurer Attachments: HUPA-84-patch.txt The patch follows -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Closed] (HUPA-84) Make web.xml dtd compliant
[ https://issues.apache.org/jira/browse/HUPA-84?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jochen Gazda closed HUPA-84. Make web.xml dtd compliant -- Key: HUPA-84 URL: https://issues.apache.org/jira/browse/HUPA-84 Project: JAMES Hupa Issue Type: Bug Components: client Reporter: Jochen Gazda Assignee: Norman Maurer Attachments: HUPA-84-patch.txt The patch follows -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
Re: How to build James from trunk
Hi, james-project:1.9-SNAPSHOT should be 1.8.1 or 1.8.2-SNAPSHOT (1.9-SNAPSHOT are rest that need cleanup). All James projects have their own lifecycle, but also communicate with each other. For example, bidirectional dependencies, strategy for assemble maven module... are something we talk about. Ideas and fixes welcome! Thx, Eric On 21/02/12 15:31, Stefano Bagnara wrote: 2012/2/21 Jochen Gazdagazdahims...@gmail.com: (1) [] But as for parent references I am asking myself what can be the reason for distinct versions in the parent's project.version and its child's project.parent.version? Here is an example from the current trunk: apache-jsieve has version 0.6-SNAPSHOT in its pom, but 0.5-SNAPSHOT is referenced in apache-jsieve-assemble's pom as its parent. Both m2e and mvn install complain about that. When I replace 0.5-SNAPSHOT in apache-jsieve-assemble's pom with 0.6-SNAPSHOT it works. Is it a bug? IMO ti does not make sense and it is a bug. I guess the issue is related to the use of parent module in a subfolder pattern, that is much more difficult to deal with. apache-james-mailbox referencing james-project 1.8.1-SNAPSHOT as its parent is another example. Why does it not reference james-project 1.8.2-SNAPSHOT? Maybe simply because the last time we worked on mailbox we only had 1.8.1-SNAPSHOT and the parent moved forward in the mean time. This is not a big issue, but you can move mailvox to 1.8.1 final or to 1.8.2-SNAPSHOT if it helps. Generally, which are there situations in which parent reference version lower than parent trunk version make sense? It simply happens because we don't start upgrading every project pom when we move the parent forward but we only upgrade them when we need a release. Otherwise we should always try to build with the latest available released parent (not even a snapshot). (2) In (1) I spoke about the case when referenced version is lover than the trunk version. Here I am asking about the opposite: hupa-parent references james-project 1.9-SNAPSHOT as its parent but the version of james-project in the trunk is 1.8.2-SNAPSHOT. This cannot be OK, can it? Well, when you work with snapshot everything can be right or wrong. If you release 1.8 then you automatically create 1.9-SNAPSHOT.. after a while you decide to release 1.9-SNAPSHOT as 1.8.1 and this will move you to 1.8.2-SNAPSHOT. As they are snapshots it is not so bad. hupa-parent should be fixed to reference james-project 1.8.2-SNAPSHOT as its parent, should it not? BTW, it would be better to point to 1.8.1 because it probably doesn't need anymore to point to a snapshot for the parent. (3) Generally, is the following sequence always expected to work and if it does not, is it a reason to file a bug in Jira? rm -Rf $HOME/.m2/repository cd james/current svn update mvn clean install -DskipTests I often found problematic to run a single pass mvn clean install but runinng the mvn clean package mvn install for each project (in the right order, so to not depend on only snapshot repositories) is expected to work and if it doesn't work we should probably fix something. Stefano - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org -- eric | http://about.echarles.net | @echarles - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
Make the namespace handling consistent and predictable
Gentlemen,
On the way to usable group folders and ACL, I found that namespaces
are not handled consistently.
(1) in StoreMessageManager.isGroupFolder(MailboxSession), if the
present folder is the current user's INBOX, mailbox.getNamespace() and
session.getPersonalSpace() should return the same value, which they do
not.
I could achieve the desired behavior when I changed this part of
SimpleMailboxSession constructor from
if (otherUsersSpace == null (sharedSpaces == null ||
sharedSpaces.isEmpty())) {
this.personalSpace = ;
} else {
this.personalSpace = MailboxConstants.USER_NAMESPACE;
}
to
this.personalSpace = MailboxConstants.USER_NAMESPACE;
Can this cause any unwanted consequences?
(2) in AbstractMailboxProcessor.buildFullPath(ImapSession, String),
MailboxConstants.USER_NAMESPACE is used on two places where IMO
mailboxSession.getPersonalSpace() would be a better choice just for
the case that -- for whatever reason -- the session gets configured
differently. Is it a good idea?
(3) I find the rewriting of and null namespace values to
MailboxConstants.USER_NAMESPACE in MailboxPath(String, String, String)
constructor problematic. Callers should be fully responsible for the
namespace value.
should be allowed as a legal namespace prefix, e.g. for a shared namespace.
As for null, is there any good reason for the rewriting?
I see that changing the rewriting of and/or null namespace in
MailboxPath would enforce an extensive refactoring.
(4) MailboxPath has three fields: namespace, user and name. We should
make them final and their setters should be removed to avoid
unauthorised or unexpected changes. As far as I can see there are only
a few easily refactorable locations where the setters are invoked.
Best,
gazda
-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
Re: [VOTE] Release Apache James jSieve 0.5
Hi Stefano, See comment inside. I will cancel the vote and relaunch a new one after fixing assembly. Thx for your review, Eric On 21/02/12 12:01, Stefano Bagnara wrote: 2012/2/20 Eric Charlese...@apache.org: Hi there, In preparation of James server 3.0b4 release, we have have to release jSieve 0.5. This release uses the latest mime4j 0.7.2. which makes it compatible with server. The manager module is not taken in this release as it depends on a server snapshot. If manager depends on server then it cannot be included in the jsieve tree as server already depends on jsieve and we don't want bidirectional dependency (or we'll be hit by this at each release cycle) jsievemanager is aimed to be used within server, we must resolve that bidirectional issue wherever jsievemanager is inside or outside jsieve (let's tackle on JSIEVE-86). You can see the list of changes on https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10412version=12314991 So please cast your VOTE: https://repository.apache.org/content/repositories/orgapachejames-003 [X] -1 Something is wrong I can't find the source package for this release (AFAIK we can't vote binaries). It was available in the 0.4 package (http://apache.fastbull.org/james/apache-jsieve/0.4/apache-james-jsieve-0.4-src.zip) , so maybe something gone wrong with the latest pom changes or with the release process. src are available: https://repository.apache.org/content/repositories/orgapachejames-003/org/apache/james/apache-jsieve-core/0.5/apache-jsieve-core-0.5-sources.jar https://repository.apache.org/content/repositories/orgapachejames-003/org/apache/james/apache-jsieve-mailet/0.5/apache-jsieve-mailet-0.5-sources.jar https://repository.apache.org/content/repositories/orgapachejames-003/org/apache/james/apache-jsieve-util/0.5/apache-jsieve-util-0.5-sources.jar ... but a single tarball with all of them is not... - I had issues with the assemble module, desactivated it for the release, now I fixed it. Stefano - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org -- eric | http://about.echarles.net | @echarles - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JSIEVE-86) Potential bidirectional dependency between jsieve manager and server
[ https://issues.apache.org/jira/browse/JSIEVE-86?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13212835#comment-13212835 ] Eric Charles commented on JSIEVE-86: I think steve was seeing this as a separate library independent of jsieve and server. This can make sense, but for practical reasons (release, maintenance,...) I see it more withing sieve. Now, if the dependency on server file-api makes it not possible. The ultimate solution to me would be to extract the classes common to different projects to a james-common library, but I already told you were not in favor of it. The integration of managesieve in server would make things easier for now, for sure. Potential bidirectional dependency between jsieve manager and server Key: JSIEVE-86 URL: https://issues.apache.org/jira/browse/JSIEVE-86 Project: JAMES jSieve Issue Type: New Feature Reporter: Eric Charles sieve manager is aimed to be used in server james-server-filesystem-api is the one to talk about... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
Can the support for missing ACL commands be committed now?
Eric, may I commit now? Or should I do it after the upcoming mailbox release? I have changes in: - apache-james-imap-api - apache-james-imap-message - apache-james-imap-processor - apache-james-mailbox-api - apache-james-mailbox-store Best, gazda - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
Re: Can the support for missing ACL commands be committed now?
Just commit now, Norman Am 21.02.2012 um 20:47 schrieb Jochen Gazda gazdahims...@gmail.com: Eric, may I commit now? Or should I do it after the upcoming mailbox release? I have changes in: - apache-james-imap-api - apache-james-imap-message - apache-james-imap-processor - apache-james-mailbox-api - apache-james-mailbox-store Best, gazda - 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: How to build James from trunk
Thank your replies, Stefano and Eric. See inline. Best, gazda On Tue, Feb 21, 2012 at 3:31 PM, Stefano Bagnara apa...@bago.org wrote: 2012/2/21 Jochen Gazda gazdahims...@gmail.com: (1) [] But as for parent references I am asking myself what can be the reason for distinct versions in the parent's project.version and its child's project.parent.version? Here is an example from the current trunk: apache-jsieve has version 0.6-SNAPSHOT in its pom, but 0.5-SNAPSHOT is referenced in apache-jsieve-assemble's pom as its parent. Both m2e and mvn install complain about that. When I replace 0.5-SNAPSHOT in apache-jsieve-assemble's pom with 0.6-SNAPSHOT it works. Is it a bug? IMO ti does not make sense and it is a bug. I guess the issue is related to the use of parent module in a subfolder pattern, that is much more difficult to deal with. Eric seems to work on jsieve at the moment. apache-jsieve-assemble module was commented out from its parent and it does not harm my builds now. apache-james-mailbox referencing james-project 1.8.1-SNAPSHOT as its parent is another example. Why does it not reference james-project 1.8.2-SNAPSHOT? Maybe simply because the last time we worked on mailbox we only had 1.8.1-SNAPSHOT and the parent moved forward in the mean time. This is not a big issue, but you can move mailvox to 1.8.1 final or to 1.8.2-SNAPSHOT if it helps. I think we can forget about this one too. There is 1.8.1 at present in the trunk which works for me. And yesterday, when I tried to compile it was 1.9-SNAPSHOT and not 1.8.1-SNAPSHOT as I told you. Sorry. Generally, which are there situations in which parent reference version lower than parent trunk version make sense? It simply happens because we don't start upgrading every project pom when we move the parent forward but we only upgrade them when we need a release. Otherwise we should always try to build with the latest available released parent (not even a snapshot). Why should we always try to build with the latest available released parent? And who is we here? Did you mean (a) we = developers building James to test our own changes or is it (b) we = developers building a release for the public? At the moment I can identify myself with (a): I am trying to find a way how to effectively test my own changes in a freshly built James instance. I will consider what you recommend at the bottom: mvn clean package mvn install for each project (in the right order, so to not depend on only snapshot repositories) (2) In (1) I spoke about the case when referenced version is lover than the trunk version. Here I am asking about the opposite: hupa-parent references james-project 1.9-SNAPSHOT as its parent but the version of james-project in the trunk is 1.8.2-SNAPSHOT. This cannot be OK, can it? Well, when you work with snapshot everything can be right or wrong. If you release 1.8 then you automatically create 1.9-SNAPSHOT.. after a while you decide to release 1.9-SNAPSHOT as 1.8.1 and this will move you to 1.8.2-SNAPSHOT. As they are snapshots it is not so bad. hupa-parent should be fixed to reference james-project 1.8.2-SNAPSHOT as its parent, should it not? BTW, it would be better to point to 1.8.1 because it probably doesn't need anymore to point to a snapshot for the parent. (3) Generally, is the following sequence always expected to work and if it does not, is it a reason to file a bug in Jira? rm -Rf $HOME/.m2/repository cd james/current svn update mvn clean install -DskipTests I often found problematic to run a single pass mvn clean install but runinng the mvn clean package mvn install for each project (in the right order, so to not depend on only snapshot repositories) is expected to work and if it doesn't work we should probably fix something. Stefano - 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
[jira] [Updated] (IMAP-359) Implement missing ACL commands SETACL, LISTRIGHTS, MYRIGHTS and DELETERIGHTS
[ https://issues.apache.org/jira/browse/IMAP-359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jochen Gazda updated IMAP-359: -- Summary: Implement missing ACL commands SETACL, LISTRIGHTS, MYRIGHTS and DELETERIGHTS (was: Implement missing ACL commands SETACL, LISTRIGHTS and MYRIGHTS) Implement missing ACL commands SETACL, LISTRIGHTS, MYRIGHTS and DELETERIGHTS Key: IMAP-359 URL: https://issues.apache.org/jira/browse/IMAP-359 Project: JAMES Imap Issue Type: Task Components: Processor Reporter: Jochen Gazda GETACL implemented already -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
Re: Make the namespace handling consistent and predictable
I have filled this in Jira under
https://issues.apache.org/jira/browse/MAILBOX-167
On Tue, Feb 21, 2012 at 8:31 PM, Jochen Gazda gazdahims...@gmail.com wrote:
Gentlemen,
On the way to usable group folders and ACL, I found that namespaces
are not handled consistently.
(1) in StoreMessageManager.isGroupFolder(MailboxSession), if the
present folder is the current user's INBOX, mailbox.getNamespace() and
session.getPersonalSpace() should return the same value, which they do
not.
I could achieve the desired behavior when I changed this part of
SimpleMailboxSession constructor from
if (otherUsersSpace == null (sharedSpaces == null ||
sharedSpaces.isEmpty())) {
this.personalSpace = ;
} else {
this.personalSpace = MailboxConstants.USER_NAMESPACE;
}
to
this.personalSpace = MailboxConstants.USER_NAMESPACE;
Can this cause any unwanted consequences?
(2) in AbstractMailboxProcessor.buildFullPath(ImapSession, String),
MailboxConstants.USER_NAMESPACE is used on two places where IMO
mailboxSession.getPersonalSpace() would be a better choice just for
the case that -- for whatever reason -- the session gets configured
differently. Is it a good idea?
(3) I find the rewriting of and null namespace values to
MailboxConstants.USER_NAMESPACE in MailboxPath(String, String, String)
constructor problematic. Callers should be fully responsible for the
namespace value.
should be allowed as a legal namespace prefix, e.g. for a shared namespace.
As for null, is there any good reason for the rewriting?
I see that changing the rewriting of and/or null namespace in
MailboxPath would enforce an extensive refactoring.
(4) MailboxPath has three fields: namespace, user and name. We should
make them final and their setters should be removed to avoid
unauthorised or unexpected changes. As far as I can see there are only
a few easily refactorable locations where the setters are invoked.
Best,
gazda
-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (MAILBOX-167) Make the namespace handling consistent and predictable
Make the namespace handling consistent and predictable
--
Key: MAILBOX-167
URL: https://issues.apache.org/jira/browse/MAILBOX-167
Project: James Mailbox
Issue Type: Bug
Reporter: Jochen Gazda
Assignee: Norman Maurer
(1) in StoreMessageManager.isGroupFolder(MailboxSession), if the
present folder is the current user's INBOX, mailbox.getNamespace() and
session.getPersonalSpace() should return the same value, which they do
not. This makes some ACL commands to fail.
I could achieve the desired behavior when I changed this part of
SimpleMailboxSession constructor from
if (otherUsersSpace == null (sharedSpaces == null ||
sharedSpaces.isEmpty())) {
this.personalSpace = ;
} else {
this.personalSpace = MailboxConstants.USER_NAMESPACE;
}
to
this.personalSpace = MailboxConstants.USER_NAMESPACE;
Can this cause any unwanted consequences?
(2) in AbstractMailboxProcessor.buildFullPath(ImapSession, String),
MailboxConstants.USER_NAMESPACE is used on two places where IMO
mailboxSession.getPersonalSpace() would be a better choice just for
the case that -- for whatever reason -- the session gets configured
differently. Is it a good idea?
(3) I find the rewriting of and null namespace values to
MailboxConstants.USER_NAMESPACE in MailboxPath(String, String, String)
constructor problematic. Callers should be fully responsible for the
namespace value.
should be allowed as a legal namespace prefix, e.g. for a shared namespace.
As for null, is there any good reason for the rewriting?
I see that changing the rewriting of and/or null namespace in
MailboxPath would enforce an extensive refactoring.
(4) MailboxPath has three fields: namespace, user and name. We should
make them final and their setters should be removed to avoid
unauthorised or unexpected changes. As far as I can see there are only
a few easily refactorable locations where the setters are invoked.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (IMAP-359) Implement missing ACL commands SETACL, LISTRIGHTS, MYRIGHTS and DELETERIGHTS
[ https://issues.apache.org/jira/browse/IMAP-359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13212961#comment-13212961 ] Jochen Gazda commented on IMAP-359: --- The changes were committed but I am leaving this open because of MAILBOX-167. I left ACL disabled in spring-server.xml for the same reason. Implement missing ACL commands SETACL, LISTRIGHTS, MYRIGHTS and DELETERIGHTS Key: IMAP-359 URL: https://issues.apache.org/jira/browse/IMAP-359 Project: JAMES Imap Issue Type: Task Components: Processor Reporter: Jochen Gazda GETACL implemented already -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
Re: How to build James from trunk
2012/2/21 Jochen Gazda gazdahims...@gmail.com: Why should we always try to build with the latest available released parent? And who is we here? Did you mean (a) we = developers building James to test our own changes or is it (b) we = developers building a release for the public? At the moment I can identify myself with (a): I am trying to find a way how to effectively test my own changes in a freshly built James instance. I will consider what you recommend at the bottom: (a) With time we should have less parent changes. We had a few of them lately, but I think things will settle. The parent is similar to other dependencies. You don't upgrade them whenever you can, but once in a while you make a dependency update round and you check that everything works fine with the updated environment. (b) Most time we change the parent is to inherit some website change declared in the parent, so we care about this mainly during the release cycle. mvn clean package mvn install for each project (in the right order, so to not depend on only snapshot repositories) I saw a typo in my previous comment you quoted: s/only/online/ Stefano - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JSIEVE-86) Potential bidirectional dependency between jsieve manager and server
[ https://issues.apache.org/jira/browse/JSIEVE-86?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13212975#comment-13212975 ] Stefano Bagnara commented on JSIEVE-86: --- I didn't looked at manager previously, but I see manager is a multimodule project and the only module depending on james-server is named server and is a single class. So my suggestion is to keep everything in jsieve but the server module and simply put the server module into the james-server trunk under a sievemanager module (or something similar). Would this work? (otherwise I'm fine with having all of it in james-server, too). Potential bidirectional dependency between jsieve manager and server Key: JSIEVE-86 URL: https://issues.apache.org/jira/browse/JSIEVE-86 Project: JAMES jSieve Issue Type: New Feature Reporter: Eric Charles sieve manager is aimed to be used in server james-server-filesystem-api is the one to talk about... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
Re: [VOTE] Release Apache James jSieve 0.5
2012/2/21 Eric Charles e...@apache.org: Hi Stefano, See comment inside. I will cancel the vote and relaunch a new one after fixing assembly. Thx for your review, Eric Thanks to you for the hard work! Reviewing is easy compared to pushing releases! On 21/02/12 12:01, Stefano Bagnara wrote: (http://apache.fastbull.org/james/apache-jsieve/0.4/apache-james-jsieve-0.4-src.zip) , so maybe something gone wrong with the latest pom changes or with the release process. src are available: https://repository.apache.org/content/repositories/orgapachejames-003/org/apache/james/apache-jsieve-core/0.5/apache-jsieve-core-0.5-sources.jar https://repository.apache.org/content/repositories/orgapachejames-003/org/apache/james/apache-jsieve-mailet/0.5/apache-jsieve-mailet-0.5-sources.jar https://repository.apache.org/content/repositories/orgapachejames-003/org/apache/james/apache-jsieve-util/0.5/apache-jsieve-util-0.5-sources.jar ... but a single tarball with all of them is not... - I had issues with the assemble module, desactivated it for the release, now I fixed it. I'm not sure this is right, as they are not the full sources of our product: they don't include the root stuff (like the website and release notes) and they don't include tests. One thing to check after you fix the assembly is the LICENSE/NOTICE for the bin assembly: they have to include references to the jars included in the binary tar. Stefano - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
Jenkins build is back to normal : james-server-trunk #2652
See https://builds.apache.org/job/james-server-trunk/2652/ - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
Build failed in Jenkins: james-app-trunk #624
See https://builds.apache.org/job/james-app-trunk/624/ -- [...truncated 524 lines...] [INFO] Installing /home/jenkins/.m2/repository/org/apache/james/apache-james-mailbox-api/0.4-SNAPSHOT/apache-james-mailbox-api-0.4-SNAPSHOT.jar to https://builds.apache.org/job/james-app-trunk/ws/trunk/target/appassembler/lib/apache-james-mailbox-api-0.4-20120221.211142-356.jar [INFO] Installing /home/jenkins/.m2/repository/org/apache/james/apache-james-mailbox-tool/0.4-SNAPSHOT/apache-james-mailbox-tool-0.4-SNAPSHOT.jar to https://builds.apache.org/job/james-app-trunk/ws/trunk/target/appassembler/lib/apache-james-mailbox-tool-0.4-20120221.211701-273.jar [INFO] Installing /home/jenkins/.m2/repository/org/apache/geronimo/specs/geronimo-annotation_1.0_spec/1.1.1/geronimo-annotation_1.0_spec-1.1.1.jar to https://builds.apache.org/job/james-app-trunk/ws/trunk/target/appassembler/lib/geronimo-annotation_1.0_spec-1.1.1.jar [INFO] Installing /home/jenkins/.m2/repository/org/apache/james/protocols/protocols-api/1.6.2/protocols-api-1.6.2.jar to https://builds.apache.org/job/james-app-trunk/ws/trunk/target/appassembler/lib/protocols-api-1.6.2.jar [INFO] Installing /home/jenkins/.m2/repository/org/apache/james/apache-mailet/2.4/apache-mailet-2.4.jar to https://builds.apache.org/job/james-app-trunk/ws/trunk/target/appassembler/lib/apache-mailet-2.4.jar [INFO] Installing /home/jenkins/.m2/repository/org/springframework/spring-core/3.1.0.RELEASE/spring-core-3.1.0.RELEASE.jar to https://builds.apache.org/job/james-app-trunk/ws/trunk/target/appassembler/lib/spring-core-3.1.0.RELEASE.jar [INFO] Installing /home/jenkins/.m2/repository/org/springframework/spring-asm/3.1.0.RELEASE/spring-asm-3.1.0.RELEASE.jar to https://builds.apache.org/job/james-app-trunk/ws/trunk/target/appassembler/lib/spring-asm-3.1.0.RELEASE.jar [INFO] Installing /home/jenkins/.m2/repository/org/springframework/spring-beans/3.1.0.RELEASE/spring-beans-3.1.0.RELEASE.jar to https://builds.apache.org/job/james-app-trunk/ws/trunk/target/appassembler/lib/spring-beans-3.1.0.RELEASE.jar [INFO] Installing /home/jenkins/.m2/repository/org/springframework/spring-context/3.1.0.RELEASE/spring-context-3.1.0.RELEASE.jar to https://builds.apache.org/job/james-app-trunk/ws/trunk/target/appassembler/lib/spring-context-3.1.0.RELEASE.jar [INFO] Installing /home/jenkins/.m2/repository/org/springframework/spring-expression/3.1.0.RELEASE/spring-expression-3.1.0.RELEASE.jar to https://builds.apache.org/job/james-app-trunk/ws/trunk/target/appassembler/lib/spring-expression-3.1.0.RELEASE.jar [INFO] Installing /home/jenkins/.m2/repository/org/springframework/spring-web/3.1.0.RELEASE/spring-web-3.1.0.RELEASE.jar to https://builds.apache.org/job/james-app-trunk/ws/trunk/target/appassembler/lib/spring-web-3.1.0.RELEASE.jar [INFO] Installing /home/jenkins/.m2/repository/commons-configuration/commons-configuration/1.6/commons-configuration-1.6.jar to https://builds.apache.org/job/james-app-trunk/ws/trunk/target/appassembler/lib/commons-configuration-1.6.jar [INFO] Installing /home/jenkins/.m2/repository/commons-lang/commons-lang/2.6/commons-lang-2.6.jar to https://builds.apache.org/job/james-app-trunk/ws/trunk/target/appassembler/lib/commons-lang-2.6.jar [INFO] Installing /home/jenkins/.m2/repository/javax/mail/mail/1.4.4/mail-1.4.4.jar to https://builds.apache.org/job/james-app-trunk/ws/trunk/target/appassembler/lib/mail-1.4.4.jar [INFO] Installing /home/jenkins/.m2/repository/log4j/log4j/1.2.16/log4j-1.2.16.jar to https://builds.apache.org/job/james-app-trunk/ws/trunk/target/appassembler/lib/log4j-1.2.16.jar [INFO] Installing /home/jenkins/.m2/repository/org/apache/james/james-server-lifecycle-spring/3.0-beta4-SNAPSHOT/james-server-lifecycle-spring-3.0-beta4-SNAPSHOT.jar to https://builds.apache.org/job/james-app-trunk/ws/trunk/target/appassembler/lib/james-server-lifecycle-spring-3.0-beta4-SNAPSHOT.jar [INFO] Installing /home/jenkins/.m2/repository/org/apache/geronimo/specs/geronimo-annotation_1.1_spec/1.0.1/geronimo-annotation_1.1_spec-1.0.1.jar to https://builds.apache.org/job/james-app-trunk/ws/trunk/target/appassembler/lib/geronimo-annotation_1.1_spec-1.0.1.jar [INFO] Installing /home/jenkins/.m2/repository/org/apache/geronimo/specs/geronimo-jpa_2.0_spec/1.0/geronimo-jpa_2.0_spec-1.0.jar to https://builds.apache.org/job/james-app-trunk/ws/trunk/target/appassembler/lib/geronimo-jpa_2.0_spec-1.0.jar [INFO] Installing /home/jenkins/.m2/repository/org/apache/james/james-server-cli/3.0-beta4-SNAPSHOT/james-server-cli-3.0-beta4-SNAPSHOT.jar to https://builds.apache.org/job/james-app-trunk/ws/trunk/target/appassembler/lib/james-server-cli-3.0-beta4-SNAPSHOT.jar [INFO] Installing /home/jenkins/.m2/repository/commons-cli/commons-cli/1.2/commons-cli-1.2.jar to https://builds.apache.org/job/james-app-trunk/ws/trunk/target/appassembler/lib/commons-cli-1.2.jar [INFO] Installing
Re: Limit Mail Box Size
Hi Eric, Do you have any inputs for me on Individual user mail box size functionality? Thanks, Sai On Tue, Feb 21, 2012 at 8:42 AM, Saibabu Vallurupalli saibabu.vallurupa...@gmail.com wrote: Hi, Good morning. Is there a way we can limit the mail box size for each user? Thanks, Sai.
[jira] [Closed] (MAILBOX-160) Mapping of ACL to to READ-WRITE and READ-ONLY response codes
[ https://issues.apache.org/jira/browse/MAILBOX-160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jochen Gazda closed MAILBOX-160. Resolution: Fixed Mapping of ACL to to READ-WRITE and READ-ONLY response codes Key: MAILBOX-160 URL: https://issues.apache.org/jira/browse/MAILBOX-160 Project: James Mailbox Issue Type: Improvement Components: store Reporter: Jochen Gazda Assignee: Norman Maurer Attachments: MAILBOX-160-patch.txt Patch follows -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Closed] (MAILBOX-157) Review the ACL persistence in MaildirFolder
[ https://issues.apache.org/jira/browse/MAILBOX-157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jochen Gazda closed MAILBOX-157. Resolution: Fixed Review the ACL persistence in MaildirFolder --- Key: MAILBOX-157 URL: https://issues.apache.org/jira/browse/MAILBOX-157 Project: James Mailbox Issue Type: Task Components: maildir mailbox Reporter: Jochen Gazda Assignee: Norman Maurer There are two FIXMEs in org.apache.james.mailbox.maildir.MaildirFolder. Further the ACL persistence should be tested. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
ACL support plans
Gentlemen, In the next weeks, I would like to proceed with https://issues.apache.org/jira/browse/IMAP-358 Enforce rights required to perform different IMAP4rev1 Commands in IMAP processors. Just two questions: (1) Is it still OK if I further work under apache-james-imap and not under protocols-imap? Is there a rough estimate when will apache-james-imap become obsolete? (2) Tests: Is there a recommended way how to test the enforcement of the individual rights in James? I have written some tests for GETACL, SETACL, LISTRIGHTS, MYRIGHTS and DELETERIGHTS in the apache-james-imap-processor project. All of them are directed towards the respective processors. Could please somebody review esp. the test*Right*() methods in them and tell me if it is sufficient to test the security of other IMAP commands in this way? Best, gazda - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[CANCELED} Re: [VOTE] Release Apache James jSieve 0.5
Hi Stefano, I don't understand what you mean with the references in the LICENSE/NOTICE. If you look at jsieve 0.4 release, there are no such references, and to my understanding it's not the goal of these files to list the jars. Btw, one thing to do is to update the RELEASE_NOTE.txt (one more reason to cancel). Thx, Eric On 21/02/12 22:46, Stefano Bagnara wrote: 2012/2/21 Eric Charlese...@apache.org: Hi Stefano, See comment inside. I will cancel the vote and relaunch a new one after fixing assembly. Thx for your review, Eric Thanks to you for the hard work! Reviewing is easy compared to pushing releases! On 21/02/12 12:01, Stefano Bagnara wrote: (http://apache.fastbull.org/james/apache-jsieve/0.4/apache-james-jsieve-0.4-src.zip) , so maybe something gone wrong with the latest pom changes or with the release process. src are available: https://repository.apache.org/content/repositories/orgapachejames-003/org/apache/james/apache-jsieve-core/0.5/apache-jsieve-core-0.5-sources.jar https://repository.apache.org/content/repositories/orgapachejames-003/org/apache/james/apache-jsieve-mailet/0.5/apache-jsieve-mailet-0.5-sources.jar https://repository.apache.org/content/repositories/orgapachejames-003/org/apache/james/apache-jsieve-util/0.5/apache-jsieve-util-0.5-sources.jar ... but a single tarball with all of them is not... - I had issues with the assemble module, desactivated it for the release, now I fixed it. I'm not sure this is right, as they are not the full sources of our product: they don't include the root stuff (like the website and release notes) and they don't include tests. One thing to check after you fix the assembly is the LICENSE/NOTICE for the bin assembly: they have to include references to the jars included in the binary tar. Stefano - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org -- eric | http://about.echarles.net | @echarles - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
Re: Limit Mail Box Size
Hi Sai, There is the MailboxQuotaFixed mailet match=MailboxQuotaFixed=200m class=ToProcessor processorbounces/processor /mailet It reads all them mails from inbox and sums the size, which is rather inefficient (see JAMES-1198). There is also MAILBOX-64 with existing implementation in mailbox-api and mailbox-store, but no implementation today in any of the concrete mailboxes (jpa, maildir...). This will allow to do much more efficient and flexible (per user, per folder,...), but there is some work out-there. Thx, Eric On 22/02/12 02:38, Saibabu Vallurupalli wrote: Hi Eric, Do you have any inputs for me on Individual user mail box size functionality? Thanks, Sai On Tue, Feb 21, 2012 at 8:42 AM, Saibabu Vallurupalli saibabu.vallurupa...@gmail.com wrote: Hi, Good morning. Is there a way we can limit the mail box size for each user? Thanks, Sai. -- eric | http://about.echarles.net | @echarles - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
