Hi,
i fear this one is behond me:(
there are two things that to my knowledge shouldn't be there if you're
using the fetchmailrc I think you're using. I'll point to these two
point below.
I think you have in ~/.procmailrc something like:
set postmaster "tony"
set bouncemail
set properties ""
poll postoffice.worldnet.att.net aka worldnet.att.net, the-sphere.org
with proto POP3
user arodriguez there with password not-this-one is tony here
options keep fetchall
the "aka worldnet.att.net" should take care of the first fetchmail complaint
and the "user ... is tony here" should tell fetchmail whom to deliver to.
> Here is what I got last:
>
> [EMAIL PROTECTED]:~$ fetchmail -v -v ; date
> fetchmail: 5.3.3 querying postoffice.worldnet.att.net (protocol POP3) at Fri,
> 15 Dec 2000 16:34:38 -0500 (EST)
...
> reading message 1 of 16 (14488 octets)
> About to rewrite Return-Path: <[EMAIL PROTECTED]>
> Rewritten version is Return-Path: <[EMAIL PROTECTED]>
>
> fetchmail: analyzing Received line:
> Received: from cannon9.mp3.com ([63.241.16.242])
> by mtiwgwc28.worldnet.att.net
> (InterMail vM.4.01.03.10 201-229-121-110) with SMTP
> id <[EMAIL PROTECTED]>
> for <[EMAIL PROTECTED]>;
> Fri, 15 Dec 2000 20:52:51 +0000
> fetchmail: line rejected, mtiwgwc28.worldnet.att.net is not an alias of the
> mailserver
This relected thing worries me, as we told fetchmail to accept the whole
domain of worldnet.att.net with this aka thingy.
...
> fetchmail: no local matches, forwarding to tony
This 'no local matches' worries me too. He gets into failback mode here and
is trying to deliver to the postmaster (in your case tony:) instead of
directly to tony on behalve of the "user ...is tony here" line we gave him.
So the above two errors should have been fixed with the corrected fetchmailrc
file I think you're using. I take it that your running this "fetchmail -v -v"
as the user tony, and I take it that your using ~tony/.fetchmailrc. So let's
check and double check that you're using the right .fetchmailrc file with the
right content. If so, than I'm out of my wit:[
This leaves us with the this is the real error that is keeping you from
receiving files locally:
> fetchmail: SMTP connect to localhost failed
To check this I think someone proposed to you earlier on in this thread
to check whether you could connect to exim locally with this:
$ telnet localhost smtp
which should give output like:
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
220 animus.fel.iae.nl ESMTP Exim 3.12 #1 Sat, 16 Dec 2000 14:03:04 +0100
to get out of this enter
quit
please verify with the above that your exim is running and accessible via
its standard port.
--
groetjes, carel
