chaica wrote:
> Allowing custom muas outside supported muas exclude the possibility to give
> feedback to the user about what happened *after* reportbug gave the bug
> report to the mua. How can reportbug know if your script/custom software is
> available on your system and efficiently working ?
On Jun 07, cha...@ohmytux.com wrote:
Allowing custom muas outside supported muas exclude the possibility to give
feedback to the user about what happened *after* reportbug gave the bug
report to the mua. How can reportbug know if your script/custom software is
available on your system and
I use my preferred MUA (Icedove) precisely because reportbug does not give me
any feedback about whether a bug has been sent. If I use Icedove then I have a
copy in my sent folder.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble?
Hi Paul,
Thanks for the report, it is true MUA support has changed a lot recently.
Allowing custom muas outside supported muas exclude the possibility to give
feedback to the user about what happened *after* reportbug gave the bug
report to the mua. How can reportbug know if your script/custom
That makes sense I guess.
How about a custom-mua option for those of us who can write our own code
to support MUAs reportbug doesn't (yet) support or will never support?
If the script fails (returns != 0) you can assume that delivery failed.
--
bye,
pabs
http://wiki.debian.org/PaulWise
Package: reportbug
Version: 4.4
Severity: important
I just upgraded from lenny to squeeze and was disappointed to find that
reportbug no longer supports custom MUAs. reportbug doesn't support my
preferred MUA (evolution) so I use a custom MUA script to dump reportbug
mails into my evolution
6 matches
Mail list logo
