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 Stefano Bagnara <ap...@bago.org> on 2006/11/18 13:14:12 UTC
Ougoing spool stuck in James 2.3.0RC4 (Was: JAMES status?)
I really hoped it was older :-/
And this reply is to change the subject, because we were off topic.
Stefano
Norman Maurer wrote:
> Hi Stefano,
>
> its a rc4. I will upgrade it soon to final version.
>
> bye
> Norman
>
> Stefano Bagnara schrieb:
>> Jürgen Hoffmann wrote:
>>> The problem is that James still accepts E-Mails coming in, he just
>>> does not
>>> deliver them afterwards. Maybe this is within James, or within one of
>>> our
>>> mailets. We are investigating this now under our test environment.
>> Maybe the problem is the "outgoing" spool that is locked.
>>
>> This was the issue we fixed in RC3 that happened when there was only
>> error messages in the spool or more than 1000 error messages in the
>> spool.
>>
>> Are you sure the James you use is RC3 and not an RC3-candidate (a
>> snapshot of something between RC2 and RC3)? (We packaged RC3 on Sep 12)
>>
>> https://issues.apache.org/jira/browse/JAMES-603?page=all
>>
>> Btw the "kill -3" dump will give us much more details on this.
>>
>> Stefano
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org