[SM-USERS] different version of squirrelmail - different behavior when log-in with wrong username/password
Hi all, I use squirrelmail-1.4.8-21.el5.centos, plugin squirrel_logger-2.3.1-1.2.7, sendmail-8.13.8-10.el5_11, dovecot-1.0.7-9.el5_11.4, php-5.1.6-45.el5_11, httpd-2.2.3-91.el5.centos, fail2ban-0.8.14-1.el5, CentOS 5 with kernel 2.6.18-406.el5. When I try login to squirrelmail with bad user or bad password, I get message: Unknown user or password incorrect. squirrel-plugin write about that to logfile and fail2ban read that bad attempts and do its work (I want to use fail2ban for blocking attacks). New servers: CentOS 6: squirrelmail-1.4.22-4.el6.noarch, plugin squirrel_logger-2.3.1-1.2.7, sendmail-8.14.4-9.el6.x86_64, dovecot-2.0.9-19.el6.1.x86_64, php-5.3.3-46.el6_6.x86_64, httpd-2.2.15-47.el6.centos.x86_64, fail2ban-0.9.2-1.el6.noarch, kernel 2.6.32-504.16.2.el6.x86_64. CentOS 7: squirrelmail-1.4.22-15.el7.noarch, plugin squirrel_logger-2.3.1-1.2.7, postfix-2.10.1-6.el7.x86_64, dovecot-2.2.10-4.el7_0.1.x86_64, php-5.4.16-36.el7_1.x86_64, httpd-2.4.6-31.el7.centos.1.x86_64, fail2ban-0.9.2-1.el7.noarch, kernel 3.10.0-229.11.1.el7.x86_64. When I try login to squirrelmail with bad user or bad password, I get another message: ERROR: Connection dropped by IMAP server. squirrel-plugin do nothing. Here are logs: CentOS 5: /var/log/secure Sep 9 09:18:16 pink dovecot-auth: pam_krb5[30187]: error resolving user name 'pokusak' to uid/gid pair Sep 9 09:18:16 pink dovecot-auth: pam_krb5[30187]: error getting information about 'pokusak' Sep 9 09:18:16 pink dovecot-auth: pam_unix(dovecot:auth): check pass; user unknown Sep 9 09:18:16 pink dovecot-auth: pam_unix(dovecot:auth): authentication failure; logname= uid=0 euid=0 tty=dovecot ruser= rhost=:::127.0.0.1 Sep 9 09:18:16 pink dovecot-auth: pam_krb5[30187]: error resolving user name 'pokusak' to uid/gid pair Sep 9 09:18:16 pink dovecot-auth: pam_krb5[30187]: error getting information about 'pokusak' Sep 9 09:18:16 pink dovecot-auth: pam_succeed_if(dovecot:auth): error retrieving information about user pokusak /var/log/maillog Sep 9 09:18:19 pink dovecot: imap-login: Aborted login: user=, method=PLAIN, rip=:::127.0.0.1, lip=:::127.0.0.1, TLS CentOS 6: /var/log/secure Sep 9 09:24:22 purple auth: pam_krb5[20083]: error resolving user name 'pokusak' to uid/gid pair Sep 9 09:24:22 purple auth: pam_krb5[20083]: error getting information about 'pokusak' Sep 9 09:24:22 purple auth: pam_unix(dovecot:auth): check pass; user unknown Sep 9 09:24:22 purple auth: pam_unix(dovecot:auth): authentication failure; logname= uid=0 euid=0 tty=dovecot ruser=pokusak rhost=192.168.140.245 Sep 9 09:24:22 purple auth: pam_succeed_if(dovecot:auth): error retrieving information about user pokusak /var/log/maillog Sep 9 09:24:26 purple dovecot: imap-login: Aborted login (auth failed, 1 attempts): user=, method=PLAIN, rip=192.168.140.245, lip=192.168.140.245, TLS I need the same behavior as CentOS 5: Get correct message about Unknown user or password incorrect (or make squirrel-plugin write something to log). I want to use fail2ban for blocking attacks with new servers with CentOS 6 and CentOS 7. I googled a lot but find no answers to my problem. Any help will be appreciated. -- Miroslav Geisselreiter IT administrator -- Monitor Your Dynamic Infrastructure at Any Scale With Datadog! Get real-time metrics from all of your servers, apps and tools in one place. SourceForge users - Click here to start your Free Trial of Datadog now! http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140 - squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@lists.sourceforge.net List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
[SM-USERS] different version of squirrelmail - different behavior when log-in with wrong username/password
I use squirrelmail-1.4.8-21.el5.centos, plugin squirrel_logger-2.3.1-1.2.7, sendmail-8.13.8-10.el5_11, dovecot-1.0.7-9.el5_11.4, php-5.1.6-45.el5_11, httpd-2.2.3-91.el5.centos, fail2ban-0.8.14-1.el5, CentOS 5 with kernel 2.6.18-406.el5. When I try login to squirrelmail with bad user or bad password, I get message: Unknown user or password incorrect. squirrel-plugin write about that to logfile and fail2ban read that bad attempts and do its work (I want to use fail2ban for blocking attacks). New servers: CentOS 6: squirrelmail-1.4.22-4.el6.noarch, plugin squirrel_logger-2.3.1-1.2.7, sendmail-8.14.4-9.el6.x86_64, dovecot-2.0.9-19.el6.1.x86_64, php-5.3.3-46.el6_6.x86_64, httpd-2.2.15-47.el6.centos.x86_64, fail2ban-0.9.2-1.el6.noarch, kernel 2.6.32-504.16.2.el6.x86_64. CentOS 7: squirrelmail-1.4.22-15.el7.noarch, plugin squirrel_logger-2.3.1-1.2.7, postfix-2.10.1-6.el7.x86_64, dovecot-2.2.10-4.el7_0.1.x86_64, php-5.4.16-36.el7_1.x86_64, httpd-2.4.6-31.el7.centos.1.x86_64, fail2ban-0.9.2-1.el7.noarch, kernel 3.10.0-229.11.1.el7.x86_64. When I try login to squirrelmail with bad user or bad password, I get another message: ERROR: Connection dropped by IMAP server. squirrel-plugin do nothing. Here are logs: CentOS 5: /var/log/secure Sep 9 09:18:16 pink dovecot-auth: pam_krb5[30187]: error resolving user name 'pokusak' to uid/gid pair Sep 9 09:18:16 pink dovecot-auth: pam_krb5[30187]: error getting information about 'pokusak' Sep 9 09:18:16 pink dovecot-auth: pam_unix(dovecot:auth): check pass; user unknown Sep 9 09:18:16 pink dovecot-auth: pam_unix(dovecot:auth): authentication failure; logname= uid=0 euid=0 tty=dovecot ruser= rhost=:::127.0.0.1 Sep 9 09:18:16 pink dovecot-auth: pam_krb5[30187]: error resolving user name 'pokusak' to uid/gid pair Sep 9 09:18:16 pink dovecot-auth: pam_krb5[30187]: error getting information about 'pokusak' Sep 9 09:18:16 pink dovecot-auth: pam_succeed_if(dovecot:auth): error retrieving information about user pokusak /var/log/maillog Sep 9 09:18:19 pink dovecot: imap-login: Aborted login: user=, method=PLAIN, rip=:::127.0.0.1, lip=:::127.0.0.1, TLS CentOS 6: /var/log/secure Sep 9 09:24:22 purple auth: pam_krb5[20083]: error resolving user name 'pokusak' to uid/gid pair Sep 9 09:24:22 purple auth: pam_krb5[20083]: error getting information about 'pokusak' Sep 9 09:24:22 purple auth: pam_unix(dovecot:auth): check pass; user unknown Sep 9 09:24:22 purple auth: pam_unix(dovecot:auth): authentication failure; logname= uid=0 euid=0 tty=dovecot ruser=pokusak rhost=192.168.140.245 Sep 9 09:24:22 purple auth: pam_succeed_if(dovecot:auth): error retrieving information about user pokusak /var/log/maillog Sep 9 09:24:26 purple dovecot: imap-login: Aborted login (auth failed, 1 attempts): user=, method=PLAIN, rip=192.168.140.245, lip=192.168.140.245, TLS I need the same behavior as CentOS 5: Get correct message about Unknown user or password incorrect (or make squirrel-plugin write something to log). I want to use fail2ban for blocking attacks with new servers with CentOS 6 and CentOS 7. I googled a lot but find no answers to my problem. Any help will be appreciated. -- Miroslav Geisselreiter IT administrator -- Monitor Your Dynamic Infrastructure at Any Scale With Datadog! Get real-time metrics from all of your servers, apps and tools in one place. SourceForge users - Click here to start your Free Trial of Datadog now! http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140 - squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@lists.sourceforge.net List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
Re: [SM-USERS] different version of squirrelmail - different behavior when log-in with wrong username/password
On 09/09/2015 02:50 AM, Miroslav Geisselreiter wrote: > dovecot-1.0.7-9.el5_11.4, php-5.1.6-45.el5_11, > httpd-2.2.3-91.el5.centos, fail2ban-0.8.14-1.el5, CentOS 5 with kernel > 2.6.18-406.el5. > When I try login to squirrelmail with bad user or bad password, I get > message: Unknown user or password incorrect. squirrel-plugin write about > that to logfile and fail2ban read that bad attempts and do its work (I > want to use fail2ban for blocking attacks). > > New servers: > CentOS 6: squirrelmail-1.4.22-4.el6.noarch, plugin > squirrel_logger-2.3.1-1.2.7, sendmail-8.14.4-9.el6.x86_64, > dovecot-2.0.9-19.el6.1.x86_64, php-5.3.3-46.el6_6.x86_64, Miroslav, It looks like the primary difference is: dovecot-1.0.7-9.el5_11.4 New servers: CentOS 6: dovecot-2.0.9-19.el6.1.x86_64 If I understand that the problem you have is the difference in reporting a bad username between Centos 5 & 6, the most likely culprit is the difference in the way dovecot itself responds between versions 1 & 2. I don't have a dovecot 1 box to test, but I would check the dovecot documentation to see if that is the source of the reporting difference. fail2ban itself should be capable of working with either -- David C. Rankin, J.D.,P.E. -- Monitor Your Dynamic Infrastructure at Any Scale With Datadog! Get real-time metrics from all of your servers, apps and tools in one place. SourceForge users - Click here to start your Free Trial of Datadog now! http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140 - squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@lists.sourceforge.net List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
Re: [SM-USERS] different version of squirrelmail - different behavior when log-in with wrong username/password
On 9.9.2015 v 15:03 David C. Rankin wrote: > On 09/09/2015 02:50 AM, Miroslav Geisselreiter wrote: >> dovecot-1.0.7-9.el5_11.4, php-5.1.6-45.el5_11, >> httpd-2.2.3-91.el5.centos, fail2ban-0.8.14-1.el5, CentOS 5 with kernel >> 2.6.18-406.el5. >> When I try login to squirrelmail with bad user or bad password, I get >> message: Unknown user or password incorrect. squirrel-plugin write about >> that to logfile and fail2ban read that bad attempts and do its work (I >> want to use fail2ban for blocking attacks). >> >> New servers: >> CentOS 6: squirrelmail-1.4.22-4.el6.noarch, plugin >> squirrel_logger-2.3.1-1.2.7, sendmail-8.14.4-9.el6.x86_64, >> dovecot-2.0.9-19.el6.1.x86_64, php-5.3.3-46.el6_6.x86_64, > Miroslav, > > It looks like the primary difference is: > > dovecot-1.0.7-9.el5_11.4 > > > New servers: > CentOS 6: > > dovecot-2.0.9-19.el6.1.x86_64 > > If I understand that the problem you have is the difference in reporting a > bad username between Centos 5 & 6, the most likely culprit is the difference > in > the way dovecot itself responds between versions 1 & 2. > > I don't have a dovecot 1 box to test, but I would check the dovecot > documentation to see if that is the source of the reporting difference. > fail2ban > itself should be capable of working with either > Thank you, David, for answer. In the meantime I solved the situation: I changed config for squirrel_logger plugin to allow logging also ERROR messages and set filter for fail2ban to catch "ERROR: Connection dropped by IMAP server". On CentOS 7 it was necessary to edit php.ini and set date.timezone for my timezone, otherwise time in logs was incorrect (two hours in past) and fail2ban did not blocked anything. This is not the best solution but works for me at least now. Miroslav. -- Monitor Your Dynamic Infrastructure at Any Scale With Datadog! Get real-time metrics from all of your servers, apps and tools in one place. SourceForge users - Click here to start your Free Trial of Datadog now! http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140 - squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@lists.sourceforge.net List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
[SM-USERS] We are back from Summer Siesta
Great food and great times since 1959. View this email in your browser (http://us8.campaign-archive2.com/?u=35472b1dadb647486aff7b044&id=a8813b3af2&e=203b9518b7) Copyright © 2015 El Parador Cafe, All rights reserved. You are receiving this e-mail because you are our customer or we do business with you. Our mailing address is: El Parador Cafe 325 East 34th Street New York, NY 10016 USA Want to change how you receive these emails? You can ** update your preferences (http://elparadorcafe.us8.list-manage.com/profile?u=35472b1dadb647486aff7b044&id=41ba5ef649&e=203b9518b7) or ** unsubscribe from this list (http://elparadorcafe.us8.list-manage1.com/unsubscribe?u=35472b1dadb647486aff7b044&id=41ba5ef649&e=203b9518b7&c=a8813b3af2) -- Monitor Your Dynamic Infrastructure at Any Scale With Datadog! Get real-time metrics from all of your servers, apps and tools in one place. SourceForge users - Click here to start your Free Trial of Datadog now! http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140 - squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@lists.sourceforge.net List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
Re: [SM-USERS] different version of squirrelmail - different behavior when log-in with wrong username/password
On 9/9/15, Miroslav Geisselreiter wrote: > On 9.9.2015 v 15:03 David C. Rankin wrote: >> On 09/09/2015 02:50 AM, Miroslav Geisselreiter wrote: >>> dovecot-1.0.7-9.el5_11.4, php-5.1.6-45.el5_11, >>> httpd-2.2.3-91.el5.centos, fail2ban-0.8.14-1.el5, CentOS 5 with kernel >>> 2.6.18-406.el5. >>> When I try login to squirrelmail with bad user or bad password, I get >>> message: Unknown user or password incorrect. squirrel-plugin write about >>> that to logfile and fail2ban read that bad attempts and do its work (I >>> want to use fail2ban for blocking attacks). >>> >>> New servers: >>> CentOS 6: squirrelmail-1.4.22-4.el6.noarch, plugin >>> squirrel_logger-2.3.1-1.2.7, sendmail-8.14.4-9.el6.x86_64, >>> dovecot-2.0.9-19.el6.1.x86_64, php-5.3.3-46.el6_6.x86_64, >> Miroslav, >> >> It looks like the primary difference is: >> >> dovecot-1.0.7-9.el5_11.4 >> >> >> New servers: >> CentOS 6: >> >> dovecot-2.0.9-19.el6.1.x86_64 >> >> If I understand that the problem you have is the difference in >> reporting a >> bad username between Centos 5 & 6, the most likely culprit is the >> difference in >> the way dovecot itself responds between versions 1 & 2. >> >> I don't have a dovecot 1 box to test, but I would check the dovecot >> documentation to see if that is the source of the reporting difference. >> fail2ban >> itself should be capable of working with either >> > Thank you, David, for answer. > In the meantime I solved the situation: > I changed config for squirrel_logger plugin to allow logging also ERROR > messages and set filter for fail2ban to catch "ERROR: Connection dropped > by IMAP server". On CentOS 7 it was necessary to edit php.ini and set > date.timezone for my timezone, otherwise time in logs was incorrect (two > hours in past) and fail2ban did not blocked anything. > This is not the best solution but works for me at least now. The best solution would be for you to fix your Dovecot configuration. Works fine for me: $ dovecot --version 2.2.16 $ telnet localhost 143 A LOGIN t...@test.com asdf A NO [AUTHENTICATIONFAILED] Authentication failed. B LOGOUT * BYE Logging out B OK Logout completed. Connection closed by foreign host. -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php -- Monitor Your Dynamic Infrastructure at Any Scale With Datadog! Get real-time metrics from all of your servers, apps and tools in one place. SourceForge users - Click here to start your Free Trial of Datadog now! http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140 - squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@lists.sourceforge.net List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
[SM-USERS] New Mail plugin
Hello mailing list, I'm a long time user of SM. I recently got a Linode and upgraded SM to 1.5.2. I use SM for family and friends. Nothing serious. New mail has always been a little intermittent for me. I see there is a bug listed in v1.5.1 but not in v1.5.2 so I'm wondering if I have done something wrong. As I write this I have sent me an email from an external site and SM's left pane INBOX has a (1) next to it and Firefox tab has "0 New Messages" as a title. No popup. I have an exception for popups in Firefox for my webmail address. It looks like I have Folder preferences and New Mail options selected properly. I have not configured sound. In the past all I did was resubmit on New Mail Options page and that would fix it. I installed SM 1.5.2 in /usr/share/squirrelmail.devel but I'm not sure that was correct. All other plugins work fine. My configuration: Postfix 2.11 MySQL 5.5 Dovecot 2.2 PHP 5.6 Apache2 2.4 SSL cert protecting Squirrelmail vhost. Client: Windows 7 Firefox 40.0.3 Plugins: Autocomplete 3.0 Compatibility 2.0.16 New Mail CORE Add Address 1.0.3 Multiple Attachments 1.0 Thanks for a very nice product! Dave Anderson -- Monitor Your Dynamic Infrastructure at Any Scale With Datadog! Get real-time metrics from all of your servers, apps and tools in one place. SourceForge users - Click here to start your Free Trial of Datadog now! http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140 - squirrelmail-users mailing list Posting guidelines: http://squirrelmail.org/postingguidelines List address: squirrelmail-users@lists.sourceforge.net List archives: http://news.gmane.org/gmane.mail.squirrelmail.user List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
Re: [SM-USERS] Error when searching messages
Third try. Anyone around here can give me a bit of help, please? > Maybe I started this message with the wrong sentence. So I'm writing again - > but assuming someone will read the original message as needed, because it has > all details that I imagine are needed. > > As the admin of a few Squirrelmail installations, I have reports of users > that can't search their messages; they are using specific IMAP servers. > Squirrelmail shows a strange error (see original message), which does not > point me to anything to solve the problem, or to find the solution. May you > help me? > > Another problem is that clicking in the message list headers to choose what > field for message sorting causes an very bad error. Users cannot refresh > message lists anymore! There is no way for them to reset the configuration. I > must manually remove the sort option from each user configuration file. > > With Squirrelmail configured for each of these different IMAP servers, I run > its configtest. No problem is pointed (see original message). So, why do I > have these and other problems? > >> I get an error when searching my inbox for some subject. I use an IMAP >> server to this account. >> >> The error message (in Portuguese) is: >> >> === >> ERRO: >> Erro: pedido não pode ser completado. >> Requisição: FETCH (FLAGS UID RFC822.SIZE INTERNALDATE >> BODY.PEEK[HEADER.FIELDS (Date To Cc From Subject X-Priority Importance >> Priority Content-Type)]) >> Razão alegada: FETCH token is invalid >> === >> >> Which should be something like this, in English: >> >> === >> ERROR: >> Error: request can't be completed. >> Request: FETCH (FLAGS UID RFC822.SIZE INTERNALDATE BODY.PEEK[HEADER.FIELDS >> (Date To Cc From Subject X-Priority Importance Priority Content-Type)]) >> Informed reason: FETCH token is invalid >> === >> >> A configtest run on this install, right now, gives: >> >> >> SquirrelMail configtest >> >> This script will try to check some aspects of your SquirrelMail >> configuration and point you to errors whereever it can find them. You need >> to go run conf.pl in the config/ directory first before you run this script. >> SquirrelMail version: 1.4.22 >> Config file version: 1.4.0 >> Config file last modified: 24 08 2015 02:31:37 >> >> Checking PHP configuration... >> PHP version 5.3.13 OK. >> Running as me(123) / group(1000) >> display_errors: 1 >> error_reporting: 22519 >> variables_order OK: EGPCS. >> PHP extensions OK. Dynamic loading is enabled. >> Checking paths... >> Data dir OK. >> Attachment dir OK. >> Plugins OK. >> Themes OK. >> Default language OK. >> Base URL detected as: https://my.domain.name.com/~squirrel/path/src >> (location base autodetected) >> Checking outgoing mail service >> SMTP server OK (220 carretel.grude.ufmg.br ESMTP Service (Lotus Domino >> Release 8.5.3FP6HF1016) ready at Mon, 24 Aug 2015 02:32:47 -0300) >> Checking IMAP service >> IMAP server ready (* OK Domino IMAP4 Server Release 8.5.3FP6HF1016 ready >> Mon, 24 Aug 2015 02:32:47 -0300) >> Capabilities: * CAPABILITY IMAP4rev1 AUTH=PLAIN LITERAL+ NAMESPACE QUOTA >> UIDPLUS >> Checking internationalization (i18n) settings... >> gettext - Gettext functions are available. On some systems you must have >> appropriate system locales compiled. >> mbstring - Mbstring functions are available. >> recode - Recode functions are unavailable. >> iconv - Iconv functions are available. >> timezone - Webmail users can change their time zone settings. >> Checking database functions... >> not using database functionality. >> >> Congratulations, your SquirrelMail setup looks fine to me! >> >> >> >> So. What should I do? >> >> There are other problems with Squirrelmail that I never tried to fix, but >> might be related: in the message lists, clicking on date, subject, size or >> date, to sort messages with them gives an error that I could only fix by >> manually editing the Squirrel config file, removing this sort option. The >> error makes it impossible to reopen the folder where I clicked the option to >> unclick it. This is very bad because normal users of this Squirrel install >> cannot do this. I do it as the admin, but would't be much fun to do this >> everytime an user clicks on something simple that is there waiting. >> >> If more information is needed, please ask. Suggestions are also welcome. >> >> Thank you, >> >> André >> >> -- >> - >> squirrelmail-users mailing list >> Posting guidelines: http://squirrelmail.org/postingguidelines >> List address: squirrelmail-users@lists.sourceforge.net >> List archives: http://news.gmane.org/gmane.mail.squirrelmail.user >> List info (subscribe/unsubscribe/change options): >> https://lists.sourceforge.net/lists/listinfo/squirrelmail-users > >
