Bug 194451

Summary: upgrade to 2.6.2 changes POP settings
Product: [Fedora] Fedora Reporter: Armijn Hemel <armijn>
Component: evolutionAssignee: Matthew Barnes <mbarnes>
Status: CLOSED INSUFFICIENT_DATA QA Contact:
Severity: high Docs Contact:
Priority: medium    
Version: 5CC: mcepl, mcepl
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-10-02 17:44:15 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Armijn Hemel 2006-06-08 10:02:16 UTC
Description of problem:

After the upgrade to Evolution 2.6.2 on my home machine the settings for the POP
accounts was changed by the upgrade to use TLS, even if the POP accounts were
not using any encryption.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. have a POP account without encryption
2. update evolution to 2.6.2
3.
  
Actual results:

POP suddenly uses TLS.

Expected results:

Nothing, evolution shouldn't have changed those settings.
Additional info:

Comment 1 Armijn Hemel 2006-06-08 10:16:01 UTC
Note, also sending mail via SMTP uses TLS now, even if it was configured not to
use TLS before. Bumping to severity=high.

Comment 2 Matthew Barnes 2007-01-01 21:53:49 UTC
Apologies for taking so long to respond.

Have you encountered this problem again in subsequent updates to Evolution?

Comment 3 Armijn Hemel 2007-03-06 00:13:03 UTC
Well, I configured everything correctly now, but I think it still defaults to
using TLS.

Comment 4 Matěj Cepl 2007-08-31 15:21:03 UTC
The distribution against which this bug was reported is no longer supported,
could you please reproduce this with the updated version of the currently
supported distribution (Fedora Core 6, or Fedora 7, or Rawhide)? If this issue
turns out to still be reproducible, please let us know in this bug report.  If
after a month's time we have not heard back from you, we will have to close this
bug as INSUFFICIENT_DATA.

Setting status to NEEDINFO, and awaiting information from the reporter.

Thanks in advance.

Comment 5 Matthew Barnes 2007-10-02 17:44:15 UTC
Closing as INSUFFICIENT_DATA.