Glyn Millington wrote:
> 
> On Sun, Jun 25, 2000 at 09:24:44AM -0400, thus spake ~*Mark*~:
> >
> > I re-ran the install.sh and made sure that ports 25 and 110 are indeed
> > open. FM is still not bringing down the mail for use in Pine. I really
> > came to like that program! Wish I could get it running again.
> > --
> > Mark
> 
> Hi, Mark.
> 
> I wonder where the problem really is here!
> 
> Just in case, check port 25 and sendmail
> Try
> 
> telnet localhost (or whatever your hostname) 25
> 
> If you get a response type in
> 
> HELO localhost
> 
> You should get a cheery  "pleased to meet you message" from
> sendmail.  If not there is something wrong with sendmail, or your
> firewall will not even let YOU in.
> 
> --------------------------------------
> Like this:-
> 
> [glyn@glyn-thebearded glyn]$ telnet glyn-thebearded 25
> Trying 10.12.11.26...
> Connected to glyn-thebearded.localdomain.
> Escape character is '^]'.
> 220 glyn-thebearded.localdomain ESMTP Sendmail 8.9.3/8.9.3; Sun, 25 Jun 2000 
>16:32:40 +0100
> HELO glyn-thebearded
> 250 glyn-thebearded.localdomain Hello glyn-thebearded.localdomain [10.12.11.26], 
>pleased to meet you
> -------------------------------------------------------
> 
> Is fetchmail bringing down the mail anywhere?
> 
> set syslog
> 
> in your .fetchmailrc will send out put to maillog - you might
> then get some indication of where the mail IS going.
> 
> -------------------------------------------------------
> 
> If that doesn't shed any light could you let us have a look at
> your fetchmailrc and a few chunks from maillog?
> 
> Good luck?
> 
> Glyn M
> 
> --
>        ******************************************************
>        * "The soul is greater than the hum of its parts. "  *
>        *                 Douglas Hoftstatder                *
>        ******************************************************

On second thought I followed your example to the letter this time.

I typed:        telnet localhost.localdomain 25  <ENTER>

the resonse was:        Trying 192.168.99.1...
                telnet: Unable to connect to remote host: no route to                  
                 host

Now I'm REALLY stumped.
-- 
Mark

I love my Linux Box....!
        REASON #1 -- ...it's not Windows!
Registered Linux user #1299563

Reply via email to