Message:
A new issue has been created in JIRA.
-
View the issue:
http://nagoya.apache.org/jira/secure/ViewIssue.jspa?key=JSIEVE-3
Here is an overview of the issue
Message:
A new issue has been created in JIRA.
-
View the issue:
http://nagoya.apache.org/jira/secure/ViewIssue.jspa?key=JAMES-151
Here is an overview of the issue
:
http://nagoya.apache.org/jira/secure/ViewIssue.jspa?key=JAMES-151page=history
-
View the issue:
http://nagoya.apache.org/jira/secure/ViewIssue.jspa?key=JAMES-151
Here is an overview of the issue
Message:
The following issue has been closed.
-
View the issue:
http://nagoya.apache.org/jira/secure/ViewIssue.jspa?key=JAMES-151
Here is an overview of the issue
indicating the problem. The MailAttribute can be detected in the
MailetChain and the mail processed as required.
-
View the issue:
http://nagoya.apache.org/jira/secure/ViewIssue.jspa?key=JAMES-149
Here is an overview
in the Mailet API.
Changes:
Fix Version changed to 3.0
-
For a full history of the issue, see:
http://nagoya.apache.org/jira/secure/ViewIssue.jspa?key=JAMES-149page=history
Message:
A new issue has been created in JIRA.
-
View the issue:
http://nagoya.apache.org/jira/secure/ViewIssue.jspa?key=JAMES-152
Here is an overview of the issue
of the issue, see:
http://nagoya.apache.org/jira/secure/ViewIssue.jspa?key=JAMES-142page=history
-
View the issue:
http://nagoya.apache.org/jira/secure/ViewIssue.jspa?key=JAMES-142
Here is an overview of the issue
Message:
The following issue has been closed.
-
View the issue:
http://nagoya.apache.org/jira/secure/ViewIssue.jspa?key=JAMES-142
Here is an overview of the issue
-
For a full history of the issue, see:
http://nagoya.apache.org/jira/secure/ViewIssue.jspa?key=JAMES-152page=history
-
View the issue:
http://nagoya.apache.org/jira/secure/ViewIssue.jspa?key=JAMES-152
Here is an overview
Message:
The following issue has been resolved as FIXED.
-
View the issue:
http://nagoya.apache.org/jira/secure/ViewIssue.jspa?key=JAMES-152
Here is an overview of the issue
Message:
A new issue has been created in JIRA.
-
View the issue:
http://nagoya.apache.org/jira/secure/ViewIssue.jspa?key=JAMES-153
Here is an overview of the issue
)
at
org.apache.james.util.thread.ExecutableRunnable.execute(ExecutableRunnable.java:89)
at org.apache.james.util.thread.WorkerThread.run(WorkerThread.java:125)
-
View this comment:
http://nagoya.apache.org/jira/secure/ViewIssue.jspa?key=JAMES-144page
this comment:
http://nagoya.apache.org/jira/secure/ViewIssue.jspa?key=JAMES-144page=comments#action_16256
-
View the issue:
http://nagoya.apache.org/jira/secure/ViewIssue.jspa?key=JAMES-144
Here is an overview of the issue
Message:
A new issue has been created in JIRA.
-
View the issue:
http://nagoya.apache.org/jira/secure/ViewIssue.jspa?key=JAMES-154
Here is an overview of the issue
://nagoya.apache.org/jira/secure/ViewIssue.jspa?key=JAMES-154
Here is an overview of the issue:
-
Key: JAMES-154
Summary: fetchmail config. files not copied to .sar
Type: Bug
Status: Resolved
Priority: Major
Resolution
Message:
A new issue has been created in JIRA.
-
View the issue:
http://nagoya.apache.org/jira/secure/ViewIssue.jspa?key=JAMES-156
Here is an overview of the issue
Message:
A new issue has been created in JIRA.
-
View the issue:
http://nagoya.apache.org/jira/secure/ViewIssue.jspa?key=JAMES-157
Here is an overview of the issue
://nagoya.apache.org/jira/secure/ViewIssue.jspa?key=JAMES-157
Here is an overview of the issue:
-
Key: JAMES-157
Summary: AbstractQuotaMatcher subclasses should not match when reverse path is NULL
Type: Bug
Status
.
-
View the issue:
http://nagoya.apache.org/jira/secure/ViewIssue.jspa?key=JAMES-156
Here is an overview of the issue:
-
Key: JAMES-156
Summary: AbstractStorageQuota matcher
Message:
A new issue has been created in JIRA.
-
View the issue:
http://nagoya.apache.org/jira/secure/ViewIssue.jspa?key=JAMES-158
Here is an overview of the issue
Message:
A new issue has been created in JIRA.
-
View the issue:
http://nagoya.apache.org/jira/secure/ViewIssue.jspa?key=JAMES-159
Here is an overview of the issue
Message:
A new issue has been created in JIRA.
-
View the issue:
http://issues.apache.org/jira/secure/ViewIssue.jspa?key=JAMES-233
Here is an overview of the issue
;
+ user = authorize_id;
+ }
-
View the issue:
http://issues.apache.org/jira/secure/ViewIssue.jspa?key=JAMES-233
Here is an overview of the issue
Message:
A new issue has been created in JIRA.
-
View the issue:
http://issues.apache.org/jira/secure/ViewIssue.jspa?key=JAMES-234
Here is an overview of the issue
Message:
The following issue has been closed.
-
View the issue:
http://issues.apache.org/jira/secure/ViewIssue.jspa?key=JAMES-234
Here is an overview of the issue
of the issue, see:
http://issues.apache.org/jira/secure/ViewIssue.jspa?key=JAMES-235page=history
-
View the issue:
http://issues.apache.org/jira/secure/ViewIssue.jspa?key=JAMES-235
Here is an overview of the issue
Message:
A new issue has been created in JIRA.
-
View the issue:
http://issues.apache.org/jira/browse/JAMES-240
Here is an overview of the issue
Message:
A new issue has been created in JIRA.
-
View the issue:
http://issues.apache.org/jira/browse/JAMES-241
Here is an overview of the issue
Changes:
type changed from Improvement to Bug
priority changed from Major to Critical
-
For a full history of the issue, see:
http://issues.apache.org/jira/browse/JAMES-241?page=history
Critical to Major
-
For a full history of the issue, see:
http://issues.apache.org/jira/browse/JAMES-241?page=history
-
View the issue:
http
Message:
A new issue has been created in JIRA.
-
View the issue:
http://issues.apache.org/jira/browse/JAMES-243
Here is an overview of the issue
to MailStore MailRepository
Component changed from Mailet API
-
For a full history of the issue, see:
http://issues.apache.org/jira/browse/JAMES-242?page=history
)
-
For a full history of the issue, see:
http://issues.apache.org/jira/browse/JAMES-160?page=history
-
View the issue:
http://issues.apache.org/jira/browse/JAMES-160
Here is an overview of the issue
Message:
A new issue has been created in JIRA.
-
View the issue:
http://issues.apache.org/jira/browse/JAMES-244
Here is an overview of the issue
Message:
A new issue has been created in JIRA.
-
View the issue:
http://issues.apache.org/jira/browse/JAMES-245
Here is an overview of the issue
Message:
A new issue has been created in JIRA.
-
View the issue:
http://issues.apache.org/jira/browse/JSIEVE-7
Here is an overview of the issue
.
-
View the issue:
http://issues.apache.org/jira/browse/JSIEVE-7
Here is an overview of the issue:
-
Key: JSIEVE-7
Summary: I would be great to have
Message:
A new issue has been created in JIRA.
-
View the issue:
http://issues.apache.org/jira/browse/JSIEVE-8
Here is an overview of the issue
does not offer the service
org.apache.avalon.cornerstone.services.connection.ConnectionManager/1.0.0 required.
-
View this comment:
http://issues.apache.org/jira/browse/JAMES-246?page=comments#action_27914
Message:
A new issue has been created in JIRA.
-
View the issue:
http://issues.apache.org/jira/browse/JAMES-247
Here is an overview of the issue
Message:
A new issue has been created in JIRA.
-
View the issue:
http://issues.apache.org/jira/browse/JAMES-248
Here is an overview of the issue
Message:
A new issue has been created in JIRA.
-
View the issue:
http://issues.apache.org/jira/browse/JAMES-249
Here is an overview of the issue
approach, and preserves support for multiple A records for a single host.
-
View the issue:
http://issues.apache.org/jira/browse/JAMES-249
Here is an overview of the issue
code.
Do you have any reason to believe that there is currently a problem in James?
-
View this comment:
http://issues.apache.org/jira/browse/JAMES-248?page=comments#action_28040
Message:
A new issue has been created in JIRA.
-
View the issue:
http://issues.apache.org/jira/browse/JAMES-250
Here is an overview of the issue
Message:
A new issue has been created in JIRA.
-
View the issue:
http://issues.apache.org/jira/browse/JAMES-251
Here is an overview of the issue
.
-
View this comment:
http://issues.apache.org/jira/browse/JAMES-249?page=comments#action_34995
-
View the issue:
http://issues.apache.org/jira/browse/JAMES-249
Here is an overview of the issue
Message:
A new issue has been created in JIRA.
-
View the issue:
http://issues.apache.org/jira/browse/JAMES-252
Here is an overview of the issue
-
For a full history of the issue, see:
http://issues.apache.org/jira/browse/JAMES-123?page=history
-
View the issue:
http://issues.apache.org/jira/browse/JAMES-123
Here is an overview of the issue
to SpoolManager Processors
Component changed from Mailet API
-
For a full history of the issue, see:
http://issues.apache.org/jira/browse/JAMES-96?page=history
one level of nesting. A better solution would be good, but this should handle
most cases.
-
View the issue:
http://issues.apache.org/jira/browse/JAMES-96
Here is an overview of the issue
-
For a full history of the issue, see:
http://issues.apache.org/jira/browse/JAMES-138?page=history
-
View the issue:
http://issues.apache.org/jira/browse/JAMES-138
Here is an overview of the issue
:
http://issues.apache.org/jira/browse/JAMES-138?page=history
-
View the issue:
http://issues.apache.org/jira/browse/JAMES-138
Here is an overview of the issue
System: Other
Platform: Other
priority changed to Minor
-
For a full history of the issue, see:
http://issues.apache.org/jira/browse/JAMES-126?page=history
.
This should be addressed in James v3.
-
View this comment:
http://issues.apache.org/jira/browse/JAMES-140?page=comments#action_35000
-
View the issue:
http
Operating System: All
Platform: All to Operating System: All
Platform: All
priority changed to Minor
-
For a full history of the issue, see:
http://issues.apache.org/jira/browse/JAMES-140?page=history
://issues.apache.org/jira/browse/JAMES-146?page=history
-
View the issue:
http://issues.apache.org/jira/browse/JAMES-146
Here is an overview of the issue:
-
Key: JAMES-146
Fix Version changed to 2.2.0a19
-
For a full history of the issue, see:
http://issues.apache.org/jira/browse/JAMES-144?page=history
-
View
.
-
View the issue:
http://issues.apache.org/jira/browse/JAMES-144
Here is an overview of the issue:
-
Key: JAMES-144
Summary: POP3Handler breaks with message numbers out of bounds
Type: Bug
Message:
The following issue has been closed.
Resolver: Noel J. Bergman
Date: Tue, 13 Apr 2004 3:08 PM
Updated to ORO 2.0.8. Already updated to dnsjava 1.6.2.
-
View the issue:
http://issues.apache.org/jira
-
For a full history of the issue, see:
http://issues.apache.org/jira/browse/JAMES-124?page=history
-
View the issue:
http://issues.apache.org/jira/browse/JAMES-124
Here
destroys the mailets
JamesSpoolManager.dispose() now tells the spooler threads to terminate and then waits
(up to 1 minute) for them to complete.
-
View the issue:
http://issues.apache.org/jira/browse/JAMES-9
Here is an overview
-
For a full history of the issue, see:
http://issues.apache.org/jira/browse/JAMES-49?page=history
-
View the issue:
http://issues.apache.org/jira/browse/JAMES-49
Here
/Mailets (bundled)
Component changed from SpoolManager Processors
-
For a full history of the issue, see:
http://issues.apache.org/jira/browse/JAMES-99?page=history
-
For a full history of the issue, see:
http://issues.apache.org/jira/browse/JAMES-134?page=history
-
View the issue:
http://issues.apache.org/jira/browse/JAMES-134
Here
-
For a full history of the issue, see:
http://issues.apache.org/jira/browse/JAMES-134?page=history
-
View the issue:
http://issues.apache.org/jira/browse/JAMES-134
Here is an overview
-
For a full history of the issue, see:
http://issues.apache.org/jira/browse/JAMES-34?page=history
-
View the issue:
http://issues.apache.org/jira/browse/JAMES-34
Here is an overview of the issue
-
For a full history of the issue, see:
http://issues.apache.org/jira/browse/JAMES-112?page=history
-
View the issue:
http://issues.apache.org/jira/browse/JAMES-112
Here is an overview of the issue
.
-
View the issue:
http://issues.apache.org/jira/browse/JAMES-72
Here is an overview of the issue:
-
Key: JAMES-72
Summary: SMTP Handler DATA buffering issue
Type: Bug
Status: Resolved
priority changed to Minor
Version changed to 2.1.3
Version changed to 2.0a3
Version changed to 2.2.0a18
-
For a full history of the issue, see:
http://issues.apache.org/jira
, it appears that Sylpheed is not RFC compliant, and in a way that an RFC
compliant server is forbidden from accepting. The line terminator MUST be CRLF.
-
View the issue:
http://issues.apache.org/jira/browse/JAMES-143
Here
.
-
View the issue:
http://issues.apache.org/jira/browse/JAMES-247
Here is an overview of the issue:
-
Key: JAMES-247
Summary: James Does Not Work With Oracle DB For Spool Repository
this comment:
http://issues.apache.org/jira/browse/JAMES-246?page=comments#action_35012
-
View the issue:
http://issues.apache.org/jira/browse/JAMES-246
Here is an overview of the issue
-
For a full history of the issue, see:
http://issues.apache.org/jira/browse/JAMES-245?page=history
-
View the issue:
http://issues.apache.org/jira/browse/JAMES-245
Here is an overview of the issue
the issue:
http://issues.apache.org/jira/browse/JAMES-240
Here is an overview of the issue:
-
Key: JAMES-240
Summary: LinearProcessor.verifyMailAddresses should catch
java.lang.ArrayStoreException
Type: Bug
?
-
View this comment:
http://issues.apache.org/jira/browse/JAMES-248?page=comments#action_35016
-
View the issue:
http://issues.apache.org/jira/browse/JAMES-248
Here is an overview of the issue
or
dbfile), the message is streamed directly from store to wire. When resetHandler is
called in the finally {} clause of handleConnection, the objects are released.
-
View this comment:
http://issues.apache.org/jira/browse
.
-
View the issue:
http://issues.apache.org/jira/browse/JAMES-253
Here is an overview of the issue:
-
Key: JAMES-253
Summary: deadlock in mordred connection pool
Type: Bug
Status: Resolved
Message:
A new issue has been created in JIRA.
-
View the issue:
http://issues.apache.org/jira/browse/JAMES-254
Here is an overview of the issue
that block.
Reportedly, this is a sign of a problem present in Sun JVM 1.4.0 and 1.4.1. It seems
to have been exacerbated by the fix for JAMES-253.
-
View this comment:
http://issues.apache.org/jira/browse/JAMES-254?page=comments
Message:
A new issue has been created in JIRA.
-
View the issue:
http://issues.apache.org/jira/browse/JAMES-255
Here is an overview of the issue
Message:
The following issue has been closed.
Resolver: Noel J. Bergman
Date: Thu, 15 Apr 2004 7:25 PM
Fixed. Changed to use ERROR level instead of DEBUG level.
-
View the issue:
http://issues.apache.org/jira
.
-
For a full history of the issue, see:
http://issues.apache.org/jira/browse/JAMES-254?page=history
-
View the issue:
http://issues.apache.org/jira/browse/JAMES-254
Here is an overview of the issue
:
http://issues.apache.org/jira/browse/JAMES-254?page=history
-
View the issue:
http://issues.apache.org/jira/browse/JAMES-254
Here is an overview of the issue
, see:
http://issues.apache.org/jira/browse/JAMES-254?page=history
-
View the issue:
http://issues.apache.org/jira/browse/JAMES-254
Here is an overview of the issue
a deadlock issue
in mordred exposed this problem.
-
View the issue:
http://issues.apache.org/jira/browse/JAMES-254
Here is an overview of the issue:
-
Key: JAMES
:
http://issues.apache.org/jira/browse/JAMES-250?page=history
-
View the issue:
http://issues.apache.org/jira/browse/JAMES-250
Here is an overview of the issue
-
For a full history of the issue, see:
http://issues.apache.org/jira/browse/JAMES-140?page=history
-
View the issue:
http://issues.apache.org/jira/browse/JAMES-140
Here is an overview of the issue
:
http://issues.apache.org/jira/browse/JAMES-239?page=history
-
View the issue:
http://issues.apache.org/jira/browse/JAMES-239
Here is an overview of the issue
:
http://issues.apache.org/jira/browse/JAMES-99?page=history
-
View the issue:
http://issues.apache.org/jira/browse/JAMES-99
Here is an overview of the issue
:
http://issues.apache.org/jira/browse/JAMES-238?page=history
-
View the issue:
http://issues.apache.org/jira/browse/JAMES-238
Here is an overview of the issue
history of the issue, see:
http://issues.apache.org/jira/browse/JAMES-235?page=history
-
View the issue:
http://issues.apache.org/jira/browse/JAMES-235
Here is an overview of the issue
Message:
A new issue has been created in JIRA.
-
View the issue:
http://issues.apache.org/jira/browse/JAMES-256
Here is an overview of the issue
Message:
A new issue has been created in JIRA.
-
View the issue:
http://issues.apache.org/jira/browse/JAMES-257
Here is an overview of the issue
Message:
A new issue has been created in JIRA.
-
View the issue:
http://issues.apache.org/jira/browse/JAMES-258
Here is an overview of the issue
Message:
A new issue has been created in JIRA.
-
View the issue:
http://issues.apache.org/jira/browse/JAMES-260
Here is an overview of the issue
Message:
A new issue has been created in JIRA.
-
View the issue:
http://issues.apache.org/jira/browse/JAMES-262
Here is an overview of the issue
:
http://issues.apache.org/jira/browse/JAMES-262?page=comments#action_35133
-
View the issue:
http://issues.apache.org/jira/browse/JAMES-262
Here is an overview of the issue
-configuration issue.
-
View the issue:
http://issues.apache.org/jira/browse/JAMES-155
Here is an overview of the issue:
-
Key: JAMES-155
Summary: how can I
1 - 100 of 22271 matches
Mail list logo