Language:
switch to room list switch to menu My folders
Go to page: First ... 26 27 28 29 [30] 31
[#] Fri Nov 20 2020 00:21:14 EST from ParanoidDelusions @ Uncensored

Subject: Re: Corrupted attachments

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

So, I have a question... 

When I first tried to install on Raspbian - the easy-install documentation on Citadel.org didn't work for Raspbian - and I wrote up the document, attached, to show how I got it to work. 

Are you using a web document that *isn't* from Citadel.org to get the easy-install to work, and if so, is it the same documentation as I've attached? 

Because - it could simply be that I missed something in my install document - and that is why we're all seeing the same issue, if that is the case. 

Thu Nov 19 2020 22:36:41 EST from jtbreazeoutlook.com @ Uncensored Subject: Re: Corrupted attachments

I'm doing easyinstall.

Thu Nov 19 2020 09:05:36 PM EST from warbaby @ Uncensored Subject: Re: Corrupted attachments

> Is there even a en_US webcit.mo file

Not in the current webcit head. Consider

https://www.citadel.org/webcit_built_successfull_with_locale_support_but_it_s_nailed_to_one.html

Just to clarify, are these packages you're using, or are you doing easyinstall?

 

Thu Nov 19 2020 08:56:30 PM EST from jtbreazeoutlook.com @ Uncensored Subject: Re: Corrupted attachments

I think I have the issue narrowed down to a locale issue. I have now have the server running on a completely different Pi with a different OS (switched from Raspbian to Ubuntu Mate) and used sendcommand to migrate the server, and after re-installing the server again on the new pi through easyinstall, AND reset the local of Ubuntu, which took about 2 days. Since this didn't fix my issue, I dove into the locale files on webcit, which are NOT where they say they should be in the documentation, I only have en_GB, no en_US files, so, no webcit.mo file to be found, so I can't match the locale of webcit to the locale of my server that it stores files on. Could this be the issue? Is there even a en_US webcit.mo file I could find somewhere? The documentation seems to refer to that being a thing.

Tue Nov 17 2020 05:54:13 PM EST from jtbreazeoutlook.com @ Uncensored Subject: Re: Corrupted attachments

I'm encountering this issue now too. Sorry for adding an extra post with the same exact issue, it took me a while to figure out how to search this thread. I'm using a Pi 4, brand new, new SD card, and new install it Citadel, used the easy install. Everything else is working great, and email attachments leave the server OK, but coming in is when they get corrupted. I did that text file thing to view, and I got similar results. When it left, it was 115 bytes, and when it arrived it was 162 bytes. 

File contents when sent: The quick brown fox jumps over the lazy dog. Now is the time for all good men to come to the aid of their country.

File contents when arrived: The quick brown fox jumps over the lazy dog. Now is the tÿö–ÖRf÷"ÆÂvööBÖVâFò6öÖRFòF†R–BöbF†V—"6÷VçG'’ïÿ

Ÿÿ

So, what can we do about this? I've got some users that need their PDF files pronto, and I need a fix asap.
Tue Aug 25 2020 09:21:21 EDT from alex007 @ Uncensored Subject: Re: Corrupted attachments

it has something to do with character encoding I think.

My editor gedit says, that the original file I sent ist UTF-8 encoded, the file I downloaded with webcit is ISO 8859-15 encoded. See the files attached.

Does this only occur for German installations ?

 

Mon Aug 24 2020 10:22:18 EDT from phaake37 @ Uncensored Subject: Re: Corrupted attachments

All,

 

Did this ever get resolved?  I just tried this on my Citadel Server (Raspberry PI 3B+) and my text file produced:

 

TEXT
TEXT
TEXT
TEXT
TEXT
1234
1234
1234
1234
123ÿó@Ð

 

the Original:

TEXT
TEXT
TEXT
TEXT
TEXT
1234
1234
1234
1234
1234

So it appears to be something with appending to the file or? 

 

Any ideas?

Thanks!

 

 

Sat May 09 2020 23:13:54 EDT from warbaby @ Uncensored Subject: Re: Corrupted attachments

You might try a few more text uploads with various strings and see if there is any consistency with the char length.  

You might try creating some new files with a text editor and see how they look after a reboot.

I predict it is going to be failing Chink SD card writes, rather than a problem with Citadel. 

Or at least, replacing the Chink SD card would be my first approach, since that's a more widely known problem. 

Who knows all the various ways they fail? It might not be a total failure, just not writing properly.

Sometimes you can edit and save a file, it looks okay if you cat it out, but shows garbage after rebooting.

 

Sat May 09 2020 06:58:25 PM EDT from MAS3 @ Uncensored Subject: Re: Corrupted attachments

Thanks for the suggestion.

I created a small file, containing this text:

 

This is a text file created by the standard windows text editor.
It is not a large file, but i'm sure it will be corrupted once it's sent.

So let's see what will happen to it.

 

And this was what was received in the attachment (i'm not sure it will show exactly as i received due to the corruption)
Hmm seems there's more to it, as the font size has changed after copy / paste, and indentation was added:

 

This is a text file created by the standard windowsüÑ•áЁ•‘¥Ñ½È¸4)%Ё¥Ì¹½Ð„±…ɝ”™¥±”°‰ÕЁ¤´ÍÕÉ—ò—Bv–ÆÂ&R6÷''WFVBöæ6R—Bw26VçBàРХ6òÆWBw2?ÙYHÚ]Ú[\[ˆÈ]ƒBþ¾



 



 



 



(, 0 bytes) [View| Download]
(, 0 bytes) [View| Download]

 



(, 0 bytes) [View| Download]
(, 0 bytes) [View| Download]

 



(, 0 bytes) [View| Download]
(, 0 bytes) [View| Download]

 



(, 0 bytes) [View| Download]
(, 0 bytes) [View| Download]

 



(, 0 bytes) [View| Download]
(, 0 bytes) [View| Download]

 



blub2.txt (text/plain, 95 bytes) [View| Download]
blub2webcit.txt (text/plain, 99 bytes) [View| Download]
PiSetupV01.docx (application/vnd.openxmlformats-officedocument.wordprocessingml.document, 2222244 bytes) [ View | Download ]
[#] Fri Nov 20 2020 00:34:12 EST from jtbreazeoutlook.com @ Uncensored

Subject: Re: Corrupted attachments

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

That's not quite the steps I had to take, though I did follow the guide on pimylifeup more than I did the citadel.org one, since the former had an easier-to-follow guide for spamassassin and clamav. I didn't have to set up a user before I did the easyinstall, that's always worked for me, on Raspbian or Ubuntu Mate, but I still got the same issue on either OS. 

Fri Nov 20 2020 12:21:14 AM EST from ParanoidDelusions @ Uncensored Subject: Re: Corrupted attachments

So, I have a question... 

When I first tried to install on Raspbian - the easy-install documentation on Citadel.org didn't work for Raspbian - and I wrote up the document, attached, to show how I got it to work. 

Are you using a web document that *isn't* from Citadel.org to get the easy-install to work, and if so, is it the same documentation as I've attached? 

Because - it could simply be that I missed something in my install document - and that is why we're all seeing the same issue, if that is the case. 

Thu Nov 19 2020 22:36:41 EST from jtbreazeoutlook.com @ Uncensored Subject: Re: Corrupted attachments

I'm doing easyinstall.

Thu Nov 19 2020 09:05:36 PM EST from warbaby @ Uncensored Subject: Re: Corrupted attachments

> Is there even a en_US webcit.mo file

Not in the current webcit head. Consider

https://www.citadel.org/webcit_built_successfull_with_locale_support_but_it_s_nailed_to_one.html

Just to clarify, are these packages you're using, or are you doing easyinstall?

 

Thu Nov 19 2020 08:56:30 PM EST from jtbreazeoutlook.com @ Uncensored Subject: Re: Corrupted attachments

I think I have the issue narrowed down to a locale issue. I have now have the server running on a completely different Pi with a different OS (switched from Raspbian to Ubuntu Mate) and used sendcommand to migrate the server, and after re-installing the server again on the new pi through easyinstall, AND reset the local of Ubuntu, which took about 2 days. Since this didn't fix my issue, I dove into the locale files on webcit, which are NOT where they say they should be in the documentation, I only have en_GB, no en_US files, so, no webcit.mo file to be found, so I can't match the locale of webcit to the locale of my server that it stores files on. Could this be the issue? Is there even a en_US webcit.mo file I could find somewhere? The documentation seems to refer to that being a thing.

Tue Nov 17 2020 05:54:13 PM EST from jtbreazeoutlook.com @ Uncensored Subject: Re: Corrupted attachments

I'm encountering this issue now too. Sorry for adding an extra post with the same exact issue, it took me a while to figure out how to search this thread. I'm using a Pi 4, brand new, new SD card, and new install it Citadel, used the easy install. Everything else is working great, and email attachments leave the server OK, but coming in is when they get corrupted. I did that text file thing to view, and I got similar results. When it left, it was 115 bytes, and when it arrived it was 162 bytes. 

File contents when sent: The quick brown fox jumps over the lazy dog. Now is the time for all good men to come to the aid of their country.

File contents when arrived: The quick brown fox jumps over the lazy dog. Now is the tÿö–ÖRf÷"ÆÂvööBÖVâFò6öÖRFòF†R–BöbF†V—"6÷VçG'’ïÿ

Ÿÿ

So, what can we do about this? I've got some users that need their PDF files pronto, and I need a fix asap.
Tue Aug 25 2020 09:21:21 EDT from alex007 @ Uncensored Subject: Re: Corrupted attachments

it has something to do with character encoding I think.

My editor gedit says, that the original file I sent ist UTF-8 encoded, the file I downloaded with webcit is ISO 8859-15 encoded. See the files attached.

Does this only occur for German installations ?

 

Mon Aug 24 2020 10:22:18 EDT from phaake37 @ Uncensored Subject: Re: Corrupted attachments

All,

 

Did this ever get resolved?  I just tried this on my Citadel Server (Raspberry PI 3B+) and my text file produced:

 

TEXT
TEXT
TEXT
TEXT
TEXT
1234
1234
1234
1234
123ÿó@Ð

 

the Original:

TEXT
TEXT
TEXT
TEXT
TEXT
1234
1234
1234
1234
1234

So it appears to be something with appending to the file or? 

 

Any ideas?

Thanks!

 

 

Sat May 09 2020 23:13:54 EDT from warbaby @ Uncensored Subject: Re: Corrupted attachments

You might try a few more text uploads with various strings and see if there is any consistency with the char length.  

You might try creating some new files with a text editor and see how they look after a reboot.

I predict it is going to be failing Chink SD card writes, rather than a problem with Citadel. 

Or at least, replacing the Chink SD card would be my first approach, since that's a more widely known problem. 

Who knows all the various ways they fail? It might not be a total failure, just not writing properly.

Sometimes you can edit and save a file, it looks okay if you cat it out, but shows garbage after rebooting.

 

Sat May 09 2020 06:58:25 PM EDT from MAS3 @ Uncensored Subject: Re: Corrupted attachments

Thanks for the suggestion.

I created a small file, containing this text:

 

This is a text file created by the standard windows text editor.
It is not a large file, but i'm sure it will be corrupted once it's sent.

So let's see what will happen to it.

 

And this was what was received in the attachment (i'm not sure it will show exactly as i received due to the corruption)
Hmm seems there's more to it, as the font size has changed after copy / paste, and indentation was added:

 

This is a text file created by the standard windowsüÑ•áЁ•‘¥Ñ½È¸4)%Ё¥Ì¹½Ð„±…ɝ”™¥±”°‰ÕЁ¤´ÍÕÉ—ò—Bv–ÆÂ&R6÷''WFVBöæ6R—Bw26VçBàРХ6òÆWBw2?ÙYHÚ]Ú[\[ˆÈ]ƒBþ¾



 



 



 



(, 0 bytes) [View| Download]
(, 0 bytes) [View| Download]

 



(, 0 bytes) [View| Download]
(, 0 bytes) [View| Download]

 



(, 0 bytes) [View| Download]
(, 0 bytes) [View| Download]

 



(, 0 bytes) [View| Download]
(, 0 bytes) [View| Download]

 



(, 0 bytes) [View| Download]
(, 0 bytes) [View| Download]

 



(, 0 bytes) [View| Download]
(, 0 bytes) [View| Download]

 



blub2webcit.txt (text/plain, 99 bytes) [View| Download]
blub2.txt (text/plain, 95 bytes) [View| Download]
PiSetupV01.docx (application/vnd.openxmlformats-officedocument.wordprocessingml.document, 2222244 bytes) [ View | Download ]
[#] Fri Nov 20 2020 00:34:13 EST from ParanoidDelusions @ Uncensored

Subject: Re: Corrupted attachments

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

Somewhat related - I read that document, and I remember getting deeply into figuring out Raspbian and how it works with Citadel in order to get it up and running with the Telnet client installed. I ended up really putting together several different docs to make one, repeatable method that worked for the install. None of the other documents out there were quite complete...  

But reading it now, it is like some other person who actually knows what they're doing in Linux wrote that. I've forgotten most of what I wrote there - so, if you read the document and have questions about it - I might be useless in providing any details. 



[#] Sat Nov 21 2020 16:54:33 EST from jtbreazeoutlook.com @ Uncensored

Subject: Re: Corrupted attachments

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

So, if those locale files were only for the package install, and not easyinstall, how to I check that the easyinstall is using the correct locale? I re-ran the install after ensuring that my Ubuntu install was on the correct install using UTF-8, en_US, but incomming attachments are still corrupting, seemingly to an ISO locale, I can't remember the numbers now, but I can get them if it would help.



[#] Sun Nov 22 2020 00:08:38 EST from palloy @ Uncensored

Subject: install not working

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

Ubuntu_20.04 Server + LXDE desktop


I had citadel running here a couple of years ago, and remember needing to do some administering and getting stuck.


I downloaded and ran the easy-installer, checked for listening ports, got 80 and 443, so went in Firefox to localhost (no other name has been given),
and got " This program was unable to connect or stay connected to the Citadel server. Please report this problem to your system administrator.
Read More..."  The "read more" was a link which didn't work.
So I tried "https://localhost",  getting the same response.
I looked in the documentation, and nothing there applied.

So I followed the instructions on how to delete the package, and then installed from the Ubuntu repo package.
Getting  the version of the package didn't work, so I can't tell you what it is.
Still the same error message from Firefox.

Apache2 configuration isn't what I was expecting.  The only file in /etc/apache2/ is /etc/apache2/conf-available/javascript-common.conf:
====
Alias /javascript /usr/share/javascript/

<Directory "/usr/share/javascript/">
    Options FollowSymLinks MultiViews
</Directory>
====
I doubt that that would work, but I'm only guessing.
So does the Ubuntu repository have a non-working version ?
How do I make it work ?

I then noticed that the CPU usage was high enough to drive it to 100C, but HTOP and lxtask said 0% usage.

That seemed like a rootkit, so I tried running rkhunter, but that wouldn't run.

So I reinstalled the OS, installed citadel-suite again, and hours later got the same error in Firefox.

I need help.



[#] Sun Nov 22 2020 16:48:58 EST from sanlybowits @ Uncensored

Subject: easyinstall .... "301 Moved Permanently"

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

I was sorry to see that "curl"ing the build/install script from the "easyinstall" page results in "301 Moved Permanently"

I expect that might be around the many broken links from new hosting that I read about on 'uncensored' recently.  But, if there is a functional link, I'd like to know so I can try that.  Additionally, the link to the hosted version control is broken too with a 404 Not Found.  I'll see if I can't assemble a working system from the other code links that are working.

Can someone conjure up links to installer scripts and/or repository, please?



[#] Sun Nov 22 2020 16:59:08 EST from warbaby @ Uncensored

Subject: Re: easyinstall .... "301 Moved Permanently"

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

Broken links and the new hosting have no relationship.. But there is a lot is going on today, so expect that people are working on things. Whatever you're running into is likely very temporary.

If you want you can go back a few messages in the Support room to "HOW TO: Quickly make a build directory and compile citadel & webcit" [Nov 19th]

The latest easyinstall.sh and the new version with the -k --keep (retain source) is attached to that message. 

Everything else is to my knowledge working.  If I find out any different, I will post something here.

 

Sun Nov 22 2020 04:48:58 PM EST from sanlybowits @ Uncensored Subject: easyinstall .... "301 Moved Permanently"

I was sorry to see that "curl"ing the build/install script from the "easyinstall" page results in "301 Moved Permanently"

I expect that might be around the many broken links from new hosting that I read about on 'uncensored' recently.  But, if there is a functional link, I'd like to know so I can try that.  Additionally, the link to the hosted version control is broken too with a 404 Not Found.  I'll see if I can't assemble a working system from the other code links that are working.

Can someone conjure up links to installer scripts and/or repository, please?



 



[#] Sun Nov 22 2020 17:24:05 EST from sanlybowits @ Uncensored

Subject: Re: easyinstall .... "301 Moved Permanently"

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

Ah!  I can pull the file from the url alone with wget.  But the commands with curl and wget, as posted, on this page (https://www.citadel.org/easyinstall.html) was giving me no love.

I've gotten the script down now.  Thanks!



[#] Sun Nov 22 2020 18:24:02 EST from sanlybowits @ Uncensored

Subject: Re: easyinstall .... "301 Moved Permanently"

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

Ah!  I can pull the file from the url alone with wget.  But the commands with curl and wget, as posted, on this page (https://www.citadel.org/easyinstall.html) was giving me no love.

I've gotten the script down now.  Thanks!



[#] Sun Nov 22 2020 18:49:56 EST from warbaby @ Uncensored

Subject: Re: easyinstall .... "301 Moved Permanently"

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

sure thing my friend.

Sun Nov 22 2020 06:24:02 PM EST from sanlybowits @ Uncensored Subject: Re: easyinstall .... "301 Moved Permanently"

Ah!  I can pull the file from the url alone with wget.  But the commands with curl and wget, as posted, on this page (https://www.citadel.org/easyinstall.html) was giving me no love.

I've gotten the script down now.  Thanks!



 



[#] Sun Nov 22 2020 19:18:34 EST from sanlybowits @ Uncensored

Subject: Re: easyinstall .... "301 Moved Permanently"

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

works like a champ! so far....



[#] Mon Nov 23 2020 11:53:02 EST from hamiltra @ Uncensored

Subject: Error with easyinstaller build on Ubuntu 20.10 with fresh install

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

I did a fresh install of Ubuntu 20.10 (amd64) and tried the citadel-suite without success.  it was a very old version 917 which was throwing a lot of segfault messages into the syslog.  Uninstalled that version and did some cleanup.  Then, I tried the build from scratch using easyinstall shell and to keep the files as was posted in this forum last week, but then I got an error:

/usr/bin/ld: modules/xmpp/serv_xmpp.o:/usr/src/citadel-build.4621/citadel/./threads.h:27: multiple definition of `ThreadKey'; server_main.o:/usr/src/citadel-build.4621/citadel/threads.h:27: first defined here
/usr/bin/ld: modules/xmpp/xmpp_messages.o:/usr/src/citadel-build.4621/citadel/./threads.h:27: multiple definition of `ThreadKey'; server_main.o:/usr/src/citadel-build.4621/citadel/threads.h:27: first defined here
/usr/bin/ld: modules/xmpp/xmpp_presence.o:/usr/src/citadel-build.4621/citadel/./threads.h:27: multiple definition of `ThreadKey'; server_main.o:/usr/src/citadel-build.4621/citadel/threads.h:27: first defined here
/usr/bin/ld: modules/xmpp/xmpp_query_namespace.o:/usr/src/citadel-build.4621/citadel/./threads.h:27: multiple definition of `ThreadKey'; server_main.o:/usr/src/citadel-build.4621/citadel/threads.h:27: first defined here
/usr/bin/ld: modules/xmpp/xmpp_queue.o:/usr/src/citadel-build.4621/citadel/./threads.h:27: multiple definition of `ThreadKey'; server_main.o:/usr/src/citadel-build.4621/citadel/threads.h:27: first defined here
/usr/bin/ld: modules/xmpp/xmpp_sasl_service.o:/usr/src/citadel-build.4621/citadel/./threads.h:27: multiple definition of `ThreadKey'; server_main.o:/usr/src/citadel-build.4621/citadel/threads.h:27: first defined here
/usr/bin/ld: ldap.o:/usr/src/citadel-build.4621/citadel/threads.h:27: multiple definition of `ThreadKey'; server_main.o:/usr/src/citadel-build.4621/citadel/threads.h:27: first defined here
/usr/bin/ld: netconfig.o:/usr/src/citadel-build.4621/citadel/./threads.h:27: multiple definition of `ThreadKey'; server_main.o:/usr/src/citadel-build.4621/citadel/threads.h:27: first defined here
collect2: error: ld returned 1 exit status
gmake: *** [Makefile:134: citserver] Error 1
 Citadel Easy Install is aborting.
 The last few lines above this message may indicate what went wrong.
 Linux Debian bullseye/sid( 5.8.0-29-generic x86_64)

Please advise next steps...



[#] Mon Nov 23 2020 17:11:36 EST from palloy @ Uncensored

Subject: Re: install not working

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

OK, that's what I got too on ubuntu-20.04.

So with the easy-installer not working on Ubuntu-20.04 and -20.10, and the Ubuntu repository version not working on -20.04 and -20.20, how do you expect Ubuntu users to install Citadel ?

How come nobody can answer my question in 2 days ?



[#] Mon Nov 23 2020 23:38:01 EST from hamiltra @ Uncensored

Subject: Re: install not working

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

Two changes are needed to get this going:

in webcit: context_loop.c:

Comment out the line around line 28:

/* hamiltra */
//pthread_key_t MyConKey;         /* TSD key for MySession() */                                                                                    

The second change that I needed to do is in citadel sources:

on or near line 27, add estern...

extern pthread_key_t ThreadKey;

I believe that the source of the issue may be because Ubuntu is using newer gcc and/or make.

Citadel is built now and now can proceed with my testing...

Mon Nov 23 2020 17:11:36 EST from palloy @ Uncensored Subject: Re: install not working

OK, that's what I got too on ubuntu-20.04.

So with the easy-installer not working on Ubuntu-20.04 and -20.10, and the Ubuntu repository version not working on -20.04 and -20.20, how do you expect Ubuntu users to install Citadel ?

How come nobody can answer my question in 2 days ?



 



[#] Tue Nov 24 2020 00:32:57 EST from jtbreazeoutlook.com @ Uncensored

Subject: Re: Corrupted attachments

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

I finally am getting the hang of the sendcommand, and now believe the locale is correct. However, I'm still having corrupt attachment issues and it's getting frustrating. I found the citadel.rc file, but does that only pertain to the package install, or something? Because it has a value in it for allow_attachments=0, which would disable attachments, but, I changed it to 1, and it didn't change anything, even when I rebooted, AND ran the easyinstall again.

Would I be better off getting off the Pi and onto an x86-based server to host Citadel on? I have a few slying around, it's just big, and I wanted the Pi form factor, but at this point I'll take functioning attachments over space. Is the attachment corruption thing that I and a few other Pi users have noted only happening on Pi's?

Just looking for a solution here asap.

Sat Nov 21 2020 04:54:33 PM EST from jtbreazeoutlook.com @ Uncensored Subject: Re: Corrupted attachments

So, if those locale files were only for the package install, and not easyinstall, how to I check that the easyinstall is using the correct locale? I re-ran the install after ensuring that my Ubuntu install was on the correct install using UTF-8, en_US, but incomming attachments are still corrupting, seemingly to an ISO locale, I can't remember the numbers now, but I can get them if it would help.



 



[#] Tue Nov 24 2020 01:49:23 EST from warbaby @ Uncensored

Subject: Re: Corrupted attachments

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

> Would I be better off getting off the Pi and onto an x86-based server to host Citadel on?

Absolutely. Without a doubt. Not sure what the Pi issue is, I'm having someone ship some hardware.  We'll get to the bottom of it eventually..

But why wait?  CItadel works great and is rock stable, not needing to be fussed with for years at a time.

A working mail server is worth throwing some hardware at.  The Raspberry Pi is really more of a novelty.

You've proven you can do it, now put together a real box, with some decent hardware.

The only distro i'd avoid is OpenSuse, there are some issues with the default shell that make installation a hassle.

But other than that, you can probably get easyinstall to run on anything.  

Debian 10 is a safe and sane choice.  Grab the iso with non-free if you have proprietary network interfaces.

 



[#] Tue Nov 24 2020 02:03:58 EST from jtbreazeoutlook.com @ Uncensored

Subject: Re: Corrupted attachments

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

Great, thanks for the quick reply. I'm liking Ubuntu for the server OS, with the more current repositories, so I'll definitely be staying away from OpenSuse. I'll be keeping an eye on future updates, so I can switch back to the pi, though, it was working great otherwise, there aren't enough users with enough demand to overtax the 4 B, I was sitting at just over 1gb of ram use, and 10% cpu. I'm sold on Citadel, for sure. 

Tue Nov 24 2020 01:49:23 AM EST from warbaby @ Uncensored Subject: Re: Corrupted attachments

> Would I be better off getting off the Pi and onto an x86-based server to host Citadel on?

Absolutely. Without a doubt. Not sure what the Pi issue is, I'm having someone ship some hardware.  We'll get to the bottom of it eventually..

But why wait?  CItadel works great and is rock stable, not needing to be fussed with for years at a time.

A working mail server is worth throwing some hardware at.  The Raspberry Pi is really more of a novelty.

You've proven you can do it, now put together a real box, with some decent hardware.

The only distro i'd avoid is OpenSuse, there are some issues with the default shell that make installation a hassle.

But other than that, you can probably get easyinstall to run on anything.  

Debian 10 is a safe and sane choice.  Grab the iso with non-free if you have proprietary network interfaces.

 



 



[#] Tue Nov 24 2020 07:44:55 EST from ParanoidDelusions @ Uncensored

Subject: Re: Corrupted attachments

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

 

Tue Nov 24 2020 02:03:58 ESTfrom jtbreazeoutlook.com @ Uncensored Subject: Re: Corrupted attachments

Great, thanks for the quick reply. I'm liking Ubuntu for the server OS, with the more current repositories, so I'll definitely be staying away from OpenSuse. I'll be keeping an eye on future updates, so I can switch back to the pi, though, it was working great otherwise, there aren't enough users with enough demand to overtax the 4 B, I was sitting at just over 1gb of ram use, and 10% cpu. I'm sold on Citadel, for sure.

 


I'm running a Citadel at https://secure.wallofhate.com on a Pi 3B+ with Raspbian. It is a public BBS with Internet mail disabled. It runs fine for most of these purposes. 

I haven't had a chance to try the suggestions above on a new install to see if I can address the issues I see with attachments in messages getting corrupted. nor do I know if the issues I am seeing are related to your issues with attachment corruption - but it sure seems like there is something similar going on. I'm not completely concerned with file attachment corruption - as my goal is more to have a bulletin board for communication and discussion as an alternative social media destination. But, as soon as I get done with my current batch of projects - I intend to give it a try. 

Like you, the form factor of the Pi is ideal, and I have considered just throwing up a "real" non-Arm Linux distro on one of the mini-ATX form factor small PCs I have lying around doing nothing. It seems like if the Pi can handle it, even a Centrino or Atom based machine should be able to handle Citadel. That led me to consider a NUC, but a NUC is going to run me around $200 for the low end - and I'm not really sure that the low end outperforms a Pi 4B, at this point... that decision quickly became a series of trade offs I wasn't ecstatic about. The space I have for the BBS to live requires something Pi or NUC sized to live there, and I can't easily relocate it all because of the way my Host ISP provides a static IP address. 

But if you have a spare Intel system, like I do... nothing prevents you from building out Citadel on a IA Linux and seeing if that fixes the problems - and if it does, then you know it is something specific to the Pi architecture or the Pi Linux - and you can consider buying a NUC if small footprint is critical to you. For me, if it comes down to my users not being able to download files or add attachments or dropping $200+ for a NUC - they can live with the deficiencies of a Pi for this. 

I mean, ideally we would figure out what the problem is on the Pi - but - building an Intel system might be the best first step. If it happens *there*, it seems to be some kind of operator error. If it doesn't... it is on the Pi architecture or Distro. 



[#] Tue Nov 24 2020 07:47:42 EST from ParanoidDelusions @ Uncensored

Subject: Re: Corrupted attachments

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

You can feel free to log into my BBS and use the mail subsystem to attach documents and see if they corrupt. If you do, try posting a public message with an attachment to see if that works, too, and you might as well upload a file in a directory room too. 

If you can recreate the same issue on my BBS as on yours - maybe opening a bug report with your distro could help too. It would provide evidence it is the distro or the Pi, not Citadel. 



[#] Tue Nov 24 2020 12:04:34 EST from warbaby @ Uncensored

Subject: Re: Corrupted attachments

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

> I'm liking Ubuntu for the server OS, with the more current repositories

See the recent message thread: "Error with easyinstaller build on Ubuntu 20.10 with fresh install"

Greybeard system administrator here.  Latest/greatest is not always an advantage. Not if you value your time. Stay in the middle of the road, and compile or upgrade packages as needed with a ppa.

A mail server admin should think conservatively.  Ubuntu is guided by a commercial company that likes to chase rainbows. That ain't a good match.  Fun if you are messing around on the desktop, but not what anybody wants in a server OS. They continually make short-sighted decisions that break things..

Most intelligent people I know unhitched from that wagon long ago.  Experienced dev-ops people left Ubuntu Server about a decade ago, because Canonical doesn't listen, and can't control themselves from jacking around with the Server packages.   This is why you can install what should be a small, simple, stand-alone utility, and end up with 50 new packages + Apache2 as a dependency.

They constantly cause problems like the one in the email thread above.

Tue Nov 24 2020 07:44:55 AM EST from ParanoidDelusions @ Uncensored Subject: Re: Corrupted attachments

 

Tue Nov 24 2020 02:03:58 ESTfrom jtbreazeoutlook.com @ Uncensored Subject: Re: Corrupted attachments

Great, thanks for the quick reply. I'm liking Ubuntu for the server OS, with the more current repositories, so I'll definitely be staying away from OpenSuse. I'll be keeping an eye on future updates, so I can switch back to the pi, though, it was working great otherwise, there aren't enough users with enough demand to overtax the 4 B, I was sitting at just over 1gb of ram use, and 10% cpu. I'm sold on Citadel, for sure.

 


I'm running a Citadel at https://secure.wallofhate.com on a Pi 3B+ with Raspbian. It is a public BBS with Internet mail disabled. It runs fine for most of these purposes. 

I haven't had a chance to try the suggestions above on a new install to see if I can address the issues I see with attachments in messages getting corrupted. nor do I know if the issues I am seeing are related to your issues with attachment corruption - but it sure seems like there is something similar going on. I'm not completely concerned with file attachment corruption - as my goal is more to have a bulletin board for communication and discussion as an alternative social media destination. But, as soon as I get done with my current batch of projects - I intend to give it a try. 

Like you, the form factor of the Pi is ideal, and I have considered just throwing up a "real" non-Arm Linux distro on one of the mini-ATX form factor small PCs I have lying around doing nothing. It seems like if the Pi can handle it, even a Centrino or Atom based machine should be able to handle Citadel. That led me to consider a NUC, but a NUC is going to run me around $200 for the low end - and I'm not really sure that the low end outperforms a Pi 4B, at this point... that decision quickly became a series of trade offs I wasn't ecstatic about. The space I have for the BBS to live requires something Pi or NUC sized to live there, and I can't easily relocate it all because of the way my Host ISP provides a static IP address. 

But if you have a spare Intel system, like I do... nothing prevents you from building out Citadel on a IA Linux and seeing if that fixes the problems - and if it does, then you know it is something specific to the Pi architecture or the Pi Linux - and you can consider buying a NUC if small footprint is critical to you. For me, if it comes down to my users not being able to download files or add attachments or dropping $200+ for a NUC - they can live with the deficiencies of a Pi for this. 

I mean, ideally we would figure out what the problem is on the Pi - but - building an Intel system might be the best first step. If it happens *there*, it seems to be some kind of operator error. If it doesn't... it is on the Pi architecture or Distro. 



 



Go to page: First ... 26 27 28 29 [30] 31