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 578429 - evolution ignores proxy settings for smtp
evolution ignores proxy settings for smtp
Status: RESOLVED DUPLICATE of bug 614632
Product: evolution-data-server
Classification: Platform
Component: Mailer
2.26.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
evolution[smtp]
: 555496 579814 606334 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2009-04-08 21:34 UTC by sam tygier
Modified: 2010-06-04 16:55 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24



Description sam tygier 2009-04-08 21:34:32 UTC
evolution 2.24.5 (evolution-2.24.5-1.fc10.i386)

I have created a proxy using
ssh -D 5555 remotesystem

i have set evolution to use it in preference -> network preferences, manual configuration, put localhost, 5555 in the SOCKS option.

my email still appears to come from my local broadband IP address, rather than the remotesystem.
Comment 1 Akhil Laddha 2009-04-09 03:57:19 UTC
Not sure but bug 555888 may be helpful 
Comment 2 sam tygier 2009-04-09 16:43:11 UTC
thanks Akhil. the patch on that page does not seem to cover SMTP (based on a quick grep for 'smtp'). i tried 2.26.0. the preferences now only has boxes for HTTP and HTTPS proxy information. if i fill these in, SMTP is still send directly.
Comment 3 Milan Crha 2009-04-14 15:02:35 UTC
Right, no code in camel directory had been touched by the above bug. Honestly, I have no much idea how to implement this under camel directory.
Comment 4 Matthew Barnes 2009-04-14 16:26:45 UTC
Bear in mind libedataserver is off limits to Camel.
Camel will probably have to grow its own proxy API.
Comment 5 Milan Crha 2009-04-14 17:27:15 UTC
(In reply to comment #4)
> Bear in mind libedataserver is off limits to Camel.
> Camel will probably have to grow its own proxy API.

I thought so, but found that Camel uses libedataserver things already.
Comment 6 Matthew Barnes 2009-04-14 19:28:51 UTC
It does still, but I'm working to undo that (e.g. bug #424744).  The goal is to someday split Camel off as a separate module (like gtkhtml or libsoup).  But we can't do that if it depends on E-D-S libraries.
Comment 7 Milan Crha 2009-11-10 13:36:34 UTC
*** Bug 579814 has been marked as a duplicate of this bug. ***
Comment 8 Benedict Stein 2010-01-08 15:32:04 UTC
coming from https://bugzilla.gnome.org/show_bug.cgi?id=606334 it looks like the overall preferences windows for proxy settings in evo doesn't work or ?
Comment 9 Benedict Stein 2010-01-08 15:32:59 UTC
*** Bug 606334 has been marked as a duplicate of this bug. ***
Comment 10 Benedict Stein 2010-01-08 15:34:24 UTC
would be kind of you to add https://launchpad.net/bugs/487655 as "see also - realtead bug"

(guess only admin and original poster can do)
Comment 11 Milan Crha 2010-01-11 10:29:05 UTC
Benedict, your SMTP is about proxy in mailer, which is done by Camel in Evolution, which is discussed above, and as this bug is still opened, there hadn't been done with it anything yet, unfortunately.
Comment 12 Stanislas Couix 2010-03-13 07:54:46 UTC
Hi,

How can I help resolving this bug ? should I post camel_debug ?

But I don't know if <a href="https://bugzilla.gnome.org/show_bug.cgi?id=606334">bug 606334</a> is really a duplicate of this bug as 606334 affects evolution 2.28.x and this one affects 2.26.x

In ubuntu jaunty, with evolution 2.26.x, I was able to get mail under my work proxy and it never failed
Now, with 2.28, I can't. So I guess the problem is related to 2.28.x and not 2.26.x

But maybe I'm completely wrong !!

In each case, let me know if you need camel_debug=all

Stan
Comment 13 Akhil Laddha 2010-03-31 07:03:39 UTC
*** Bug 555496 has been marked as a duplicate of this bug. ***
Comment 14 Federico Mena Quintero 2010-06-04 16:55:24 UTC

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