hi,
ok, finally, I figured it out - here's the clue, from c-client's drivers.txt:
#--[drivers.txt]------------------------------------------------------------
Prefix Interpretation of Suffix
------ ------------------------
/ [black box] preceeds a user name; "/foo/bar" means
"black box user foo's mailbox bar"
[not black box] preceeds an absolute path name.
~ [not black box] preceeds a user name; "~foo/bar" means
"UNIX user foo's mailbox bar"
#ftp/ preceeds UNIX user ftp's mailbox name
#public/ preceeds UNIX user imappublic's mailbox name
#shared/ preceeds UNIX user imapshared's mailbox name
All other names are interpreted in the context of the UNIX user's home
directory (not black box), the black box user's black box directory
(black box), or UNIX user ftp's home directory (anonymous).
#---------------------------------------------------------------------------
and from strace log, which shows mail_open() looks for
/var/mail/anonymous/<my-msinfo_mbox_name>
so, the culprit is that, from terminal the c-client functions are called
in 'not black box' while in other contexts - eg. a cronjob - they're in
'black box' mode:
src/mailsync_main.cc: env_init( getenv("USER"), getenv("HOME"));
and from crond USER is unset hence mode -> 'black box'.
To wit, changing the cronjob item as follows:
26 23 * * * export USER=$LOGNAME; mailsync inbox-local-server >/dev/null 2>&1
works like from terminal.
That'd be the culprit for similar bugrep as well.
Perhaps worth documenting in mailsync's docs?
thanks
--
paolo
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
