I sure wish I was coding, but there's so much else to work on right now...
I spent the evening redesigining the front page of http://www.citadel.org
The page looks a little more modern now. It's tough, as a hacker, for me to reduce the amount of information on that front page. I want to give everyone as much as I can right away. But, business sense and a review of what others are doing seem to dictate that the front page should just capture viewers' attention and then lead them to more information.
So, that big banner which takes up most of the screen will eventually rotate between three or four different banners, each highlighting a different reason why you should use Citadel.
One of them might even jump on the cloud computing hypewagon and point out that Citadel integrates perfectly with "infrastructure as a service" architectures.
The tag line will of course be "Castle on a Cloud" <big stupid grin>
Hi,
how does webcit 8.0 log? I found out that the options -t and -x are still working and the specified files are created. That seams odd, as webcit doesn't use them.
The syslog facilities are user and daemon. But what are the severities?
Where should the default log go, or do we use the distribution defaults?
Thanks
Stefan
Subject: Re: webcit logging questions
citserver and webcit both use syslog() now.
Each program is also set up so that if run in the foreground, it will log to stderr as well.
The documentation for the following option is missing in webcit/README.txt:
-h home_dir
-d
-D path
-T val
The default http_port is 2000 and not 80 as mentioned.
should we link this howto on our site referencing those imap copy tools?
http://www.howtoforge.com/how-to-migrate-mailboxes-between-imap-servers-with-imap-tools
All,
As I mentioned I was going to do, I have started work on packaging Net::Citadel for Debian.
Now, how to proceed with getting into Debian? I could see about getting it into the support by the Debian Perl team (which I've been planning to join in any case). OTOH, it is Citadel specific and when I first brought up packaging it for Debian, I was under the impression that it would or could be supported by the Debian Citadel packaging team in some way.
Note that I also found a minor bug in the documentation, which I've already submitted at CPAN.
Jame
whew. deleting my trashbin with 2k messages happenes in the time of an eye twinkle on release 8 webcit :]
Subject: citadel 8 <-> phpimap fuckup...
hm, so I did a little debugging with squirrelmail.
this is the message it spills:
| Body retrieval error. The reason for this is most probably that the message is malformed. | |
| Command: | FETCH 4738 BODY[2] |
| Response: | OK |
| Message: | UID FETCH completed |
| FETCH line: | * 1 FETCH (UID 4738 shgixsgi |
thats whats on the wire:
#
T 127.0.0.1:34997 -> 127.0.0.1:143 [AP]
A006 UID FETCH 4738 BODY[2].
##
T 127.0.0.1:143 -> 127.0.0.1:34997 [AP]
* 1 FETCH (UID 4738 shgixsgi.
BODY[2] {0}.
).
A006 OK UID FETCH completed.
the plain text body is
shgixsgi
which it seems was requested.
if I get that correctly, that body isn't supposed to be inside of that line?
need to compare with 7.8x... any hints?
Subject: Re: citadel 8 <-> phpimap fuckup...
ok, found & fixed.
hope that this is all.
Hi,
I'm looking into systemd stuff right now. I'm not sure if citadel is "systemd ready" (I haven't tested it yet), but this document (http://0pointer.de/public/systemd-man/daemon.html) describes systemd's requirements on a daemon. May be it's of interest for someone.
Regards
Stefan
Wed Nov 09 2011 03:54:14 EST from Stefan @ Uncensored Subject: systemdHi,
I'm looking into systemd stuff right now. I'm not sure if citadel is "systemd ready" (I haven't tested it yet), but this document (http://0pointer.de/public/systemd-man/daemon.html) describes systemd's requirements on a daemon. May be it's of interest for someone.
Regards
Stefan
fuckers.
http://refspecs.freestandards.org/LSB_3.1.1/LSB-Core-generic/LSB-Core-generic/iniscrptact.html
redirects to http://www.linuxfoundation.org/
Hi,
there seams to be a bug with the citserver's "-h <homedir>" option.
When calling:
# citserver -d -h /my/dir
I get the log message:
unable to change into directory [/var/run/citadel/my/dir/]: No such file or directory
The /var/run/citadel prefix seams wrong.
Regards
Stefan
Hi,
is citserver's "-t <trace_file>" option still supported?
When calling:
# citserver -d -t/tmp/test -lmail -x3
then the file "/tmp/test" is created, but is empty and stays empty.
Regards
Stefan
-D will print out all directories calculated
a leading / should make -h absolute, without relative.
Fri Nov 11 2011 10:54:53 AM EST from Stefan @ Uncensoredunable to change into directory [/var/run/citadel/my/dir/]: No such file or directoryThe /var/run/citadel prefix seams wrong.
Regards
Stefan
What does the "-D" option show for that?
Sun Nov 13 2011 10:52:31 ESTfrom jame @ Rocasa Mail System Subject: Re:What does the "-D" option show for that?
Strange. I can not reproduce the problem. Forget it.
IG: What about citserver's "-t <trace_file>" option? Should it still work?
Hi devs,
I attached a systemd service file. If you think that file is OK, then add it to the source tarball, please.
There is a small problem with systemd: As far as I know it's not possible to print a message to stdout/stderr while starting a service. A user who is starting an unconfigured citserver will not be notified that something went wrong.
----------------
# systemctl start citadel.service
# echo $?
0
# systemctl status citadel.service
...
Active: failed ...
Main PID: 5616 (code=exited, status=101) ...
# tail -7 /var/log/maillog
citserver[5617]: *** Citadel server engine v8.01 (build (unknown)) ***
citserver[5617]: Copyright ...
citserver[5617]: This programm ...
citserver[5617]:
citserver[5617]: Called as: /usr/sbin/citserver
citserver[5617]: libcitadel(unnumbered)
citserver[5617]: Loading citadel.config
# citserver -d -lmail -x3 -h
# echo $?
0
# tail -1 /var/log/mail
citserver[5631]: Loading citadel.config
----------------
citserver should not quit with a return code of 0, because that would suggest that it started properly.
citserver should log that it could not open citadel.config, and may log a hint to run 'citadel-setup'.
Best regards
Stefan
Hi,
With systemd there is no need for a init file or links to it in the rc.? directories. As citadel-setup doesn't know anything about systemd it will create the init file (that's fatal) and/or suggest to create the links and will fail with:
Error
failed to set system V init links
that's not fatal, but will irritate the user.
Regards
Stefan
Mon Oct 17 2011 06:05:01 AM EDT from jame Subject: Net::CitadelAs I mentioned I was going to do, I have started work on packaging Net::Citadel for Debian. ....