Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 9 Jun 1997 08:30:28 +0800
From:      chas <sweeting@neuronet.com.my>
To:        freebsd-isp@freebsd.org
Subject:   2 error messages may shed light on mailhub problem ?
Message-ID:  <3.0.32.19970609082400.00dbda38@neuronet.com.my>

next in thread | raw e-mail | index | archive | help
Last week I asked for help regarding customers being unable
to collect mail from a mailhub I am running on a FreeBSD 
box with several virtual domains (implemented through changes
to rule S98 of sendmail). Thanks to everyone for the advice
though I could not pinpoint the error in my configuration.

As mentioned, we are not an ISP. So the customer connects
via dial up to one of this country's 2 ISPs. I have noticed 2
error messages only appear on the console the past week.
These are :

NAA00753: SYSERR(root): collect: I/O error on connection from
btr-21-101.tm.net.my, from=<sumi@mdc.com.my.: Connection reset by
btr-21-101.tm.net.my

and

jun 7 23:23:23 popper: Unable to get canonical name f client, err=60


Does anyone have any idea if this is :
a) a misconfiguration at the ISP ?
b) an error with qpopper ?
c) the client's email program (eudora 3 or NS 3) ?


tm.net.my is the name of the ISP in question.
mdc.com.my is the name of the virtual email domain being run 
on the mailhub (peace.com.my).



 if it helps :

resolv.conf:
------------
domain  peace.com.my
nameserver      202.184.153.3


etc/host
--------
127.0.0.1               localhost localhost.peace.com.my
202.184.153.15          dove.peace.com.my       dove 


etc/host.conf
-------------
bind
hosts


As suggest by John Beukema :
"Could be DNS. try pinging with an IP address not a name.  
Put the IP number and domain name in /etc/hosts and put host 
ahead of bind in /etc/host.conf"

I could ping ok. Do you actually mean putting the 
IP number of the virtual domain in /etc/hosts too ?
Apologies for my ignorance. 
I have not once had problems collecting mail (only 
sometimes pinging) from an account I have at this virtual
domain (mdc.com.my) over LAN so I think DNS
is not the problem.

sorry for dragging this one out.

Thank you very much in advance - this problem is seriously
stressing us and the customer out,

chas












Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3.0.32.19970609082400.00dbda38>