From nobody@FreeBSD.org  Sun Feb  1 14:10:30 2004
Return-Path: <nobody@FreeBSD.org>
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 3833516A4CE
	for <freebsd-gnats-submit@FreeBSD.org>; Sun,  1 Feb 2004 14:10:30 -0800 (PST)
Received: from www.freebsd.org (www.freebsd.org [216.136.204.117])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 1B15D43D46
	for <freebsd-gnats-submit@FreeBSD.org>; Sun,  1 Feb 2004 14:10:16 -0800 (PST)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (localhost [127.0.0.1])
	by www.freebsd.org (8.12.10/8.12.10) with ESMTP id i11M98dL036051
	for <freebsd-gnats-submit@FreeBSD.org>; Sun, 1 Feb 2004 14:09:08 -0800 (PST)
	(envelope-from nobody@www.freebsd.org)
Received: (from nobody@localhost)
	by www.freebsd.org (8.12.10/8.12.10/Submit) id i11M986D036048;
	Sun, 1 Feb 2004 14:09:08 -0800 (PST)
	(envelope-from nobody)
Message-Id: <200402012209.i11M986D036048@www.freebsd.org>
Date: Sun, 1 Feb 2004 14:09:08 -0800 (PST)
From: Joe <FBSD_User@a1poweruser.com>
To: freebsd-gnats-submit@FreeBSD.org
Subject: log-in-vain issues it's msg every time 'mail' command is used.
X-Send-Pr-Version: www-2.0

>Number:         62230
>Category:       conf
>Synopsis:       log-in-vain issues it's msg every time 'mail' command is used.
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sun Feb 01 14:20:12 PST 2004
>Closed-Date:    Mon Feb 02 08:22:05 PST 2004
>Last-Modified:  Mon Feb  2 10:50:19 PST 2004
>Originator:     Joe
>Release:        FBSD 4.9  & 5.2 & 5.2.1
>Organization:
>Environment:
>Description:
Turned on sysctl log-in-vain knob on firewall/sendmail gateway machine. Every time I use the build in 'mail' command to create and send an email to to another user on local LAN domain name, log-in-vain issues these messages. Logged in as root sending email to root also produces same results. 
Connection attempt to TCP 127.0.0.1:113 from 127.0.0.1:1034 flags:0x02
Connection attempt to TCP 127.0.0.1:113 from 127.0.0.1:1034 flags:0x02
Connection attempt to UDP 127.0.0.1:512 from 127.0.0.1:1047

Also get
Connection attempt to UDP 127.0.0.1:512 from 127.0.0.1:1047
message when Lan user connects to qpopper to retrive their mail.



     
>How-To-Repeat:
turn on log-in-vail knob. uses 'mail' command to send root an message.  
>Fix:
    Change log-in-vain code to let this condition pass as valid and not issue message.  
>Release-Note:
>Audit-Trail:

From: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net>
To: Joe <FBSD_User@a1poweruser.com>
Cc: freebsd-gnats-submit@FreeBSD.org, freebsd-bugs@FreeBSD.org
Subject: Re: conf/62230: log-in-vain issues it's msg every time 'mail' command
 is used.
Date: Mon, 2 Feb 2004 06:10:28 +0000 (UTC)

 On Sun, 1 Feb 2004, Joe wrote:
 
 Hi,
 
 > >Description:
 > Turned on sysctl log-in-vain knob on firewall/sendmail gateway machine. Every time I use the build in 'mail' command to create and send an email to to another user on local LAN domain name, log-in-vain issues these messages. Logged in as root sending email to root also produces same results.
 > Connection attempt to TCP 127.0.0.1:113 from 127.0.0.1:1034 flags:0x02
 > Connection attempt to TCP 127.0.0.1:113 from 127.0.0.1:1034 flags:0x02
 
 auth lookup most likely by your MTA w/o ident service turned on.
 
 
 > Connection attempt to UDP 127.0.0.1:512 from 127.0.0.1:1047
 >
 > Also get
 > Connection attempt to UDP 127.0.0.1:512 from 127.0.0.1:1047
 > message when Lan user connects to qpopper to retrive their mail.
 
 Most likely not when you connect to qpopper but when mail gets
 delivered to a mailbox.
 
 For procmail you can turn it off with
 COMSAT=no
 in procmailrc.
 
 For postfix you can use
 biff = no
 in main.cf.
 
 
 This is _not_ a log-in-vain issue but some common mail setup. Perhaps
 better asked on questions@ ?
 
 -- 
 Bjoern A. Zeeb				bzeeb at Zabbadoz dot NeT
 56 69 73 69 74				http://www.zabbadoz.net/
