Re: Kmail - Sending Emails Unable

--nextPart6621867.oiGErgHkdL
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"; protected-headers="v1"
From: Soren Stoutner <[email protected]>
To: [email protected]
Subject: Re: Kmail - Sending Emails Unable
Date: Mon, 26 Jan 2026 10:04:14 -0700
Message-ID: <6596188.AJdgDx1Vlc@soren-desktop>
Organization: Debian
In-Reply-To: <[email protected]>
MIME-Version: 1.0

On Monday, January 26, 2026 7:25:57=E2=80=AFAM Mountain Standard Time Sune =
Vuorela=20
wrote:
> On 2026-01-22, Patrick Franz <[email protected]> wrote:
> >> In the previous version of KMail, since the beginning of 2026, sent
> >> messages were successfully sent and received but did not appear in
> >> the Sent Items folder. I don't know what to do, especially since I've
> >> looked at the logs and I don't see anything unusual. Is there a way
> >> to trace the issue to get a starting point for a solution?
> >=20
> > I encountered the same problem. The solution was to change the port for
> > the connection from 465 to 587. Actually, kmail can fix that
> > automatically for you if you let it figure it out on its own.
>=20
> Sorry about that. There was weird 'defaults' that was actually stored as
> 'defaults' rather than the resulting value. I fixed the defaults but
> didn't expect it to has this effect.
> I don't think anything can be done at this point other than document the
> issue taht people needs to fix the connection port.
>=20
> (The default was either starttls on 465 or smtp-over-ssl on 587 which is
> a not-helpful default - I've forgotten which one it was )

The port you need depends on the settings of the email server you are=20
connecting to.  Some servers need one, some servers need the other, some=20
servers work on both, and some servers work on something else.

The autodetection option can often figure out what is needed, but if not th=
en=20
the user needs to consult the documentation from the email provider.

=2D-=20
Soren Stoutner
[email protected]
--nextPart6621867.oiGErgHkdL
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part.
Content-Transfer-Encoding: 7Bit

-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEEJKVN2yNUZnlcqOI+wufLJ66wtgMFAml3no4ACgkQwufLJ66w
tgORahAAnTw+ufqWOPp1gPfnf08/rIK3kLEjmJn0Dmyan7mMDkuHkFR/bS/B3Elt
4gKY3csBa3hN/u9Y/OXK4NIlfdB1iUbdqNrYnFs5I/xp2QgM44ndtOYOXxW6ZgFG
Uxd9JYeRcYFTaG2wZPKJFX3lsHTq/Of7MJBQrU8DwCxW7CRu0xKhbOqgASYH30nq
7PWInQX9p8QSosFi0BKW30xqB/77KqN16+GbxNOdIhS6znI7tC4NKuX/Hna1iCE+
P6AhjelpQ0P6eC/L7KIWEByZqoSUr0VkgS+a6iPoxLatLbzkjEVnFT2UXl+XDAjN
rrNt9ecchrBzuJ7b5FznblRrLARZiBkO0aIanxwDWLT5gZcbgQVu+WBx9KUfAlYl
3YGuuPJmDXHXiEgoMoTBHNPBeAnfyF4o5sDMgZMC1gkktjzoMieN9mcmGugAyKUT
rwb7ZtKyhISeIr3nn2i1CJ86DRcrIDtT/QsS3UsfNMS89SfAzgFnZgjN4GoYiks7
8zQcpU3Xgibcrl4PxnbMqteHPhP0jf3x8l78hLwfPzkGVHJy8IbpJsfQKUxR7pER
iWrYHAZLMvoK9+/xhtVhmryOv2G4rPKLiQpRchyaQPSye/eBCGKrgJX9x594+j/0
Fs87AbJNc6m1e395EcO5NDiZ7mkZtmrsquTF23C/QxGv2GWSAvY=
=7iqH
-----END PGP SIGNATURE-----

--nextPart6621867.oiGErgHkdL--