Language:
switch to room list switch to menu My folders
Go to page: First ... 14 15 16 17 [18] 19 20 21 22 ... Last
[#] Mon Feb 26 2018 12:49:46 EST from EDIS @ Uncensored

Subject: Server Migration

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

Hi there!

I'm trying to migrate a citadel server from one server to another. I was trying to use the replication utility, but couldn't find any real documentation on it.

 

I can re-configure the useres and such if I need to, I just need to move all the emails over.

 

Thanks in advance for your help!



[#] Mon Feb 26 2018 12:51:57 EST from bobdoe @ Uncensored

Subject: Re: Unable to connect pidgin to citadel server

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

 

Mon Feb 26 2018 12:28:50 PM EST from IGnatius T Foobar @ Uncensored Subject: Re: Unable to connect pidgin to citadel server
Citadel XMPP honors the 'starttls' command to upgrade a non-encrypted connection to an encrypted connection. I'm surprised to hear that there are clients which cannot be configured to ignore certificate trust errors, but if that is the case, there are a number of places offering free SSL certificates now, so you can try-before-you-buy.

Citadel Server and WebCit both follow the same procedure for auto-generating a certificate at startup if you haven't supplied one:

1. If there is no private key, one is generated.
2. A certificate signing request (CSR) is generated using that key.
3. If there is no public certificate, a self-signed certificate is generated using the key and CSR.

If you are applying to a certificate authority for a "real" certificate, the generated key will be fine to use, but the CSR will probably have incorrect information in it. Here's a quick rundown of what you need to do, for Citadel or any other software which needs an SSL certificate.

1. Generate a key with a command like:
openssl genrsa -out citadel.key 2048

2. Generate a certificate signing request:
openssl req -new -key citadel.key -out citadel.csr
Answer all prompts carefully!

3. Submit your CSR to the certificate authority of your choice. When they supply your signed certificate, they will likely indicate to you that there are one or more intermediate certificates that must be included. Create a file called "citadel.cer" containing your server's certificate, followed by the intermediate certificate(s).

4. Restart citserver. Connect to it and see if it works.

WebCit is the same way, except the filenames are webcit.[key|csr|cer] instead of citadel.[key|csr|cer]. It's probably easier to test with WebCit first, since you can easily verify it with your web browser, and then copy the files over to Citadel after testing.
You can and should use the same key/cert for both programs.

In the future we will be looking into implementing the Let's Encrypt framework to automatically obtain and install free SSL certificates, but that is some way off at this point. In the mean time I'm pleased to see that the number of options for trial and short term SSL certificates at no cost has increrased.

Thanks very much for answering.

As I previously mentioned, I have already reviewed -more than once- the documents at citadel.org site, so I was already well aware of what you just explained. Sorry if I didn't mention it earlier.

Just wanted to mention this before keeping trying a few more possible stuff. Somewhere in Pidgin site I had read it can actually handle self-signed or untrusted certificates just well; it just didn't say how to. I was about to search again there but the site is currently down...

From the docs and what you just explained, I'd guess Citadel currently lacks self-signed certificate support at least for XMPP...



[#] Mon Feb 26 2018 12:58:55 EST from EDIS @ Uncensored

Subject: Re: Server Migration

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

Note: i've seen the page that says not to use the replication function for this. The other suggested methods don't seem to have worked.



[#] Mon Feb 26 2018 16:09:59 EST from IGnatius T Foobar @ Uncensored

Subject: Re: Unable to connect pidgin to citadel server

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

From the docs and what you just explained, I'd guess Citadel currently lacks self-signed certificate support at least for XMPP...

Well ... not quite.  It's not really an issue specific to XMPP, or even to Citadel.

Any server that supports SSL/TLS, on any protocol which uses it, is just going to supply whatever certificate you've installed on it.  The server does not care whether the client chooses to trust it.   It's the client's decision whether to trust the server certificate or not.  The server cannot choose to "support" any specific type of certificate.  Only the client can do that.



[#] Mon Feb 26 2018 16:11:08 EST from IGnatius T Foobar @ Uncensored

Subject: Re: Server Migration

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

 

Note: i've seen the page that says not to use the replication function for this. The other suggested methods don't seem to have worked.

If you're going from like-to-like architecture (for example, 64-bit Intel on both sides) it's best to just copy the data files over.

 



[#] Mon Feb 26 2018 16:45:41 EST from bgerum @ Uncensored

Subject: Re: citadel refuses to start after OpenSuSE upgrade - now with Easyins

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

 

Sun Feb 25 2018 21:46:41 EST from IGnatius T Foobar @ Uncensored Subject: Re: citadel refuses to start after OpenSuSE upgrade - now with Easyins

 

checking for libical/ical.h... yes
checking for icaltimezone_set_tzid_prefix in -lical... yes
checking sieve2.h usability... yes
checking sieve2.h presence... yes
checking for sieve2.h... yes
checking for sieve2_license in -lsieve... no
configure: error: libsieve was not found and is required.  More info: http://www.citadel.org/doku.php/installation:start
Operating system: Linux 4.4.104-39-default( 4.4.104-39-default x86_64)

According to that log, it couldn't link to libsieve, even though libsieve had clearly been installed.  That is quite weird.

Can you attach the full log please?  We need to see what happened during the libsieve build.

 

unfortunately the 2nd try has overwritten the original log. I also did some updates overnight... but attached you find the current EasyInstall Log

 



 



citadel-install-log.txt (text/plain, 13387 bytes) [View| Download]
[#] Mon Feb 26 2018 21:04:35 EST from bobdoe @ Uncensored

Subject: Re: Unable to connect pidgin to citadel server

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

 

Mon Feb 26 2018 04:09:59 PM EST from IGnatius T Foobar @ Uncensored Subject: Re: Unable to connect pidgin to citadel server

From the docs and what you just explained, I'd guess Citadel currently lacks self-signed certificate support at least for XMPP...

Well ... not quite.  It's not really an issue specific to XMPP, or even to Citadel.

Any server that supports SSL/TLS, on any protocol which uses it, is just going to supply whatever certificate you've installed on it.  The server does not care whether the client chooses to trust it.   It's the client's decision whether to trust the server certificate or not.  The server cannot choose to "support" any specific type of certificate.  Only the client can do that.



Yes, already just realized.

So I did some more tests, with 2 versions of Pidgin: current 2.12.0 one; and 2.7.3, which was the last one having the same options as screenshots illustrated here
http://www.citadel.org/doku.php/faq:everydayuse:jabber#configuring.a.jabber.client.to.access.citadel
I tried this old build as well to see if having the option to disable SSL could make a difference.

Setup, just for review:
Citadel 917 installed from easy-install on Centos 7.4, both firewalld and selinux disabled
Server's ip: 10.0.1.5
Testing user: user123
Pidgin clients running on Windows 10

 

So, summarizing again what I tried and what I got:
--Use old style SSL, either with port 5222 and 5223 (both Pidgin versions):
   no certificate error, but Pidgin gets stuck in "Connecting..." forever according to its debug window.
--Export Citadel server's certificate with Firefox, name it after server's hostname (ip address), and manually adding it to Pidgin
--Run "openssl s_client -connect 10.0.1.5:5222 -starttls xmpp" in Centos server, and copying generated cert to Pidgin on Windows (filename is ip address):
   I need to correct myself in these 2. It seems last time I had messed up server. It fixed and I could try for real this time.
   This time Pidgin accepted the certificate. But now a new problem arouse. I posted Pidgin's 2.12.0 debug window output here https://pastebin.com/Kr2dAr81 .

In Pidgin 2.12.0 line 67 "connection: purple_connection_error_reason called with NULL description" was the killer one marked in red.
Log for Pidgin 2.7.3 was virtually the same, except that lines 66 and 67 were not there; killer error was the "Don't know howto do 'set'!".
But the interesting thing is, this "set" error is present in both logs.

Just in case I posted in Pidgin forums. To my surprise, they pointed at the "set" error:
"The software you're using is lacking some basic core XMPP stuff in its implementation, namely something like this https://tools.ietf.org/html/rfc6120#page-95 "

Think this could be a bug?

Thanks again.



[#] Mon Feb 26 2018 23:58:15 EST from warbaby @ Uncensored

Subject: Re: Unable to connect pidgin to citadel server

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

What we really need is a Lua module to authenticate Prosody thru the Citadel API.  Prosody supports lots of XEP specs, and has a fairly active community.  It's lightweight, and can run just fine along Citadel on small VPS.  I've used it for years. We just need to hook them up.

Even if you were to get your SSL sorted out, you'll immediately want some XMPP feature that Citadel doesn't support, and may not ever.. so, it's easier to write the authentication than waste more time testing old versions of pidgin.  If a few of us got together, we could have it done in a few days, if not hours.  All XMPP clients are junk btw.  

I spent some time with auth_imap a while ago, but don't recall what happened.  It may work.  Take a look at the other auth modules.  They are only ~75-100 loc.

https://modules.prosody.im/type_auth.html

 

 

Mon Feb 26 2018 04:09:59 PM EST from IGnatius T Foobar @ Uncensored Subject: Re: Unable to connect pidgin to citadel server

From the docs and what you just explained, I'd guess Citadel currently lacks self-signed certificate support at least for XMPP...

Well ... not quite.  It's not really an issue specific to XMPP, or even to Citadel.

Any server that supports SSL/TLS, on any protocol which uses it, is just going to supply whatever certificate you've installed on it.  The server does not care whether the client chooses to trust it.   It's the client's decision whether to trust the server certificate or not.  The server cannot choose to "support" any specific type of certificate.  Only the client can do that.



Yes, already just realized.

So I did some more tests, with 2 versions of Pidgin: current 2.12.0 one; and 2.7.3, which was the last one having the same options as screenshots illustrated here
http://www.citadel.org/doku.php/faq:everydayuse:jabber#configuring.a.jabber.client.to.access.citadel
I tried this old build as well to see if having the option to disable SSL could make a difference.

Setup, just for review:
Citadel 917 installed from easy-install on Centos 7.4, both firewalld and selinux disabled
Server's ip: 10.0.1.5
Testing user: user123
Pidgin clients running on Windows 10

 

So, summarizing again what I tried and what I got:
--Use old style SSL, either with port 5222 and 5223 (both Pidgin versions):
   no certificate error, but Pidgin gets stuck in "Connecting..." forever according to its debug window.
--Export Citadel server's certificate with Firefox, name it after server's hostname (ip address), and manually adding it to Pidgin
--Run "openssl s_client -connect 10.0.1.5:5222 -starttls xmpp" in Centos server, and copying generated cert to Pidgin on Windows (filename is ip address):
   I need to correct myself in these 2. It seems last time I had messed up server. It fixed and I could try for real this time.
   This time Pidgin accepted the certificate. But now a new problem arouse. I posted Pidgin's 2.12.0 debug window output here https://pastebin.com/Kr2dAr81 .

In Pidgin 2.12.0 line 67 "connection: purple_connection_error_reason called with NULL description" was the killer one marked in red.
Log for Pidgin 2.7.3 was virtually the same, except that lines 66 and 67 were not there; killer error was the "Don't know howto do 'set'!".
But the interesting thing is, this "set" error is present in both logs.

Just in case I posted in Pidgin forums. To my surprise, they pointed at the "set" error:
"The software you're using is lacking some basic core XMPP stuff in its implementation, namely something like this https://tools.ietf.org/html/rfc6120#page-95 "

Think this could be a bug?

Thanks again.



 



[#] Tue Feb 27 2018 12:43:28 EST from bobdoe @ Uncensored

Subject: Re: Unable to connect pidgin to citadel server

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

I dared to take a look at Citadel source code out of curiosity.
By all means I'm no dev and I may have dared too much for myself, but... could it be there might be something missing in this part?
http://code.citadel.org/?p=citadel.git;a=blob;f=citadel/modules/xmpp/serv_xmpp.c;h=3248a11cb39bbbf98b1281ec78082c10d3da3774;hb=HEAD#l177

In general, can this be fixed?



[#] Wed Feb 28 2018 00:00:10 EST from Zhouyang @ Uncensored

Subject: Fix crashes when some external APIs fail

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

Hi,

I'm a PhD student. I analyzed the Citadel source code and found some potential API bugs that may cause crashes. These crashes are mainly caused by insufficient error handling of API functions like chown or fopen.

I think it's unsafe to assume the library function would be correct. It would be better if we could handle the error properly. Attached please find the patch against the current development version. Hopefully, it can solve these potential bugs.

 

Best,

Zhouyang



api_bugs_citadel-trunk.patch (text/x-patch, 3236 bytes) [ View | Download ]
[#] Wed Feb 28 2018 02:36:33 EST from dnsserver @ Uncensored

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

Hi,

I am Md.Moniruzzaman,I want to try install and configure Citadel mail server. But I can't understand the system of citadel.How I can install and configure citadel server in Open-suse.If any one give sequential instruction than i will got the system.

Thank you. 



[#] Wed Feb 28 2018 03:59:08 EST from dnsserver @ Uncensored

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

Hi,

I want to try install and configure Citadel mail server. But I can't understand the system of citadel.How I can install and configure citadel server in Open-suse.If any one give sequential instruction than i will got the system.

Thank you. 



[#] Wed Feb 28 2018 09:32:34 EST from warbaby @ Uncensored

Subject: Re: Unable to connect pidgin to citadel server

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

 

Prosody is an XMPP server, not a client. 



Tue Feb 27 2018 10:58:00 AM EST from bobdoe @ Uncensored Subject: Re: Unable to connect pidgin to citadel server

 

Mon Feb 26 2018 11:58:15 PM EST from warbaby @ Uncensored Subject: Re: Unable to connect pidgin to citadel server

What we really need is a Lua module to authenticate Prosody thru the Citadel API.  Prosody supports lots of XEP specs, and has a fairly active community.  It's lightweight, and can run just fine along Citadel on small VPS.  I've used it for years. We just need to hook them up.

Even if you were to get your SSL sorted out, you'll immediately want some XMPP feature that Citadel doesn't support, and may not ever.. so, it's easier to write the authentication than waste more time testing old versions of pidgin.  If a few of us got together, we could have it done in a few days, if not hours.  All XMPP clients are junk btw.  

I spent some time with auth_imap a while ago, but don't recall what happened.  It may work.  Take a look at the other auth modules.  They are only ~75-100 loc.

https://modules.prosody.im/type_auth.html

 

 

Mon Feb 26 2018 04:09:59 PM EST from IGnatius T Foobar @ Uncensored Subject: Re: Unable to connect pidgin to citadel server

From the docs and what you just explained, I'd guess Citadel currently lacks self-signed certificate support at least for XMPP...

Well ... not quite.  It's not really an issue specific to XMPP, or even to Citadel.

Any server that supports SSL/TLS, on any protocol which uses it, is just going to supply whatever certificate you've installed on it.  The server does not care whether the client chooses to trust it.   It's the client's decision whether to trust the server certificate or not.  The server cannot choose to "support" any specific type of certificate.  Only the client can do that.



Yes, already just realized.

So I did some more tests, with 2 versions of Pidgin: current 2.12.0 one; and 2.7.3, which was the last one having the same options as screenshots illustrated here
http://www.citadel.org/doku.php/faq:everydayuse:jabber#configuring.a.jabber.client.to.access.citadel
I tried this old build as well to see if having the option to disable SSL could make a difference.

Setup, just for review:
Citadel 917 installed from easy-install on Centos 7.4, both firewalld and selinux disabled
Server's ip: 10.0.1.5
Testing user: user123
Pidgin clients running on Windows 10

 

So, summarizing again what I tried and what I got:
--Use old style SSL, either with port 5222 and 5223 (both Pidgin versions):
   no certificate error, but Pidgin gets stuck in "Connecting..." forever according to its debug window.
--Export Citadel server's certificate with Firefox, name it after server's hostname (ip address), and manually adding it to Pidgin
--Run "openssl s_client -connect 10.0.1.5:5222 -starttls xmpp" in Centos server, and copying generated cert to Pidgin on Windows (filename is ip address):
   I need to correct myself in these 2. It seems last time I had messed up server. It fixed and I could try for real this time.
   This time Pidgin accepted the certificate. But now a new problem arouse. I posted Pidgin's 2.12.0 debug window output here https://pastebin.com/Kr2dAr81 .

In Pidgin 2.12.0 line 67 "connection: purple_connection_error_reason called with NULL description" was the killer one marked in red.
Log for Pidgin 2.7.3 was virtually the same, except that lines 66 and 67 were not there; killer error was the "Don't know howto do 'set'!".
But the interesting thing is, this "set" error is present in both logs.

Just in case I posted in Pidgin forums. To my surprise, they pointed at the "set" error:
"The software you're using is lacking some basic core XMPP stuff in its implementation, namely something like this https://tools.ietf.org/html/rfc6120#page-95 "

Think this could be a bug?

Thanks again.



 



To clarify:
I only tested the old 2.7.3 version of Pidgin in order to temporarily put the SSL variable out of here (i.e., unchecking the option) and see if it made a difference. For some reason it still asked for the SSL certificate, *but* gave the option to accept the "unknown" certificate, which latest version 2.12.0 no longer allows by default.
As I also mentioned, I however managed to sort the SSL thing in latest Pidgin 2.12.0 release.
So in the end, SSL seems to no longer be the issue here, both leading to a different common error:
"Don't know howto do 'set'!"

I was also about to try Prosody client, but then I read they discontinued Windows builds, and unfortunately Windows clients are needed here in the place.

By the way, I forgot to mention, I *did do* searches around internet about this "set" error, and found little to no good hits. Then I posted in the Pidgin boards and got that response.



 



[#] Wed Feb 28 2018 10:33:08 EST from bgerum @ Uncensored

Subject: Re: citadel refuses to start after OpenSuSE upgrade - now with Easyins

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

 

Mon Feb 26 2018 16:45:41 EST from bgerum @ Uncensored Subject: Re: citadel refuses to start after OpenSuSE upgrade - now with Easyins

 

Sun Feb 25 2018 21:46:41 EST from IGnatius T Foobar @ Uncensored Subject: Re: citadel refuses to start after OpenSuSE upgrade - now with Easyins

 

checking for libical/ical.h... yes
checking for icaltimezone_set_tzid_prefix in -lical... yes
checking sieve2.h usability... yes
checking sieve2.h presence... yes
checking for sieve2.h... yes
checking for sieve2_license in -lsieve... no
configure: error: libsieve was not found and is required.  More info: http://www.citadel.org/doku.php/installation:start
Operating system: Linux 4.4.104-39-default( 4.4.104-39-default x86_64)

According to that log, it couldn't link to libsieve, even though libsieve had clearly been installed.  That is quite weird.

Can you attach the full log please?  We need to see what happened during the libsieve build.

 

unfortunately the 2nd try has overwritten the original log. I also did some updates overnight... but attached you find the current EasyInstall Log

 

How can I trigger a complete recompilation?

 



(, 0 bytes) [View| Download]

 



citadel-install-log.txt (text/plain, 13387 bytes) [View| Download]
[#] Thu Mar 01 2018 11:15:34 EST from IGnatius T Foobar @ Uncensored

Subject: Re: Unable to connect pidgin to citadel server

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

Even if you were to get your SSL sorted out, you'll immediately want
some XMPP feature that Citadel doesn't support, and may not ever..
so, it's easier to write the authentication than waste more time
testing old versions of pidgin.  If a few of us got together, we
could have it done in a few days, if not hours.  All XMPP clients
are junk btw.  

I must admit that XMPP has not been a high priority because the protocol in general seems to be dying. The idea of it being a universal protocol for instant messaging was awesome, and if the adoption rate remained high, it would be worth coping with the fact that the protocol itself is really overengineered.
There was a time when I could fire up Pidgin or Trillian and have it connect simultaneously to AIM, ICQ, Google, Facebook, and Uncensored. That was awesome.

But today? AIM is gone, Google and Facebook want everyone to use proprietary clients to enhance users' level of captivity in their walled gardens, and being able to pass instant messages *between* systems remains a distant dream.

XMPP will remain in Citadel for the foreseeable future, but if you want to run a third party XMPP server, I'd certainly be interested in providing whatever authentication hooks you need to make it happen. Of course, you then have to sacrifice the ability to send messages between XMPP and Citadel clients, which was the original point of having the server inside Citadel in the first place.

What if we implemented IRC protocol? That might be more useful.

[#] Sat Mar 03 2018 00:33:25 EST from julianc @ Uncensored

Subject: ERRORs installing Citadel using "Easy Installer" on ARM64 Machine

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

Hi,

 

as stated above I run into ERRORs installing Citadel on my machine (Ubuntu 16.04 LTS with ARM64 processor). When I try to use the precompiled packages I am stuck with an old version with bugs that have been fixed like two years ago. (Citadel runs as root and ...)

 

So I turned to using the "Easy Installer". Sadly it fails and this is the excerpt from the logfile:

 

2018-03-03 05:01:40 (378 KB/s) - 'libical-easyinstall.tar.gz' saved [1173542/1173542]

checking build system type... ./config.guess: unable to guess system type

This script, last modified 2009-11-20, has failed to recognize
the operating system you are using. It is advised that you
download the most up to date version of the config scripts from

  http://git.savannah.gnu.org/gitweb/?p=config.git;a=blob_plain;f=config.guess;hb=HEAD
and
  http://git.savannah.gnu.org/gitweb/?p=config.git;a=blob_plain;f=config.sub;hb=HEAD

If the version you run (./config.guess) is already up to date, please
send the following data and any information you think might be
pertinent to <config-patches@gnu.org> in order to provide the needed
information to handle your system.

config.guess timestamp = 2009-11-20

uname -m = aarch64
uname -r = 4.4.119-mainline-rev1
uname -s = Linux
uname -v = #1 SMP Wed Feb 28 10:44:16 UTC 2018

/usr/bin/uname -p =
/bin/uname -X     =

hostinfo               =
/bin/universe          =
/usr/bin/arch -k       =
/bin/arch              =
/usr/bin/oslevel       =
/usr/convex/getsysinfo =

UNAME_MACHINE = aarch64
UNAME_RELEASE = 4.4.119-mainline-rev1
UNAME_SYSTEM  = Linux
UNAME_VERSION = #1 SMP Wed Feb 28 10:44:16 UTC 2018
configure: error: cannot guess build type; you must specify one
Operating system: Linux Debian stretch/sid ( 4.4.119-mainline-rev1 aarch64)

 

As you can see all that needs to be done is updating the scripts (according to my understanding). Is this correct assessment of the situation?

 



[#] Sun Mar 04 2018 14:07:32 EST from IGnatius T Foobar @ Uncensored

Subject: Re: ERRORs installing Citadel using "Easy Installer" on ARM64 Machine

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

As you can see all that needs to be done is updating the scripts
(according to my understanding). Is this correct assessment of the
situation?

Thanks for the heads up! I did a bit of searching and it appears that "config.guess" is bundled with the "automake" package. This probably means that the machine that builds the source packages needs to have its build toolset updated.

We will get to work on that. Thanks again.

[#] Sun Mar 04 2018 16:04:32 EST from "Craig Mcgee" <craig.mcgee@guilt-management.org.uk> to <room_Citadel_Support@citadel.org>

Subject: email server function feature?

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

Hello there, I hope this is the wright place and list to post this on?
 
I'm just wondering if the Citadel email server has the below feature, as my old email provider bluebottle had it and I found it extremely useful!
take care
craig.
 
my old provider bluebottle had a great feature. so it would have 2 lists, a allow list and block list. whenever an email arrived at my address, bluebottle would check it and if the address was on the whitelist bang it would arrive in my inbox, if it was on the blocklist it would be deleted automatically. now here comes the nice bit. if the address wasnt on any of the 2 lists, bluebottle would put the email in a pending folder, accessible on the webmail. so i could go in there, each email was a checkbox, check off the emails I want to whitelist, and click allow. addresses added to whitelist, and emails delivered to inbox. i would then check all the boxes next to the emails i didnt want to receive, bang email addresses auto added to blocklist emails deleted, and any more emails from those addresses would be auto deleted without being added to pending. bluebottle shut so now dont have that service any more!


[#] Mon Mar 05 2018 19:07:36 EST from trundle @ Uncensored

Subject: TLS/SSL/ encryption?

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

Hi Gang,

Been a lurker for quite sometime. Wanted to join in conversations but  I wanted to successfully deploy citadel mainly to use for spice works ticket system.

After going through the docs and googling, I feel like i know nothing about servers/networking/linux, even tho I have been a tech for a couple a years.

I can receive mail only if I open port 25, but curious how to get ssl/tls. I understand(or thought I did) that a tls session is wrapped around the message. 

I have applied a cert via letsencypt.

I would like to verify encryption is happening and not plain auth.

My ultimate goal is to stop gmail/yahoo/office365 to not saying my message was not encrypted or is that beacsue of my free cert from  letsencrypt?

I am sure someone has asked this, but failing to search for those posts. 

Is it possible to get some insight, suggestions, or link to search the support more thoroughly.

Willing to bang head and get through the headaches.

IF I am missing something easy, please slap me.

Thank you

<KnoNothingTech>



[#] Tue Mar 06 2018 03:13:11 EST from bardhi232 @ Uncensored

Subject: Connect via outlook to the Citadel Mail Server

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

Hello,

 

In our company we have a citadel email server which all the employees use and we would like if possible to make it happen for everyone to connect to their email address using Microsoft Outlook as it is company policy to use that. IMAP port and SMTP port is already open to the server, but outlook is not able to connect to the mail server. If someone has made that possible could you please assist me on how to make that as well?

 

Thank you in advance

Fatbardh Hysa



Go to page: First ... 14 15 16 17 [18] 19 20 21 22 ... Last