From: Barry Pollock <barryp@mail.hurontel.on.ca>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: fetchmail question
Date: Tue, 11 Nov 2003 15:45:04 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.58.0311111539370.1123@box> (raw)
In-Reply-To: <20031111144603.GA18602@lrxms.net>
I found that if /etc/fetchmailrc is missing the system will get the mail
if ~/.fetchmailrc exists and you make a call to fetchmail for each user
that requires.
I could never get the system-wide fetchmail to work properly in debian.
The documentation didn't explain it properly.
If you get your /etc/fetchmailrc file to work for you, let me know.
Barry
On Tue, 11 Nov 2003, Scott Howell wrote:
> Barry,
>
> I found the problem with Bill's help. I apparently misunderstood the
> purpose of the system-wide fetchmailrc file. I placed one in my home
> directory and it worked just fine for fetching my wife's and my mail.
> I need to go back and figure out what Debian does with the system-wide
> fetchmail file and perhaps it points back to the one in the user's home
> directory.
>
> tnx
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
Scott Howell
` Gregory Nowak
` Barry Pollock
` Scott Howell
` Barry Pollock
` Scott Howell
` Kenny Hitt
` Scott Howell
` Chuck Hallenbeck
` Barry Pollock [this message]
` Geoff Shang
` Scott Howell
-- strict thread matches above, loose matches on Subject: below --
Richard Villa
` Igor Gueths
` Richard Villa
` Gregory Nowak
` William F. Acker WB2FLW +1-303-777-8123
` Janina Sajka
` Richard Villa
` Steve Holmes
` Igor Gueths
` Janina Sajka
` Steve Holmes
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=Pine.LNX.4.58.0311111539370.1123@box \
--to=barryp@mail.hurontel.on.ca \
--cc=speakup@braille.uwo.ca \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).