[Akonadi] [Bug 315049] New: Unable to access .onion TLD via IMAP Resource.

[Jason Oliveira]

https://bugs.kde.org/show_bug.cgi?id=315049

            Bug ID: 315049
           Summary: Unable to access .onion TLD via IMAP Resource.
    Classification: Unclassified
           Product: Akonadi
           Version: 4.10
          Platform: Ubuntu Packages
               URL: http://jhiwjjlqpyawmpjx.onion/
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: IMAP resource
          Assignee: ervin at kde.org
          Reporter: aidono at tormail.net
                CC: kdepim-bugs at kde.org, vkrause at kde.org

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.

-- 
You are receiving this mail because:
You are on the CC list for the bug.