Re: [qmailtoaster] badmailfrom

2019-08-31 Thread Noriyuki Hayashi
Hi It also can block on the /var/qmail/control/badmailfrom as below. .*\ @.* !.*@.*\..* .*%.* @(.*\.)*\.pro Let's try. Have a good weekend. Regards, Noriyuki Hayashi @ voiplus.net On Fri, 30 Aug 2019 23:21:21 +0200 Stevan Stevic wrote: > How to block all email sent from all .pro domains? >

Re: [qmailtoaster] password modification issue

2019-08-31 Thread Tahnan Al Anas
Hi Eric, Additionally I am getting below error in log of dovecot process_limit (100) reached, client connections are being dropped -- -- Best Regards Muhammad Tahnan Al Anas On Sat, Aug 31, 2019 at 12:58 PM Tahnan Al Anas wrote: > Hi Eric, > > I tried below settings but still I am getting t

Re: [qmailtoaster] password modification issue

2019-08-31 Thread Eric Broch
Tahnan, With stock qmail & dovecot I was able to login to squirrelmail with password 'X' logout, change password in qmailadmin to password 'Y', and login to squirrelmail with password 'Y' Then, to my preference, I changed /etc/dovecot/toaster.conf setting auth_mechanisms = plain login digest-md

Re: [qmailtoaster] password modification issue

2019-08-31 Thread Tahnan Al Anas
Hi Eric, Thanks for replying, I think issue is related with dovecot process limit. Can you tell me which file I need to modify to increase dovecot process limit? normally it should be present in dovecot.con file. I am attaching my dovecot file with this mail. master: Warning: service(imap-login):

Re: [qmailtoaster] password modification issue

2019-08-31 Thread Eric Broch
Try this In toaster.conf add service imap-login { service_count = 0 #client_limit = $default_client_limit process_min_avail = 4 # number of CPU cores vsz_limit = 1G}service pop3-login { service_count = 0} and restart dovecot From: https://wiki2.dovecot.org/LoginProcess On Sat, Aug 31, 2019