Hello, I'm often hit by this bug, as I have several Debian instances where no e-mail conection is available. So I save the report of reportbug, transfer the file to another machine and then I need to massage the e-mail to get it accepted (currently removing all but the base64 part, running "base64 -d " on the remaining part and inserting the output back into the original mail. I'm probably going to skript it soon.
So it would be very helpful for me if either temporarily stored
e-mails of reportbug are not stored in base64 format at all or at
least configurable, so that I can always see the contents after "mutt
-H reportbug …".
Since all e-mails sent by mutt at least arrived in the BTS without
problems I do not see the point of encoding e-mails in base64 at all.
(But there may be use cases, so makeing this configurable would
probably be the best option).
Having the BTS accept the base64 encoded e-mails is suboptimal, as I
can no longer read the e-mails in mutt and sometimes I notice things
just before sending, prompting me to update the report in mutt.
Greetings
Helge
--
Dr. Helge Kreutzmann [email protected]
Dipl.-Phys. http://www.helgefjell.de/debian.php
64bit GNU powered gpg signed mail preferred
Help keep free software "libre": http://www.ffii.de/
signature.asc
Description: Digital signature
