Message:
The following issue has been closed.
Resolver: Danny Angus
Date: Mon, 7 Jun 2004 2:28 AM
DuH! My bad this isn't a defect
-
View the issue:
http://issues.apache.org/jira/browse/JAMES-275
Here is an
Message:
The following issue has been re-assigned.
Assignee: Danny Angus (mailto:[EMAIL PROTECTED])
-
View the issue:
http://issues.apache.org/jira/browse/JAMES-275
Here is an overview of the issue:
Hi,
Okay we just ran into the following at a site, where James is setup as a
mailprocessing gateway.
The backend system (apparently it must have a few years on it's back) uses
addresses like:
@YYY.XXX.DK:[EMAIL PROTECTED]
ie. the old RFC-821 source route style.
Now James hickups at this
Hello
Has anyone ever tried running James with the server option
to enable the HotSpot Server engine?
What were your experiences, does it make a difference, is
it recommended, etc?
Just curious.
Hes.
-
- - - - - - - - - - - - - - - - - -
Hes
[ ] +1 - Release james 2.2.0RC5 as James 2.2.0
[ ] -1 - Do not release due to ___
--- Noel
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Has anyone ever tried running James with the server option
Yes. I don't recall the performance difference, but I seem to recall that it was
significant. However, prior to JVM 1.4.2, there were problems that could cause a
lockup.
--- Noel
[X] +1 - Release james 2.2.0RC5 as James 2.2.0
-Chris (user)
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]