misc/85087: send-pr should prefer to use HTTP, rather than mail

Giorgos Keramidas keramida at ceid.upatras.gr
Thu Aug 18 18:50:13 GMT 2005

The following reply was made to PR misc/85087; it has been noted by GNATS.

From: Giorgos Keramidas <keramida at ceid.upatras.gr>
To: Bob Ippolito <bob at redivi.com>
Cc: bug-followup at 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 at redivi.com> wrote:
 >On Aug 18, 2005, at 3:54 AM, Giorgos Keramidas wrote:
 >>On 2005-08-18 12:02, Bob Ippolito <bob at 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 at freebsd.org>, ctladdr=<bob at go.mochibot.com>
 >>> (1001/1001), delay=18:01:22, xdelay=00:00:01, mailer=esmtp,
 >>> pri=3362068, relay=mx1.freebsd.org. [], dsn=4.2.0,
 >>> stat=Deferred: 450 Client host rejected: cannot find your hostname,
 >>> []
 >> 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

More information about the freebsd-bugs mailing list