Re: Unable to delete blob file for mail

Tellier Benoit <[email protected]>
Newsgroups gmane.comp.jakarta.james.user
Organization Apache Foundation - James Project
Message-ID <[email protected]>
Hello Matt,

On 28/05/2020 17:47, Matt Pryor wrote:
> [...]
> Is there a compiled
> jar I could download with the fix or will I have to build it all myself
> from source?

If you are patient (~2 weeks) I can include this log enhancement in
upcoming 3.5.0 release.

Otherwise, you will have to compile it.

Regards,

Benoit

> 
> Matt
> 
> 
> On Thu, 28 May 2020 at 04:01, Tellier Benoit <[email protected]> wrote:
> 
>>
>>
>> On 27/05/2020 20:03, Matt Pryor wrote:
>>> Hi there
>>>
>>> I am seeing this a lot in our wrapper log, we are using James 3.4.0.
>>>
>>> 0/05/27 12:50:43 | WARN  12:50:43,694 |
>>> org.apache.james.queue.activemq.ActiveMQMailQueueItem | Unable to delete
>>> blob message file for mail
>>> Mail1590076890427-f333aa04-fd52-4fff-8538-de51963d52b7-to-gmail.com
>>> INFO   | jvm 1    | 202
>>>
>>> It seems to continue to attempt to send the email as also getting
>> recurring
>>> DNS errors for invalid domains.
>>>
>>> Any suggestions on how to solve this?
>>>
>>
>> I opened https://issues.apache.org/jira/browse/JAMES-3195 related to
>> your issue.
>>
>> The first thing is that the stacktrace is lost, thus we miss this
>> valuable debugging information.
>>
>> https://github.com/linagora/james-project/pull/3401 is an attempt to
>> solve it.
>>
>> Now what could happen:
>>
>>  - The URL attached to your messages is malformed
>>  - The given files do not exist, are already deleted.
>>
>> From there:
>>
>>  - Do you notice some functional problems? (are some mails dropped)
>>  - What is the file usage of the mailqueue in /var ? (du -h -d 2
>> $james/var ?)
>>
>> Best regards,
>>
>> Benoit
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>
>>
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.