Re: perlbug - where is my bugreport

You have finished composing your message. At this point, you have 
a few options. You can:

    * [Se]nd the message to perlbug@perl.org and root@localhost, 
    * [D]isplay the message on the screen,
    * [R]e-edit the message
    * Display or change the message's [su]bject
    * Save the message to a [f]ile to mail at another time
    * [Q]uit without sending a message

Action (Send/Display/Edit/Subject/Save to File):
[download]

If you selected 'Send' it may be stuck locally if your mail program is not properly configured.

Comment on Re: perlbug - where is my bugreport Download Code

Replies are listed 'Best First'.
Re^2: perlbug - where is my bugreport by Skeeve (Parson) on Feb 20, 2019 at 07:37 UTC
I fear that's it :( `s$$([},&%#}/&/]+}%&{});#$&&s&&$^X.($'^"%]=\&(\|?{%` `+`.+=%;.#_}\&"^"-+%*).}%:##%}={~=~:.")&e&&s""`$''`"e	[reply] [d/l] [select]
Re^3: perlbug - where is my bugreport by marto (Cardinal) on Feb 20, 2019 at 07:39 UTC
I've hardly used it, but each time I selected the 'save' option, as I know my local system does not have mail configured, and have to send it using my mail client.	[reply]
Re^3: perlbug - where is my bugreport by kcott (Archbishop) on Feb 21, 2019 at 07:30 UTC
G'day Skeeve, I had the same problem, and for the same reason, some years ago. The solution was as ++marto indicated: send with my own email client. I just wanted to add a word of caution when doing this. When I first did this, I formatted the email as (what I thought was) a single `<pre>` block of monospace text. My email client decided to reformat this into a multi-nested series of `<pre>` and `<p>` blocks (I wasn't aware this had happened). When I checked on RT, it said the post was too long to display and indicated an attachment (which showed this horrible, email-client-generated mess). The fix was to change the settings for `perlbug@perl.org` in my email client to send in "Plain Text Only". All subsequent posts to RT have appeared without any problems. — Ken	[reply] [d/l] [select]