[Bug 1166499] New: kmail smtp broken with eclipso.eu provider
http://bugzilla.opensuse.org/show_bug.cgi?id=1166499 Bug ID: 1166499 Summary: kmail smtp broken with eclipso.eu provider Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: x86-64 OS: Linux Status: NEW Severity: Normal Priority: P5 - None Component: KDE Applications Assignee: opensuse-kde-bugs@opensuse.org Reporter: stakanov@freenet.de QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- With the stock version of the Kmail: with eclipso.eu provider it is impossible to send smtp messages to provider. What fails is authentication. The normal settings (which work on TW) are: whatevermail@eclipso.eu server: mail@eclipso.de smtp server: mail.eclipso.de 587 Plain With these settings TW does send problem free. But with Leap since about two days if fails no matter what with "Server error, incorrect authentication data" The very settings do work w.o. problem on the TW version of kmail. I have the doubt it might have been some openssl update or similar that may have caused this. I have not found a way to document the exchange between kmail and the server. So if you know how to do this, I am taker. Thank you. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1166499 http://bugzilla.opensuse.org/show_bug.cgi?id=1166499#c1 Wolfgang Bauer <wbauer@tmo.at> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |wbauer@tmo.at --- Comment #1 from Wolfgang Bauer <wbauer@tmo.at> --- Could you try to find out which update caused this? There wasn't really a change to the KDE packages in Leap 15.1 that might have broke it... -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1166499 http://bugzilla.opensuse.org/show_bug.cgi?id=1166499#c2 --- Comment #2 from Wolfgang Bauer <wbauer@tmo.at> --- PS: there was an update to libgcrypt 3 days ago. Does it maybe help if you reinstall the older version? E.g. Open YaST->Software Management, search for the package (libgcrypt20 in this case), and click on the "Versions" tab to install the previous version. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1166499 http://bugzilla.opensuse.org/show_bug.cgi?id=1166499#c3 Stakanov Schufter <stakanov@freenet.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(wbauer@tmo.at) --- Comment #3 from Stakanov Schufter <stakanov@freenet.de> --- (In reply to Wolfgang Bauer from comment #2)
PS: there was an update to libgcrypt 3 days ago. Does it maybe help if you reinstall the older version?
E.g. Open YaST->Software Management, search for the package (libgcrypt20 in this case), and click on the "Versions" tab to install the previous version.
Yes, this does restore functionality. However, there is a problem with this provider as it seems. I have the same also with 15.2 beta (but the sending works and the reception fails). I suppose 15.2 beta and current 15.1 share the same library? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1166499 http://bugzilla.opensuse.org/show_bug.cgi?id=1166499#c4 Wolfgang Bauer <wbauer@tmo.at> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|KDE Applications |Basesystem Assignee|opensuse-kde-bugs@opensuse. |screening-team-bugs@suse.de |org | --- Comment #4 from Wolfgang Bauer <wbauer@tmo.at> --- (In reply to Stakanov Schufter from comment #3)
(In reply to Wolfgang Bauer from comment #2)
PS: there was an update to libgcrypt 3 days ago. Does it maybe help if you reinstall the older version?
E.g. Open YaST->Software Management, search for the package (libgcrypt20 in this case), and click on the "Versions" tab to install the previous version.
Yes, this does restore functionality. So it is actually a problem in libgcrypt it seems, reassigning.
However, there is a problem with this provider as it seems. I have the same also with 15.2 beta (but the sending works and the reception fails). I suppose 15.2 beta and current 15.1 share the same library? I assume this is the case, yes. Or at least they share the same bug.
-- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1166499 Wolfgang Bauer <wbauer@tmo.at> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|screening-team-bugs@suse.de |pmonrealgonzalez@suse.com -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1166499 Wolfgang Bauer <wbauer@tmo.at> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(wbauer@tmo.at) | -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1166499 http://bugzilla.opensuse.org/show_bug.cgi?id=1166499#c5 Stakanov Schufter <stakanov@freenet.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CONFIRMED --- Comment #5 from Stakanov Schufter <stakanov@freenet.de> --- I am having constant troubles with smtp on this provider. I tried to drop back with the library, worked for some time now again: Synchronization error 5.5.1 https://www.experts-exchange.com/questions/26432981/Mail-Flow-Issue-503-5-5-... Here you find more or less exactly this issue. Did we patch recently something in postfix? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1166499 http://bugzilla.opensuse.org/show_bug.cgi?id=1166499#c6 Stakanov Schufter <stakanov@freenet.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #6 from Stakanov Schufter <stakanov@freenet.de> --- I am closing this for now. As it turns out the issue seams to be on the provider side. If this should present itself again though, I might be forced to reopen it. Sorry for the noise. Closing as invalid for now. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com