guam eats a lot of system resources
Valentin Laskov <[email protected]>
| Newsgroups | gmane.comp.kde.devel.kroupware |
|---|---|
| Message-ID | <56044eec-1f5c-bd4a-35cb-34523bbd5abd__8238.49121095321$1582882690$gmane$org@festa.bg> |
Hi all, I have another guam issue. It eats a lot of system resources and I have a lot of kernel messages (dmesg) Out of memory: Kill process 1067 (beam.smp) It started this way: /usr/lib64/erlang/erts-7.3.1.2/bin/beam.smp -Bd -- -root /usr/lib64/erlang/lib/kolab_guam-0.9.5 .... Regards! Valentin Laskov На 24.02.2020 в 16:02, Ladislav Slanina написа: > Hi Mat. > > A year ago at this place guys sugest me switch guam off and use directly imap. After that logging should work. > > Greetings, ladas > >> Hey, >> >> since GUAM is proxying the imap connections, cyrus only ever sees >> localhost connections. >> >> Anyone know how to setup guam to log the connections? Mostly looking >> towards logging failed attempts with the IP attempting to login. >> Want to setup a bruteforce block via fail2ban.... >> >> Thanks in advance >> Mat >> _______________________________________________ >> users mailing list >> [email protected] >> https://lists.kolab.org/mailman/listinfo/users >> > _______________________________________________ users mailing list [email protected] https://lists.kolab.org/mailman/listinfo/users