[ 
https://issues.apache.org/jira/browse/JAMES-744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Norman Maurer resolved JAMES-744.
---------------------------------

    Resolution: Cannot Reproduce

Mark as cannot reproduce..

> MBoxMailRepository  can't parse mboxrd files
> --------------------------------------------
>
>                 Key: JAMES-744
>                 URL: https://issues.apache.org/jira/browse/JAMES-744
>             Project: JAMES Server
>          Issue Type: Bug
>          Components: MailStore & MailRepository
>            Reporter: Norman Maurer
>            Assignee: Norman Maurer
>             Fix For: 3.0
>
>
> From ml:
> Hi,
> I think I've answered my own question and discovered a bug with 
> MBoxMailRepository and a fix is below.
> Line 283
> was:
> prevMessageStart = ins.getFilePointer() - line.length() ;
> should be:
> prevMessageStart = ins.getFilePointer() - line.length() - 2;
> This is the case because we need to subtract -1 to back up in front of the 
> character we are looking for and -1 because the readLine doesnt return the 
> carriage return
> Now the preMessageStart points to the F character in the pattern From .......
> and line 413
> was:
> ins.seek(messageStart -1);
> should be:
> ins.seek(messageStart );
> Given that the messageStart now points at the F character there is no longer 
> a need to back up one character.
> The full file is attached.
> Now I can parse Thunderbird mail files without a problem
> Rgds,
> Phil
> > I've been trying to use the MBoxMailRepository to parse a Thunderbird mail 
> > file.
> > It doesnt seem to work propely. (After loading the messages, the retrieve 
> > operation quite often doesnt return a message for a key).
> >
> > Is this because the MBoxMailRepository class doesnt support mboxrd? 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to