Language:
switch to room list switch to menu My folders
Go to page: First ... 15 16 17 18 [19] 20
[#] Tue Oct 15 2019 15:00:40 EDT from branco @ Uncensored

Subject: Unable to bind ports..user rights issue?

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

Hi guys, 

I have recently installed Citadel using the easy install, everything appears to work except the opening of ports. 

When i start the server i get this message in the console:

 

citserver[1632]: extensions: Citadel had trouble on starting up. We couldn't bind all ports you configured to be provided by Citadel Server.

 This means, Citadel won't be the service provider for a specific service you configured it to.

 

If you don't want Citadel to provide these services, turn them off in WebCit via: "Admin->System Preferences->Network".

 

The failed ports and sockets are: extensions: TCP port 0.0.0.0:504: (citadel-TCP) ;extensions: TCP port 0.0.0.0:143: (IMAP) ;extensions: TCP port 0.0.0.0:993: (IMAPS) ;extensions: TCP port 0.0.0.0:119: (NNTP) ;extensions: TCP port 0.0.0.0:563: (NNTPS) ;extensions: TCP port 0.0.0.0:110: (POP3) ;extensions: TCP port 0.0.0.0:995: (POP3S) ;extensions: TCP port 0.0.0.0:25: (SMTP-MTA) ;extensions: TCP port 0.0.0.0:587: (SMTP-MSA) 

 

If you want Citadel to provide you with that functionality, check the output of "netstat -lnp" on Linux, or "netstat -na" on BSD and disable the program that binds these ports.

To make both ways actualy take place restart the citserver with "sendcommand down"

 

The errors returned by the system were:

Can't bind: Permission denied; Can't bind: Permission denied; Can't bind: Permission denied; Can't bind: Permission denied; Can't bind: Permission denied; Can't bind: Permission denied; Can't bind: Permission denied; Can't bind: Permission denied; Can't bind: Permission denied

 

 

Is this a user rights issue? I created the user citadel during the installation process and gave it ownership of the entire /usr/local/citadel folder.

Web interface works fine and I've setup all required ports there, but it looks like citadel is not listening on any of them:

Active Internet connections (only servers)

Proto Recv-Q Send-Q Local Address           Foreign Address         State      

tcp        0      0 127.0.0.1:6010          0.0.0.0:*               LISTEN     

tcp        0      0 0.0.0.0:2020            0.0.0.0:*               LISTEN     

tcp        0      0 0.0.0.0:5222            0.0.0.0:*               LISTEN     

tcp        0      0 127.0.0.53:53           0.0.0.0:*               LISTEN     

tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN     

tcp6       0      0 ::1:6010                :::*                    LISTEN     

tcp6       0      0 :::443                  :::*                    LISTEN     

tcp6       0      0 :::80                   :::*                    LISTEN     

tcp6       0      0 :::22                   :::*                    LISTEN     

udp        0      0 127.0.0.53:53           0.0.0.0:*                          

udp        0      0 172.31.46.125:68        0.0.0.0:*        

 

Any help will be greatly appreciated. 

 

Cheers, 

Branco

 

 

 



[#] Tue Oct 15 2019 16:28:24 EDT from warbaby @ Uncensored

Subject: Joe Biden Collapse/Missed Space Issue In Subject Line

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

[This is is an actual programming defect, not system support.  I am not currently on the dev list, so am posting here instead.. ]

SYNOPSIS:  Message with Subject Line greater than 69 characters sent via SMTP has all whitespace greedily left trimmed from 69th char to the next printable char.  Sometimes a space character is the intended character at Subject pos 69. 

SCOPE:  Universal. 

VERSION: Citadel 921, ezinstall 

OS: Debian 8 "Jessie"

STEPS TO REPRODUCE: Send yourself a message through your Citadel box via SMTP, with the following subject line:

01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01

You will see, upon it's arrival it appears as:

01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 0101 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01

This, like Joe Biden, shows the consistent collapse on any character count past 69, regardless of whether it is a space or tab.  Whitespace at or after position "69" is trimmed to the next printable character.  
 
Here is an example Subject Line with 10 extra spaces: 

01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01          01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01

it is returned as 

01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 0101 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01

This issue also occurs with tabs. I did not test for all possible white space characters. 

ATTEMPTS TO RESOLVE:
 
Tested for condition.  I looked at code but did not find. I do not have environment set up to compile at this time. 
 
 
THOUGHTS:
 
It's probably very near an isspace() where the "short subject string" with a length of 69 is strcat() back together with "rest of subject string." I would consider the addition of a single space between the two parts to be a good solution.   I don't have much of an expectation of using tabs, bells, or form feeds in subject lines, although I do frequently like to have a space appearing at offset 69.  For such an minor issue, it has had a very bad effect on my self-esteem. I've had to talk to people about it. In all my carefully crafted long subject lines, I appear to have a broken spacebar or to write like Joe Biden. Correspondingly, I am recommending a priority level of "VERY HIGH". 
 
 


[#] Tue Oct 15 2019 16:53:28 EDT from warbaby @ Uncensored

Subject: Re: Unable to bind ports..user rights issue?

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

kill apache or nginx or whatever you have listening on 80 and 443, then try to start it again. 

Tue Oct 15 2019 03:00:40 PM EDT from branco @ Uncensored Subject: Unable to bind ports..user rights issue?

Hi guys, 

I have recently installed Citadel using the easy install, everything appears to work except the opening of ports. 

When i start the server i get this message in the console:

 

citserver[1632]: extensions: Citadel had trouble on starting up. We couldn't bind all ports you configured to be provided by Citadel Server.

 This means, Citadel won't be the service provider for a specific service you configured it to.

 

If you don't want Citadel to provide these services, turn them off in WebCit via: "Admin->System Preferences->Network".

 

The failed ports and sockets are: extensions: TCP port 0.0.0.0:504: (citadel-TCP) ;extensions: TCP port 0.0.0.0:143: (IMAP) ;extensions: TCP port 0.0.0.0:993: (IMAPS) ;extensions: TCP port 0.0.0.0:119: (NNTP) ;extensions: TCP port 0.0.0.0:563: (NNTPS) ;extensions: TCP port 0.0.0.0:110: (POP3) ;extensions: TCP port 0.0.0.0:995: (POP3S) ;extensions: TCP port 0.0.0.0:25: (SMTP-MTA) ;extensions: TCP port 0.0.0.0:587: (SMTP-MSA) 

 

If you want Citadel to provide you with that functionality, check the output of "netstat -lnp" on Linux, or "netstat -na" on BSD and disable the program that binds these ports.

To make both ways actualy take place restart the citserver with "sendcommand down"

 

The errors returned by the system were:

Can't bind: Permission denied; Can't bind: Permission denied; Can't bind: Permission denied; Can't bind: Permission denied; Can't bind: Permission denied; Can't bind: Permission denied; Can't bind: Permission denied; Can't bind: Permission denied; Can't bind: Permission denied

 

 

Is this a user rights issue? I created the user citadel during the installation process and gave it ownership of the entire /usr/local/citadel folder.

Web interface works fine and I've setup all required ports there, but it looks like citadel is not listening on any of them:

Active Internet connections (only servers)

Proto Recv-Q Send-Q Local Address           Foreign Address         State      

tcp        0      0 127.0.0.1:6010          0.0.0.0:*               LISTEN     

tcp        0      0 0.0.0.0:2020            0.0.0.0:*               LISTEN     

tcp        0      0 0.0.0.0:5222            0.0.0.0:*               LISTEN     

tcp        0      0 127.0.0.53:53           0.0.0.0:*               LISTEN     

tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN     

tcp6       0      0 ::1:6010                :::*                    LISTEN     

tcp6       0      0 :::443                  :::*                    LISTEN     

tcp6       0      0 :::80                   :::*                    LISTEN     

tcp6       0      0 :::22                   :::*                    LISTEN     

udp        0      0 127.0.0.53:53           0.0.0.0:*                          

udp        0      0 172.31.46.125:68        0.0.0.0:*        

 

Any help will be greatly appreciated. 

 

Cheers, 

Branco

 

 

 



 



[#] Tue Oct 15 2019 18:08:18 EDT from branco @ Uncensored

Subject: Unable to bind ports..user rights issue?

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

Hi guys, 

I have recently installed Citadel using the easy install, everything appears to work except the opening of ports. 

When i start the server i get this message in the console:

 

citserver[1632]: extensions: Citadel had trouble on starting up. We couldn't bind all ports you configured to be provided by Citadel Server.

 This means, Citadel won't be the service provider for a specific service you configured it to.

 

If you don't want Citadel to provide these services, turn them off in WebCit via: "Admin->System Preferences->Network".

 

The failed ports and sockets are: extensions: TCP port 0.0.0.0:504: (citadel-TCP) ;extensions: TCP port 0.0.0.0:143: (IMAP) ;extensions: TCP port 0.0.0.0:993: (IMAPS) ;extensions: TCP port 0.0.0.0:119: (NNTP) ;extensions: TCP port 0.0.0.0:563: (NNTPS) ;extensions: TCP port 0.0.0.0:110: (POP3) ;extensions: TCP port 0.0.0.0:995: (POP3S) ;extensions: TCP port 0.0.0.0:25: (SMTP-MTA) ;extensions: TCP port 0.0.0.0:587: (SMTP-MSA) 

 

If you want Citadel to provide you with that functionality, check the output of "netstat -lnp" on Linux, or "netstat -na" on BSD and disable the program that binds these ports.

To make both ways actualy take place restart the citserver with "sendcommand down"

 

The errors returned by the system were:

Can't bind: Permission denied; Can't bind: Permission denied; Can't bind: Permission denied; Can't bind: Permission denied; Can't bind: Permission denied; Can't bind: Permission denied; Can't bind: Permission denied; Can't bind: Permission denied; Can't bind: Permission denied

 

 

Is this a user rights issue? I created the user citadel during the installation process and gave it ownership of the entire /usr/local/citadel folder.

Web interface works fine and I've setup all required ports there, but it looks like citadel is not listening on any of them:

Active Internet connections (only servers)

Proto Recv-Q Send-Q Local Address           Foreign Address         State      

tcp        0      0 127.0.0.1:6010          0.0.0.0:*               LISTEN     

tcp        0      0 0.0.0.0:2020            0.0.0.0:*               LISTEN     

tcp        0      0 0.0.0.0:5222            0.0.0.0:*               LISTEN     

tcp        0      0 127.0.0.53:53           0.0.0.0:*               LISTEN     

tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN     

tcp6       0      0 ::1:6010                :::*                    LISTEN     

tcp6       0      0 :::443                  :::*                    LISTEN     

tcp6       0      0 :::80                   :::*                    LISTEN     

tcp6       0      0 :::22                   :::*                    LISTEN     

udp        0      0 127.0.0.53:53           0.0.0.0:*                          

udp        0      0 172.31.46.125:68        0.0.0.0:*        

 

Any help will be greatly appreciated. 

 

Cheers, 

Branco

 

 

 



[#] Tue Oct 15 2019 18:09:48 EDT from branco @ Uncensored

Subject: Re: Unable to bind ports..user rights issue?

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

Ports 80 and 443 are fine, i can connect to WebCit, and there is no apache or nginx - clean ubuntu server install. 

The issue are the other mail ports (265, 143, 587, etc)

 

BR, 

 

Branco

Tue Oct 15 2019 16:53:28 EDT from warbaby @ Uncensored Subject: Re: Unable to bind ports..user rights issue?

kill apache or nginx or whatever you have listening on 80 and 443, then try to start it again. 

Tue Oct 15 2019 03:00:40 PM EDT from branco @ Uncensored Subject: Unable to bind ports..user rights issue?

Hi guys, 

I have recently installed Citadel using the easy install, everything appears to work except the opening of ports. 

When i start the server i get this message in the console:

 

citserver[1632]: extensions: Citadel had trouble on starting up. We couldn't bind all ports you configured to be provided by Citadel Server.

 This means, Citadel won't be the service provider for a specific service you configured it to.

 

If you don't want Citadel to provide these services, turn them off in WebCit via: "Admin->System Preferences->Network".

 

The failed ports and sockets are: extensions: TCP port 0.0.0.0:504: (citadel-TCP) ;extensions: TCP port 0.0.0.0:143: (IMAP) ;extensions: TCP port 0.0.0.0:993: (IMAPS) ;extensions: TCP port 0.0.0.0:119: (NNTP) ;extensions: TCP port 0.0.0.0:563: (NNTPS) ;extensions: TCP port 0.0.0.0:110: (POP3) ;extensions: TCP port 0.0.0.0:995: (POP3S) ;extensions: TCP port 0.0.0.0:25: (SMTP-MTA) ;extensions: TCP port 0.0.0.0:587: (SMTP-MSA) 

 

If you want Citadel to provide you with that functionality, check the output of "netstat -lnp" on Linux, or "netstat -na" on BSD and disable the program that binds these ports.

To make both ways actualy take place restart the citserver with "sendcommand down"

 

The errors returned by the system were:

Can't bind: Permission denied; Can't bind: Permission denied; Can't bind: Permission denied; Can't bind: Permission denied; Can't bind: Permission denied; Can't bind: Permission denied; Can't bind: Permission denied; Can't bind: Permission denied; Can't bind: Permission denied

 

 

Is this a user rights issue? I created the user citadel during the installation process and gave it ownership of the entire /usr/local/citadel folder.

Web interface works fine and I've setup all required ports there, but it looks like citadel is not listening on any of them:

Active Internet connections (only servers)

Proto Recv-Q Send-Q Local Address           Foreign Address         State      

tcp        0      0 127.0.0.1:6010          0.0.0.0:*               LISTEN     

tcp        0      0 0.0.0.0:2020            0.0.0.0:*               LISTEN     

tcp        0      0 0.0.0.0:5222            0.0.0.0:*               LISTEN     

tcp        0      0 127.0.0.53:53           0.0.0.0:*               LISTEN     

tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN     

tcp6       0      0 ::1:6010                :::*                    LISTEN     

tcp6       0      0 :::443                  :::*                    LISTEN     

tcp6       0      0 :::80                   :::*                    LISTEN     

tcp6       0      0 :::22                   :::*                    LISTEN     

udp        0      0 127.0.0.53:53           0.0.0.0:*                          

udp        0      0 172.31.46.125:68        0.0.0.0:*        

 

Any help will be greatly appreciated. 

 

Cheers, 

Branco

 

 

 



 



 



[#] Wed Oct 16 2019 03:51:23 EDT from TheOneLaw @ Uncensored

Subject: Re: Unable to bind ports..user rights issue?

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

As I am having a related problem,

the question arises - does rebooting the system affect the port bindings ?

the reason I ask is that my system binds ports okay only on system boot
 but anytime I use the "restart now" inside webcit > administration citserver abandons everything.

( ports 80 and 443 are bound by webcit, not citserver)

Tue Oct 15 2019 18:09:48 EDT from branco @ Uncensored Subject: Re: Unable to bind ports..user rights issue?

Ports 80 and 443 are fine, i can connect to WebCit, and there is no apache or nginx - clean ubuntu server install. 

The issue are the other mail ports (265, 143, 587, etc)

 

BR, 

 

Branco

 

 



 



 



[#] Wed Oct 16 2019 12:25:48 EDT from TheOneLaw @ Uncensored

Subject: Re: STARTTLS on SMTP port 25

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

Looks like a Houdini moment.

In exasperation issued the STARTTLS command into a telnet test and the response was:

root@myoldmail:~# telnet xx.xx.xxx.xxx 25
Trying xx.xx.xxx.xxx...
Connected to xx.xx.xxx.xxx.
Escape character is '^]'.
220 mynewmail.org ESMTP Citadel server ready.
ehlo home
250-Hello home (xx.xx.xxx.xxx [xx.xx.xxx.xxx])
250-HELP
250-SIZE 10485760
250-AUTH LOGIN PLAIN
250-AUTH=LOGIN PLAIN
250 8BITMIME
STARTTLS
220 Begin TLS negotiation now
^C

huh.

If so then the only thing missing is the advertisement,

250 STARTTLS

 which may be just a cosmetic requirement ?:

According to ssl-tools.net the STARTTLS is working as needed but this is dubious - no email was 250actually sent..

Some method to require encryption for all inbound might be nice but not sure if that is even realistic...

 

Mon Oct 14 2019 15:57:06 EDT from TheOneLaw @ Uncensored Subject: Re: STARTTLS on SMTP port 25

STARTTLS also missing

on DEBIAN BUSTER via easy-install.

 

wondering if this implicates anything important:

(from Debian stretch effort)

/usr/bin/ld: warning: libssl.so.1.0.2, needed by /usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/libcurl.so, may conflict with libssl.so.1.1
/usr/bin/ld: warning: libcrypto.so.1.0.2, needed by /usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/libcurl.so, may conflict with libcrypto.so.1.1



 



[#] Wed Oct 16 2019 13:55:39 EDT from TheOneLaw @ Uncensored

Subject: Re: STARTTLS on SMTP port 25

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

Looks like port 25 has STARTTLS but nobody uses it due to the missing line?:

....citserver[519]: context: session (SMTP-MTA) started from ssl-tools.net...

Bail...

Wed Oct 16 2019 12:25:48 EDT from TheOneLaw @ Uncensored Subject: Re: STARTTLS on SMTP port 25

Looks like a Houdini moment.

In exasperation issued the STARTTLS command into a telnet test and the response was:

root@myoldmail:~# telnet xx.xx.xxx.xxx 25
Trying xx.xx.xxx.xxx...
Connected to xx.xx.xxx.xxx.
Escape character is '^]'.
220 mynewmail.org ESMTP Citadel server ready.
ehlo home
250-Hello home (xx.xx.xxx.xxx [xx.xx.xxx.xxx])
250-HELP
250-SIZE 10485760
250-AUTH LOGIN PLAIN
250-AUTH=LOGIN PLAIN
250 8BITMIME
STARTTLS
220 Begin TLS negotiation now
^C

huh.

If so then the only thing missing is the advertisement,

250 STARTTLS

 which may be just a cosmetic requirement ?:

According to ssl-tools.net the STARTTLS is working as needed but this is dubious - no email was 250actually sent..

Some method to require encryption for all inbound might be nice but not sure if that is even realistic...

 



[#] Thu Oct 17 2019 08:51:01 EDT from TheOneLaw @ Uncensored

Subject: SMTP MSA on Port 25 serving SMTP MTA inbound connections

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

I was truly hoping this would not be necessary,

but it does appear that

c3rebro2

found the best answer which simply looks like this:

 

 

It does seem to work with most of the mail servers I need to receive from,

now they choose to use encryption during SMTP connections,

unlike how they connected on the MTA port - bareskin naked with no encryption at all.

Works for now, hope this helps someone.

 

 

 Sat Jun 08 2019 18:14:39 EDT from c3rebro2 @ Uncensored

Yeah - you're right. Maybe i should have left it alone.

I now reverted all changes (restored a full server backup after the -self modified- install scripts messed up the system with several changes).

The final solution currently looks really weird to me but seem to work:

 

- Network configuration: I re-mapped my msa port 587 to the mta port 25 in the wan to lan rules.

- In Citadel: i disabled the mta port 25 completely and changed the msa port to 25.

 

I have really no clue if this is how it is supposed to be. but: if i now send a mail to myself from e.g. gmail, gmx or company account i can see the starttls init procedure which was missing before. Iam really too lazy to switch to a postfix, dovecot and roundcube setup (including migration of gigs of mail data).



 



[#] Tue Oct 22 2019 12:27:48 EDT from simon2371 @ Uncensored

Subject: Re: Citadel stop working BDB0075 DB_PAGE_NOTFOUND

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

Thank you.Its works!!



[#] Wed Oct 23 2019 03:36:16 EDT from madadam @ Uncensored

Subject: ctdlmigrate problem

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

Hi,

I have a nicely working citadel (824)  on a RaspberryPi (raspbian, jessie).

Trying to migrate to freshly installed citadel (917) on PC (x86_64, Ubuntu 18.04).

It all seems to go well, apart from some inconsequential locale warnings, but it ends with "*** Citadel migration was unsuccessful. ***". See the attached screenlog.txt.

syslog:
 citserver[1873]: sysdep: client_read_blob() failed: StrBufReadBLOBBuffered: to many selects; aborting.

Is there any way of circumventing this without having to change the code?

Thanks,
Marge



screenlog.txt (text/plain, 5769 bytes) [View| Download]
[#] Wed Oct 23 2019 05:32:52 EDT from troyjmaj @ Uncensored

Subject: is ip6 the problem ?

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

i did this 

 sudo netstat -nltp |grep cit

tcp6       0      0 :::504                  :::*                    LISTEN      25620/./citserver

tcp6       0      0 :::9080                 :::*                    LISTEN      14644/webcit

tcp6       0      0 :::25                   :::*                    LISTEN      25620/./citserver

tcp6       0      0 :::993                  :::*                    LISTEN      25620/./citserver

tcp6       0      0 :::995                  :::*                    LISTEN      25620/./citserver

tcp6       0      0 :::2020                 :::*                    LISTEN      25620/./citserver

tcp6       0      0 :::5222                 :::*                    LISTEN      25620/./citserver

tcp6       0      0 :::110                  :::*                    LISTEN      25620/./citserver

tcp6       0      0 :::143                  :::*                    LISTEN      25620/./citserver

tcp6       0      0 :::465                  :::*                    LISTEN      25620/./citserver

tcp6       0      0 :::563                  :::*                    LISTEN      25620/./citserver

tcp6       0      0 :::9043                 :::*                    LISTEN      1176/webcit

tcp6       0      0 :::119                  :::*                    LISTEN      25620/./citserver

is there a way can get it to listen on both ip6 AND ip4 ??
 
thank you in advance 
 
troy johnston


[#] Fri Oct 25 2019 11:27:11 EDT from FrostyBison @ Uncensored

Subject: How to hide alternate authentication buttons on the login page

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

I will be demoing Citadel as a potential groupware application for an Amateur Radio club and need some help tailoring what webcit displays to meet our needs.

This installation will be accessed over an isolated radio network which, due to FCC rules, can not use encryption. I've successfully disabled encrypted services such as HTTPS, IMAPS, etc.

We don't need the authentication selector buttons (internal, openid, google, yahoo, etc) on the login page since we can only use the internal method.

How can I hide or remove the authentication selection buttons?



[#] Fri Oct 25 2019 11:40:42 EDT from FrostyBison @ Uncensored

Subject: Re: How to hide alternate authentication buttons on the login page

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

How can I hide or remove the authentication selection buttons?


As usual I found the solution immediately after posing a question. It turns out I need to edit /usr/local/webcit/static/r/get_logged_in.html


[#] Fri Oct 25 2019 23:40:21 EDT from troyjmaj @ Uncensored

Subject: calanders

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

is there a way to export the calanders in citadel to regular html / php ??

 

thanks in advance for your help 

 

 



[#] Mon Oct 28 2019 12:34:28 EDT from FrostyBison @ Uncensored

Subject: Clues about corrupted file attachments

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

Here are some results from attaching an image (PNG) and an ASCII file to room messages:
My browser could not display the attached image. Clicking the "view" link in the message returned a "The image ... cannot be displayed because it contains errors" message. I downloaded the attached image and compared it to the original:



steve@hydra:~/Downloads$ ls -l sk*
-rw-r--r-- 1 steve steve 74280 Oct 28 10:49 sk-1920x1080-overscan.png

-rw-r--r-- 1 steve steve 73202 Sep 28 07:42 sk-1920x1080-overscan.png-org

steve@hydra:~/Downloads$ md5sum sk*
86c05857c070c2e18f081a26e46d936d sk-1920x1080-overscan.png
2f2a9a1170ae29a6d5a85b42874d3b19 sk-1920x1080-overscan.png-orig

steve@hydra:~/Downloads$



So what came out is not the same as what went in.
Attempting to view the image with the Imagemagick display utility threw this error:
steve@hydra:~/Downloads$ display sk-1920x1080-overscan.png
display-im6.q16: pHYs: CRC error `sk-1920x1080-overscan.png' @ warning/png.c/MagickPNGWarningHandler/1654.

display-im6.q16: [1D][D1][25][35]: invalid chunk type `sk-1920x1080-overscan.png' @ error/png.c/MagickPNGErrorHandler/1628.
display-im6.q16: corrupt image `sk-1920x1080-overscan.png' @ error/png.c/ReadPNGImage/3991


The ASCII test file showed this difference:
steve@hydra:~$ diff /tmp/ascii-test-file Downloads/ascii-test-file
1c1
< Mon Oct 28 10:56:01 CDT 2019
---
Mon Oct 28 10:56:01 CDT 2019o?=
\ No newline at end of file
steve@hydra:~$

Hope this is useful.

System details:
Citadel 927, WebCit 925, server build 927 from a recent easy install
Raspbian 10.1 (updated before the easy install)

[#] Tue Oct 29 2019 13:45:01 EDT from AMacleod @ Uncensored

Subject: 550 Error

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

Hi, I have a Citadel server running for one particular domain, call it a.com, which works fine.  For convenience, I have the same server set to permit b.com (hosted on GSuite) as a "Masqueradable domain" - this also works fine.

What I cannot do is send email from b.com (the masqueradable domain) to a.com (hosted locally on Citadel.)  The email is bounced with error 550 "You must log in to send mail from b.com"

Is there any way around this issue?

Thanks,

AJ



[#] Tue Oct 29 2019 18:44:05 EDT from calcmandan @ Uncensored

Subject: What is the current released version

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

Hi folks

I've been hosting my own mail server for a few years now and I've been a bad bad boy. Haven't patched her up once. She was installed using easy install but it just has to be out of date, or I'm crazy.

Currently I'm running Citadel 911 with WebCit 904, server build 911

I'm looking for a resource on the website that shows the currently available version.

I've been bad, and thusly need to figure out how to update the system.



[#] Wed Oct 30 2019 16:07:20 EDT from FrostyBison @ Uncensored

Subject: Re: What is the current released version

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

I'm not sure where that version information can be found at citadel.org

But I can tell you that my easy-install on October 25th left me with Citadel 927 with WebCit 925, server build 927.



[#] Wed Oct 30 2019 17:44:22 EDT from IGnatius T Foobar @ Uncensored

Subject: Re: What is the current released version

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

Yup. Just stop your Citadel server, take a *good* backup, and run Easy Install again. You'll be upgraded to the newest and best version. Enjoy!

Go to page: First ... 15 16 17 18 [19] 20