Bug 315049 - Unable to access .onion TLD via IMAP Resource.
Summary: Unable to access .onion TLD via IMAP Resource.
Status: RESOLVED WORKSFORME
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: IMAP resource (show other bugs)
Version: 4.10
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Christian Mollekopf
URL: http://jhiwjjlqpyawmpjx.onion/
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2013-02-13 10:03 UTC by Jason Oliveira
Modified: 2018-10-27 03:55 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jason Oliveira 2013-02-13 10:03:18 UTC
I attempted to access http://jhiwjjlqpyawmpjx.onion/ via the IMAP resource, and was greeted with "Unable to connect to the server, please verify the server address".

I would assume that manually setting my proxy settings to the correct (confirmed working) https/http/socks5 ports would allow akonadi to access .onion tld's. 

My business uses tormail.org/jhiwjjlqpyawmpjx.onion to host email accounts. This issue is blocking me from being able to use kmail2/kontact as my mail client. 




Reproducible: Always

Steps to Reproduce:
1) install tor/privoxy, 
2) set "forward-socks5" rule in /etc/privoxy/config and restart privoxy
3) in systemsettings -> Network Settings -> Proxy, select "Use Manually Specified Proxy Confguration": 
  a) HTTP Proxy: 127.0.0.1     Port 8118
  b) SSL Proxy: 127.0.0.1   Port 8118
  c) SOCKS Proxy: 127.0.0.1 Port 9050
4) use browser to connect to http://jhiwjjlqpyawmpjx.onion/ (I used rekonq) and create a free account.
5) create a new IMAP account in Akonadi using the account settings created in step 4.
6) watch error occur.
Actual Results:  
I was saddened when I had to use Thunderbird to sully my all-Qt desktop.

Expected Results:  
kmail2 would have checked my imap folders for new messages, and displayed them.

Kubuntu 12.10 with KDE 4.10 backport. I've been experiencing this problem for about 6 months to a year now, so it's not exactly limited to the 4.10 SC.
Comment 1 Kevin Ottens 2013-11-16 07:31:30 UTC
The IMAP resource has a new maintainer, reassigning to him.
Comment 2 Christian Mollekopf 2013-12-03 17:21:51 UTC
Does this still apply to >= 4.11.3?
If yes, can you check .xsession-errors for additional clues. You may have to enable debug output using kdebugidalog first.
Comment 3 Andrew Crouthamel 2018-09-25 03:30:58 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Andrew Crouthamel 2018-10-27 03:55:44 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!