Re: [Duplicity-talk] Imap Support - Bug in urlparse_2_5.py

[Ian Barton]

> First, duplicity currently bundles a urlparse module that behaves in a
> non-standard way for backwards compatibility with earlier duplicity
> releases.
>
> You should diff the bundled urlparse against the system version and
> understand the splitting quirk before implementing a new duplicity
> backend.
>
> Also notice how the FTP_PASSWORD environment variable is used.
>
>
> > duplicity full -v9 ~/blosxom imap://address@hidden:mypassword/INBOX
>
> Second, convention puts the password before the @ symbol like this:
>
>   duplicity full -v9 ~/blosxom imap://ian:address@hidden/INBOX
Darik,

Thanks for all your comments, which were very helpful. My immediate 
problem was caused by forgetting to register the imap protocol in 
backend.py.

I think I shall add two new protocols imap and imaps. It looks to me as 
though the current gmail backend can only handle secure connections. 
From gmailimapbackend.py

if( parsed_url.scheme == "gmail" ):
            cl = imaplib.IMAP4_SSL
            self._conn = cl('imap.gmail.com', 993)
else:
            cl = imaplib.IMAP4
            self._conn = cl('imap.gmail.com', 143)

I can't see how the else clause can ever be executed.

Ian.