some (long) time ago I expressed my interest in trying out Citadel within a Docker container and someone here pointed me to some repository where some sort of "prototype" was available. Now, I have lost that particular link and am now asking if anyone here can (once more) provide it to me?

We ended up going in a different direction.  Instead of Docker, we built an AppImage, which just had its first beta release a couple of days ago.

AppImage, as you may know, packages an entire complex application and all of its dependencies into a single executable file that runs on many different Linux versions.  It turns out we had to change a lot of things that were based on outdated assumptions to make this happen.  For example, we ended support for the LFHS-style build and now require everything in a single directory.  These changes ought to make it a lot easier to put Citadel and its dependencies into a container, but as previously noted, we are not currently working on that.

Go ahead and try the AppImage if it can satisfy your requirements.

bart, have you tried using your full email address as the username?

For example, instead of using "bartv" try using "bartv@bartscorner.nl" instead.

And of course, watch your server logs while this is happening, to see if it mapped you to the correct user.

 

this is what i get accessing port 25 via putty from a windows pc in my local netwerk :

220 bartscorner.nl ESMTP Citadel server ready.
EHLO bartscorner.nl
250-Hello bartscorner.nl (Laborix.bartscorner.local [192.168.1.117])
250-HELP
250-SIZE 10485760
250-AUTH LOGIN PLAIN
250-AUTH=LOGIN PLAIN
250 8BITMIME
AUTH LOGIN
334 VXNlcm5hbWU6
YmFydHYK
334 UGFzc3dvcmQ6
VGhpcyBpcyBub3QgbXkgcmVhbCBwYXNzd29yZA==
535 Authentication failed.

I used https://www.base64encode.org/ to encode my credentials

This is a good webpage describing the procedure : https://www.comparitech.com/net-admin/telnet-smtp-test/

334 VXNlcm5hbWU6 decodes to  Username: in plain text

respons  YmFydHYK is bartv (username)

334 UGFzc3dvcmQ6 decodes to Password:

respons VGhpcyBpcyBub3QgbXkgcmVhbCBwYXNzd29yZA==   is my password (i used the correct one, in this posting i posted a fake one ;-) )

github was too costly? lol... the source is out there, someone just has to volunteer to maintain

Sun May 23 2021 14:11:13 EDT from IGnatius T Foobar Subject: Re: Citadel in Docker (prototype repo URL?)

some (long) time ago I expressed my interest in trying out Citadel within a Docker container and someone here pointed me to some repository where some sort of "prototype" was available. Now, I have lost that particular link and am now asking if anyone here can (once more) provide it to me?

We ended up going in a different direction.  Instead of Docker, we built an AppImage, which just had its first beta release a couple of days ago.

AppImage, as you may know, packages an entire complex application and all of its dependencies into a single executable file that runs on many different Linux versions.  It turns out we had to change a lot of things that were based on outdated assumptions to make this happen.  For example, we ended support for the LFHS-style build and now require everything in a single directory.  These changes ought to make it a lot easier to put Citadel and its dependencies into a container, but as previously noted, we are not currently working on that.

Go ahead and try the AppImage if it can satisfy your requirements.

revisited... sourceforge was too complicated? just insult to injury. citadel is a blessing of source code within superb architecture. surely I am not the only one implementing message search and forgot password routines. 

Mon May 31 2021 02:48:31 EDT from smashbot64 Subject: Re: Citadel in Docker (prototype repo URL?)

github was too costly? lol... the source is out there, someone just has to volunteer to maintain

Sun May 23 2021 14:11:13 EDT from IGnatius T Foobar Subject: Re: Citadel in Docker (prototype repo URL?)

some (long) time ago I expressed my interest in trying out Citadel within a Docker container and someone here pointed me to some repository where some sort of "prototype" was available. Now, I have lost that particular link and am now asking if anyone here can (once more) provide it to me?

We ended up going in a different direction.  Instead of Docker, we built an AppImage, which just had its first beta release a couple of days ago.

AppImage, as you may know, packages an entire complex application and all of its dependencies into a single executable file that runs on many different Linux versions.  It turns out we had to change a lot of things that were based on outdated assumptions to make this happen.  For example, we ended support for the LFHS-style build and now require everything in a single directory.  These changes ought to make it a lot easier to put Citadel and its dependencies into a container, but as previously noted, we are not currently working on that.

Go ahead and try the AppImage if it can satisfy your requirements.

 

Search should be pretty easy because there is already a full text indexer built into the message store.

As for the public repositories ... Citadel pre-dates them all, so we've always managed it ourselves.  Our public "forge" is at https://code.citadel.org/

I encountered this same authentication problem with version 931 built via easy-install.  I think the problem is with citadel/modules/smtp/serv_smtp.c where smtp_get_user(5) is called in smtp_command_loop.  From this context, the offset parameter 5 should be replaced by zero (0).  I modified the easy-install script to work with a patched copy of the tarball and the resulting build seems to work correctly.

I've had to abandon my HMAIL server (Windows XP PRO issues activating)

I have installed a Debian system with Citadel. I am looking to do some relaying of email from specific IP addresses from old devices that cannot handle auth.

Is it possible thru Citadel and can it be done via the web manager? Or will it have to be done via CLI?

