Users can't use Dovecot IMAP
Every time a user logs into Dovcot's IMAP service PAM closes the session
immediately after it opens. I would like a user to have a session open long
enough to read some emails.
dictator@drakeclasher:~$ sudo dovecot -n
# 2.1.7: /etc/dovecot/dovecot.conf
# OS: Linux 3.14-0.bpo.1-amd64 x86_64 Debian 7.8
mail_location = maildir:~/Maildir
namespace inbox {
inbox = yes
location =
mailbox Drafts {
special_use = \Drafts
}
mailbox Junk {
special_use = \Junk
}
mailbox Sent {
special_use = \Sent
}
mailbox "Sent Messages" {
special_use = \Sent
}
mailbox Trash {
special_use = \Trash
}
prefix =
}
passdb {
driver = pam
}
passdb {
args = failure_show_msg=yes %s
driver = pam
}
plugin {
sieve = ~/.dovecot.sieve
sieve_dir = ~/sieve
}
protocols = " imap lmtp"
ssl_cert =
setting service_count results in Permission denied
The load on our machines has gotten too high, so I started to see log
messages that directed me to look at this page for config changes:
https://pad.riseup.net/redirect#http%3A//wiki2.dovecot.org/SocketUnavailable
One of the things I wanted to do on that page was to set the:
service imap { service_count = 100 }
but when I added that to the service imap block, and restarted dovecot,
I see this in the logs: Error:
net_connect_unix(/run/dovecot/imap-postlogin) failed: Permission denied
I dont understand how this impacts permissions. Its clearly this
setting, because when I remove it, things work again. I found nothing
else in the logs indicating a configuration problem.
This is what the config block looked like:
service imap {
# Most of the memory goes to mmap()ing files. You may need to increase this
# limit if you have huge mailboxes.
#vsz_limit = 256M
# Max. number of IMAP processes (connections)
process_limit = 4096
service_count = 100
executable = imap imap-postlogin
}
service imap-postlogin {
# the script process runs as the user specified here (v2.0.14+):
#user = $default_internal_user
executable = script-login /usr/local/sbin/postlogin_imap
# this UNIX socket listener must use the same name as given to imap executable
unix_listener imap-postlogin {
}
}
This is with dovecot 2.2.13, thanks for any help you can provide!
micah
Re: Using dovecot to serve an email archive
On Mon, 06 Apr 2015 00:42:00 +0200 Peter Chiochetti wrote: > Am 2015-04-05 um 19:12 schrieb Ramón Casares: > > Now I am looking for an IMAP server > > that can serve this collection > > in a read-only (ro) manner. That is, > > the server should not write > > the mailarch dir at all. > > Dovecot ACL might be what you want? > > http://wiki2.dovecot.org/ACL > > Probably still writes indices… > > -- > peter I was reading about dovecot ACL. It is a means to control what users can do, but the server itself seems to be free to write indices, move files from new to cur, etc. The other problem is to force dovecot to accept the file naming scheme .R.mail Nevertheless, thank you Ramón Casares
Re: Sieve/ManageSieve documentation on Wiki2
On 4/2/2015 2:21 PM, Robert Blayzor wrote: > Is it possible the Sieve/ManageSieve documentation on the Wiki can be cleaned > up? It's incredibly confusing now. Some of the Sieve configuration > information says certain options are deprecated, but then the example on how > to configure it uses the deprecated options rather than what they *should* be > now. > > More confusion is the sieve plugin configuration listing those same > deprecated options, yet when you pull the document on how to configure > ManageSieve, it (again) uses deprecated configuration information? > > http://wiki2.dovecot.org/Pigeonhole/ManageSieve/Configuration > > > Or am I missing something? Oh right. I fixed those now, also in the tarball documentation. Regards, Stephan.
doveadm save ...
Hello, when I have with "doveadm save ..." store a message, how do I get the guid or uid of this message for the setthe flags? Hardy
