Error connecting to POP or IMAP

Bug #588397 reported by Pedro Gauna
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Cloudsn
Fix Released
Undecided
Unassigned

Bug Description

I'm having errors when launch CloudSN.
I've attached the app's log.

Revision history for this message
Pedro Gauna (lapega) wrote :
Revision history for this message
Pedro Gauna (lapega) wrote :

I've finded a workaround:

- open CloudSN window
- click in an account
- click in edit button
- click in Ok

Revision history for this message
perriman (chuchiperriman) wrote :

Have you configured the correct server port for SSL? That error can appear when you configure an SSL connection to a port without SSL support

Revision history for this message
alessandro19680 (alessandro-sisti-fastwebnet) wrote :

I have the same problem of Pedro. I used the same configuration used for evolution:
Provider: POP 3
host: the same used in evolution pop.fastwebnet.it
user: the username of my mail account
password: the same
port: 110
use SSL: no
The Pedro's workaround works for me too

Revision history for this message
perriman (chuchiperriman) wrote :

I'll try to see if there is an error in the ssl configuration, perhaps it is losing the ssl value...

Revision history for this message
perriman (chuchiperriman) wrote :

ahhhhh!!! Does the problem appear when you have updated to 0.5.14? I fixed a bug with the SSL because it has always enabled and when you update to 0.5.14 the ssl configuration doesn't exists.

If you edit the account and save again (only the first time), it must work fine forever. Can you confirm it??

Revision history for this message
Pedro Gauna (lapega) wrote :

Confirmed!

Revision history for this message
alessandro19680 (alessandro-sisti-fastwebnet) wrote :

Not at all. Whenever i shut down and restart the program, for a correct operation of the program, i must repeat the change of account

Revision history for this message
Pedro Gauna (lapega) wrote :

Yes, It's happening again... (cloudnsn 0.5.16)

Revision history for this message
alessandro19680 (alessandro-sisti-fastwebnet) wrote :

me too (cloudsn 0.5.16)

Revision history for this message
giorgio dolfo (giorgio.dolfo) wrote :

confirm the same bug with pop3 account. (cloudsn 0.5.16)

Revision history for this message
perriman (chuchiperriman) wrote :

POP3 implementation need a looooooot of love. The POP3 protocol is the worst protocol even written :)

In the next release I'll rewrite the POP3 provider based on specto

Revision history for this message
giorgio dolfo (giorgio.dolfo) wrote :

Good idea, specto works perfectly with the POP3 protocol. I tried to produce feedback for cloudsn http://forum.ubuntu-it.org/index.php/topic,393436.0.html.

Revision history for this message
Myzeus (myzeus) wrote :

Same problem in Cloudsn 0.5.12 on IMAP4 Accounts. I use the workaround already mentioned by Pedro Gauna.

Revision history for this message
Pedro Gauna (lapega) wrote :

Another workaround:

IMAP
open (as root) /usr/share/pyshared/cloudsn/providers/imapprovider.py,
and change line 96 to "self.ssl = False"

POP3
open (as root) /usr/share/pyshared/cloudsn/providers/pop3provider.py
and change line 76 to "ssl = False"

Revision history for this message
perriman (chuchiperriman) wrote :

I think that is working on the development branch (trunk) If you want, you can download it from github and try it. If it works for you, please, make me know!

Changed in cloudsn:
status: New → Fix Committed
milestone: none → 0.8.0
Changed in cloudsn:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.