Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Frank Haun <pille3000@gmx.net>
Subject: Re: Using fetchmail with gnus (on Windows)
Date: Fri, 28 Jun 2002 00:40:15 +0200	[thread overview]
Message-ID: <86d6ucbb1s.fsf@pille.my-fqdn.de> (raw)
In-Reply-To: <eleszhkm.fsf@bitstream.com>

Peter Davis <pd@world.std.com> writes:

> So this still leave me with the basic problem:  Why doesn't gnus read
> mail from this spool file.  Aargh!

In one of your earlier articles I've found:

| :path "c:\\cygwin\\var\\spool\\mail\\pdavis"
| :path "f:/cygwin/var/spool/mail/pdavis"

Where is the file, `C:' or `F:'?

Hm, maybe I'll test it tomorrow on my Windows partition and a spool
file.

[Ok, done the test]

I've copied a small spool file with 5 messages from my Unix box to
"f:/var/mail/fhaun". On W2K I use this setting with Emacs 21.2 and Oort
Gnus v0.06:

(add-to-list 'gnus-secondary-select-methods '(nnml ""))
(setq mail-sources
      '((file :path "f:/var/mail/fhaun")))

It works. _NO_ problems. For testing I've converted all "UNIX line ends"
to "DOS line ends". It works too. And if there are problems with
permissions, movemail.exe complains about it.

Frank
-- 
  line-move: End of buffer [42 times]


  reply	other threads:[~2002-06-27 22:40 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-18 16:21 Peter Davis
     [not found] ` <m3lm9cqxdh.fsf@multivac.cwru.edu>
2002-06-19  3:44   ` pd
     [not found] ` <r8j3w69o.fsf@bitstream.com>
     [not found]   ` <znxmpt5h.fsf@bitstream.com>
     [not found]     ` <868z56jtd4.fsf@pille.my-fqdn.de>
2002-06-23 13:43       ` Peter Davis
2002-06-26 14:53   ` Peter Davis
     [not found]     ` <m3it468440.fsf@multivac.cwru.edu>
2002-06-26 19:12       ` Peter Davis
2002-06-26 20:29         ` Josh Huber
2002-06-27  2:47           ` pd
     [not found]             ` <87ofdxpci6.fsf@alum.wpi.edu>
     [not found]               ` <wusk28cy.fsf@bitstream.com>
     [not found]                 ` <87y9d0ol0j.fsf@alum.wpi.edu>
2002-06-27 14:52                   ` Peter Davis
2002-06-27 15:57                     ` Josh Huber
     [not found]                       ` <it44ziwa.fsf@bitstream.com>
2002-06-27 18:45                         ` Peter Davis
2002-06-27 22:40                           ` Frank Haun [this message]
     [not found]                             ` <bs9wump3.fsf@bitstream.com>
2002-06-28  8:31                               ` Frank Schmitt
     [not found] ` <4rfgc0kv.fsf@bitstream.com>
     [not found]   ` <vafd6u4u66o.fsf@lucy.cs.uni-dortmund.de>
     [not found]     ` <vafpty3fu7y.fsf@lucy.cs.uni-dortmund.de>
     [not found]       ` <uhejfqytj.fsf@bitstream.com>
     [not found]         ` <vafn0t7cuug.fsf@lucy.cs.uni-dortmund.de>
     [not found]           ` <u8z4qpa62.fsf@bitstream.com>
     [not found]             ` <vaffzyy449z.fsf@lucy.cs.uni-dortmund.de>
     [not found]               ` <u1yagifew.fsf@bitstream.com>
     [not found]                 ` <vaflm8n8pnu.fsf@lucy.cs.uni-dortmund.de>
2002-07-08 15:00                   ` Peter Davis

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=86d6ucbb1s.fsf@pille.my-fqdn.de \
    --to=pille3000@gmx.net \
    --cc=fhaun@wtal.de \
    /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).