You should use perlbug to send bug emails. Mails not containing the footer that perlbug produces are likely to get eaten by the spam filters I think.

Note that perlbug also can give you a text file to paste into your mail.

If you want to add information to an existing bug, you need to mention "RT #12345" in your mail subject I think. The exact format is also described in the text that RT or perlbug output.

You should use perlbug to send bug emails

The issue is that nowadays, it is quite common for desktop systems to have mail delivering misconfigured and the mailer program called by perlbug may fail to actually deliver anything!

Yes - on Windows, I always let perlbug write the text to a file and then copy the text from that file into the mail I actually send.

Hi rdiez,

How long ago did you report the bug? AFAIK P5P is moderated, so it might take a little while for a moderator to get around to approving it (the email) if you're not a subscriber.

Update:

By the way, there is no way for normal people to create an account on that bug tracker.

Right above the text you quoted:

... get a Bitcard account.

I don't remember that procedure being too complicated, did you have any trouble with it?

Regards,
-- Hauke D

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).

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?

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.

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.