Bug 313993 - Mail sending problem using SMTP
Summary: Mail sending problem using SMTP
Status: RESOLVED WORKSFORME
Alias: None
Product: kmail2
Classification: Applications
Component: commands and actions (show other bugs)
Version: 4.9.4
Platform: Ubuntu Linux
: NOR major
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2013-01-27 19:13 UTC by Pavel Punegov
Modified: 2018-10-27 04:00 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Pavel Punegov 2013-01-27 19:13:28 UTC
Unable to send e-mail using SMTP account. KMail2 says "An error occurred during authentication: SASL(0): successful result:"

Tried to use both SSL and TLS with and without authentication enabled, with different authentication types, but nothing helped.
I'am using Gmail and corporate mail accounts, both don't sent e-mails. They use different settings: TLS for gmail, corporate uses SSL.

KMail2 was able to send mails on 4.9.0.

Reproducibility - always, logout/login does not help, system restart too.

Reproducible: Always

Steps to Reproduce:
1. Add SMTP account
2. Set settings using "Auto detect" button 
3. Write mail and try to send it.
Comment 1 Pavel Punegov 2013-01-27 19:14:50 UTC
I think that it may be the same problem as described in 284787
Comment 2 Pavel Punegov 2013-01-27 19:20:33 UTC
Here is  kmail errors from .xsession-errors:

$ grep kmail .xsession-errors | uniq
"/usr/bin/kmail(6214)" Soprano: "Could not connect to server at /tmp/ksocket-pavel/nepomuk-socket (ÐÐµÑ Ñакого Ñайла или каÑалога)"
"/usr/bin/kmail(6214)" Soprano: "Unsupported operation (2)": "Invalid model"
"/usr/bin/kmail(6214)" Soprano: "Invalid iterator."
"/usr/bin/kmail(6214)" Soprano: "Could not connect to server at /tmp/ksocket-pavel/nepomuk-socket (ÐÐµÑ Ñакого Ñайла или каÑалога)"
"/usr/bin/kmail(6214)" Soprano: "Unsupported operation (2)": "Invalid model"
"/usr/bin/kmail(6214)" Soprano: "Invalid iterator."
"/usr/bin/kmail(6214)" Soprano: "Could not connect to server at /tmp/ksocket-pavel/nepomuk-socket (ÐÐµÑ Ñакого Ñайла или каÑалога)"
"/usr/bin/kmail(6214)" Soprano: "Unsupported operation (2)": "Invalid model"
"/usr/bin/kmail(6214)" Soprano: "Invalid iterator."
"/usr/bin/kmail(6214)" Soprano: "Could not connect to server at /tmp/ksocket-pavel/nepomuk-socket (ÐÐµÑ Ñакого Ñайла или каÑалога)"
"/usr/bin/kmail(6214)" Soprano: "Unsupported operation (2)": "Invalid model"
"/usr/bin/kmail(6214)" Soprano: "Invalid iterator."
kmail2(6214)/kdepimlibs (mailtransport) MailTransport::SendQueuedAction::itemAccepted: Item doesn't have DispatchModeAttribute. 
kmail2(6214)/kdeui (KWindowInfo) KWindowInfo::state: Pass NET::WMState to KWindowInfo 
kmail2(6214) MessageViewer::Util::fileNameForMimetype: unknown mimetype "application/x-sh" 
kmail2(6214) MessageList::Core::ModelInvariantRowMapperPrivate::modelIndexRowToModelInvariantIndexInternal: Requested invariant for storage row index  987  not found in history 
kmail2(6214)/kdeui (KWindowInfo) KWindowInfo::state: Pass NET::WMState to KWindowInfo 
kmail2(6214) MessageViewer::Util::fileNameForMimetype: unknown mimetype "application/ics" 
kmail2(6214)/kdepimlibs (mailtransport) MailTransport::Transport::updatePasswordState: Tried to update password state of non-cloned transport. 
kmail2(6214)/libkleo QGpgMECryptoConfigComponent::runGpgConf: Running 'gpgconf --list-options "dirmngr" ' failed. ÐпеÑаÑÐ¸Ñ Ð½Ðµ позволÑеÑÑÑ , but try that command to see the real output 
kmail2(6214) SMIMECryptoConfigEntries::configEntry: "Backend error: gpgconf doesn't seem to know the entry for dirmngr/OCSP/allow-ocsp" 
kmail2(6214) SMIMECryptoConfigEntries::configEntry: "Backend error: gpgconf doesn't seem to know the entry for dirmngr/OCSP/ignore-ocsp-service-url" 
kmail2(6214) SMIMECryptoConfigEntries::configEntry: "Backend error: gpgconf doesn't seem to know the entry for dirmngr/HTTP/ignore-http-dp" 
kmail2(6214) SMIMECryptoConfigEntries::configEntry: "Backend error: gpgconf doesn't seem to know the entry for dirmngr/HTTP/disable-http" 
kmail2(6214) SMIMECryptoConfigEntries::configEntry: "Backend error: gpgconf doesn't seem to know the entry for dirmngr/HTTP/honor-http-proxy" 
kmail2(6214) SMIMECryptoConfigEntries::configEntry: "Backend error: gpgconf doesn't seem to know the entry for dirmngr/LDAP/ignore-ldap-dp" 
kmail2(6214) SMIMECryptoConfigEntries::configEntry: "Backend error: gpgconf doesn't seem to know the entry for dirmngr/LDAP/disable-ldap" 
kmail2(6214) SMIMECryptoConfigEntries::configEntry: "Backend error: gpgconf doesn't seem to know the entry for dirmngr/OCSP/ocsp-responder" 
kmail2(6214) SMIMECryptoConfigEntries::configEntry: "Backend error: gpgconf doesn't seem to know the entry for dirmngr/OCSP/ocsp-signer" 
kmail2(6214) SMIMECryptoConfigEntries::configEntry: "Backend error: gpgconf doesn't seem to know the entry for dirmngr/HTTP/http-proxy" 
kmail2(6214) SMIMECryptoConfigEntries::configEntry: "Backend error: gpgconf doesn't seem to know the entry for dirmngr/LDAP/ldap-proxy" 
kmail2(6214)/kdepimlibs (mailtransport) MailTransport::Transport::updatePasswordState: Tried to update password state of non-cloned transport. 
** (kmail:6214): WARNING **: 2 dictionaries weren't free'd.
kmail2(4160)/kdepimlibs (mailtransport) MailTransport::Transport::updatePasswordState: Tried to update password state of non-cloned transport.
Comment 3 Martin Steigerwald 2015-09-08 19:52:47 UTC
Pavel, thanks for your report. Does it still happen for you with a recent version of KDEPIM? If so please state the version of KDEPIM/Kmail, Akonadi you use and provide a new ~/.xsession-errors snippet. Thanks, Martin
Comment 4 Andrew Crouthamel 2018-09-25 21:43:13 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Andrew Crouthamel 2018-10-27 04:00:20 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!