State-Changed-From-To: open->closed 
State-Changed-By: ceri 
State-Changed-When: Mon Feb 2 08:20:36 PST 2004 
State-Changed-Why:  
This is not a problem with the log in vain code, which is doing exactly 
as it's supposed to do, but rather with the configuration of your mail 
related daemons. 

As suggested by Bjoern A. Zeeb, you should sent a post to 
questions@FreeBSD.org asking for help on configuring your system to 
resolve these issues. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=62230 

From: "JJB" <Barbish3@adelphia.net>
To: "Ceri Davies" <ceri@FreeBSD.org>,
	<bzeeb-lists@lists.zabbadoz.net>
Cc: <freebsd-bugs@FreeBSD.org>, <freebsd-gnats-submit@FreeBSD.org>,
	<questions@freebsd.org>
Subject: RE: conf/62230: log-in-vain issues it's msg every time 'mail' command is used.
Date: Mon, 2 Feb 2004 12:39:08 -0500

 I disagree with you on this.
 
 Log-in-vain purpose in life is to interrogate attempts from
 the external interface, not the localhost internal functions,
 which this clearly is what is happening.
 
 Sure there are work around solutions for this bug.
 
 If you think this is such an trivial annoyance bug that it's
 does not warrant attention, then just come out and say so,
 and not beat around the bush with work around solutions in an
 poor effort to conceal your reluctance to perform system
 maintenance activities.
 
 From what little documentation is published on Log-in-vain,
 it is not functioning correctly, period.
 
 Anybody look at the percentage of bug reports that get closed
 right out of hand to the ones that really get serious attention?
 Maybe there is some thing wrong with the evaluation criteria you
 people use to evaluate bug reports like this one.
 
 This is not an single event but an attitude that is too common
 among the people who review newly filed bug reports.
 It does nothing to foster confidence in the bug report system,
 or for that matter in the quality of the overall FBSD system.
 
 Just my observations of the over all bug reporting system, it stinks
 and needs to be readdressed so it's more amiable to really getting
 bugs fixed and not passing the buck, offering work around solutions.
 Just because there are many work around solutions does not warrant
 not
 fixing the bug causing the problem in the first place.
 
 No use beating an dead horse who can't hear what being said anyway.
 
 
 
 -----Original Message-----
 From: Ceri Davies [mailto:ceri@FreeBSD.org]
 Sent: Monday, February 02, 2004 11:22 AM
 To: FBSD_User@a1poweruser.com; ceri@FreeBSD.org;
 freebsd-bugs@FreeBSD.org
 Subject: Re: conf/62230: log-in-vain issues it's msg every time
 'mail' command is used.
 
 Synopsis: log-in-vain issues it's msg every time 'mail' command is
 used.
 
 State-Changed-From-To: open->closed
 State-Changed-By: ceri
 State-Changed-When: Mon Feb 2 08:20:36 PST 2004
 State-Changed-Why:
 This is not a problem with the log in vain code, which is doing
 exactly
 as it's supposed to do, but rather with the configuration of your
 mail
 related daemons.
 
 As suggested by Bjoern A. Zeeb, you should sent a post to
 questions@FreeBSD.org asking for help on configuring your system to
 resolve these issues.
 
 http://www.freebsd.org/cgi/query-pr.cgi?pr=62230
 

From: Ceri Davies <ceri@FreeBSD.org>
To: JJB <Barbish3@adelphia.net>
Cc: bzeeb-lists@lists.zabbadoz.net, freebsd-bugs@FreeBSD.org,
	freebsd-gnats-submit@FreeBSD.org, questions@freebsd.org
Subject: Re: conf/62230: log-in-vain issues it's msg every time 'mail' command is used.
Date: Mon, 2 Feb 2004 18:48:25 +0000

 On Mon, Feb 02, 2004 at 12:39:08PM -0500, JJB wrote:
 > I disagree with you on this.
 > 
 > Log-in-vain purpose in life is to interrogate attempts from
 > the external interface, not the localhost internal functions,
 > which this clearly is what is happening.
 
 That's simply not true.
 
 $ grep vain /etc/defaults/rc.conf
 log_in_vain="0"                 # >=1 to log connects to ports w/o listeners.
 
 > If you think this is such an trivial annoyance bug that it's
 > does not warrant attention, then just come out and say so,
 > and not beat around the bush with work around solutions in an
 > poor effort to conceal your reluctance to perform system
 > maintenance activities.
 
 It's not that I don't think it's a bug that warrants attention; I don't
 think it's a bug at all.
 
 Thanks also for your diatribe.  I don't agree with any of that either.
 
 Ceri
 -- 
>Unformatted:
