The email-only reporting is a real pain for competent devs too. I find myself wanting to report bugs on machines with no working SMTP access all the time. (arm dev boards, laptops and desktop inside companies which don't allow SMTP, and just the fact that to send email requires configuring the local MUA with the CRAM-MD5 blackmagic for secure SMTP to my mailserver - I don't want to do that for every install/chroot/image that has problems). The idea that SMTP is _always_ available comes from a desktop/server-centric view of the world.
Yes there are all sorts of workarounds (save the reportbug file, remembering to fish it out of /tmp before a reboot loses it all), cut and paste into working email on some other box, run reportbug elsewhere (risk of wrong package metadata) etc. But none of it feels like a good use of developer time.
An http (or scp?) transport would be really useful.
Ubuntu's apport-cli which does an initial contact over http to initiate a report and lets you fill the rest in online is very useful in these situations, even if I much prefer a nice email report over clicking about in launchpad. I'd really appreciate an easy way of sending in bugreps from places where SMTP is not available/configured.