mailsync doesn't use ssh

Bug #1193480 reported by Cilantro on 2013-06-21
This bug affects 1 person
Affects Status Importance Assigned to Milestone
uw-imap (Ubuntu)

Bug Description

mailsync refuses to use ssh; times out when imap connection fails
(mailsync appears to function normally in all other respects)

Steps to reproduce:
  mailsync store
where store is a properly configured mail store in $HOME/.mailsync, configured with the /secure option
(and correctly configured with /etc/rimapd pointing to imapd).

Ubuntu 12.04
mailsync 5.2.2-1.1
libc-client2007e 8:2007e~dfsg-3.2ubuntu1

$HOME/.mailsync contains an entry of the form:
store ssh {server host/secure ... }

When running "mailsync ssh", get a timeout error while trying to contact host on port 143.
Expected behavior: list of folders on host.

The following workaround was successful:

* Copy /usr/bin/mailsync binary from SuSE 11.3 (mailsync-5.2.1-167.1.x86_64)
* Copy /usr/lib64/ from SuSE 11.3 (libc-client2007e_suse-2007e_suse-3.1.x86_64)
* Link SuSE mailsync to SuSE at run time

(I also copied /etc/ from SuSE 11.3 (libc-client2007e_suse-2007e_suse-3.1.x86_64),
containing the two lines:
    set rshpath /usr/bin/rsh
    set sshpath /usr/bin/ssh
Don't think that was relevant, but didn't test exhaustively.)

Linking SuSE mailsync instead to Ubuntu libc-client results in identical incorrect behavior as Ubuntu mailsync.

Unless I'm missing something obvious (an undocumented setting?), this appears to be a bug in libc-client2007e.
(Yes, I'm a brand-new Ubuntu user, but with many years of RH and SuSE experience.)


To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers