Gnus development mailing list
 help / color / mirror / Atom feed
From: Andrew Innes <andrewi@harlequin.co.uk>
Cc: ntemacs-users@cs.washington.edu, ding@ifi.uio.no
Subject: Re: Gnus v5.2 and GNU Emacs 19.31 Win32
Date: Thu, 6 Jun 1996 21:22:06 +0100	[thread overview]
Message-ID: <199606062022.VAA17735@propos.long.harlequin.co.uk> (raw)
In-Reply-To: <x7vih4r9i2.fsf@unilab.dfci.harvard.edu> (message from Richard Pieri on 06 Jun 1996 15:57:25 -0400)

On 06 Jun 1996 15:57:25 -0400, Richard Pieri <ratinox@unilab.dfci.harvard.edu> said:
>>>>>>"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.

Yup - movemail has the ability to read directly from a mail spool file
as well, with all the proper locking code.  However, this method is
disabled on NT/Win95 precisely because Samba (widely used free software
that lets Windows machines access Unix disks over the network) doesn't
appear to implement the necessary locking calls.

>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?

Yes, movemail is hard-coded to write the output file in Babyl format,
although it could easily be modified and recompiled to output in a
different format (make sure you call it something other than movemail if
you do that, to avoid confusion).

Curiously, movemail only does this conversion when reading from a POP3
server - when reading a mail spool file directly, it just makes a
verbatim copy.

I'm sure Gnus could be made to borrow some of RMAIL's functions for
parsing Babyl files, if necessary, but modifying movemail itself would
be far simpler.

AndrewI


  reply	other threads:[~1996-06-06 20:22 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
1996-06-06 20:22   ` Andrew Innes [this message]
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=199606062022.VAA17735@propos.long.harlequin.co.uk \
    --to=andrewi@harlequin.co.uk \
    --cc=ding@ifi.uio.no \
    --cc=ntemacs-users@cs.washington.edu \
    /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).