Hello You have to correct your apache configuration. Apache has to deliver the client IP to sogo in the Proxy part with:
RequestHeader set "x-webobjects-remote-host" "%{SENDER_IP_ADDRESS}e" Kind regards, Christian Mack Am 26.04.2018 um 02:43 schrieb "George C. Aquino" (aquinogeor...@gmail.com): > Dear Sir, > > Good morning and glad to being connected within here and can you help me to > log in correctly coz I could not do so far. Thnx, Gery. > > On Wed, Apr 25, 2018 at 1:00 PM, Christoph Kreutzer <users@sogo.nu> wrote: > >> Hi, >> >> If the IPs are all 127.0.0.1 in SOGos log, then you did not correctly >> configure Apache to forward the IPs like proxies do. I think that is >> mentioned in the manual. >> >> Christoph >> >> Am 24.04.2018 um 21:48 schrieb Sergio Cesar winc (ser...@winc.net) < >> users@sogo.nu>: >> >> I wonder if one could user the webserver authentication and pass it to >> SOGo or roundcube. Than fail2ban will catch the ip from the http log. >> >> SC >> >> >> From: Sebastián Meyer >> Sent: Tuesday, April 24, 9:51 AM >> Subject: [SOGo] webmail login attacks - captcha? >> To: users@sogo.nu >> >> >> Hi, >> >> I have a couple of compromissed webmail accounts, passwords wheren't easy >> to guess. >> >> I'd like to add an increasing delay for failed logins and a captcha, is it >> possible? >> >> For IMAP and SMTP access I use fail2ban, but using it for for webmail >> access DoS attacks would be unacceptable frequently, all logins are from >> localhost (127.0.0.1) >> >> TIA, >> >> -- >> Seb >> -- >> users@sogo.nu >> https://inverse.ca/sogo/lists >> >> >> -- >> users@sogo.nu >> https://inverse.ca/sogo/lists >> >> -- >> users@sogo.nu >> https://inverse.ca/sogo/lists >> -- Christian Mack Universität Konstanz Kommunikations-, Informations-, Medienzentrum (KIM) Abteilung Basisdienste 78457 Konstanz +49 7531 88-4416
smime.p7s
Description: S/MIME Cryptographic Signature