Package: reportbug Version: 6.4.4 Severity: normal Tags: patch Having many times over the years ended up with a saved reportbug file due to local email config issues, and always stuggled to find the runes to resend it easily later, I thought it worth adding some info to the man page on this subject.
Attached is a patch doing that. This problem afflicts many so a bit more help on the man page seems a good idea. I notice that the reportbug template for this package adds advice on getting local email going. Perhaps that should go in the manpage too? -- Package-specific info: ** Environment settings: EDITOR="jed" EMAIL="woo...@wookware.org" ** /home/wookey/.reportbugrc: smtphost reportbug.debian.org:587 header "X-Debbugs-CC: woo...@wookware.org" no-cc -- System Information: Debian Release: wheezy/sid Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-35-generic (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- Configuration Files: /etc/reportbug.conf changed [not included] -- no debconf information
--- man/reportbug.1~ 2013-03-12 22:45:53.000000000 +0000 +++ man/reportbug.1 2013-06-12 14:58:09.000000000 +0000 @@ -310,7 +310,8 @@ both headers and mail body. If you want to use it as a template to create a new bug report, then you have to remove all the headers (mind the \fBSubject\fP one, though) and start the report at the -\fBPackage\fP pseudo-header. +\fBPackage\fP pseudo-header. You can send this file later with +/usr/sbin/sendmail -t < FILE .TP .B \-O, \-\-offline Disable all external queries. Currently has the same effect as @@ -526,6 +527,22 @@ should be a valid \fBhttp\fP URL for a proxy server, including any required port number (simply specifying a hostname, or omitting a port other than 80, WILL NOT WORK). +.SH SAVED REPORTBUG FILES +Reportbug sends its reports by email. If there is a problem when it +tries to send the mail, or you used -o FILE to explicitly save the +mail, then you end up with a local file containing the whole mail (the +bugreport, any attachments, and headers containing sender and +recipient info. +.TP +Problems sending reportbug emails are common because port 25 is often +blocked on the network and/or local email sending is not configured, +which is increasingly common on desktop machines. If there is a +problem sending the finished email, then it is saved in /tmp/ and the +filename printed. +.TP +Once you have configured an MTA (to accept and deliver locally-sent +mail) on the local machine, you can deliver the bug report again with +.B /usr/sbin/sendmail -t < /tmp/reportbug-filename .SH NOTES .B reportbug should probably be compatible with other bug tracking systems, like
