Gnus development mailing list
 help / color / mirror / Atom feed
From: Dmitry Yaitskov <dimas@home.com>
Subject: Re: Incoming mail screwed up by Gnus .80
Date: 12 Mar 1999 18:22:47 -0500	[thread overview]
Message-ID: <uaexi5m48.fsf@home.com> (raw)
In-Reply-To: Jack Vinson's message of "12 Mar 1999 15:51:49 -0600"

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.



      reply	other threads:[~1999-03-12 23:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-03-12 20:07 Dmitry Yaitskov
1999-03-12 21:51 ` Jack Vinson
1999-03-12 23:22   ` Dmitry Yaitskov [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=uaexi5m48.fsf@home.com \
    --to=dimas@home.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).