Incoming mail screwed up by Gnus .80

Incoming mail screwed up by Gnus .80

[Dmitry Yaitskov]

Hi,

I'm using nnml mail backend reading from POP w/pgnus .80, with some
basic mail splitting. A message got into my junk group today which
looked like (and actually was) a part of a normal mail message. The
problem was (I think) that it was a message whose body had an empty
line followed by a line starting with the word "From blah-blah-blah".
Seems like gnus decided that it was the beginning of a new mail
message, and screwed up things accordingly. Which got me thinking -
how *does* gnus decide where is the start of the next mail message in
an "IncomingXXX" file? I looked at the "IncomingXXX" files in my
~/Mail dir and did not see any dots by themselves or anything else.
Does it by design looks just for empty lines followed by "^From"? Or
am I missing something? In any case, the screwup in my case was real,
and I can provide both the "IncomingXXX" and the parsed message files
if needed.

-- 
Cheers,
-Dima.

Re: Incoming mail screwed up by Gnus .80

[Jack Vinson]

>>>>> "DY" == Dmitry Yaitskov <dimas@home.com> writes:

DY> I'm using nnml mail backend reading from POP w/pgnus .80, with some
DY> basic mail splitting. A message got into my junk group today which
DY> looked like (and actually was) a part of a normal mail message. [snip]

I don't think this is a *Gnus* problem.  I have had this happen with a
different version of movemail and it was solved through discussions with
that developer.  

I suppose the mail-source-movemail code could be missing something.  I am
using Movemail.

This has also come up recently.  Maybe there is already a solution in the
archives.

Jack

Re: Incoming mail screwed up by Gnus .80

[Dmitry Yaitskov]

Jack Vinson <jvinson@chevax.ecs.umass.edu> spake thusly:

> >>>>> "DY" == Dmitry Yaitskov <dimas@home.com> writes:
> 
> DY> I'm using nnml mail backend reading from POP w/pgnus .80, with some
> DY> basic mail splitting. A message got into my junk group today which
> DY> looked like (and actually was) a part of a normal mail message. [snip]
> 
> I don't think this is a *Gnus* problem.  I have had this happen with a
> different version of movemail and it was solved through discussions with
> that developer.  
> 
> I suppose the mail-source-movemail code could be missing something.  I am
> using Movemail.
> 
> This has also come up recently.  Maybe there is already a solution in the
> archives.

I am afraid I do not understand. I thought movemail was used to move
mail from "inbox" (which in my case is a pop server) to the user mail
directory (i.e. to one of ~/Mail/Incoming... files). If this is so,
then the problem I saw could not have been caused by movemail, could
it? The Incoming... file has the mail message correct, as far as I
understand it was screwed up by whatever split the specific message
and put it into the mail group - which is nnml in this case, again -
if I understand it correctly. What am I missing?

BTW, I did not specify a mail-source-movemail-program - from which I
gather that the movemail.exe that came with XEmacs is used by gnus by
default. Still, I don't see how this can be relevant for the problem
in question.

-- 
Cheers,
-Dima.