From nobody@FreeBSD.org  Thu Aug 18 12:02:10 2005
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 A5BD816A41F
	for <freebsd-gnats-submit@FreeBSD.org>; Thu, 18 Aug 2005 12:02:10 +0000 (GMT)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (www.freebsd.org [216.136.204.117])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 73EDF43D46
	for <freebsd-gnats-submit@FreeBSD.org>; Thu, 18 Aug 2005 12:02:10 +0000 (GMT)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (localhost [127.0.0.1])
	by www.freebsd.org (8.13.1/8.13.1) with ESMTP id j7IC2ALa052717
	for <freebsd-gnats-submit@FreeBSD.org>; Thu, 18 Aug 2005 12:02:10 GMT
	(envelope-from nobody@www.freebsd.org)
Received: (from nobody@localhost)
	by www.freebsd.org (8.13.1/8.13.1/Submit) id j7IC2Aj1052716;
	Thu, 18 Aug 2005 12:02:10 GMT
	(envelope-from nobody)
Message-Id: <200508181202.j7IC2Aj1052716@www.freebsd.org>
Date: Thu, 18 Aug 2005 12:02:10 GMT
From: Bob Ippolito <bob@redivi.com>
To: freebsd-gnats-submit@FreeBSD.org
Subject: send-pr should prefer to use HTTP, rather than mail
X-Send-Pr-Version: www-2.3

>Number:         85087
>Category:       misc
>Synopsis:       send-pr should prefer to use HTTP, rather than mail
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          change-request
>Submitter-Id:   current-users
>Arrival-Date:   Thu Aug 18 12:10:14 GMT 2005
>Closed-Date:    Fri Dec 30 23:34:19 GMT 2005
>Last-Modified:  Fri Dec 30 23:34:19 GMT 2005
>Originator:     Bob Ippolito
>Release:        FreeBSD 5.4-RELEASE i386
>Organization:
>Environment:
FreeBSD go.mochibot.com 5.4-RELEASE FreeBSD 5.4-RELEASE #0: Sun May 8 10:21:06 UTC 2005 root@harlow.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386
>Description:
I had attempted to send-pr last week, but it never went through.  It turns out that the freebsd.org MTA won't accept mail from my server:

Aug 11 23:45:57 go sm-mta[38236]: j7BCiYG9019787: to=<FreeBSD-gnats-submit@freebsd.org>, ctladdr=<bob@go.mochibot.com> (1001/1001), delay=18:01:22, xdelay=00:00:01, mailer=esmtp, pri=3362068, relay=mx1.freebsd.org. [216.136.204.125], dsn=4.2.0, stat=Deferred: 450 Client host rejected: cannot find your hostname, [216.200.21.218]
>How-To-Repeat:
Use send-pr from a machine where the MTA is misconfigured, the reverse DNS isn't correct, etc.
>Fix:
If send-pr could post via http://www.freebsd.org/send-pr.html, this problem would go away.  It's a lot more likely that HTTP would go through.

This shouldn't be too hard to do with the existing shell script infrastructure via curl, or a similar utility.
>Release-Note:
>Audit-Trail:

