Could you list the exact steps you followed so that we can reproduce this bug?

Steps to Reproduce:
1. formating "/" and "/home"
2. installing from DVD - selction KDE
3. urpmi evolution
4. starting evolution
5. configuring the IMAP - account from t-online.de
Posteingangsserver           secureimap.t-online.de (Port 993)               
Postausgangsserver          securesmtp.t-online.de (Port 465)
(Evolution has no pre-configuration for well-known e-mail provider ;) )
6. pressing [OK] Evol. starts polling IMAP from t-online.de, without asking me the e-mail password. (...and no question: "would you like to use kwalletmanager??)
7. Then "timeout" comes as message
8. If you open "Bearbeiten - Einstallung - Abrufen von E-Mails" you can see
   -- secureimap.t-online.de (Port 143) --
I cant' change it to port 993 :(

starting evolution from konsole brings following error:

(evolution:12946): evolution-mail-WARNING **: report_error_to_ui_cb: mail:failed-connect 'malatte@web.de': TLS support is not available

account setting in evolution are 'SSL on dedicated port' (selected port: 993). Same is true for gmail account, so not provider related issue. 

Same settings are working in evolution-3.10.2-1 in mga4. After upgrading the VM to mga5 evolution shows the same error.

CC: (none) => marc.lattemann

@Jürgen: It would help if you would at least read https://wiki.mageia.org/de/Wie_ein_Fehler_berichtet_wird#Prinzipien where it says clearly [translated] "Please always prefix calls to programs with LC_ALL=C so that error messages or other output will be shown in English" if you report bugs.


FWIW regarding changing the port between 143 and 993, that is done automatically when choosing either "STARTTLS after connecting" or "SSL on a dedicated port" as encryption method.
But using either encryption method results in an error, only "No encryption" seems to work, at least to query the servers supported authentication types. Also the error messages differ:


- for STARTTLS after connecting:
Failed to query server for a list of supported authentication mechanisms.
Failed to connect to IMAP server imap.arcor.de in secure mode: TLS support is not available


- for SSL on a dedicated port
Failed to query server for a list of supported authentication mechanisms.
TLS support is not available

----

Maybe the patch from https://bugzilla.redhat.com/show_bug.cgi?id=1153052 that fixed bug 14425 was never properly integrated upstream after 3.10 ... I don't see any mentions of TLS in the changelog https://github.com/GNOME/evolution-data-server/commits/master/NEWS since 3.10.


Or it's really because we use a development snapshot - maybe Olav should upgrade it to stable 3.16 (he has already commited some newer snapshots in SVN up to 3.15.92, from which it's only a small step to 3.16).
steps: 3.13.90 => 3.15.91 => 3.15.92 => 3.16.0


Would also be helpful if somebody could try to reproduce this with e.g. Fedora 21 (3.12.11) or Fedora 22 (3.16). Or maybe openSUSE Factory & 13.2, they have also similar versions compared to Fedora.

Tried LiveDVD of Fedora 22-beta and no setup of imap server needed. Sync with gmail-server works without problems.

[liveuser@localhost ~]$ rpm -qa | grep evolution
evolution-3.16.0-1.fc22.x86_64
evolution-data-server-3.16.0-1.fc22.x86_64
evolution-help-3.16.0-1.fc22.noarch
evolution-ews-3.16.0-1.fc22.x86_64

maybe it is the development version which causes issues

Please install one of the following:
- lib64glib-networking (64bit machine)
- libglib-networking (32bit machine)

and report back please

Keywords: (none) => NEEDINFO

Installation of lib64glib-networking fixes the problem on a 64bit machine

So I'm wondering if this should be a release blocker. I'm setting as such. Feel free to change back.

There's several parts involved to solve this properly:
1. By default those libglib-networking packages should be installed by default
2. Glib should Recommend those packages
3. Evolution should require that package

