But why not put the message to the error-processor so it wold be easier
to trigger such errors.
bye
Am Dienstag, den 14.02.2006, 10:36 +0100 schrieb Norman Maurer:
> Damn ok..
>
>
> Am Dienstag, den 14.02.2006, 10:27 +0100 schrieb Stefano Bagnara:
> > Norman Maurer wrote:
> > > Its a message i get and send it to the main mailserver..
> > >
> > > Where should the message located ?
> > >
> > > deadletter table ?
> >
> > Unfortunately generic exceptions in the delivery process ends in message
> > purging:
> >
> > } catch (Exception e) {
> > // Prevent unexpected exceptions from causing looping by removing
> > // message from outgoing.
> > // DO NOT CHNANGE THIS to catch Error! For example, if there were an
> > OutOfMemory condition
> > // caused because something else in the server was abusing memory, we
> > would not want to
> > // start purging the outgoing spool!
> > outgoing.remove(key);
> > throw e;
> > }
> > } catch (Throwable e) {
> > if (!destroyed) log("Exception caught in RemoteDelivery.run()", e);
> > }
> >
> >
> > If you can find a message to reproduce the issue please post it here:
> > http://issues.apache.org/jira/browse/JAMES-419?page=all
> > We already found this javamail 1.3.2 bug and applied a workaround, but
> > probably there are more conditions hitting the bug.
> >
> >
> > Stefano
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
