| Summary: | proxy not taken into account by kmail | ||
|---|---|---|---|
| Product: | [Unmaintained] kmail | Reporter: | Yohann <Bertram25> |
| Component: | general | Assignee: | kdepim bugs <pim-bugs-null> |
| Status: | RESOLVED NOT A BUG | ||
| Severity: | normal | ||
| Priority: | NOR | ||
| Version First Reported In: | 1.6.2 | ||
| Target Milestone: | --- | ||
| Platform: | Debian testing | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Yohann
2004-08-13 13:47:07 UTC
The proxy settings are completely unrelated to KMail's transport mechanisms. (It might be possible that you refer to loading external references from within a message, but you didn't describe it that way. So it is a very vague guess. If I'm right, please check the upcoming KDE 3.3 for the problem. You could then reopen this report.) On Friday 13 August 2004 14:09, Andreas Gungl wrote:
> The proxy settings are completely unrelated to KMail's transport mechanisms.
To complete that: the proxy settings in KDE's configuration are the HTTP and FTP proxies.
Confusing with socks maybe?
Sorry for having being vague... Because of, maybe, my misunderstood of the problem, I'll explain the situation. I'm behind a proxy (squid) and, as expected, when I try to fetch my mails with kmail, it says that it can't resolve the pop.server.com name... logic... But now what did I miss ? Kmail must have to do something with the proxy. Or is this all about socks ? On Friday 13 August 2004 18:24, Yohann wrote: > I'm behind a proxy (squid) That's an HTTP proxy, so it's unrelated to KMail. > and, as expected, when I try to fetch my mails with kmail, it says that it can't resolve the pop.server.com name... > logic... Not really. It's your name resolution that doesn't work. Check /etc/resolv.conf, and/or check with your ISP. was my resolv.conf. I am really stupid... What could I Say ? Sorry would be quite appropriate. |