Bug 759695

Summary:	"Receiving Email" port setting ignored during creation of new IMAP+ account
Product:	[Fedora] Fedora	Reporter:	Gabriel <gbauman>
Component:	evolution	Assignee:	Matthew Barnes <mbarnes>
Status:	CLOSED WORKSFORME	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	16	CC:	lucilanga, mbarnes, mcrha
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-12-05 19:52:33 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Gabriel 2011-12-03 06:55:42 UTC

When I create a new IMAP+ account and specify a custom IMAP server port, my setting is ignored and the account is created with the port set to 143. This happens every time I add a new IMAP+ account.

If I go in via account preferences after the fact and change the port again, the setting sticks.

Name        : evolution
Arch        : x86_64
Version     : 3.2.2
Release     : 1.fc16
Repo        : installed
From repo   : updates

How reproducible:

Create a new IMAP account using IMAP+. Set the port to "666". Finish creating the account. Open Evolution Preferences, select just created account, look at port number - it's 143.

Comment 1 Milan Crha 2011-12-05 10:40:33 UTC

Thanks for a bug report. I tried to, but I'm not able to reproduce this.
What I did:
 - Edit->Preferences->Mail Accounts->Add
 - Continue
 - file email address as "a@b"
 - Continue
 - set server type to IMAP+
 - set Server to "aaa.aa"
 - set Port to "666"
 - set Username to "aa"
 - Continue
 - Continue
 - set Server type to "sendmail"
 - Continue
 - Continue
 - Apply
 - Edit newly added account, observer Port in receiving being 666

I can also change order of Username and Port setting, but it does not change the result. I tried also with SMTP type, by setting only server name, but still no luck. I'm wondering whether this is related to an upstream bug [1], as some changes were done there for 3.2.3.

[1] https://bugzilla.gnome.org/show_bug.cgi?id=662789

Comment 2 Gabriel 2011-12-05 19:52:33 UTC

Well, I'll be darned. I replicated this about three times before posting the bug, and now I can't make it happen any more. Version has not been bumped.

I'm closing this WORKSFORME for the moment and will re-open if I encounter the problem again. Sorry for the spam.

Comment 3 Milan Crha 2011-12-06 08:01:11 UTC

No problem. I'm afraid there are very specific steps how to reproduce this, and I was unable to repeat them for some reason.