Language:
switch to room list switch to menu My folders
Go to page: [1] 2 3 4 5 ... Last
↑↑↑ Old messages ↑↑↑            ↓↓↓ New messages ↓↓↓
[#] Thu Apr 18 2013 10:35:15 EDT from jcurtis1027 @ Uncensored

Subject: Distribution Groups

[Reply] [ReplyQuoted] [Headers] [Print]

Does Citadel support Exchange like distribution groups?



[#] Thu Apr 18 2013 10:57:30 EDT from IGnatius T Foobar @ Uncensored

Subject: Re: Distribution Groups

[Reply] [ReplyQuoted] [Headers] [Print]

To do the equivalent of a distribution group, create a room and build a mailing list in it. Any mail sent to the room or posted in it will go to all members.

[#] Thu Apr 18 2013 11:45:31 EDT from alex007 @ Uncensored

Subject: Re: Calendar Frontend for citadel (SOgo Connector? + lightning)

[Reply] [ReplyQuoted] [Headers] [Print]

 

Thu Apr 18 2013 03:38:02 EDT from dothebart @ Uncensored Subject: Re: Calendar Frontend for citadel (SOgo Connector? + lightning)

synckolab is the better tool for the job; its working via imap.



Thanks! I've tested it. Adressbook sync I've already tested some months ago, it doesn't work properly. Today i've tested calendar sync - big problems with encoding charset. I've lost my calendar data. Not good.

I think it's a problem of that terrible lightning calendar, which doesn't work after several years of developing. And maybe a problem of synckolab too, I don't know. This solutions are not usable...

If there is a possibility for creating a wiki or a howto for citadel clients I would help to work on it...



[#] Thu Apr 18 2013 12:50:16 EDT from alex007 @ Uncensored

Subject: Re: Calendar Frontend for citadel sync kolab + lightning

[Reply] [ReplyQuoted] [Headers] [Print]

 

Thu Apr 18 2013 11:45:31 EDT from alex007 @ Uncensored Subject: Re: Calendar Frontend for citadel (SOgo Connector? + lightning)

 

Thu Apr 18 2013 03:38:02 EDT from dothebart @ Uncensored Subject: Re: Calendar Frontend for citadel (SOgo Connector? + lightning)

synckolab is the better tool for the job; its working via imap.



Thanks! I've tested it. Adressbook sync I've already tested some months ago, it doesn't work properly. Today i've tested calendar sync - big problems with encoding charset. I've lost my calendar data. Not good.

I think it's a problem of that terrible lightning calendar, which doesn't work after several years of developing. And maybe a problem of synckolab too, I don't know. This solutions are not usable...

If there is a possibility for creating a wiki or a howto for citadel clients I would help to work on it...



There are thre different formats in sync kolab

  • ical/Kolab1   

- this format is not recommended by the developer of sync kolab

- choosing this format, I've got charset encoding problems and (therefore?) lost of data

- citadel understand this format and can show it in webcit

 

  • Xml/kolab2
  • Xml/kolab3

- citadel doesn't understand this format in it's webcit calendar, new created entries by lightning are not visible in webcit

- but: sync works if you create new entries with lightning - it works with  acces from different lightning installations,

- but: the old entries created by webcit can not edited, respictively it has no effect of the server entries



[#] Thu Apr 18 2013 13:05:12 EDT from IGnatius T Foobar @ Uncensored

Subject: Re: Calendar Frontend for citadel (SOgo Connector? + lightning)

[Reply] [ReplyQuoted] [Headers] [Print]

If there is a possibility for creating a wiki or a howto for citadel clients

I would help to work on it...

Any and all help would be appreciated! We have our documentation already set up as a wiki on www.citadel.org so if you would like to write a series of howto documents it would be great to have some help!!

[#] Fri Apr 19 2013 09:44:15 EDT from cbraxton @ Uncensored

Subject: Re: Calendar Frontend for citadel sync kolab + lightning

[Reply] [ReplyQuoted] [Headers] [Print]

After looking at various options and trying them I basically just gave up, nothing seems to work properly. I have my users access shared calendars via Thunderbird and Lightning in read-only mode, they have to use Citadel's web interface to add or change appointments. Although klutzy, for us it's not too bad as typically the people entering the appointments and the people using/reading them are separate groups. (It's a shame that lightning doesn't have native support for Citadel, as a fully-integrated combination of the two would be excellent.)



[#] Fri Apr 19 2013 10:52:41 EDT from IGnatius T Foobar @ Uncensored

Subject: Re: Calendar Frontend for citadel sync kolab + lightning

[Reply] [ReplyQuoted] [Headers] [Print]

Lightning seems to work for me; you do have to do it at the granularity of the entire calendar (by mapping the .ics using webdav) but it does work.

[#] Fri Apr 19 2013 17:52:40 EDT from alex007 @ Uncensored

Subject: Re: Calendar Frontend for citadel sync kolab + lightning

[Reply] [ReplyQuoted] [Headers] [Print]

 

Fri Apr 19 2013 10:52:41 EDT from IGnatius T Foobar @ Uncensored Subject: Re: Calendar Frontend for citadel sync kolab + lightning
Lightning seems to work for me; you do have to do it at the granularity of the entire calendar (by mapping the .ics using webdav) but it does work.

I contacted the developer of sync kolab, we work together for a solution of the encoding problem for the ical entries...



[#] Fri Apr 19 2013 18:04:19 EDT from s3cr3to @ Uncensored

Subject: question about citadel on squeeze and upgrade to wheezy

[Reply] [ReplyQuoted] [Headers] [Print]

Maybe it's to soon to ask, and even I'll wait for months after wheeze is released.
I was wondering is someone has tested an upgrade of a debian squeeze server (with citadel, clamav, spamassassin) to wheeze.

Any issues to be aware?

In fact, I try to avoid to be on the "not supported side" even by Squeeze or citadel; and always running the most stable/supported/secure scenario.

Regards



[#] Sat Apr 20 2013 03:48:13 EDT from dothebart @ Uncensored

Subject: Re: question about citadel on squeeze and upgrade to wheezy

[Reply] [ReplyQuoted] [Headers] [Print]

I just can tell you I run it in wheezy for a while now.

usually upgrade troubles come from gtk/qt stuff in my experience, and server only environments upgrade flawless.

However, having a backup of citadel before upgrading can't hurt in any case.



[#] Mon Apr 22 2013 15:20:01 EDT from alex007 @ Uncensored

Subject: Re: Calendar Frontend for citadel sync kolab + lightning

[Reply] [ReplyQuoted] [Headers] [Print]

 

Fri Apr 19 2013 17:52:40 EDT from alex007 @ Uncensored Subject: Re: Calendar Frontend for citadel sync kolab + lightning

 

Fri Apr 19 2013 10:52:41 EDT from IGnatius T Foobar @ Uncensored Subject: Re: Calendar Frontend for citadel sync kolab + lightning
Lightning seems to work for me; you do have to do it at the granularity of the entire calendar (by mapping the .ics using webdav) but it does work.

I contacted the developer of sync kolab, we work together for a solution of the encoding problem for the ical entries...



I've got still the problem with encoding. I attached 2 files, which I grabed from thunderbird (Sourcecode of the E-Mail in the respective IMAP-Folder) The first is a calendar entry, which I generated inside citadel with webcit. The second comes from sync kolab, generated in lightning, sync kolab writes this entry in the IMAP-Folder

The content of the subject field of the entries is "Hier sind 2 oes öö"

Both, the citadel entry is not corrected encodet in lightning via sync kolab and the the sync kolab entry from lightning is not right represented in the citadel calendar (webcit).

I wonder why in the citadel generated entry (subject)  the ö is not =F6 (quoted-printable), but =C3=B6?

 

It is not clear for me who of the three (citadel, lightning,sync kolab) has problems with the encoding.

Can anybody of you discover anything in the entries, what is not correct?

 



calendar_entry_sync_kolab.txt (text/plain, 1452 bytes) [View| Download]
calendar_entry_citadel.txt (text/plain, 1461 bytes) [View| Download]
[#] Tue Apr 23 2013 05:13:48 EDT from dothebart @ Uncensored

Subject: Re: Calendar Frontend for citadel sync kolab + lightning

[Reply] [ReplyQuoted] [Headers] [Print]

 

Mon Apr 22 2013 15:20:01 EDT from alex007 @ Uncensored Subject: Re: Calendar Frontend for citadel sync kolab + lightning

 

Fri Apr 19 2013 17:52:40 EDT from alex007 @ Uncensored Subject: Re: Calendar Frontend for citadel sync kolab + lightning

 

Fri Apr 19 2013 10:52:41 EDT from IGnatius T Foobar @ Uncensored Subject: Re: Calendar Frontend for citadel sync kolab + lightning
Lightning seems to work for me; you do have to do it at the granularity of the entire calendar (by mapping the .ics using webdav) but it does work.

I contacted the developer of sync kolab, we work together for a solution of the encoding problem for the ical entries...



I've got still the problem with encoding. I attached 2 files, which I grabed from thunderbird (Sourcecode of the E-Mail in the respective IMAP-Folder) The first is a calendar entry, which I generated inside citadel with webcit. The second comes from sync kolab, generated in lightning, sync kolab writes this entry in the IMAP-Folder

The content of the subject field of the entries is "Hier sind 2 oes öö"

Both, the citadel entry is not corrected encodet in lightning via sync kolab and the the sync kolab entry from lightning is not right represented in the citadel calendar (webcit).

I wonder why in the citadel generated entry (subject)  the ö is not =F6 (quoted-printable), but =C3=B6?

 

It is not clear for me who of the three (citadel, lightning,sync kolab) has problems with the encoding.

Can anybody of you discover anything in the entries, what is not correct?

Hm, both fail to mention which characterset they're in:

MIME-Version: 1.0
Content-Type: text/calendar
Content-Transfer-Encoding: quoted-printable
User-Agent: SyncKolab 3.1.0

either one of utf8 / iso 8859-1

so maybe exactly this is the problem - in UTF8 umlauts become 2 characters, in ISO they remain one.

I guess both of them should specify the charset in first place to make it work transparent, however you should be able to configure synckolab to do utf8 - which is pretty much standard nowadays.



calendar_entry_citadel.txt (text/plain, 1461 bytes) [View| Download]
calendar_entry_sync_kolab.txt (text/plain, 1452 bytes) [View| Download]
[#] Tue Apr 23 2013 22:20:08 EDT from wylekyote @ Uncensored

Subject: password length inconsistency in webcit

[Reply] [ReplyQuoted] [Headers] [Print]

New citadel setup today .. added a bunch of users with generated passwords 24 characters long through webcit  (as they worked off the command line just fine)  Just had someone else less tty capable add the rest via the webcit interface..

 

they didn't work

 

traced the reason why to the form import having a maxlength of 20

 

<td>Password</td><td><input type="password" name="password" value="" maxlength="20"></td>


[#] Wed Apr 24 2013 04:10:40 EDT from alex007 @ Uncensored

Subject: Re: Calendar Frontend for citadel sync kolab + lightning

[Reply] [ReplyQuoted] [Headers] [Print]

 

Tue Apr 23 2013 05:13:48 EDT from dothebart @ Uncensored Subject: Re: Calendar Frontend for citadel sync kolab + lightning

 

Mon Apr 22 2013 15:20:01 EDT from alex007 @ Uncensored Subject: Re: Calendar Frontend for citadel sync kolab + lightning

 

Fri Apr 19 2013 17:52:40 EDT from alex007 @ Uncensored Subject: Re: Calendar Frontend for citadel sync kolab + lightning

 

Fri Apr 19 2013 10:52:41 EDT from IGnatius T Foobar @ Uncensored Subject: Re: Calendar Frontend for citadel sync kolab + lightning
Lightning seems to work for me; you do have to do it at the granularity of the entire calendar (by mapping the .ics using webdav) but it does work.

I contacted the developer of sync kolab, we work together for a solution of the encoding problem for the ical entries...



I've got still the problem with encoding. I attached 2 files, which I grabed from thunderbird (Sourcecode of the E-Mail in the respective IMAP-Folder) The first is a calendar entry, which I generated inside citadel with webcit. The second comes from sync kolab, generated in lightning, sync kolab writes this entry in the IMAP-Folder

The content of the subject field of the entries is "Hier sind 2 oes öö"

Both, the citadel entry is not corrected encodet in lightning via sync kolab and the the sync kolab entry from lightning is not right represented in the citadel calendar (webcit).

I wonder why in the citadel generated entry (subject)  the ö is not =F6 (quoted-printable), but =C3=B6?

 

It is not clear for me who of the three (citadel, lightning,sync kolab) has problems with the encoding.

Can anybody of you discover anything in the entries, what is not correct?

Hm, both fail to mention which characterset they're in:

MIME-Version: 1.0
Content-Type: text/calendar
Content-Transfer-Encoding: quoted-printable
User-Agent: SyncKolab 3.1.0

either one of utf8 / iso 8859-1

so maybe exactly this is the problem - in UTF8 umlauts become 2 characters, in ISO they remain one.

I guess both of them should specify the charset in first place to make it work transparent, however you should be able to configure synckolab to do utf8 - which is pretty much standard nowadays.


Thanks, maybe that's the point. I let you know, if it works, when the missing charset line is inside the entry.

But citadel should do this too, shouldn't it?



[#] Wed Apr 24 2013 21:46:08 EDT from Andrew Craig @ Uncensored

[Reply] [ReplyQuoted] [Headers] [Print]

I have citadel installed on my RaspberryPi, I am also running another web service through apache. I want that service to have port 80, and I want citadel to have port 443. How is this possible?



[#] Fri Apr 26 2013 14:55:32 EDT from IGnatius T Foobar @ Uncensored

[Reply] [ReplyQuoted] [Headers] [Print]

I have citadel installed on my RaspberryPi, I am also running another
web service through apache. I want that service to have port 80, and
I want citadel to have port 443. How is this possible?

webcit -s -p443 ...


[#] Fri Apr 26 2013 16:29:52 EDT from jwhistler66 @ Uncensored

Subject: Configure Citadel to receive emails only

[Reply] [ReplyQuoted] [Headers] [Print]

Hi all.  I would like to setup citadel to be able to process certain emails using procmail.  Our main email server is an Exchange Server, and I would like to forward certain messages based on header to the citadel server where I can process information out of the email and store it into a database.  I just want a generic email account on the citadel server that I can forward to.  I have everything setup, but the citadel server keeps rejecting the forwarded emails with:

550 You must log in to send mail from blah.com

Thanks in advance.

 



[#] Sat Apr 27 2013 12:53:47 EDT from IGnatius T Foobar @ Uncensored

Subject: Re: Configure Citadel to receive emails only

[Reply] [ReplyQuoted] [Headers] [Print]

How are you submitting mail into Citadel? LMTP via a local socket is the preferred method of integrating with third-party MTA's. In particular, if you do LMTP to lmtp-unfiltered.socket you will be relieved of most of the restrictions, with the rationale that most restrictions will be handled by your edge MTA.

[#] Sun Apr 28 2013 13:56:45 EDT from alex007 @ Uncensored

Subject: Re: Calendar Frontend for citadel sync kolab + lightning

[Reply] [ReplyQuoted] [Headers] [Print]

 

Wed Apr 24 2013 04:10:40 EDT from alex007 @ Uncensored Subject: Re: Calendar Frontend for citadel sync kolab + lightning

 

Tue Apr 23 2013 05:13:48 EDT from dothebart @ Uncensored Subject: Re: Calendar Frontend for citadel sync kolab + lightning

 

Mon Apr 22 2013 15:20:01 EDT from alex007 @ Uncensored Subject: Re: Calendar Frontend for citadel sync kolab + lightning

 

Fri Apr 19 2013 17:52:40 EDT from alex007 @ Uncensored Subject: Re: Calendar Frontend for citadel sync kolab + lightning

 

Fri Apr 19 2013 10:52:41 EDT from IGnatius T Foobar @ Uncensored Subject: Re: Calendar Frontend for citadel sync kolab + lightning
Lightning seems to work for me; you do have to do it at the granularity of the entire calendar (by mapping the .ics using webdav) but it does work.

I contacted the developer of sync kolab, we work together for a solution of the encoding problem for the ical entries...



I've got still the problem with encoding. I attached 2 files, which I grabed from thunderbird (Sourcecode of the E-Mail in the respective IMAP-Folder) The first is a calendar entry, which I generated inside citadel with webcit. The second comes from sync kolab, generated in lightning, sync kolab writes this entry in the IMAP-Folder

The content of the subject field of the entries is "Hier sind 2 oes öö"

Both, the citadel entry is not corrected encodet in lightning via sync kolab and the the sync kolab entry from lightning is not right represented in the citadel calendar (webcit).

I wonder why in the citadel generated entry (subject)  the ö is not =F6 (quoted-printable), but =C3=B6?

 

It is not clear for me who of the three (citadel, lightning,sync kolab) has problems with the encoding.

Can anybody of you discover anything in the entries, what is not correct?

Hm, both fail to mention which characterset they're in:

MIME-Version: 1.0
Content-Type: text/calendar
Content-Transfer-Encoding: quoted-printable
User-Agent: SyncKolab 3.1.0

either one of utf8 / iso 8859-1

so maybe exactly this is the problem - in UTF8 umlauts become 2 characters, in ISO they remain one.

I guess both of them should specify the charset in first place to make it work transparent, however you should be able to configure synckolab to do utf8 - which is pretty much standard nowadays.


Thanks, maybe that's the point. I let you know, if it works, when the missing charset line is inside the entry.

But citadel should do this too, shouldn't it?



Dear developer of citadel, the line charset="utf-8" belongs in they Calendar files, don't they? Is it much work to do this?



[#] Mon Apr 29 2013 03:12:24 EDT from dothebart @ Uncensored

Subject: Re: Configure Citadel to receive emails only

[Reply] [ReplyQuoted] [Headers] [Print]

 

Fri Apr 26 2013 16:29:52 EDT from jwhistler66 @ Uncensored Subject: Configure Citadel to receive emails only

Hi all.  I would like to setup citadel to be able to process certain emails using procmail.  Our main email server is an Exchange Server, and I would like to forward certain messages based on header to the citadel server where I can process information out of the email and store it into a database.  I just want a generic email account on the citadel server that I can forward to.  I have everything setup, but the citadel server keeps rejecting the forwarded emails with:

550 You must log in to send mail from blah.com

Thanks in advance.

 



at first, you can't use procmail with citadel.

however citadel offers an integrated sieve engine.

in your (test) case the sender is local to citadel, right? Citadel won't let you send those unauthenticated.

If your general usecase is to filter & process external mails with froms from other domains, this should work.

Webcit even offers a way to have mails parsed up into a json structure to improve your comfort of automated processing - since basic mail parsing tends to be a rather complicated and error prone process.



Go to page: [1] 2 3 4 5 ... Last