public inbox for linux-newbie@vger.kernel.org
 help / color / mirror / Atom feed
From: Ray Olszewski <ray@comarre.com>
To: linux-newbie@vger.kernel.org
Subject: Re: accessing email via POP3
Date: Tue, 30 Nov 2004 14:12:31 -0800	[thread overview]
Message-ID: <5.1.0.14.1.20041130140217.01f398b0@celine> (raw)
In-Reply-To: <33076594@newdoc.Dartmouth.ORG>

At 03:54 PM 11/30/2004 -0500, Karthik Vishwanath Adv03 wrote:
>Hello,
>
>I receive mail on this account that can be accessed via
>POP3. I used to use fetchmail as my mail-fetcher on an old
>machine to do this. I am trying to do the same from another
>machine that runs Redhat 9 (Linux 2.4.20-8) and seems like I
>cannot decipher how exactly to do this (perusing the
>fetchmail man page had me really confused). My .fetchmailrc
>looks like this:
>---------
>set syslog
>set daemon 10
>poll newdoc.dartmouth.org and options no dns keep
>user 'karthikv' there is 'karthik' here options
>
>---------
>
>$ fetchmail
>fetchmail:/home/karthik/.fetchmailrc:6: parse error at user
>
>How can I fix this? (BTW, I had a whole load of dependency
>issues on trying to install fetchmailconf...)


The error message says the problem is on line 6, but in the extract you 
provide, the "user" line is line 4. Have you left some part of the file out?

None of the examples for .fetchmailrc that I could locate (on a quick 
search) actually used the word "options", instead simply putting the 
desired options in those spots. So you might try deleting that word on the 
user line and the one before it.

Is it possible that a non-printing character slipped into the file (for 
example, a CRLF combo for newline instead of the Unix LF)?

All the examples I could find either used no quotes or (if there were 
embedded spaces) regular double quotes. So you might try either removing 
the single quotes or replacing them with double quotes.

Since this used to work on a different machine ... why aren't you simply 
moving the working .fetchmailrc from the old setup to the new one/

As to your BTW ... the Debian packaging system says that fetchmailconf 
depends only on fetchmail itself and the python and python-tk packages. Of 
course, that conceals some dependencies derived from those three, but it 
suggests that nothing really exotic is needed. Might you have run into some 
versioning issue (like a libc6 mismatch)? Hard to say much here, since I 
don't know Red Hat, not having used it for years.



-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

  reply	other threads:[~2004-11-30 22:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-30 20:54 accessing email via POP3 Karthik Vishwanath Adv03
2004-11-30 22:12 ` Ray Olszewski [this message]
2004-12-01 15:19 ` Ulrich Fürst
2004-12-01 17:19   ` J.
2004-12-01 22:13     ` Ulrich Fürst
2004-12-02  1:07       ` Peter
  -- strict thread matches above, loose matches on Subject: below --
2004-12-01 16:41 Karthik Vishwanath Adv03
2004-12-02  1:29 ` J.
2004-12-02  0:58 J.

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=5.1.0.14.1.20041130140217.01f398b0@celine \
    --to=ray@comarre.com \
    --cc=linux-newbie@vger.kernel.org \
    /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