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 555496 - Evolution Mail and Calendar: Evolution was not workin...
Evolution Mail and Calendar: Evolution was not workin...
Status: RESOLVED DUPLICATE of bug 578429
Product: evolution
Classification: Applications
Component: BugBuddyBugs
2.22.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Evolution was not working with proxy
Depends on:
Blocks:
 
 
Reported: 2008-10-08 05:29 UTC by baluvbk2000
Modified: 2010-03-31 07:03 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24


Description baluvbk2000 2008-10-08 05:29:49 UTC 
Evolution was not working with proxy

Error while performing operation.

Host lookup failed: smtp.gmail.com: Name or service not known


Distribution: openSUSE 11.0 (X86-64)
Gnome Release: 2.22.1 2008-06-07 (SUSE)
BugBuddy Version: 2.22.0
Comment 1 Akhil Laddha 2008-10-10 08:13:56 UTC 
Ccan you please try 2.24.0, it has network proxy support
Comment 2 Akhil Laddha 2008-11-24 03:12:15 UTC 
Closing this bug report as no further information has been provided. Please
feel free to reopen this bug if you can provide the information asked for.
Thanks!
Comment 3 baluvbk2000 2009-03-24 08:17:08 UTC 
The same error is coming in Evolution 2.24.1.1 even after setting proxy in network configuration.
Evolution was not working with proxy

Error while performing operation.

Host lookup failed: smtp.gmail.com: Name or service not known
Comment 4 Akhil Laddha 2009-03-24 08:41:15 UTC 
bug 555888 should help here. Patch is a part of 2.26.0
Comment 5 Akhil Laddha 2010-03-31 07:03:39 UTC 
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 578429 ***