[Citadel Development] (no subject)

2006-02-06 Thread IGnatius T Foobar
zwoelf: there are two problems with your ICAL object that I can see initially: 1. DTEND:200610209T200054Z is an invalid timestamp. You've got too many characters in the date portion of the field. libical barfs on this, telling us X-LIC-ERROR;X-LIC-ERRORTYPE=VALUE-PARSE-ERROR:Can't

[Citadel Development] (no subject)

2006-02-06 Thread IGnatius T Foobar
Isn't there a larger issue with RFC2047 format subject lines? If the charset declaration was unrecognized, wasn't the server attempting to render the base64-encoded text as if it encoded a Unicode string? Ah, but the questionable messages do not *have* RFC2047 format subject

[Citadel Development] Re: Python support for Citadel

2006-02-06 Thread gldnspud
Feb 7 2006 3:59 from IGnatius T [EMAIL PROTECTED] As for synchronizing accounts ... are you aware that Citadel can authenticate users against the host operating system instead of using its own user database? Yeesh, you have to go and ruin it for me and save me some time, don't you? :)I'll

[Citadel Development] (no subject)

2006-02-06 Thread IGnatius T Foobar
Heh. The Citadel accounts are still created, of course, but they're directly tied to corresponding host system accounts (and authenticated as such). Simply build Citadel using ./configure --enable-autologin. By the way, you should be using the current sources in svn if you want to do