GNOME Bugzilla – Bug 601763
Unable to send to recipients
Last modified: 2021-06-01 22:42:25 UTC
Composing or forwarding an e-mail message, I can enter a recipient's e-mail address, but when I send, the message ends up in Outbox flagged, with the "To" field empty.
Thanks for the report! We need a few pieces of information: What version of Balsa are you using? Do you enter the address and then compose the message, or do you enter the address last? Do you send using the Send toolbar button, the File:Send menu item, or ctrl+Enter?
Balsa version: 2.3.28 I enter the address & then compose the message I use the Send toolbar button
Thanks! I use 2.3.28 on an f11 box, and haven't seen this problem, so I'm puzzled :( Couple more requests: Is this intermittent, or 100% repeatable, and does it happen for all addresses, or do some go through without incident? Please turn on debugging in Edit:Preferences:Miscellaneous. You'll get much output on the console, if that's how you run Balsa, or in ~/.xsession-errors otherwise. It may give some sign of errors that would help to pinpoint the issue. If you decide to post some output for us to diagnose, please remove or sanitize any sensitive data that may have found its way in there (passwords, obviously, but also user-ids, ip address, anything else that you wouldn't want advertised to all).
(In reply to comment #3) > Thanks! I use 2.3.28 on an f11 box, and haven't seen this problem, so I'm > puzzled :( > > Couple more requests: > > Is this intermittent, or 100% repeatable, and does it happen for all addresses, > or do some go through without incident? > > Please turn on debugging in Edit:Preferences:Miscellaneous. You'll get much > output on the console, if that's how you run Balsa, or in ~/.xsession-errors > otherwise. It may give some sign of errors that would help to pinpoint the > issue. If you decide to post some output for us to diagnose, please remove or > sanitize any sensitive data that may have found its way in there (passwords, > obviously, but also user-ids, ip address, anything else that you wouldn't want > advertised to all). Outgoing e-mail fails every time, for every address I couldn't fine .xsession-errors, but here's the sanitized terminal output for 2 messages: ****@******:~$ balsa ** Message: init gpgme version 1.1.8 ** Message: protocol OpenPGP: engine /usr/bin/gpg (home (null), version 1.4.9) ** Message: protocol CMS: engine /usr/bin/gpgsm (home (null), version (null)) ** Message: protocol (null): engine /usr/bin/gpgconf (home (null), version (null)) Local mailbox Saved loaded as: LibBalsaMailboxMaildir Local mailbox **** loaded as: LibBalsaMailboxMaildir check_local_path: path "file:///home/****/mail/Saved/*****" must_scan 0. etc. Destroying children of 0x8c18290 /home/****/mail/Saved/***** etc. bmbn_scan_children_idle: mailbox "*****" was already scanned Destroying children of 0x8c5df50 /home/****/mail/Saved/***** etc. Hspell: can't open /usr/share/hspell/hebrew.wgz.sizes. Hspell: can't open /usr/share/hspell/hebrew.wgz.sizes. ** Message: balsa_sendmsg_destroy()_handler: Start. balsa_sendmsg_destroy_handler: Freeing bsmsg ** Message: balsa_sendmsg_destroy(): Stop. Send_Message: 2985300480, 4, Hspell: can't open /usr/share/hspell/hebrew.wgz.sizes. Hspell: can't open /usr/share/hspell/hebrew.wgz.sizes. ** Message: balsa_sendmsg_destroy()_handler: Start. balsa_sendmsg_destroy_handler: Freeing bsmsg ** Message: balsa_sendmsg_destroy(): Stop. Send_Message: 147781864, 4, balsa_app: Finished cleaning up. ****@*****:~$
Thanks for the info. Unfortunately, it doesn't give any clues, at least to me! I doubt the Hspell warnings are related. Can you get access to a more recent version of Balsa? Version 2.4 has some changes in the backends.
(In reply to comment #5) > Thanks for the info. Unfortunately, it doesn't give any clues, at least to me! > I doubt the Hspell warnings are related. Can you get access to a more recent > version of Balsa? Version 2.4 has some changes in the backends. Balsa 2.3.28-1 appears to be the latest in the Ubuntu repositories. Should I check periodically for update to 2.4, or is there somewhere I should go to install 2.4?
You could build from the 2.4.1 source tarball at <URL:http://pawsa.fedorapeople.org/balsa/download.html>. You'd need to install the build tool-chain and several -devel packages. Other than that, you're at the mercy of the Ubuntu maintainer ;) You could check to see if there's an updated GMime package. Not sure what else there is.
(In reply to comment #7) > You could build from the 2.4.1 source tarball at > <URL:http://pawsa.fedorapeople.org/balsa/download.html>. You'd need to install > the build tool-chain and several -devel packages. > > Other than that, you're at the mercy of the Ubuntu maintainer ;) You could > check to see if there's an updated GMime package. Not sure what else there is. It looks like Ubuntu's maintainers have been informed of the problem. This looks like the same bug: https://bugs.launchpad.net/ubuntu/+source/balsa/+bug/474767
Allow me to step in: since I updated to Karmic Koala, I have had the same problem (it also occured on my previous computer). The error message I get from Balsa when i try to send a message is «Envoi du message avec le mode gpg 0» (“sending message with mode gpg 0 [on]“). The relevant passage in bash could be (on opening, not at send time): ** Message: init gpgme version 1.1.8 ** Message: protocol OpenPGP: engine /usr/bin/gpg (home (null), version 1.4.9) ** Message: protocol CMS: engine /usr/bin/gpgsm (home (null), version (null)) ** Message: protocol (null): engine /usr/bin/gpgconf (home (null), version 2.0.12) Trouble is, I have never asked for any gpg/gnupg/seahorse option to encrypt my messages − and i can’t even de-activate/tweak such options… Since I don’t know where to find them, on seahorse nor on balsa! My version of Balsa is 2.3.28. Old, but being not so very good at computers, I prefer to rely on whatever synaptic has in stock… Sad but safe, I’m afraid! I’d be happy to provide any of you with more information. Thanks for your help anyway. G
Thanks for the input! The "gpg" message from Balsa is not an error--mode 0 simply means neither signed nor encrypted. If you're interested, you can turn on signing or encrypting or both, either per-message through the `Options' menu on Balsa's compose window, or per-identity on the `Security' tab of the dialog that is popped up by Settings:Identities... Since this problem has been reported only by Karmic users, it seems likely that it is a packaging problem, in either the Balsa package or the GMime package. As you will have noticed, not much is going on with the Launchpad bug :(
So even the fact that this message did not appear with Jaunty is not a clue? Darn, I thought it would have been a good starting point… In any case, the solution your message suggests is that I should be so bold as to install a package… myself? Alone? All in command line on that scary black and white terminal? No but seriously, is this what you’d recommend?
If the `gpg' messages didn't appear with Jaunty, it was probably because the Jaunty package for Balsa was built without gpgme support. I would guess that it's only a coincidence that gpgme support was added in the same release that loses addresses--it's hard to see how they could be related. But yes, building Balsa (and perhaps GMime) from source would most likely give you a working version. I'm not going as far as to recommend that, as you would need a complete set of build tools and various devel packages--surely someone out there in Karmic-land has already done the work?
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org. As part of that, we are mass-closing older open tickets in bugzilla.gnome.org which have not seen updates for a longer time (resources are unfortunately quite limited so not every ticket can get handled). If you can still reproduce the situation described in this ticket in a recent and supported software version, then please follow https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines and create a new enhancement request ticket at https://gitlab.gnome.org/GNOME/balsa/-/issues/ Thank you for your understanding and your help.