After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 626420 - No more option to change "keep-on-server" option from evolution to e-d-s
No more option to change "keep-on-server" option from evolution to e-d-s
Status: RESOLVED OBSOLETE
Product: evolution
Classification: Applications
Component: Mailer
2.32.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
evolution[autoconfig]
Depends on:
Blocks:
 
 
Reported: 2010-08-09 10:37 UTC by Didier Roche
Modified: 2013-09-13 01:03 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Didier Roche 2010-08-09 10:37:13 UTC
In the evolution express branch, easy account configuration do not leave anymore a way to "keep email on server" for POP account. (even with email servers which aren't in auto-config dir or where it's not set).                                                                                                                                                                                         

This part of evo express has been merged in 2.31, and so, new evo trunk suffers from the same issue as well.

The option in normally labeled "Leave Messages on Server", under "Receiving Options" for any POP account.

PS: filing against "Shell" component as there is no account capplet one.
Comment 1 Srinivasa Ragavan 2010-08-12 03:02:18 UTC
Just realized that we don't have ways to set up detailed options during create. But You can edit account. I see this option while I edit an account. Can you check up ?
Comment 2 Didier Roche 2010-08-12 06:52:40 UTC
Thanks for your answer

Hum, as said on my bug report, I'm using the evo express branch, which is based on 2.30 right? And here, I don't see any "Leave Messages on Server" option in the edit account.

Is this something fixed in 2.31 so? (I tried to look at a commit fixing it, without any success).
Comment 3 Srinivasa Ragavan 2010-08-12 06:58:30 UTC
I see this in the master branch. Possible that itz merged post 2.30.
Comment 4 Didier Roche 2010-10-07 12:14:21 UTC
Ok, I backported the change from 2.32 to 2.30, was due to the configuration branch of evo express.

Thanks a lot!