in reply to Reporting a bug in Perl is tricky

The script reported success sending the bug, but I got no feedback. I cannot find it in the bug tracker either:

It's probably lying in some queue on your end because the system perlbug used wasn't configured correctly (perhaps because it was never configured at all).

Am I right in complaining about lack of "customer care" in regards to bug reporting?

If it's not showing up in the RT, the lack of care is because noone knows you attempted to submit a bug report.

If I do not use perlbug, does the e-mail get automatically rejected?

To my knowledge, nothing gets outright rejected. "Questionable" emails are flagged for moderation. Unless it's spam, someone will release shortly after.

Ideally, you should use perlbug to generate the report even if you don't use perlbug to send it. Choose to save the report to a file instead of having it sent, then use your favourite email client to send it (inlined, not as an attachment).

Replies are listed 'Best First'.
Re^2: Reporting a bug in Perl is tricky
by rdiez (Acolyte) on May 17, 2016 at 13:34 UTC
    Thanks for all the tips. I just created the Bitcard accound and added the bug manually. I thought at first that "Bitcard" was some private company. It's all rather user unfriendly. I started perlbug from Ubuntu Linux, and how would I know whether it is misconfigured to send e-mails if it reports "OK" at the end?
[reply]

      Perlbug cannot know if the mail delivery happened to the final recipient. Perlbug hands off the mail to the local mail transfer agent (MTA), which hopefully forwards that mail to the next link in the chain. If sendmail (or whatever) is not configured to send outbound mail, hopefully it will send mail to root after the mail has lingered in its undeliverable state for some time. I don't know how Ubuntu handles its maili setup.

[reply]
[d/l]
[select]

      Thanks for all the tips.

      Welcome

      I just created the Bitcard accound and added the bug manually. I thought at first that "Bitcard" was some private company. It's all rather user unfriendly

      Why not to just use the friendly interface you just thanked me for explaining?

      I started perlbug from Ubuntu Linux, and how would I know whether it is misconfigured to send e-mails if it reports "OK" at the end?

      perlbug (and other programs using your mail system) have no control over what your mail system does after they submit an email to it, and they no reasonable way to query it.

[reply]
        I haven't used perlbug, but from the discussion (and from the source :-)) it might help to simply change the text from "Message sent" to "Message has been handed over to your mail system". For anyone who is capable of using perlbug in the first place, that should be sufficient. Rats! Now I have to find out how to make a pull request :-)

        Update: https://rt.perl.org/Public/Bug/Display.html?id=128180

[reply]

In Section Seekers of Perl Wisdom