Ray,
> Both localhost and localhost.localdomain are candidatef for appearing to
> the right of the @ sign, as alternatives to (in your case) hartford-hwp.com
> . From the failures, it appears that you are trying to use them to the left
> of the @ sign, as a substitute for brownh . Attempts to d
The failed messages you report on indicate a basic misunderstanding about
what the parts of an e-mail address do. The basic structure of a modern
e-mail address is: [EMAIL PROTECTED]
Both localhost and localhost.localdomain are candidatef for appearing to
the right of the @ sign, as alternative
I defined the To: field in ~/.fetchmailrc. Here's what I'm using now
for testing
set logfile /opt/tmp/fetchmail_dec12.log
poll pop.registeredsite.com
proto POP3
user [EMAIL PROTECTED]
password
keep
smtpname [EMAIL PROTECTED]
I now see that I did in fact have emacs set up (s
> If you are collecting ALL the mail in the mail box on the ISP server
> to go to a SINGLE mailbox on your local server then you can force
> fetchmail to rewrite the new To: header sent to sendmail with the
> --smtpname switch on the command line (or the relevant keyword in
> the fetchmailconf file
Haines,
If you are collecting ALL the mail in the mail box on the ISP server to go to a SINGLE
mailbox on your local server
then you can force fetchmail to rewrite the new To: header sent to sendmail with the
--smtpname switch on
the command line (or the relevant keyword in the fetchmailconf fil
> Haines -- It is hard to diagnose anything from this bounce, without
> information about what the original message looked like. A ways down
> in the bounce report is this information:
Unfortunately, I can't reproduce the error. I repeated what I had done
earlier, which I believe was to send a tes
Haines -- It is hard to diagnose anything from this bounce, without
information about what the original message looked like. A ways down in the
bounce report is this information:
Date: Tue, 10 Dec 2002 13:58:47 -0500
Message-Id: <[EMAIL PROTECTED]>
From: Haines Brown <[EMAIL PROTECTED]>
To: 127.
I ran fetchmail -V to get the version and other info, and there's
little difference from what I've got with my current (RH7.3)
system. The only difference is that on my current (RH7.3) system, old
messages are flushed before retrieval, while on new system (RH8.0)
--flush off.
At 08:11 PM 12/10/02 -0500, Haines Brown wrote:
[...]
Here is the result of my telnet experiment:
# telnet localhost 25
Trying 127.0.0.1...
Connected to hartford-hwp.com (127.0.0.1).
Escape character is '^]'.
220 hartford-hwp.com ESMTP Sendmail 8.12.5/8.12.5; Tue, 10 Dec 2002
17:52:23 -0500
HELO
Ray,
>The first messages was an undeliverable notive from when I tried to
>send myself a test message almost a week ago:
>
> [EMAIL PROTECTED] Deferred: hartford-hwp.com.: Network is
> unreachable
Hard to say at this point. The message should have been deliverable
to my current (RH7.3 machine)
Comments below, interspersed.
At 02:43 PM 12/10/02 -0500, Haines Brown wrote:
Here are some preliminary results on fetchmail.
--
When I originally ran netsat -l, I got:
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State
Here are some preliminary results on fetchmail.
--
When I originally ran netsat -l, I got:
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State
tcp0 0 127.0.0.1:smtp *:* LISTEN
But
OK. From what you posted ... specifically the "netstat -l" output ... we
know that *something* is listening on port 25. Specifically:
tcp0 0
127.0.0.1:smtp *:* LISTEN
Next step is to find out what that something is. There are several ways to
do
Haines,
I didn't catch the early posts on this topic but did see ray's about looking into
sendmail
and fetchmail config so here comes my "sendmail 101" class.
The netstat command is showing sendmail (smtp) listening on 127.0.0.1 (this is local
to the
machine, the loopback address.)
I normally
On a RH8.0 installation I've been trying to get going since October,
one problem has been that I can't receive e-mail. The first problem
was a broken rp-pppoe. When that fixed, I could at least browse the
web. Next I faced messed up rules for iptables, but I've removed the
firewall. Since the probl
15 matches
Mail list logo
