Gnus development mailing list
 help / color / mirror / Atom feed
From: Richard Pieri <ratinox@unilab.dfci.harvard.edu>
Cc: Gnus Mailing List <ding@ifi.uio.no>
Subject: Re: Gnus v5.2 and GNU Emacs 19.31 Win32
Date: 06 Jun 1996 15:57:25 -0400	[thread overview]
Message-ID: <x7vih4r9i2.fsf@unilab.dfci.harvard.edu> (raw)
In-Reply-To: Andrew Innes's message of Thu, 6 Jun 1996 18:34:16 +0100

-----BEGIN PGP SIGNED MESSAGE-----

>>>>> "AI" == Andrew Innes <andrewi@harlequin.co.uk> writes:

AI> movemail only reads your inbox (only via POP3 on NT/Win95)

That would do it, then.  Gnus relies on movemail to safely copy the
inbox to a work file before deleting the inbox.  One workaround is to
use another program when trying to read from a local spool (the mv
program in the unix95 archive seems to work; the MS-DOS MOVE.EXE does
not).  If you are doing this on a "live" filesystem, one that an SMTP
daemon can write to, do not do this, you could loose mail.

However, I have now discovered another problem with the ntemacs
movemail: it converts the incoming mail file (from the POP3 server) to a
Babyl file, which is a big pain in the behind since Gnus is not geared
to parse a non-Unix (or MMDF) mail file.  Is this the normal behavior
for movemail?  Is there any way to disable it (I can't find anything in
the primary Emacs distribution sources that shows how)?  Or is there a
replacement for movemail that does not act so -- IMO -- brain-damaged?

-----BEGIN PGP SIGNATURE-----
Version: 2.6.3
Charset: noconv

iQCVAwUBMbc4KZ6VRH7BJMxHAQGHnQP9ESkHIrexc7zyypuLMQgWZ9uWsEpzIMmu
ILNfwenctSi27jeoZGbLSk2GwTjNe3oDcJBkwDiKI0BAgBERpRcCI7veYM8Zq8h7
+AipsRkvnYlOrBnVW88pTAeW9WpcwIRicKNgp0Tt36y6YhDBL5cytjwkjk3a6vGO
IblXtjxartA=
=YLG4
-----END PGP SIGNATURE-----
-- 
Richard Pieri/Information Services \ Variety is the spice of life: one day
<ratinox@unilab.dfci.harvard.edu>   \ ignore people, the next day annoy
http://www.dfci.harvard.edu/         \ them. -A cat's guide to life


       reply	other threads:[~1996-06-06 19:57 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <199606061734.SAA14372@propos.long.harlequin.co.uk>
1996-06-06 19:57 ` Richard Pieri [this message]
1996-06-06 20:22   ` Andrew Innes
1996-06-06 21:14   ` Lars Magne Ingebrigtsen
1996-06-07  3:10     ` Richard Pieri
1996-06-07 15:46     ` Richard Pieri
1996-06-07 16:00     ` Richard Pieri
1996-06-07 16:46       ` michael lamoureux
1996-06-07 18:20         ` Richard Pieri
1996-06-07 19:18           ` Lars Magne Ingebrigtsen
1996-06-07 20:41             ` Richard Stanton
1996-06-08 12:30               ` Richard Pieri
1996-06-09  5:17                 ` Richard Stanton
1996-06-08 12:32             ` Richard Pieri
1996-06-09  4:09               ` Lars Magne Ingebrigtsen
1996-06-06 16:58 Richard Pieri

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=x7vih4r9i2.fsf@unilab.dfci.harvard.edu \
    --to=ratinox@unilab.dfci.harvard.edu \
    --cc=ding@ifi.uio.no \
    /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).