SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Do you by any chance have telecentro.com.ar as your FQDN?
My fault. The block should say:
Code:
###### Lo de abajo ANDA
busybox sendmail -v -f estefan34@telecentro.com.ar \
-S tcsmtp.telecentro.com.ar:25 \
-auestefan34@telecentro.com.ar -apxxxxxxxxxxxx \
enriquestefanini@yahoo.com.ar
I can directly give you my /etc/hosts, which for me is the prime suspect:
Code:
estefan34@telecentro:~$ cat /etc/hosts
# For loopbacking.
127.0.0.1 localhost
xxx.xxx.xxx.xxx telecentro.com.ar telecentro
yyy.yyy.yyy.yyy local.DN2 local
# End of hosts.
estefan34@telecentro:~$
local.DN2 is another machine in my LAN. My user name is 'estefan34'.
Any mistakes in those two lines in /etc/hosts would immediately be felt by either my machine or the other machine in the LAN. Ergo, the file is OK, if I am not wrong.
Of interest, maybe is this, from the link I gave above:
Quote:
When invoked from the command line, fetchmail will poll all of the configured
servers from the .fetchmailrc file and deliver the messages to the default mail
spool for that user in /var/mail/ or hand the messages off to the specfied mda
command.
Fetchmail will deliver the message to the current user’s mailbox under the
following conditions:
There is no mda is specified for the account in question in the
.fetchmailrc.
There are no local users are specified with the is "[local-user]" here;
syntax in the account specification within the .fetchmailrc file.
There are no corresponding local users for the remote usernames on the
server.
If fetchmail is running as the root user, it will drop privledges to deliver
messages to specific user accounts. If fetchmail is unable to deliver messages
as root it will deposit them in the system’s “postmaster” account. The
postmaster account defaults to postmaster, and the mail spool is located at
/var/mail/postmaster, unless modified
I can directly give you my /etc/hosts, which for me is the prime suspect:
Code:
estefan34@telecentro:~$ cat /etc/hosts
# For loopbacking.
127.0.0.1 localhost
xxx.xxx.xxx.xxx telecentro.com.ar telecentro
yyy.yyy.yyy.yyy local.DN2 local
# End of hosts.
estefan34@telecentro:~$
local.DN2 is another machine in my LAN. My user name is 'estefan34'.
I am not a DNS guru but there probably is something wrong with your local host name. Locally it is telecentro (as at the prompt we see estefan34@telecentro) while /etc/hosts gives telecentro an alias to an outside address. I suggest you change your local name to something else than telecentro and try it one more time.
Replace
xxx.xxx.xxx.xxx telecentro.com.ar telecentro
by
xxxx.xxx.xxx.xx foo23.foo685 foo23
?
EDIT: I did it but it fails, with the same error.
Code:
stefan34@telecentro:~$ fetchmail
gethostbyname failed for telecentro
Name or service not knownCannot find my own host in hosts database to qualify it!
Trying to continue with unqualified hostname.
DO NOT report broken Received: headers, HELO/EHLO lines or similar problems!
DO repair your /etc/hosts, DNS, NIS or LDAP instead.
244 messages for estefan34@telecentro.com.ar at tcpop.telecentro.com.ar (8591634 octets).
fetchmail: Connection errors for this poll:
name 0: connection to localhost:smtp [127.0.0.1/25] failed: Connection refused.
fetchmail: SMTP connect to localhost failed
fetchmail: SMTP transaction error while fetching from estefan34@telecentro.com.ar@tcpop.telecentro.com.ar and delivering to SMTP host localhost
reading message estefan34@telecentro.com.ar@tcpop.telecentro.com.ar:1 of 244 (1036 octets)fetchmail: Query status=10 (SMTP)
estefan34@telecentro:~$
If xxx.xxx.xxx.xxx pointing to telecentro/foo23 is an outside IP, then delete it completely. Let your DNS find telecentro's IP address OR change your local machine name and domain to something other than telecentro.
This might explain why sendmail fails, but it does not explain Seamonkey's failure.
I think you should post once again the current
1- /etc/hosts
2- localhost name (user@xxx)
3- fetchmailrc
as we might have inadvertantly done something wrong. Your penultimate post said "gethostname failed for telecentro" which suggested fetchmailrc contained "telecentro" instead of full server address. Because hosts file had it as an alias to telecentro.com.ar, it had succeeded previously.
Secondly, if no mail delivery agent is defined in fetchmailrc, fetchmail will deliver messages to localhost port 25 for sendmail to pick them up. That requires a proper hosts file.
Third, if you have another machine (not tainted, a live distro perhaps) or maybe a Windows partition, it might be a good idea to check if username and password is correct for the mail server. If mail goes through we now know that settings are correct and there's something wrong on the linux side.
estefan34@juan:~$ slogin root@local
slogin: Could not resolve hostname local: Name or service not known
estefan34@juan:~$ slogin semoi@local
slogin: Could not resolve hostname local: Name or service not known
estefan34@juan:~$
From the other machine, local
Code:
semoi@local:~$ slogin estefan34@juan
slogin: juan: Name or service not known
semoi@local:~$ slogin estefan34@juan
The current state of the machine is:
Code:
estefan34@juan:~$ cat /etc/hosts
#
# hosts This file describes a number of hostname-to-address
# mappings for the TCP/IP subsystem. It is mostly
# used at boot time, when no name servers are running.
# On small systems, this file can be used instead of a
# "named" name server. Just add the names, addresses
# and any aliases to this file...
#
# By the way, Arnt Gulbrandsen <agulbra@nvg.unit.no> says that 127.0.0.1
# should NEVER be named with the name of the machine. It causes problems
# for some (stupid) programs, irc and reputedly talk. :^)
#
# For loopbacking.
127.0.0.1 localhost
192.168.1.123 juan.com.ar juan
# End of hosts.
estefan34@juan:~$
arsivci0, thought I had backed up the files after succeeding in both reception and transmition but, for some cause, the thing wount work again, not having forgotten to run netconfig and boot after touching /etc/hosts (hostname= telecentro). But for some reason I am getting
when running busybox popmaildir. What a bad luck. Not only I did backups but marked them with certain word within the file! Some part of the system is remembering the 'juan' token (new hostname).
EDIT: i'LL have to ask the ISP a new password, but it means to have to wait 48hs. What do you think?
Sorry for belated response, time difference; I'm 7 hours ahead of you, I guess.
fetchmailrc:
Your username seems to be wrong:
it should be "estefan34@telecentro.com.ar" I believe. For the password, I can not comment :-)
/etc/hosts:
Is "juan.com.ar" a registered domain name? Hope you did not make it up (someone more knowledgeable about DNS might step in here as I recall this is a bad idea). A bogus name or juan.example.com may serve better.
You're welcome. Time lags 3 hs with respect to Greenwich here. I had not replicated identical conditions. So, please do as if post #57 does not exist. I will be ready, then, to resume the fetchmail stuff by the day after tomorrow. First I need to recapitulate what has been done in the last 48 hs.
juan.com.ar is not a registered domain name as far as I know.
"A bogus name or juan.example.com may serve better.": alright.
Up to now two good things have happened:
(a) I now know mail reaching my ISP servers is accesible to me and that I can reach the outside trough those servers, thus ending a whole year of uncertainty. There is no such thing as "the ISP is blocking my mail, knowingly or not".
(b) I have been succesful in using tools given me by my system in establishing communication with said servers (busybox sendmail/popmaildir).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.