RE: [cobalt-users] Cube2 slow pop3 logins

[erichelm@xxxxxxxxxxxx (Eric Helm)]

I think I may have found the root of the delay but I am clueless as to how
to fix this problem.
It appears that the mail program is trying to do reverse dns or something.
Any ideas to fix this?
When the internal network ip of the cube is used as the pop and smtp server
address, everything works great.
Here is a sample of the maillog file where I suspect is the problem: There
are a few hundred lines similar to this.

Jun  6 07:50:35 mail in.qpopper[12172]: (v?) POP login by user "xxxxxxx" at
(xxx.xxx.xxx.xxx) xxx.xxx.xxx.xxx
Jun  6 07:50:38 mail in.qpopper[12173]: (v?) Unable to get canonical name of
client xxx.xxx.xxx.xxx: Host name lookup failure (2)

-----Original Message-----
From: cobalt-users-admin@xxxxxxxxxxxxxxx
[mailto:cobalt-users-admin@xxxxxxxxxxxxxxx]On Behalf Of Stephen Sloan
Sent: Wednesday, June 06, 2001 2:39 PM
To: cobalt-users@xxxxxxxxxxxxxxx
Subject: Re: [cobalt-users] Cube2 slow pop3 logins


Here is a fix I posted a while back:

"Have you tried entering your workstations in the Qube's hosts file
(/etc/hosts). I was having trouble getting POP3 to respond quickly until I
added all of my workstations to my hosts file. This is easy if each has its
own IP address, just enter the IP address and workstation name for each. In
my case, since I use DHCP, I entered each IP address in the range set for
DHCP followed by Workstation1, Workstation2,... This has resolved all of my
problems with POP3 response (now instant)."

The following is an excerpt from our hosts file:

"
127.0.0.1 localhost
192.168.1.1 mincocube.mincocorp.com # main interface
XXX.XXX.XX.XXX cobalt-eth1.mincocorp.mincocorp.com # main interface
192.168.1.2 workstation2
192.168.1.3 workstation3
192.168.1.4 workstation4
192.168.1.5 workstation5
"