[g...@vmgump]: Project james-jsieve (in module james-jsieve) failed

2008-10-05 Thread Gump
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at [EMAIL PROTECTED] Project james-jsieve has an issue affecting its community integration. This issue affects

Re: Message-ID and JAMES Server (JAMES-875)

2008-10-05 Thread Stefano Bagnara
Martijn Brinkers ha scritto: >>> Exchange 2007? Is it Exchange 2007 Server or does Exchange identify also >>> a MUA product? I'd like to have at least another example. I wouldn't go >>> RFC uncompliant to follow M$ proprietary solutions. If Exchange 2007 is >> I don't think RFC2888 says something a

Re: Message-ID and JAMES Server (JAMES-875)

2008-10-05 Thread Martijn Brinkers
> > Exchange 2007? Is it Exchange 2007 Server or does Exchange identify also > > a MUA product? I'd like to have at least another example. I wouldn't go > > RFC uncompliant to follow M$ proprietary solutions. If Exchange 2007 is > > I don't think RFC2888 says something about dropping duplicate >

Re: Message-ID and JAMES Server (JAMES-875)

2008-10-05 Thread Martijn Brinkers
> Can you name some of "Most mail clients"? In the past 10 years I used > many different MUAs and I'm sure I've always been subscribed to at least > one list with 2 different accounts receiving each list messages at least > twice with the same Message-ID: in all of the MUAs I used I received > eac

Re: Message-ID and JAMES Server (JAMES-875)

2008-10-05 Thread Stefano Bagnara
Martijn Brinkers ha scritto: >> Yes, do you see a problem with this? > > That depends on the mailets you use. What if you split a message and for > one part of the recipients you change something to the message (like add > a header or disclaimer) and the other part you sent the message as is. Rea

Re: Message-ID and JAMES Server (JAMES-875)

2008-10-05 Thread Martijn Brinkers
> Yes, do you see a problem with this? That depends on the mailets you use. What if you split a message and for one part of the recipients you change something to the message (like add a header or disclaimer) and the other part you sent the message as is. Currently the message that was not modifie

Re: Message-ID and JAMES Server (JAMES-875)

2008-10-05 Thread Stefano Bagnara
Martijn Brinkers ha scritto: > But what happens with messages that are split into multiple messages (because > of a matcher)? Do they get the same message-id? Yes, do you see a problem with this? It seems this also happen when your MUA sends a message to multiple recipients on different domains.

Re: Message-ID and JAMES Server (JAMES-875)

2008-10-05 Thread Martijn Brinkers
But what happens with messages that are split into multiple messages (because of a matcher)? Do they get the same message-id? And what if the message has been changed in such a way that the message is no longer similar to the original message? Should it get a new message-id when the message con

Re: Status of trunk [WAS: Re: [jira] Commented: (JAMES-876) cannot start as spring-deployment when built from trunk as described in HOW-TO.TXT]

2008-10-05 Thread Robert Burrell Donkin
On Sat, Oct 4, 2008 at 11:40 AM, Stefano Bagnara <[EMAIL PROTECTED]> wrote: > Robert Burrell Donkin ha scritto: >> On Fri, Oct 3, 2008 at 8:15 AM, Stefano Bagnara <[EMAIL PROTECTED]> wrote: >>> Robert Burrell Donkin ha scritto: On Wed, Oct 1, 2008 at 1:39 PM, Stefano Bagnara <[EMAIL PROTECTED]

Re: Message-ID and JAMES Server (JAMES-875)

2008-10-05 Thread Norman Maurer
+1 I think now its time for a 2.3.2 release. Maybe before ApacheCon US ? Cheers, Norman 2008/10/5 Stefano Bagnara <[EMAIL PROTECTED]> > Hi all, > > I just updated my local server to include the patch I proposed in > JAMES-875. > > This basically adds this code to MimeMessageWrapper: > - >

JAMES Server Nightly Build Report

2008-10-05 Thread JAMES Nightly Build System
An automated nightly build of JAMES has been posted to http://people.apache.org/builds/james/nightly/ Any unit test errors from the build should be reported below: -