From: Giorgos Keramidas <keramida@ceid.upatras.gr>
To: Bob Ippolito <bob@redivi.com>
Cc: bug-followup@freebsd.org
Subject: Re: misc/85087: send-pr should prefer to use HTTP, rather than mail
Date: Thu, 18 Aug 2005 16:54:40 +0300

 On 2005-08-18 12:02, Bob Ippolito <bob@redivi.com> wrote:
 >
 > I had attempted to send-pr last week, but it never went through.  It
 > turns out that the freebsd.org MTA won't accept mail from my server:
 >
 > Aug 11 23:45:57 go sm-mta[38236]: j7BCiYG9019787:
 > to=<FreeBSD-gnats-submit@freebsd.org>, ctladdr=<bob@go.mochibot.com>
 > (1001/1001), delay=18:01:22, xdelay=00:00:01, mailer=esmtp,
 > pri=3362068, relay=mx1.freebsd.org. [216.136.204.125], dsn=4.2.0,
 > stat=Deferred: 450 Client host rejected: cannot find your hostname,
 > [216.200.21.218]
 
 The problem is one that can be solved by properly configuring your DNS
 setup.  There is a very good reason why the MX of FreeBSD.org refuses to
 accept email from unresolvable addresses.  It saves us from a ton of
 spam mail :-)
 
 > Use send-pr from a machine where the MTA is misconfigured, the reverse
 > DNS isn't correct, etc.
 
 That's not a send-pr bug, neither an MX bug in FreeBSD.org, IMHO.
 
 > If send-pr could post via http://www.freebsd.org/send-pr.html, this
 > problem would go away.  It's a lot more likely that HTTP would go
 > through.
 >
 > This shouldn't be too hard to do with the existing shell script
 > infrastructure via curl, or a similar utility.
 
 Only this is not possible either.  The web-based bug submission form
 includes an image that is human-readable, but cannot easily be handled
 by a script.
 
 You should really look into fixing your DNS problems.  Posting email
 from an address that doesn't resolve properly these days is a bit silly,
 since many servers use DNS queries to filter out most of the "naive
 spammers who don't have valid forward & backward resolution set up
 correctly".  You'll have problems with other mail servers too, until you
 fix your DNS setup.
 
 

From: Bob Ippolito <bob@redivi.com>
To: Giorgos Keramidas <keramida@ceid.upatras.gr>
Cc: bug-followup@freebsd.org
Subject: Re: misc/85087: send-pr should prefer to use HTTP, rather than mail
Date: Thu, 18 Aug 2005 08:31:14 -1000

 On Aug 18, 2005, at 3:54 AM, Giorgos Keramidas wrote:
 
 > On 2005-08-18 12:02, Bob Ippolito <bob@redivi.com> wrote:
 >
 >>
 >> I had attempted to send-pr last week, but it never went through.  It
 >> turns out that the freebsd.org MTA won't accept mail from my server:
 >>
 >> Aug 11 23:45:57 go sm-mta[38236]: j7BCiYG9019787:
 >> to=<FreeBSD-gnats-submit@freebsd.org>, ctladdr=<bob@go.mochibot.com>
 >> (1001/1001), delay=18:01:22, xdelay=00:00:01, mailer=esmtp,
 >> pri=3362068, relay=mx1.freebsd.org. [216.136.204.125], dsn=4.2.0,
 >> stat=Deferred: 450 Client host rejected: cannot find your hostname,
 >> [216.200.21.218]
 >>
 >
 > The problem is one that can be solved by properly configuring your DNS
 > setup.  There is a very good reason why the MX of FreeBSD.org  
 > refuses to
 > accept email from unresolvable addresses.  It saves us from a ton of
 > spam mail :-)
 
 Users do not necessarily have control over their reverse DNS.  Yes, I  
 could go and fix my reverse DNS for this particular server, but I  
 don't have a pressing need to and it's not really worth the  
 administration hassle just to report FreeBSD issues.  These machines  
 are not on the internet to send or receive mail, and there's no other  
 practical reason for reverse DNS to be set up properly.
 
 Bugs should be easy to report, and this isn't making it easy.   
 Knowing that send-pr isn't going to work from any servers sitting in  
 that colo, and that send-pr doesn't have an easy way to ship reports  
 to a machine that does, I'm unlikely to report bugs at all...  
 especially if they have attachments that I do not have on my  
 workstation.  The PR that was lost in the MTA queue due to this issue  
 was actually an enhancement for a port, and this kind of response is  
 really not encouraging me to bother with contributing to FreeBSD.
 
 I'm not saying that you should relax the MTA rules, I'm saying that  
 there should be an alternate path for send-pr.  One without an image- 
 based captcha, of course.
 
 -bob
 

