Package: mailsync
Version: 5.2.2-1
Severity: important
hi,
I'm using mailsync in a script to be run both from terminal and via cronjob.
So far I've been using only the 1st mode, and it's fine.
Now I tried to let crond take care of it, but it doesn't work, bailing out
with 'no such mailbox' looking for the msinfo mbox:
from terminal:
#------------------------------------------------------------------
Only simulating
Synchronizing stores "localhost-inbox" <-> "server-inbox"...
Authorizing against {localhost/imap}
Authorizing against {server/imap}
INBOX:
3 duplicates in server-inbox
Authorizing against {server/imap}
Authorizing against {localhost/imap}
9 copied localhost-inbox->server-inbox.
295 copied server-inbox->localhost-inbox.
1491 remain.
#------------------------------------------------------------------
cronjob:
#------------------------------------------------------------------
Error: Can't open mailbox .mailsync_info: no such mailbox
Error: Couldn't open msinfo box .mailsync_info.
Aborting!
Only simulating
Synchronizing stores "localhost-inbox" <-> "server-inbox"...
Authorizing against {localhost/imap}
Authorizing against {server/imap}
#------------------------------------------------------------------
the msinfo mbox is ~/.mailsync_info, I'm pretty sure the working path of
mailsync is ~/ in both cases.
The error seems to come from mail_open() in libc-client, 1st called in
Channel::read_lasttime_seen().
An strace log on Sarge shows just lots of errors opening /dev/tty in cronjob
case, but not on Etch. Result is the same though, ie mailsync always fail
as a cronjob.
I'm rating this bug 'important' since mailsync seems unusable from cronjob,
which (to me) sounds like it's main purpose instead.
This seems somewhat related to #215572 and/or perhaps #187513
thanks
--
paolo
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
