You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by no...@apache.org on 2003/10/20 08:04:26 UTC
cvs commit: james-server/src/java/org/apache/james/transport JamesSpoolManager.java
noel 2003/10/19 23:04:26
Modified: src/java/org/apache/james/transport Tag: branch_2_1_fcs
JamesSpoolManager.java
Log:
Possible fix to prevent looping within the spooler?
Revision Changes Path
No revision
No revision
1.20.4.10 +15 -1 james-server/src/java/org/apache/james/transport/JamesSpoolManager.java
Index: JamesSpoolManager.java
===================================================================
RCS file: /home/cvs/james-server/src/java/org/apache/james/transport/JamesSpoolManager.java,v
retrieving revision 1.20.4.9
retrieving revision 1.20.4.10
diff -u -r1.20.4.9 -r1.20.4.10
--- JamesSpoolManager.java 20 Oct 2003 06:03:15 -0000 1.20.4.9
+++ JamesSpoolManager.java 20 Oct 2003 06:04:26 -0000 1.20.4.10
@@ -393,6 +393,20 @@
getLogger().error("Exception processing " + key + " in JamesSpoolManager.run "
+ e.getMessage(), e);
}
+ /* Move the mail to ERROR state? If we do, it could be
+ * deleted if an error occurs in the ERROR processor.
+ * Perhaps the answer is to resolve that issue by
+ * having a special state for messages that are not to
+ * be processed, but aren't to be deleted? The message
+ * would already be in the spool, but would not be
+ * touched again.
+ if (mail != null) {
+ try {
+ mail.setState(Mail.ERROR);
+ spool.store(mail);
+ }
+ }
+ */
}
}
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org