Planning on standing up a Citadel at our makerspace

How much support is still in the current version for dialup modems?

CDL

Planning on standing up a Citadel at our makerspace

How much support is still in the current version for dialup modems?

CDL

Sure, ill try both :)

Sat Jun 05 2021 11:07:16 AM EDT from IGnatius T Foobar Subject: Re: AppImage releases of Citadel

You should be able to run the 32 bit image on a 64 bit board. In fact, I would love it if you could try that.

On the BPI M3 ->  ./citadel-1622326264-armv7l.appimage: error while loading shared libraries: libz.so: cannot open shared object file: No such file or directory

Sorry, exact error on the Jetson ->  bash: ./citadel-1622326264-armv7l.appimage: No such file or directory

Figured its better than over here than in announcements.. 

Findings so far. ( all ARM )

• In general 32bit images apparently wont run on 64bit Armbian or Ubuntu.  Just as a test i grabbed cura 32 bit for RPI and get the same inaccurate message "No such file or directory" i got with 32bit citadel on 64bit board.
• 32bit image on 32bit Armbian gives me the same error regardless of cura or citadel:   AppImage: error while loading shared libraries: libz.so: cannot open shared object file: No such file or directory
• I also tried 64 bit cura on 64bit Armbian, and got the same libZ message as i got on 32/32. So that also must be a Appimage thing. I woudl have expected those libraries to come from inside the image.  I do have libz installed, so i must research.   Once i sort that i suspect matching image to architecture will work.
• I wonder if this is all due to the builds being built "for" RPI and mine being another OS.  Part of research to be done.

Hey guys! I was successfully able to install Citadel a few days ago using the Easy Install process, as outlined in the documentation/installation instructions. It was quite an easy install and worked perfectly. I later deleted the three folders as mentioned in the docs since I wanted to test out some other software. I inevitably came to the conclusion the Citadel would be the best for me to use... I installed it again using the same process, but now I get the following error: "didn't find Template [login] 5 5". The Javascript console also shows that favicon.ico is "net::ERR_EMPTY_RESPONSE". I have tried re-installing about 3 times and it happens each time. I have tried reboots and  it still does not work. I am using a Raspberry Pi 2 Model B+ with Raspberry Pi OS 32-bit Lite. Thanks in advance!

Installing zlib1g-dev fixes the lib error when platform matches appimage. odd you have to do that on the host, shouldn't that all be packaged in the image? 

Just a warning i have NOT looked into this more yet. It starts, crashes and then repeats tying indefinitely.  I had this same issue with Armbian bullseye on the 32bit BPI but i figured i should put it back to buster and try it again.

This was running from a direct root login via ssh, not sudo/shell. Command line included.  

______________________

root@bananapim3:~# ./citadel-1622326264-armv7l.appimage run

ctdlvisor: Welcome to the Citadel System, brought to you using AppImage.

ctdlvisor: LD_LIBRARY_PATH = /tmp/.mount_citadegxy60w/usr/lib

ctdlvisor:            PATH = /tmp/.mount_citadegxy60w/usr/bin

ctdlvisor:          APPDIR = /tmp/.mount_citadegxy60w

ctdlvisor:  data directory = /usr/local/citadel

ctdlvisor:       HTTP port = 80

ctdlvisor:      HTTPS port = 443

ctdlvisor: citserver running on pid=2355

ctdlvisor: executing /tmp/.mount_citadegxy60w/usr/local/citadel/citserver with data directory /usr/local/citadel

ctdlvisor: webcit (HTTP) running on pid=2356

ctdlvisor: executing /tmp/.mount_citadegxy60w/usr/local/webcit/webcit

ctdlvisor: webcit (HTTPS) running on pid=2357

ctdlvisor: executing /tmp/.mount_citadegxy60w/usr/local/webcit/webcit

ctdlvisor: pid=2355 exited, status=139, exitcode=0

ctdlvisor: citserver crashed on signal 11

ctdlvisor: citserver running on pid=2358

ctdlvisor: executing /tmp/.mount_citadegxy60w/usr/local/citadel/citserver with data directory /usr/local/citadel

ctdlvisor: pid=2358 exited, status=139, exitcode=0

ctdlvisor: citserver crashed on signal 11

after killing it witha control-c:

^Cctdlvisor: caught signal 2

ctdlvisor: waiting for all child process to exit...

ctdlvisor: 2367 (Citadel Server) ended, status=139

ctdlvisor: waiting for all child process to exit...

ctdlvisor: 2356 (WebCit HTTP) ended, status=15

ctdlvisor: waiting for all child process to exit...

ctdlvisor: 2357 (WebCit HTTPS) ended, status=15

ctdlvisor: waiting for all child process to exit...

ctdlvisor: exit code 0

It must be me. somehow. I forgot i had an old PI 2 in a drawer ( was for BeePI emulator but sort of lost interest and dismissed it out of my head ). 

Current Raspbian 'lite'.. SSH over, sudo to a shell. Create the data folder.  Grab the rile via wget. Change permissions..... 'run'.. It didnt need the extra stuff the BPI needed. But same results, except it eventually died on its own ( perhaps i didnt wait long enough on the BPI ).   It dont like me.    *pout*