From: Giorgos Keramidas <keramida@ceid.upatras.gr>
To: Bob Ippolito <bob@redivi.com>
Cc: bug-followup@freebsd.org
Subject: Re: misc/85087: send-pr should prefer to use HTTP, rather than mail
Date: Thu, 18 Aug 2005 21:41:42 +0300

 On 2005-08-18 08:31, Bob Ippolito <bob@redivi.com> wrote:
 >On Aug 18, 2005, at 3:54 AM, Giorgos Keramidas wrote:
 >>On 2005-08-18 12:02, Bob Ippolito <bob@redivi.com> wrote:
 >>> I had attempted to send-pr last week, but it never went through.  It
 >>> turns out that the freebsd.org MTA won't accept mail from my server:
 >>>
 >>> Aug 11 23:45:57 go sm-mta[38236]: j7BCiYG9019787:
 >>> to=<FreeBSD-gnats-submit@freebsd.org>, ctladdr=<bob@go.mochibot.com>
 >>> (1001/1001), delay=18:01:22, xdelay=00:00:01, mailer=esmtp,
 >>> pri=3362068, relay=mx1.freebsd.org. [216.136.204.125], dsn=4.2.0,
 >>> stat=Deferred: 450 Client host rejected: cannot find your hostname,
 >>> [216.200.21.218]
 >>>
 >>
 >> The problem is one that can be solved by properly configuring your DNS
 >> setup.  There is a very good reason why the MX of FreeBSD.org
 >> refuses to
 >> accept email from unresolvable addresses.  It saves us from a ton of
 >> spam mail :-)
 >
 > Users do not necessarily have control over their reverse DNS.
 
 The ISP/provider of the addresses does though.
 
 > Yes, I could go and fix my reverse DNS for this particular server, but
 > I don't have a pressing need to and it's not really worth the
 > administration hassle just to report FreeBSD issues.  These machines
 > are not on the internet to send or receive mail, and there's no other
 > practical reason for reverse DNS to be set up properly.
 
 You don't need a real forward & reverse address for *all* of your
 machines.  Just the one that acts as a mail gateway.
 
 If it's too much trouble, you can always use the send-pr "save" facility
 and copy the bug report to a machine that *can* send messages.
 
 > Bugs should be easy to report, and this isn't making it easy.
 
 I'm honestly sorry that you think it is difficult in the first place.
 Unblocking all the broken DNS setups out there just for the sake of the
 bugs database is probably more dangerous though.  The spam messages that
 reach the lists, for example, would probably increase a lot.
 
 > Knowing that send-pr isn't going to work from any servers sitting in
 > that colo, and that send-pr doesn't have an easy way to ship reports
 > to a machine that does, I'm unlikely to report bugs at all...
 
 It does.  You can save the bug report *after* completing it as usual
 with send-pr, and then move the report "template" to another machine.
 Send that template to the address specified in the mail headers of the
 PR template, and all will work fine.
 
 > especially if they have attachments that I do not have on my
 > workstation.  The PR that was lost in the MTA queue due to this issue
 > was actually an enhancement for a port, and this kind of response is
 > really not encouraging me to bother with contributing to FreeBSD.
 
 I know what you are saying.  I'm just very reluctant to ask postmaster@
 about removing the DNS restriction, since it's there for a good reason.
 
 > I'm not saying that you should relax the MTA rules, I'm saying that
 > there should be an alternate path for send-pr.  One without an image-
 > based captcha, of course.
 
 That path would be then eligible for spammer attacks.  The bugs database
 has been attacked more than once by annoying trolls posting garbage as
 "bug reports".  We can't have that, so it's not a good idea to remove
 the captcha.
 
 If FreeBSD really means something to you, is it too much to ask that you
 either use the web interface (with the existing captcha parts) or set up
 your DNS properly, so that email can be sent directly?
 
 - Giorgos
 
State-Changed-From-To: open->closed 
State-Changed-By: remko 
State-Changed-When: Fri Dec 30 23:33:31 UTC 2005 
State-Changed-Why:  
This is not a bug.  Giorgos explained an alternative way to 
deliver problem reports to our team, i think that is sufficient 
and therefor the PR should be closed. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=85087 
>Unformatted:
