Re: balsa : sending msgs impossible



Hi Bob,

On 06/12/2016 01:32:21 PM Sun, Bob Goodwin wrote:
On 06/12/16 11:31, Peter Bloomfield wrote:

Port 465 is for SSL connections, which IIRC are not supported by libesmtp, Balsa's SMTP backend. Using port 465 for 
mail also seems to be deprecated [1]. If you set Preferences => Miscellaneous => Debug and run Balsa from a 
terminal, you should see the conversation with the mail server (along with a host of other debugging 
messages)--that may help diagnose the problem.

Peter
+

[root Box10 .balsa]# balsa
** Message: init gpgme version 1.4.3
** Message: protocol OpenPGP: engine /usr/bin/gpg2 (home (null), version 2.1.11)
** Message: protocol CMS: engine /usr/bin/gpgsm (home (null), version 2.1.11)
** Message: protocol GPGCONF: engine /usr/bin/gpgconf (home (null), version 2.1.11)
** Message: protocol Assuan: engine /root/.gnupg/S.gpg-agent (home !GPG_AGENT, version 1.0)
** Message: protocol UIServer: engine /root/.gnupg/S.uiserver (home (null), version 1.0)
** Message: OpenPGP protocol supported
** Message: CMS (aka S/MIME) protocol supported
Network is available   (Sun Jun 12 13:22:22 2016)
Error creating proxy: The connection is closed (g-io-error-quark, 18)
Error creating proxy: The connection is closed (g-io-error-quark, 18)
Error creating proxy: The connection is closed (g-io-error-quark, 18)
Error creating proxy: The connection is closed (g-io-error-quark, 18)
Error creating proxy: The connection is closed (g-io-error-quark, 18)
** Message: could not retrieve the key with fingerprint 1F5FD4B5B92A74F5: GPGME: End of file
** Message: balsa_sendmsg_destroy()_handler: Start.
balsa_sendmsg_destroy_handler: Freeing bsmsg
** Message: balsa_sendmsg_destroy(): Stop.


I don't know how to interpret that?

Bob

I don't know where those proxy-related errors arise--Balsa code doesn't seem to contain any messages about 
proxies.

The key-retrieval message comes from viewing a message that's either signed or encrypted, so it shouldn't be 
related to sending.

Messages from balsa_sendmsg_destroy are related to cleaning up after placing a message in the queue to be 
sent, and I believe are quite normal. I expected to see a conversation like:

Send_Message: 139768100817456, 1, Connected to MTA
S: 220 smtp.mail.att.net ESMTP ready
C: EHLO w500
S: 250-smtp.mail.att.net
250-PIPELINING
250-SIZE 41697280
250-8 BITMIME
250 STARTTLS
C: STARTTLS
S: 220 2.0.0 Start TLS
...

after them. Did you cut it, or was "Debug" not enabled?

Peter

Attachment: pgpGjiGXjxlJp.pgp
Description: PGP signature



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]