Earl: I can't find where MHonArc generates this next message, if it indeed
I do not know where this comes from.
No new messages
That would be generated if MHonArc never found the beginning of a message
("From " line that I cited earlier) in the .mbx file. The fact that you
saw no dots (".") to indicate each detected message indicates that the file
MHonArc read contained no delimited messages.
Great diagnosis. If you are not getting any dots, then MHonArc
never got an intital match of the message separator. The first
line of you mbx should match the MSGSEP resource.
- message separators ("From " lines) different from what MHonArc is trying
affected by MH_MSGSEP environment variable and possible a
(also settable via command line, but you're not using that)
- input file is empty
- (remote, maybe nonsense) input file does not have 0x0A newline
terminators; but you should get at least one message detected if the
message separator is set properly (including left at its default).
Probably not. If the whole mbx was read in on the first read,
then EOF will be set before trying to read the first message. If
mbx was on a Mac and the file was not FTP'ed in ASCII mode, then
no newlines will be in the file. Therefore, the first line read made
on the file will read the entire file.
Are you by any chance setting the MH_MSGSEP environment variable, or
redefinging the message separator in a resource file?
I am a bit confused why it is trying to read .../msce-lis.mbxy. Where
does this come from?
I suspect that is not generated by Mhonarc.
I agree. And if it is, I do not know why.