Message body get lost after call saveChanges() and move to other processor
--
Key: JAMES-559
URL: http://issues.apache.org/jira/browse/JAMES-559
Project: James
Type: Bug
Versions: 3.0,
Norman Maurer wrote:
So the problem only appears after call saveChanges() in a mailet and
move it to a other processor ? That whould explain why i not notice it
on our Server ..
Someone wrote a junit test for this so far?
I'm working on it but I cannot reproduce it using a mock environment
Norman Maurer wrote:
Am Sonntag, den 09.07.2006, 12:25 +0200 schrieb Bernd Fondermann:
Noel J. Bergman wrote:
Bernd, we should have some round-trip testing that would detect this sort of
problem. :-)
What Postage today is already helpful at is building a clean room
environment. All mail
[
http://issues.apache.org/jira/browse/JAMES-559?page=comments#action_12419903 ]
Norman Maurer commented on JAMES-559:
-
After more testing it seems that the problem appears only with file repos. I
tested it also with db and dbfile. No problem ..
SetMimeHeader not throw an MessagingException if needed config values missed
Key: JAMES-560
URL: http://issues.apache.org/jira/browse/JAMES-560
Project: James
Type: Bug
Components:
Author: norman
Date: Sun Jul 9 06:02:12 2006
New Revision: 420289
URL: http://svn.apache.org/viewvc?rev=420289view=rev
Log:
Throw MessagingException if needed config values missed. See JAMES-560
Modified:
User aliasing does not work
---
Key: JAMES-561
URL: http://issues.apache.org/jira/browse/JAMES-561
Project: James
Type: Bug
Components: Matchers/Mailets (bundled)
Versions: 3.0, 2.3.0b2
Reporter: Vincenzo Gianferrari Pini
Stefano Bagnara wrote:
I'm working on it but I cannot reproduce it using a mock environment yet.
See the below. All I did was telnet into JAMES and post a sample message,
and in the root processor I used SetMimeHeader.
--- Noel
Index:
Norman Maurer wrote:
IMHO such a debugging should be better done with JUNIT tests...
Postage is great for performance tests etc..
JUNIT testing is not the same as an external test harness. We should be
able to drive a test from SMTP connection through to POP3 or IMAP. So
Postage could send a
Bernd Fondermann wrote:
Bernd, we should have some round-trip testing that would detect
this sort of problem. :-)
What Postage today is already helpful at is building a clean room
environment. All mail is kept within. This is good for debugging or
staging to production.
I know. :-)
Norman Maurer wrote:
So the problem only appears after call saveChanges() in a mailet and
move it to a other processor ?
It appears to happen whenever you change a header and not the body. A
defect in how we optimized message handling.
--- Noel
[
http://issues.apache.org/jira/browse/JAMES-559?page=comments#action_12419912 ]
Noel J. Bergman commented on JAMES-559:
---
This appears to be a side-effect of optimizing message handling. Since the
message is not in memory, we lose it when we call
Noel J. Bergman wrote:
Perhaps adding BSF (or JSR-223) support to Postage would be a good thing.
Postage providing core capabilities, and allowing scripting for tests.
OK, good idea. I'd like to have standard tests, like checking headers,
built into Postage directly and provide scripting for
[ http://issues.apache.org/jira/browse/JAMES-559?page=all ]
Stefano Bagnara reassigned JAMES-559:
-
Assign To: Stefano Bagnara
Message body get lost after call saveChanges() and move to other processor
[
http://issues.apache.org/jira/browse/JAMES-561?page=comments#action_12419917 ]
Norman Maurer commented on JAMES-561:
-
After some debug it seems that the UsersRepositoryAliasingForwarding Mailet get
not called. No time now to investigate time on this
[ http://issues.apache.org/jira/browse/JAMES-561?page=all ]
Norman Maurer reassigned JAMES-561:
---
Assign To: Norman Maurer
User aliasing does not work
---
Key: JAMES-561
URL:
[
http://issues.apache.org/jira/browse/JAMES-561?page=comments#action_12419928 ]
Noel J. Bergman commented on JAMES-561:
---
Just to keep people following this in the loop, Norman observed on IM that The
problem is that ((JamesUser) user).getAliasing()
I just found and fixed it. Unfortunately, I'm 30,000 feet in the air, but as
soon as I land in LA this evening (about 4 hours from now), I'll commit the
fix, unless someone has beaten me to it.
Norman observed on IM that The problem is that
((JamesUser) user).getAliasing() return false.
Author: noel
Date: Sun Jul 9 21:08:16 2006
New Revision: 420415
URL: http://svn.apache.org/viewvc?rev=420415view=rev
Log:
Fix JAMES-561. Check was comparing for the name being EQUAL instead of NOT
EQUAL (changed)
Modified:
Author: noel
Date: Sun Jul 9 21:10:37 2006
New Revision: 420416
URL: http://svn.apache.org/viewvc?rev=420416view=rev
Log:
Remove in order to copy replacement from trunk
Removed:
james/server/branches/v2.3/src/java/org/apache/james/transport/mailets/UsersRepositoryAliasingForwarding.java
Author: noel
Date: Sun Jul 9 21:13:36 2006
New Revision: 420417
URL: http://svn.apache.org/viewvc?rev=420417view=rev
Log:
Copy fix for JAMES-561 from trunk.
Added:
james/server/branches/v2.3/src/java/org/apache/james/transport/mailets/UsersRepositoryAliasingForwarding.java
- copied
[ http://issues.apache.org/jira/browse/JAMES-561?page=all ]
Noel J. Bergman resolved JAMES-561:
---
Fix Version: 2.3.0
3.0
Resolution: Fixed
Committed fix to both trunk and v2.3 branch. The check for an aliased name had
the
22 matches
Mail list logo
