From: Cheryl Homiak <chomiak@chartermi.net>
To: "blinux-list@redhat.com" <blinux-list@redhat.com>
Subject: Re: problems with incoming mail solved
Date: Sat, 17 Nov 2001 23:07:23 -0600 (CST) [thread overview]
Message-ID: <Pine.LNX.4.40.0111172303540.1172-100000@maranatha.chartermi.net> (raw)
In-Reply-To: <Pine.LNX.4.40.0111061156290.372-100000@maranatha>
Thought I should hpdate this in case somebody else has this problem. I
finally got an answer to this from somebody on the debian-user list. I
discovered that my loopback interface was not coming up automatically on
boot; this was causing fetchmail's/exim's strange behavior. The remedy was
to place in my /etc/network/interfaces the line
auto lo eth0
parent reply other threads:[~ UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <Pine.LNX.4.40.0111061156290.372-100000@maranatha>]
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.40.0111172303540.1172-100000@maranatha.chartermi.net \
--to=chomiak@chartermi.net \
--cc=blinux-list@redhat.com \
/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).