[07:53:33]
<niklas> Hi all, is there a way to change how long a yunohost/ssowat session is valid? i.e. after what amount of time of inactivity users have to re-login?
[08:14:05]
<wazdra> Hey ! I want to setup an email address to use with paperless-ngx. There is already a paperless-ngx user created with the installation. Is there an easy way to "activate" the address paperless-ngx@mydomain.tld ?
[08:20:42]
<tituspijean> @wazdra:matrix.org YunoHost apps can have a setting that allows them to send emails, but that does not enable them receive them. They will not have inboxes.
Paperless-NGX is made so that you put your email credentials in its configuration so that the app monitors your incoming emails.
[08:24:10]
<tituspijean> @wazdra:matrix.org or do you somehow want the app to send emails?
[08:27:16]
<wazdra> I see ! Thanks for the clarification :)
[08:28:26]
<wazdra> I wanted to do both actually: send documents via mail to paperless@mydomain to have them imported, but also being able to ask paperless to send documents via mail (as https://docs.paperless-ngx.com/usage/#email-sharing)
[08:29:25]
<tituspijean> Oh OK! I was not aware of that second feature. This can be worked on.
[08:34:12]
<wazdra> Having one unified email address for this would have been nice, but it's not that big of a problem!
[16:33:58]
<everlastingos> Hey, my config files looks just like yours, both of them, and yes the fresh install is on the same version.
[16:35:54]
<everlastingos> mine fail2ban here is emty, can you share your config so can I copy it and test
[17:19:48]
<Chatpitaine Caverne> everlastingos: Here is /etc/fail2ban/fail2ban.conf :
```
# Fail2Ban main configuration file
#
# Comments: use '#' for comment lines and ';' (following a space) for inline comments
#
# Changes: in most of the cases you should not modify this
# file, but provide customizations in fail2ban.local file, e.g.:
#
# [DEFAULT]
# loglevel = DEBUG
#
[DEFAULT]
# Option: loglevel
# Notes.: Set the log level output.
# CRITICAL
# ERROR
# WARNING
# NOTICE
# INFO
# DEBUG
# Values: [ LEVEL ] Default: INFO
#
loglevel = INFO
# Option: logtarget
# Notes.: Set the log target. This could be a file, SYSTEMD-JOURNAL, SYSLOG, STDERR or STDOUT.
# Only one log target can be specified.
# If you change logtarget from the default value and you are
# using logrotate -- also adjust or disable rotation in the
# corresponding configuration file
# (e.g. /etc/logrotate.d/fail2ban on Debian systems)
# Values: [ STDOUT | STDERR | SYSLOG | SYSOUT | SYSTEMD-JOURNAL | FILE ] Default: STDERR
#
logtarget = /var/log/fail2ban.log
# Option: syslogsocket
# Notes: Set the syslog socket file. Only used when logtarget is SYSLOG
# auto uses platform.system() to determine predefined paths
# Values: [ auto | FILE ] Default: auto
syslogsocket = auto
# Option: socket
# Notes.: Set the socket file. This is used to communicate with the daemon. Do
# not remove this file when Fail2ban runs. It will not be possible to
# communicate with the server afterwards.
# Values: [ FILE ] Default: /var/run/fail2ban/fail2ban.sock
#
socket = /var/run/fail2ban/fail2ban.sock
# Option: pidfile
# Notes.: Set the PID file. This is used to store the process ID of the
# fail2ban server.
# Values: [ FILE ] Default: /var/run/fail2ban/fail2ban.pid
#
pidfile = /var/run/fail2ban/fail2ban.pid
# Option: allowipv6
# Notes.: Allows IPv6 interface:
# Default: auto
# Values: [ auto yes (on, true, 1) no (off, false, 0) ] Default: auto
#allowipv6 = auto
# Options: dbfile
# Notes.: Set the file for the fail2ban persistent data to be stored.
# A value of ":memory:" means database is only stored in memory
# and data is lost when fail2ban is stopped.
# A value of "None" disables the database.
# Values: [ None :memory: FILE ] Default: /var/lib/fail2ban/fail2ban.sqlite3
dbfile = /var/lib/fail2ban/fail2ban.sqlite3
# Options: dbpurgeage
# Notes.: Sets age at which bans should be purged from the database
# Values: [ SECONDS ] Default: 86400 (24hours)
dbpurgeage = 1d
# Options: dbmaxmatches
# Notes.: Number of matches stored in database per ticket (resolvable via
# tags <ipmatches>/<ipjailmatches> in actions)
# Values: [ INT ] Default: 10
dbmaxmatches = 10
[Definition]
[Thread]
# Options: stacksize
# Notes.: Specifies the stack size (in KiB) to be used for subsequently created threads,
# and must be 0 or a positive integer value of at least 32.
# Values: [ SIZE ] Default: 0 (use platform or configured default)
#stacksize = 0
```
[17:24:16]
<everlastingos> oh thanks! seems to work now!!!!
[19:46:16]
<netzfetz> I cant get active sync to work. Do I need to tweak any .conf files, or is something else off=
[19:46:35]
<netzfetz> Sorry. I need to provide context. I meant in Sogo.
[19:48:38]
<netzfetz> It seems that Active Sync itself is working well but somehow the request of the client doesnt get a answer that leads to a working integration.