Strange. I use v3.5.13.1 (now preliminary 3.5.13.2) on Debian Squeeze, I use KMail and SMTP for sending mails and have not noticed any problems.

Is there any information written in .xsession-errors?

(In reply to comment #1)
> Strange. I use v3.5.13.1 (now preliminary 3.5.13.2) on Debian Squeeze, I use
> KMail and SMTP for sending mails and have not noticed any problems.
> 
> Is there any information written in .xsession-errors?

Lots. However, there isn't much pertaining to Kmail. Almost all pertaining to HAL and K3b (I've been burning lots of CDs).

I did manage to get some stuff at the tail end after restarting Kmail, running a mail sync via IMAP, then 'attempting' to send my queued messages. I will attach the tail end (the part AFTER the K3b/HAL messages, when I ran Kmail).

Created attachment 1076 [details]
snippet from my .xsession-errors file, pertaining to the Kmail issue.

Is this problem still valid? The "Could not load library! Trying exec...." stdout messages were updated some time back to a different text so at to not look like an error message. I'm using KMail from GIT and only use POP3/SMTP and don't have any problems.

(In reply to comment #4)
> Is this problem still valid? The "Could not load library! Trying exec...."
> stdout messages were updated some time back to a different text so at to not
> look like an error message. I'm using KMail from GIT and only use POP3/SMTP and
> don't have any problems.

Yes, it's valid. It is occurring on the nightlies for Debian Squeeze, has been for quite some time.

To confirm it still happening, I just tried sending a message, and I did a dist-upgrade this morning (so the latest nightlies are installed). It still doesn't recognize SMTP as a protocol.

It may sound silly, but do you really have the KIO for SMTP installed ?
Check that file /opt/trinity/lib64/trinity/kio_smtp.so exists.

If not, you must install it. I think the package is called "tdepim-kio-pim-plugins" or something similar.

Note: On debian and ubuntu is path /opt/trinity/lib/trinity/kio_smtp.so and package kdebase-kio-plugins-trinity. Package kmail-trinity has it as a dependency, so I suppose that is definitely present.

The KIO (TIO?) packages pertaining to tdepim are definitely installed (they show every time dist-upgrade pulls in the nightlies), however I am not home right now, so I will have to check the files later.

I have just confirmed this bug on the Arch Linux using the 3.5.13 repo mentioned on their wiki. I am therefor changing the platform from Debian Squeeze to All. Note that my Debian Squeeze machine is running the R14 nightlies provided by Tim's quickbuild server.

The file mentioned by Slavek exists on the Arch install. I will check the Debian install later when I have a chance to site down for awhile.

(In reply to comment #7)
> Note: On debian and ubuntu is path /opt/trinity/lib/trinity/kio_smtp.so and
> package kdebase-kio-plugins-trinity. Package kmail-trinity has it as a
> dependency, so I suppose that is definitely present.

That file does not exist on my Debian Squeeze system, however I do have a /opt/trinity/lib/trinity/tdeio_smtp.so . It's possible that Kmail wasn't updated to use the renamed file.

This bug is confirmed on CentOS using 3.5.13.1, however neither kio_smtp nor tdeio_smtp is present. This case may simply be an issue in the spec files used to create the RPMs.

It's working here, Centos 6.4 with TDE 3.5.13.1.

You must install package "trinity-tdebase-kio-pim-plugins" for SMTP support in KmailL

(In reply to comment #12)
> It's working here, Centos 6.4 with TDE 3.5.13.1.
> 
> You must install package "trinity-tdebase-kio-pim-plugins" for SMTP support in
> KmailL

That package is already installed. Running 'yum reinstall trinity-tdebase-kio-pim-plugins' does succeed, however it does not fix this issue. Also, doing 'ls -a /opt/trinity/lib64/ | grep smtp' does not show any files whatsoever.

If it is not already, trinity-tdebase-kio-pim-plugins

(In reply to comment #13)
> (In reply to comment #12)
> > It's working here, Centos 6.4 with TDE 3.5.13.1.
> > 
> > You must install package "trinity-tdebase-kio-pim-plugins" for SMTP support in
> > KmailL
> 
> That package is already installed. Running 'yum reinstall
> trinity-tdebase-kio-pim-plugins' does succeed, however it does not fix this
> issue. Also, doing 'ls -a /opt/trinity/lib64/ | grep smtp' does not show any
> files whatsoever.
> 
> If it is not already, trinity-tdebase-kio-pim-plugins

To complete my sentence (stupid touchpad!), it should be a dependency of trinity-tdepim.

Of course you won't find the file under /opt/trinity/lib64, because it is located under /opt/trinity/lib64/trinity .

$ ls -l /opt/trinity/lib64/trinity/*smtp*
-rw-r--r-- 1 root root    746 juin   3 21:07 /opt/trinity/lib64/trinity/kio_smtp.la
-rwxr-xr-x 1 root root 144304 juin   3 21:09 /opt/trinity/lib64/trinity/kio_smtp.so


And yes, I've already added the tdebase-kio-pim-plugins as dependency for kmail in TDE 3.5.13.2 .

I've just installed a new virtual machine with Centos 6.4, TDE 3.5.13.1, and I can send and receive mail with kmail using SMTP and IMAP.

I don't think your problem is related to SMTP protocol itself.
Are you using SSL or TLS ? Is kmail configured correctly for the SMTP server you are using (look at the security related options) ?

(In reply to comment #15)
> Of course you won't find the file under /opt/trinity/lib64, because it is
> located under /opt/trinity/lib64/trinity .
> 
> $ ls -l /opt/trinity/lib64/trinity/*smtp*
> -rw-r--r-- 1 root root    746 juin   3 21:07
> /opt/trinity/lib64/trinity/kio_smtp.la
> -rwxr-xr-x 1 root root 144304 juin   3 21:09
> /opt/trinity/lib64/trinity/kio_smtp.so
> 
> 
> And yes, I've already added the tdebase-kio-pim-plugins as dependency for kmail
> in TDE 3.5.13.2 .
> 
> I've just installed a new virtual machine with Centos 6.4, TDE 3.5.13.1, and I
> can send and receive mail with kmail using SMTP and IMAP.
> 
> I don't think your problem is related to SMTP protocol itself.
> Are you using SSL or TLS ? Is kmail configured correctly for the SMTP server
> you are using (look at the security related options) ?

I am certain that my settings are correct. They are exactly the same as the settings I used in 3.5.12 and 3.5.13 (the pre-SRU version), and they worked back then. I have even compared them to the settings Google says to use for GMail, and it matches up.

I tried deleting both the IMAP and SMTP accounts I am trying to send from, then re-added them. Immediately prior, I tried sending emails and got unrecognized protocol message. After, it sends without issue. Both attempts were the *same exact* settings, so I know for fact that the settings are not the issue.

This may be influenced by bug #1571. I suggest this because, in Composer, I enabled View -> Mail Transport to find that it was attempting to use a Mail Transport called Gmail, the default name assigned to my IMAP and SMTP accounts by the Kmail setup wizard, however I had renamed both. Renaming meant that Gmail was no longer a valid mail transport.

I did a Google search for this issue, and it has existed since before TDE. In fact, there's a bug report in the official KDE bug tracker from 2003 on Slackware:

https://bugs.kde.org/show_bug.cgi?id=53448

That is now three confirmed distros where this issue occurs: Slackware, Debian, and CentOS, across several different versions of KDE/TDE ranging from KDE 3.0.5 to TDE R14. I even saw forum posts for other distros where people reported this issue, so I can now confirm it isn't just me experiencing this.

(In reply to comment #17)
> I tried deleting both the IMAP and SMTP accounts I am trying to send from, then
> re-added them. Immediately prior, I tried sending emails and got unrecognized
> protocol message. After, it sends without issue. Both attempts were the *same
> exact* settings, so I know for fact that the settings are not the issue.
> 
> This may be influenced by bug #1571. I suggest this because, in Composer, I
> enabled View -> Mail Transport to find that it was attempting to use a Mail
> Transport called Gmail, the default name assigned to my IMAP and SMTP accounts
> by the Kmail setup wizard, however I had renamed both. Renaming meant that
> Gmail was no longer a valid mail transport.
<snip>

The incorrect mail transport was prior to deleting/re-adding the accounts. It now lists the correct one.

I just confirmed that this is the caused: I renamed my SMTP account and tried sending an email. It still listed the original name of the SMTP account as the Mail Transport and it told me it came up with the unrecognized transport protocol error. I renamed the SMTP account back to the original name, then told it to send the email that had just failed, and it went through without any issue.

As far as I can see, this is resolved in R14 (though I haven't tested as thoroughly as in comments 17 and 18). I am wandering if this bug is still valid, and if so, what info is needed to get it resolved.

(In reply to Kristopher from comment #19)
> As far as I can see, this is resolved in R14 (though I haven't tested as
> thoroughly as in comments 17 and 18). I am wandering if this bug is still
> valid, and if so, what info is needed to get it resolved.

Marking as such.  If components of the report are noticed in R14 at a later date please reopen this report.

Thanks for reporting!