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:
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
LocalDelivery Mailet should not use deprecated
UsersRepositoryAliasingForwarding mailet
---
Key: JAMES-1378
URL: https://issues.apache.org/jira/browse/JAMES-1378
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:
[
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
Default mailet configuration should not apply RecipientRewriteTable
---
Key: JAMES-1379
URL: https://issues.apache.org/jira/browse/JAMES-1379
Project: JAMES Server
Issue Type:
[
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
[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:
[
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
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:
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)
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:
[
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
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:
Default mailet configuration should not apply InSpammerBlacklist
Key: JAMES-1380
URL: https://issues.apache.org/jira/browse/JAMES-1380
Project: JAMES Server
Issue Type:
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
--
[
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
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:
[
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
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
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
Hi,
Good morning.
Is there a way we can limit the mail box size for each user?
Thanks, Sai.
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
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:
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
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:
[
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:
[
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:
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
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
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
[
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
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
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
-
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
[
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
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
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
[
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
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
[
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
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:
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
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
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.
[
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
[
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
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
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
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
50 matches
Mail list logo
