Language:
switch to room list switch to menu My folders
Go to page: 1 2 [3] 4 5 6 7 ... Last
[#] Tue Jan 24 2017 09:46:48 EST from dovzamir @ Uncensored

Subject: invalid recipient - node name in email address

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

Hi all,

I just installed Citadel and am having trouble with email addresses of my local users. My address should be dov at mydomain.com but for some reason I can only send mail if I add the nodename (mail.mydomain.com). Mail is getting into the system but is not being displayed to the user.

Any suggestions?

I am running under ubuntu 14.04 LTS with citadel ver. 8.24.



[#] Tue Jan 24 2017 09:51:44 EST from warbaby @ Uncensored

Subject: Re: Issue with "Primary Internet e-mail address" and aliases.-

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

The addresses listed in Advanced > Update Your Contact Information (textarea) are used for Return-Path (composing/sending)

If you want to receive mail at an alias, edit  the file

/usr/local/citadel/network/mail.aliases

(or wherever your installer put citadel's mail.aliases) and add an entry.  

<alias>,<actual_box>

eg:

support,bill

grandmasterfllash@altdomain, ted

 

etc...

 

If you are using an alternate mail client, create a 'identity' for the alias, so you can choose how you will send the mail (eg, Return-Path)

 



Tue Jan 24 2017 05:33:51 AM EST from jcigala @ Uncensored Subject: Issue with "Primary Internet e-mail address" and aliases.-

I aren't receive email for several email aliases. In Webcit, when I look in "Advanced > Update your contact information" I see how the "Primary Internet e-mail address" change, taking any given address from the "Internet e-mail aliases" box. When I try to correct the Primary address in order to put it my email (which isn't in the Aliases box), I click "Save changes" and re-enter in the "Update..." page, my email are changing again for any given address from the Aliases box. Worst of all, I don't receive emails in none of the address on the Aliases box.

I am receiving email in my Primary address, of course the same as my account name + the domain -even if the email address has changed in the "Primary Internet e-mail address" text box.

Recently, I migrated to a new server, exactly the same operating system than previous (CentOS 7.3) and I installed (easy install) Citadel in the new server and then copy the previous /citadel directory into it. Before this, I updated the old Citadel to the last version -the same in both server.

What can I do? Thanks!



 



[#] Tue Jan 24 2017 15:13:51 EST from cituser2017 @ Uncensored

Subject: Segfault first run

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

Errormessage after run citserver

 

segfault at 10000014c ip 00007f3f12bf89d1 sp 00007ffceed65bb0 error 4 in libdb-5.3.so

 

pls. help

 

beste regards



[#] Tue Jan 24 2017 16:34:17 EST from cituser2017 @ Uncensored

Subject: Re: Segfault first run

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

this is complete run:

 

citserver[11678]: *** Citadel server engine ***
citserver[11678]: Version 906 (build 408a64d) ***
citserver[11678]: Copyright (C) 1987-2017 by the Citadel development team.
citserver[11678]: This program is distributed under the terms of the GNU General Public License.
citserver[11678]:
citserver[11678]: Called as: /usr/local/citadel/citserver
citserver[11678]: libcitadel(unnumbered)
citserver[11678]: Creating lockfile
citserver[11678]: master_startup() started
citserver[11678]: Checking directory access
citserver[11678]: Opening databases
citserver[11678]: bdb(): open_databases() starting
citserver[11678]: Compiled db: Berkeley DB 5.3.28: (March 31, 2016)
citserver[11678]:   Linked db: Berkeley DB 5.3.28: (September  9, 2013)
citserver[11678]: Linked zlib: 1.2.8
citserver[11678]: bdb(): Setting up DB environment
citserver[11678]: dbenv->open(dbenv, /usr/local/citadel/data/, 75043, 0)
citserver[11678]: DB: BDB2526 Finding last valid log LSN: file: 1 offset 121684
citserver[11678]: DB: BDB1514 Recovery starting from [1][28]
citserver[11678]: DB: BDB1518 Recovery complete at Tue Jan 24 22:31:21 2017
citserver[11678]: DB: BDB1519 Maximum transaction ID 8000001c recovery checkpoint [1][122846]
citserver[11678]: Starting up DB
citserver[11678]: Initializing configuration system

[1]+  Segmentation fault      /usr/local/citadel/citserver

 

journalctl -f:

kernel: citserver[11678]: segfault at 10000014c ip 00007f25d8c319d1 sp 00007fff98c6fd90 error 4 in libdb-5.3.so[7f25d8b27000+1bf000]

 

 



[#] Tue Jan 24 2017 16:55:37 EST from cituser2017 @ Uncensored

Subject: Re: Segfault first run

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

This happened at "make":

 

CC database.c
database.c: In function ‘cdb_store’:
database.c:514:12: warning: assignment discards ‘const’ qualifier from pointer target type [enabled by default]
  dkey.data = ckey;
            ^
database.c: In function ‘cdb_fetch’:
database.c:661:12: warning: assignment discards ‘const’ qualifier from pointer target type [enabled by default]
  dkey.data = key;
            ^
CC domain.c



modules/calendar/serv_calendar.c: In function ‘ical_send_out_invitations’:
modules/calendar/serv_calendar.c:2151:6: warning: passing argument 1 of ‘icaltimezone_get_tzid’ discards ‘const’ qualifier from pointer target type [enabled by default]
      icalparameter_new_tzid(icaltimezone_get_tzid(z))
      ^
In file included from modules/calendar/serv_calendar.c:21:0:
/usr/include/libical/ical.h:3356:13: note: expected ‘struct icaltimezone *’ but argument is of type ‘const struct icaltimezone *’
 const char* icaltimezone_get_tzid   (icaltimezone *zone);
             ^
modules/calendar/serv_calendar.c:2160:3: warning: passing argument 1 of ‘icaltimezone_get_component’ discards ‘const’ qualifier from pointer target type [enabled by default]
   zc = icalcomponent_new_clone(icaltimezone_get_component(attached_zones[i]));
   ^
In file included from modules/calendar/serv_calendar.c:21:0:
/usr/include/libical/ical.h:3374:16: note: expected ‘struct icaltimezone *’ but argument is of type ‘const struct icaltimezone *’
 icalcomponent* icaltimezone_get_component (icaltimezone *zone);
                ^
CC modules/checkpoint/serv_checkpoint.c




modules/migrate/serv_migrate.c: In function ‘migr_xml_end’:
modules/migrate/serv_migrate.c:685:27: warning: cast discards ‘__attribute__((const))’ qualifier from pointer target type [-Wcast-qual]
    CtdlSetConfigStr(ikey, (char *)ChrPtr(migr_chardata));
                           ^
CC modules/mrtg/serv_mrtg.c



[#] Wed Jan 25 2017 10:42:58 EST from bennabiy @ Uncensored

Subject: Funny things happening with new citadel install

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

I just recently did an easy install with LDAP support (which is working, logins work etc) but for some reason I cannot edit the GAB entries as the Aide admin user, and I constantly have to stop the server, rerun setup telling it citadel for the user, and the citadel port (defaults to root and 0 ) .

 

Any thoughts?



[#] Wed Jan 25 2017 21:16:59 EST from bennabiy @ Uncensored

Subject: Re: Message on Restart

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

I too am getting the same message. I also notice that certain settings are being reset as well every time the citserver is restarted. 

Is there a way to make these changes permanent?



[#] Thu Jan 26 2017 02:26:30 EST from russellb234 @ Uncensored

Subject: ctdlmigrate

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

Hi all,

I've run into a problem I'd like to sort if possible.

I had citadel running on a raspberry pi for a couple of years, and it was pretty stable.

Recently I decided to move it to a surplus x86 box running Ubuntu 16.04.

I tried using the ctdlmigrate utility, and also using the

./sendcommand "MIGR export" >exported.xml to make a backup and re-import it.

I've ended up with a whole list of blank emails and errors showing in the logs such as
CC[575]MSGMessage 6593 appears to be corrupted.


It's not a vast problem if I don't recover the old messages, but I'd like to see if I can possibly do so.

I still have the SD-card with the raspian installation on it, and if necessary can put it in a ~pi for copying

Has anyone any advice other than "Abandon hope"?

Thanks in advance

Russell


[#] Thu Jan 26 2017 04:46:50 EST from hyperanalysis @ Uncensored

Subject: Re: Database Recovery Assistance

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

...any help with this from anyone please? :-(



[#] Thu Jan 26 2017 04:47:49 EST from hyperanalysis @ Uncensored

Subject: Re: Database Recovery Assistance

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

...with this I mean, sorry - can anyone give any pointers please?

Wed Jun 01 2016 05:40:37 EDT from hyperanalysis @ Uncensored Subject: Database Recovery Assistance

Greetings All,

Last night my server was accidentally restarted without shutting citadel down gracefully first. When it came back up citadel won't start, and it looks like my database is corrupt. I'm getting the following when attempting to restart the service:

citserver[3580]: cdb_fetch(9): BDB0075 DB_PAGE_NOTFOUND: Requested page not found

I've taken a backup copy of my data and logs directories, then attempted to run db_recover -cvf in the data directory, which gives me:
 
BDB2526 Finding last valid log LSN: file: 1 offset 28
 
I've also tried running the database_cleanup tool, which give me this:
 
Dumping cdb.00
db_dump: BDB0058 page 256: illegal page type or format
db_dump: BDB0061 PANIC: Invalid argument
db_dump: BDB0060 PANIC: fatal region error detected; run recovery
db_dump: BDB5117 close: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery
db_dump: BDB1581 File handles still open at environment close
db_dump: BDB1582 Open file handle: /mnt/md1/citadel/data/cdb.00
db_dump: BDB0060 PANIC: fatal region error detected; run recovery
db_dump: dbenv->close: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery
Exiting.
 
At this stage I'm a bit lost, the recovery tools tell me to run the recovery tools? :-(
 
Any and all help would be greatly appreciated!!!
 
Kind regards,
Iain.


 



[#] Sun Jan 29 2017 11:30:04 EST from bennabiy @ Uncensored

Subject: Downgrade from latest git to previous version?

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

Is it possible to downgrade from the latest git master to a previous tagged release (I am assuming not before release 902) to see if the bugs we are experiencing are due to the changes on the current master?

If I can fix these issues and help better the codebase, I would like to see that happen, but if not, I would like to revert back to a more stable situation. I am using LDAP as my authentication method, and I know it works because users are using it. 

My current issues are:

Global Address Book is unable to be edited by my aide user (the main admin account, not just a promoted aide). I am unable to make modifications to the information in the vcards.

I have attached a picture showing the display of the Global Address Book. I remember with previous versions that LDAP did not touch the GAB, and so it was not changed on each login by a client, but I noticed that even if I do update the GAB, once a client logs in, it reverts back.

 

Also, I currently cannot get certain configs to persist beyond a restart of citserver. I wonder if the changes are not making it to the database, but only persisiting in RAM. This includes things like Port number for the citadel networking, and settings like allowing self registration.

I have a few other issues, but if I could get these resolved it would make things leaps and bounds better.

 

Thank you.



Screenshot at 2017-01-25 22:13:18.png (image/png, 376733 bytes) [ View | Download ]
[#] Mon Jan 30 2017 13:45:04 EST from l-l @ Uncensored

Subject: Server hardening

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

I'm setting up a Citadel server more as a private webmail server (exposed to the internet, but only private accounts allowed anywhere but the login screen) and am looking for information on hardening the server.

In addition to any existing best practices out there (where?) these are the things I'm looking to change/configure:

  • Change login page to not identify the system in use.
  • Stop Webcit login failures from displaying the difference between an incorrect password and an unknown username (this allows dictionary like attacks to enumerate user accounts on the server for spamming or other nefarious purposes.
  • Locate any existing fail2ban filters for Webcit and or Citadel to identify and eliminate brute force attacks against the login page and/or e-mail services. I can write the regexes myself but prefer not to reinvent the wheel if it has...already been invented.
  • Other ways to prevent Webcit/Citadel from identifying itself via service banners, etc. (I haven't looked into this one much, so not sure how much there is to do)
  • Any other security oriented settings you can think of.

Thanks



[#] Mon Jan 30 2017 14:04:53 EST from warbaby @ Uncensored

Subject: Re: Server hardening

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

We should do some sharing of these fail2ban filters and talk about security. I have some things to share. This isn't probably the best place for it, developers mailing list probably not either..  I'll ask some of these gentlemen if we can get a citadel security list going.  But rather than just adding a public room here, I'd like to be able to post from my own client, so I don't have to log in to talk/answer questions.  If you want to talk in the meantime, hmu support@mailx3.com 

 

Mon Jan 30 2017 01:45:04 PM EST from l-l @ Uncensored Subject: Server hardening

I'm setting up a Citadel server more as a private webmail server (exposed to the internet, but only private accounts allowed anywhere but the login screen) and am looking for information on hardening the server.

In addition to any existing best practices out there (where?) these are the things I'm looking to change/configure:

  • Change login page to not identify the system in use.
  • Stop Webcit login failures from displaying the difference between an incorrect password and an unknown username (this allows dictionary like attacks to enumerate user accounts on the server for spamming or other nefarious purposes.
  • Locate any existing fail2ban filters for Webcit and or Citadel to identify and eliminate brute force attacks against the login page and/or e-mail services. I can write the regexes myself but prefer not to reinvent the wheel if it has...already been invented.
  • Other ways to prevent Webcit/Citadel from identifying itself via service banners, etc. (I haven't looked into this one much, so not sure how much there is to do)
  • Any other security oriented settings you can think of.

Thanks



 



[#] Mon Jan 30 2017 15:46:24 EST from l-l @ Uncensored

Subject: Re: Server hardening

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

Thanks, sounds good.

 

Mon Jan 30 2017 14:04:53 EST from warbaby @ Uncensored Subject: Re: Server hardening

We should do some sharing of these fail2ban filters and talk about security. I have some things to share. This isn't probably the best place for it, developers mailing list probably not either..  I'll ask some of these gentlemen if we can get a citadel security list going.  But rather than just adding a public room here, I'd like to be able to post from my own client, so I don't have to log in to talk/answer questions.  If you want to talk in the meantime, hmu support@mailx3.com 

 

Mon Jan 30 2017 01:45:04 PM EST from l-l @ Uncensored Subject: Server hardening

I'm setting up a Citadel server more as a private webmail server (exposed to the internet, but only private accounts allowed anywhere but the login screen) and am looking for information on hardening the server.

In addition to any existing best practices out there (where?) these are the things I'm looking to change/configure:

  • Change login page to not identify the system in use.
  • Stop Webcit login failures from displaying the difference between an incorrect password and an unknown username (this allows dictionary like attacks to enumerate user accounts on the server for spamming or other nefarious purposes.
  • Locate any existing fail2ban filters for Webcit and or Citadel to identify and eliminate brute force attacks against the login page and/or e-mail services. I can write the regexes myself but prefer not to reinvent the wheel if it has...already been invented.
  • Other ways to prevent Webcit/Citadel from identifying itself via service banners, etc. (I haven't looked into this one much, so not sure how much there is to do)
  • Any other security oriented settings you can think of.

Thanks



 



 



[#] Tue Jan 31 2017 13:12:46 EST from bennabiy @ Uncensored

Subject: Admin unable to set vcards etc

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

My admin user is able to make changes like adding floors etc, but is unable to make changes to users vcards (for setting aliases) in an LDAP environment.

Is there a way to look into the database at the settings directly, now that the configs are migrating into DB?

Also, users are unable to rename folders through IMAP client, or delete their mail folders.



[#] Fri Feb 03 2017 15:21:58 EST from Pingumann @ Uncensored

Subject: Mailng List does not first mail for new member

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

Hi all,

I want to join the mailing list. I entered the info and have not received a mail with a link to join.

Is it normal behaviour?

BR Pingumann



[#] Fri Feb 03 2017 15:32:26 EST from Pingumann @ Uncensored

Subject: Re: Mailng List does not send first mail for new member

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

 

Fri Feb 03 2017 15:21:58 EST from Pingumann @ Uncensored Subject: Mailng List does not first mail for new member

Hi all,

I want to join the mailing list. I entered the info and have not received a mail with a link to join.

Is it normal behaviour?

BR Pingumann



 



[#] Fri Feb 03 2017 17:38:50 EST from Pingumann @ Uncensored

Subject: Uninstall Citadel

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

Hi all,

Citadel installed on a Ubuntu 16.04: Linux version 4.4.0-042stab120.16 (root@kbuild-rh6-x64.eng.sw.ru) (gcc version 4.4.6 20120305 (Red Hat 4.4.6-4) (GCC) ) #1 SMP Tue Dec 13 20:58:28 MSK 2016, Ubuntu 16.04.1 LTS, xenial.

The quick install (sudo ./install.sh) was followd with all the defaults. At the very ast, it exited with the line that listening on 80 is already by another application.

As the configuration files to set up a virtual site for citadel.conf in the:

1. /var/www/vhosts/default/htdocs and in the

2. /etc/citadel

were configured for port 80, it was expected to be able to be set up for port 2000. Nothing changed. (sudo service apache2 restart was done).

No files were found in:

3. /etc/apache2/sites-available and

4. /etc/apache2/sites-enabled.

The default virtual setup of Ubuntu 16.04 uses this config. Citadell did something quit of its own. Note that apache was selected as webserver in the install.

Then "sudo apt remove citadel-suite" was done.

It was reported to be done, and after that "sudo apt purge citadel-suite", "sudo apt update", and "sudo apt autoremove" was run to clean the system.

A new installation was strted. None of the options selections were asked again as was in the very first installation. It just runs te installation without any questions or options selection.

How can the very first installation state be started again?

 

 



[#] Fri Feb 03 2017 17:49:20 EST from Pingumann @ Uncensored

Subject: Uninstall or re-config citadel

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

Hi all,


Citadel installed on a Ubuntu 16.04: Linux version 4.4.0-042stab120.16 (root@kbuild-rh6-x64.eng.sw.ru) (gcc version 4.4.6 20120305 (Red Hat 4.4.6-4) (GCC) ) #1 SMP Tue Dec 13 20:58:28 MSK 2016, Ubuntu 16.04.1 LTS, xenial.


At the very last, it exited with the line that listening on 80 is already by another application.


As the configuration files to set up a virtual site for citadel.conf in the:


1. /var/www/vhosts/default/htdocs and in the
2. /etc/citadel


were configured for port 80, it was expected to be able to be set up for port 2000. Nothing changed. (sudo service apache2 restart was done).

No files regarding citadel were found in:


3. /etc/apache2/sites-available and
4. /etc/apache2/sites-enabled.



The default virtual setup of Ubuntu 16.04 uses this config. Citadel did something quit of its own. Note that apache was selected as web-server in the install.
Then "sudo apt remove citadel-suite" was done.


It was reported to be done, and after that "sudo apt purge citadel-suite", "sudo apt update", and "sudo apt autoremove" was run to clean the system.
A new installation was started.


Then, none of the options and selections were asked as was in the very first installation. It just runs the installation without any questions or options selection.
It ends again without the errors about the port, but it cannot be reached because another app is using port 80.


How can the very first installation state be started again, or can the installation on Ubuntu 16.04 be configured to run on port 2000?



[#] Fri Feb 03 2017 17:57:06 EST from Pingumann @ Uncensored

Subject: IGNORE - Re: Uninstall Citadel

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

 

Fri Feb 03 2017 17:38:50 EST from Pingumann @ Uncensored Subject: Uninstall Citadel

Hi all,

Citadel installed on a Ubuntu 16.04: Linux version 4.4.0-042stab120.16 (root@kbuild-rh6-x64.eng.sw.ru) (gcc version 4.4.6 20120305 (Red Hat 4.4.6-4) (GCC) ) #1 SMP Tue Dec 13 20:58:28 MSK 2016, Ubuntu 16.04.1 LTS, xenial.

The quick install (sudo ./install.sh) was followd with all the defaults. At the very ast, it exited with the line that listening on 80 is already by another application.

As the configuration files to set up a virtual site for citadel.conf in the:

1. /var/www/vhosts/default/htdocs and in the

2. /etc/citadel

were configured for port 80, it was expected to be able to be set up for port 2000. Nothing changed. (sudo service apache2 restart was done).

No files were found in:

3. /etc/apache2/sites-available and

4. /etc/apache2/sites-enabled.

The default virtual setup of Ubuntu 16.04 uses this config. Citadell did something quit of its own. Note that apache was selected as webserver in the install.

Then "sudo apt remove citadel-suite" was done.

It was reported to be done, and after that "sudo apt purge citadel-suite", "sudo apt update", and "sudo apt autoremove" was run to clean the system.

A new installation was strted. None of the options selections were asked again as was in the very first installation. It just runs te installation without any questions or options selection.

How can the very first installation state be started again?

 

 

Please ignore. See next post.

 



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