Re: Log IPs of IMAP connections (attempts)

Hey Matthias

Currently I don't know of any possbility to turn connection logging on 
in guam. If someone is fluent with erlang they're welcome to join in and 
help us fixing and extending guam in this regard.

For those asking what guam does: Guam is the IMAP Reverse Proxy sitting 
in front of cyrus-imapd. When you're IMAP Clients connects to Kolab and 
listing all the IMAP folders, guam is "hiding" the groupware folders 
(like Calendars, Contacts, etc.) to non-kolab aware clients. Sure you 
can turn guam off and reconfigure cyrus (in cyrus.conf) to start listing 
on :143 and :993 again.

Beware that unware users of your email server don't know nothing about 
the ~9 additional folders. And if they deleting those "strange" email 
folders and objects they could end up losing their contacts or calender 
entries.

Apart from that: Any help with guam is appriciated.

--
Daniel Hoffend


Am 2020-02-23 15:39, schrieb Matthias Busch:
> 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