High user number tune
Halo,
This might seem like another indirect thread.
I Monday started new job, first task must replace courier. The job use
POP3. and IMAP only for webmail, but must server support 4K POP3 at one
times. I see from similar thread current settings not adequate , we will
use TLS and if wiki read right Iprotocol
So am close in think that need ?
service pop3-login {
process_limit = 4096
}
service pop3 {
process_limit = 4096
}
service imap-login {
process_limit = 2048
}
service imap {
process_limit = 2048
}
then we have
service managesieve {
process_limit = 1024
}
is that all we need change? I see in other thread someone says service
anvil but I can not find out about it, does need change as well ?
Why is it so complicated to change to let more user on, most other change
one setting, dovecot want dozen :(
Re: Pigeonhole sieve misfile
On 7/13/2014 1:54 AM, Patrick Domack wrote: > I'm having an issue with sieve putting some emails into the spam > folder, that should not be matching the spam rule. > > I tried looking but can't seem to find a debug option. > > Is there any way I can get a log of what the sieve rule path that > matches so I can locate the misfiring rule? or maybe something else > that is going on. > > I already checked the dovecot sieve log file, and there is nothing in > there. Use the sieve-test tool. Regards, Stephan.
Re: macros
On 07/11/2014 03:59 AM, Arkadiusz Miśkiewicz wrote: > > Does dovecot support any form of macros? I would like to share configuration > file between several servers. Configs are different only in tiny aspects. > As a last resort, you can use `make` to accomplish this. dovecot-server.conf.sh -- id=55 something="SELECT FROM * WHERE something" mechanisms="digest-md5" dovecot-main.conf.sh source ~/dovecot-server.conf.sh cat < $@
Pigeonhole sieve misfile
I'm having an issue with sieve putting some emails into the spam folder, that should not be matching the spam rule. I tried looking but can't seem to find a debug option. Is there any way I can get a log of what the sieve rule path that matches so I can locate the misfiring rule? or maybe something else that is going on. I already checked the dovecot sieve log file, and there is nothing in there.
Re: If local Dovecot stops working, check lo
Am 12.07.2014 13:31, schrieb Steve Litt: > ifdown lo > ifup lo > > A malfunctioning lo will cause Dovecot not to connect to clients. My > experience with Debian Wheezy is that lo "goes down" a lot, so this is > one of the first things I do when odd stuff happens uhm if you *loopback device* goes down your machine has a serious problem - within 15 years Linux expierience i never faced a broken "lo" device and i guess the same for 99.% of all admins signature.asc Description: OpenPGP digital signature
If local Dovecot stops working, check lo
Hi all, You probably know this already, but just in case... Let's say you have your email client getting mail from a Dovecot server on the same computer (which is a really good way of doing things, by the way). Then one day your email client starts saying "connection refused" after a suitably long timeout. So then, to find out where things are getting stuck, you do the following command: openssl s_client -connect 127.0.0.1:993 -quiet And you don't even get an OK back. This means it's not your username or password, because you never even got that far. Before spending a lot of time doing diagnostic tests and narrowing it to the root cause, try this as root: ifdown lo ifup lo A malfunctioning lo will cause Dovecot not to connect to clients. My experience with Debian Wheezy is that lo "goes down" a lot, so this is one of the first things I do when odd stuff happens. HTH, SteveT Steve Litt* http://www.troubleshooters.com/ Troubleshooting Training * Human Performance