In detail:
1. Adds this to rpmsrate-raw. However, the package name differs between 32bit and 64bit. Not sure how to do that :-(

2. I've added this, have to ask for a freeze break push

3. Unfortunately Evolution in SVN is way ahead of Cauldron. This as the package couldn't be build (build problems). So I cannot just ask for freeze break as it would be more than just adding a "Requires". I guess I should revert back to Cauldron and then add it.

Keywords: NEEDINFO => (none)
Priority: High => release_blocker

Removing release blocker tag as it can be fixed through update

CC: (none) => ennael1

Anne, Evolution is inside LiveCD and classical media

Manuel, but it won't break the install. Maybe this is something for the Errata, since there is an easy workaround to perform after the installation by manually install the missing package?

I'll make an updated Evolution package for Mageia 5. It should be easier because they should branch the latest released SPEC.

(In reply to Olav Vitters from comment #12)
> I'll make an updated Evolution package for Mageia 5. It should be easier
> because they should branch the latest released SPEC.

Please also write something in the Errata.

Added in errata for Mageia 5:
https://wiki.mageia.org/en/Mageia_5_Errata#Evolution
IMAP accounts can not be configured, because Evolution does not ask for password 15971. A workaround is to install either:

    lib64glib-networking (64bit machine) or
    libglib-networking (32bit machine).

CC: (none) => yves.brungard_mageia
Whiteboard: MGA5TOO FOR_ERRATA => MGA5TOO IN_ERRATA

(In reply to papoteur from comment #14)
> Added in errata for Mageia 5:
> https://wiki.mageia.org/en/Mageia_5_Errata#Evolution
> IMAP accounts can not be configured, because Evolution does not ask for
> password 15971. A workaround is to install either:
> 
>     lib64glib-networking (64bit machine) or
>     libglib-networking (32bit machine).

I've corrected the errata. The problem is accounts with SSL/TLS. IMAP is not the issue.

Thanks Olav.

Fixed in Cauldron SVN. Having build issues there.

I have uploaded a patched/updated package for Mageia 5.

You can test this by installing the package and setting an account with SSL/TLS options.

Suggested advisory:
========================

Updated Evolution packages fix bug:

In Evolution, users could not set or change SSL/TLS email account options due to a missing dependency.

References:
https://bugs.mageia.org/show_bug.cgi?id=15971
========================

Updated packages in core/updates_testing:
========================
Wrote: /home/iurt/rpmbuild/RPMS/i586/evolution-3.13.90-1.1.mga5.i586.rpm
Wrote: /home/iurt/rpmbuild/RPMS/i586/evolution-devel-3.13.90-1.1.mga5.i586.rpm
Wrote: /home/iurt/rpmbuild/RPMS/i586/evolution-debuginfo-3.13.90-1.1.mga5.i586.rpm

Source RPMs: 
evolution-3.13.90-1.1.mga5.src.rpm

Assignee: olav => qa-bugs

QA: We've managed to build 3.16.3 (which is stable version of 3.13.90; there was no 3.14.x version) on Cauldron. I'm going to ask on dev@ if I can submit that as update for Mageia 5.

CC: (none) => olav

Testing started with Evolution 3.13.90 running on KDE out of Mageia 5 general release (64bit).

Testing procedure:

- Logged into gmail directly and created a new account, vzawalin2@gmail.com, specifying a password different from any other gmail account of mine. Enabled IMAP

- Sent an email using Firefox from vzawalin1@gmail.com to vzawalin2@gmail.com.

- Created an account in evolution for vzawalin2@gmail.com, *not* specifying a password.

- Exited configuration and restarted evolution. I was immediately asked for the password to vzawalin2@gmail.com. Took a screen shot.

So, I have not been able to replicate this bug.  Have I missed something?

CC: (none) => vzawalin1

Re comment 20:

I am unable to reproduce this bug with version 3.13.90 with existing updates (not updates-testing) repositories.  Does anyone object to my whiteboarding this as OK/64?

Advisory committed to svn.

CC: (none) => davidwhodgins
Whiteboard: IN_ERRATA => IN_ERRATA advisory

Does this still need a QA run?

CC: (none) => brtians1

(In reply to Vladimir Zawalinski from comment #21)
> Re comment 20:
> 
> I am unable to reproduce this bug with version 3.13.90 with existing updates
> (not updates-testing) repositories.  Does anyone object to my whiteboarding
> this as OK/64?

That's probably because you already had the missing dependency. I've checked the RPMs and the dependency has been added as expected. Since the program works for you, and based on the RPM diffs I checked, I'm validating this simple update.

Keywords: (none) => validated_update
Whiteboard: IN_ERRATA advisory => IN_ERRATA advisory MGA5-64-OK
CC: (none) => sysadmin-bugs

An update for this issue has been pushed to Mageia Updates repository.

http://advisories.mageia.org/MGAA-2015-0069.html

Status: NEW => RESOLVED
Resolution: (none) => FIXED