Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Josh Huber <huber@alum.wpi.edu>
Subject: Re: Using fetchmail with gnus (on Windows)
Date: Thu, 27 Jun 2002 11:57:18 -0400	[thread overview]
Message-ID: <87znxgn28x.fsf@alum.wpi.edu> (raw)
In-Reply-To: <y9d0zscg.fsf@bitstream.com>

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

> Oh great.  So once I finally get everything working, I'll have to
> change it all when Oort becomes real?  ;^)

No, I don't think so.  You'll probably have to change a couple things,
but nothing serious. (I think! :)

Basically, the default should work in both cases (5.8.8, oort)

> I won't use daemon mode because I want my office mail left on the
> POP server when I'm out, so I can read it at home, and vice versa.
> In fact, it's this nasty business of wanting to leave mail on one
> server and not another that's started me looking at fetchmail in the
> first place.

Right, I see now.

> Agreed!  I would like the spool file to work as a mail source.

Right, and this should be one of those settings which just works.  I
wonder if there are some problems due to you using Windows?  Does
movemail work on windows?

copy your spool file to a temp file, and test movemail:

cp /var/spool/mail/pdavis /tmp/foo
movemail /tmp/foo /tmp/bar

check to see if /tmp/bar has the contents of your spool file.  Making
sure movemail works and is in your path would be a good thing to do, I
think.

Hope that helps,

-- 
Josh Huber


  reply	other threads:[~2002-06-27 15:57 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 [this message]
     [not found]                       ` <it44ziwa.fsf@bitstream.com>
2002-06-27 18:45                         ` Peter Davis
2002-06-27 22:40                           ` Frank Haun
     [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=87znxgn28x.fsf@alum.wpi.edu \
    --to=huber@alum.wpi.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).