Mourning the loss of our friend, WhitPhil.
There's no such thing as a stupid question, but they're the easiest to answer.
JoinTour
Login
Search
 
Linux and Unix
Tag Cloud
access audio blue screen boot bsod connection crash dell desktop driver dvd email error excel firefox hard drive hardware hijackthis internet keyboard laptop malware monitor motherboard network networking outlook problem processor ram recovery router safe mode screen slow sound spyware tdlwsp.dll trojan upgrade vba video virus vista vundo windows windows 7 windows vista windows xp wireless
Search
Search for:
Tech Support Guy Forums > Operating Systems > Linux and Unix >
Sendmail and xinetd/ident (auth port 113)

Tip: Click here to scan for System Errors and Optimize PC performance
[ Sponsored Link ]

Closed Thread
 
Thread Tools
wcmiller's Avatar
Junior Member with 18 posts.
 
Join Date: Nov 2000
06-Jun-2002, 07:11 PM #1
Question Sendmail and xinetd/ident (auth port 113)
Using Red Hat Linux 7.2 (enigma) Kernel 2.4.7 on an i686, and the version of Sendmail and BIND that came with it (revised May 2002).

When POP3 E-mail requests go to this host, it requests and auth (port 113) response. Since the clients accessing mail do not have authentication running, the host waits for the default 30 seconds, retries, waits for another 30 seconds, then finally gives up and delivers mail.

In the older versos of Red Hat Linux, auth was served by a process called Identd, which could be either deactivated for POP3, or you could set its timeout to practically nothing (instead of 30 seconds).

In this new version of Linux, it appears that xinetd (note spelling....it is not a transposition on my part) has supplanted identd. However, it is no longer an option for POP3....xinetd manages POP3 connections (as well as others) and apparently can't be unbound. There also seems to be no apparent way to set the timeout way low for the auth queries.

I need to know if there is a way to tell Sendmail not to use auth. I understand there is, but I'm having a heck of a time finding it. Thanks.
sahil's Avatar
Junior Member with 7 posts.
 
Join Date: May 2002
16-Jun-2002, 05:10 PM #2
I'm assuming your /etc/xinetd.d/ipop3 configuration looks something like this:<br><blockquote><code>

service pop3
{
disable = yes
socket_type = stream
wait = no
user = root
server = /usr/sbin/ipop3d
log_on_success += USERID
log_on_failure += USERID
}
</blockquote></code>

Add a "#" before each "log_on" line, which has been causing the 30-sec delay. This is a decision on the administrator's part to decrease the quality of his or her logging for that service so that your users may get their mails quickly.

--
Sahil <sahil@despammed.com>
Closed Thread Bookmark and Share

THIS THREAD HAS EXPIRED.
Are you having the same problem? We have volunteers ready to answer your question, but first you'll have to join for free. Need help getting started? Check out our Welcome Guide.

Smart Search

Find your solution!



Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
 
WELCOME TO TECH SUPPORT GUY! Are you looking for the solution to your computer problem? Join our site today to ask your question -- for free! Our site is run completely by volunteers who want to help you solve your computer problems. See our Welcome Guide to get started.

Thread Tools


You Are Using:
Server ID
Advertisements do not imply our endorsement of that product or service.
All times are GMT -5. The time now is 03:23 AM.
Copyright © 1996 - 2009 TechGuy, Inc. All rights reserved.
Powered by vBulletin, Copyright © 2000 - 2009, Jelsoft Enterprises Ltd.
Powered by Cermak Technologies, Inc.