Re: Balsa 2.5.6-1:Cannot initialize GSS security context

Albrecht Dreß <[email protected]>
Newsgroups gmane.comp.gnome.apps.balsa
Message-ID <[email protected]>
Hi John Jack Doe:

Am 15.12.18 13:15 schrieb(en) [email protected]:
> I am using balsa git version 2.5.3a-144-g8d6ac09 on my old 32 bit machine and it works perfectly with the Microsoft server. As a temporary workaround I compose emails for the business account of my employer on my new 64 bit machine, and copy the mail file to my 32 bit old machine for sending.

Just to clarify the place where I should start digging: on your /old/ machine, do you authenticate to the SMTP server using
(a) GSS = Kerberos, i.e. you have to say (in a terminal) something like “kinit <username>” before opening Balsa, and (again in a terminal) “klist” reports a valid ticket?  Or
(b) did you build Balsa yourself, presumably without GSS support, and you authenticate with username and password?

If (b) is your config on the old machine, the quick fix would be building the latest GIT version on your new box, but *without* GSS support (add “--with-gss=no” to the configure options).  I will provide a fix asap which falls back from gss to username + password auth if the former fails.

Best,
Albrecht.

_______________________________________________
balsa-list mailing list
[email protected]
https://mail.gnome.org/mailman/listinfo/balsa-list
signature.asc (application/pgp-signature, 488 B)
-----BEGIN PGP SIGNATURE-----

iQEzBAABCgAdFiEEcCEPemLFTtyGf4zATKlvDmfn2fgFAlwXhDkACgkQTKlvDmfn
2fgxUAf8COt9pFm11eYmzsKdHzGm3X9Z8CuxHcTBb8m852ngO+3pkqPj4PkQfDiO
b1xn9uoWkUexqxp+MCRPsmNls1pqZPNIOu0TRfv/cYl54DulivXBWE5vrq+SfIw3
egexkSVM8xLevH9yf6MFXpd3Tb5LylAZx6u/0J+oOvqDTLQOR4+IBdpA8Kz0GVZB
UBvLDQYgCADC7VCjQlhnq35rp42asIInW6U2Rutl3XCsMBCkhmCt9tHwYKrOTp8k
2cxj2XVn+sNStvpZ3tkCRGNAlQSKrZ84glxy3BcmQLsfc/C0YpBALvvq3qZVeRlz
kDgzr+H8wRvPBy3asfVuSDB3nFD4mw==
=rEXp
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.