[Dovecot] Conditional jump or move depends on uninitialised value(s)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Timo, Dovecot 2.2.6 compiled on Ubuntu 10.04 fails on "make check" with the following errors. "make install" is finishing just fine and Dovecot itself works flawlessly so far. - - 8< - http header invalid [0]: parse failure ... : ok: Expected ':' after header field name 'Server', but found ' ' http header invalid [0] .. : ok http header invalid [1]: parse failure ... : ok: Expected ':' after header field name 'X', but found ' ' http header invalid [1] .. : ok http header invalid [2]: parse failure ... : ok: Expected LF after CR at end of header, but found 'A' http header invalid [2] .. : ok http header invalid [3]: parse failure ... : ok: Expected line end after header field 'Accept', but found 0x7f http header invalid [3] .. : ok http header invalid [4]: parse failure ... : ok: Expected ':' after header field name 'Suhosin-Patch', but found ' ' http header invalid [4] .. : ok http header invalid [5]: parse failure ... : ok: Excessive header size http header invalid [5] .. : ok http header invalid [6]: parse failure ... : ok: Excessive header field size http header invalid [6] .. : ok http header invalid [7]: parse failure ... : ok: Excessive number of header fields http header invalid [7] .. : ok 0 / 66 tests failed ==15579== Conditional jump or move depends on uninitialised value(s) ==15579==at 0x804F987: http_header_parse_next_field (http-header-parser.c:294) ==15579==by 0x804F361: test_http_header_parse_valid (test-http-header-parser.c:181) ==15579==by 0x8050251: test_run_funcs (test-common.c:228) ==15579==by 0x80503D1: test_run (test-common.c:236) ==15579==by 0x804F164: main (test-http-header-parser.c:343) ==15579== ==15579== Conditional jump or move depends on uninitialised value(s) ==15579==at 0x804F98D: http_header_parse_next_field (http-header-parser.c:294) ==15579==by 0x804F361: test_http_header_parse_valid (test-http-header-parser.c:181) ==15579==by 0x8050251: test_run_funcs (test-common.c:228) ==15579==by 0x80503D1: test_run (test-common.c:236) ==15579==by 0x804F164: main (test-http-header-parser.c:343) ==15579== ==15579== Conditional jump or move depends on uninitialised value(s) ==15579==at 0x804F9B0: http_header_parse_next_field (http-header-parser.c:296) ==15579==by 0x804F361: test_http_header_parse_valid (test-http-header-parser.c:181) ==15579==by 0x8050251: test_run_funcs (test-common.c:228) ==15579==by 0x80503D1: test_run (test-common.c:236) ==15579==by 0x804F164: main (test-http-header-parser.c:343) ==15579== ==15579== Conditional jump or move depends on uninitialised value(s) ==15579==at 0x804FC92: http_header_parse_next_field (http-header-parser.c:320) ==15579==by 0x804F361: test_http_header_parse_valid (test-http-header-parser.c:181) ==15579==by 0x8050251: test_run_funcs (test-common.c:228) ==15579==by 0x80503D1: test_run (test-common.c:236) ==15579==by 0x804F164: main (test-http-header-parser.c:343) ==15579== ==15579== Conditional jump or move depends on uninitialised value(s) ==15579==at 0x804F9B2: http_header_parse_next_field (http-header-parser.c:296) ==15579==by 0x804F361: test_http_header_parse_valid (test-http-header-parser.c:181) ==15579==by 0x8050251: test_run_funcs (test-common.c:228) ==15579==by 0x80503D1: test_run (test-common.c:236) ==15579==by 0x804F164: main (test-http-header-parser.c:343) ==15579== ==15579== Conditional jump or move depends on uninitialised value(s) ==15579==at 0x804F987: http_header_parse_next_field (http-header-parser.c:294) ==15579==by 0x804F225: test_http_header_parse_invalid (test-http-header-parser.c:325) ==15579==by 0x8050251: test_run_funcs (test-common.c:228) ==15579==by 0x80503D1: test_run (test-common.c:236) ==15579==by 0x804F164: main (test-http-header-parser.c:343) ==15579== ==15579== Conditional jump or move depends on uninitialised value(s) ==15579==at 0x804F98D: http_header_parse_next_field (http-header-parser.c:294) ==15579==by 0x804F225: test_http_header_parse_invalid (test-http-header-parser.c:325) ==15579==by 0x8050251: test_run_funcs (test-common.c:228) ==15579==by 0x80503D1: test_run (test-common.c:236) ==15579==by 0x804F164: main (test-http-header-parser.c:343) ==15579== ==15579== Conditional jump or move depends on uninitialised value(s) ==15579==at 0x804F9B0:
[Dovecot] Dsync: Mailbox changes caused a desync.
Hi! Here such synchronization error: dovecot: dsync-local(a...@aaa.com): Warning: Mailbox changes caused a desync. You may want to run dsync again. dovecot: dsync-remote(a...@aaa.com): Warning: /var/mail/virtual/aaa.com/alex/.INBOX.System/dovecot-uidlist: Duplicate file entry at line 2298: 1380157263.M585262P25253.mail1.aaa.com,S=2476,W=2553 (uid 3645 -> 3662) dovecot: dsync-remote(a...@aaa.com): Warning: Maildir /var/mail/virtual/aaa.com/alex/.INBOX.System: Expunged message reappeared, giving a new UID (old uid=3650, file=1380157264.M261919P17392.mail2.aaa.com,S=2476,W=2553) dovecot: dsync-remote(a...@aaa.com): Warning: Maildir /var/mail/virtual/aaa.com/alex/.INBOX.System: Expunged message reappeared, giving a new UID (old uid=3651, file=1380157263.M586977P17315.mail2.aaa.com,S=3119,W=3175) dovecot: dsync-remote(a...@aaa.com): Warning: Maildir /var/mail/virtual/aaa.com/alex/.INBOX.System: Expunged message reappeared, giving a new UID (old uid=3652, file=1380157264.M261920P17392.mail2.aaa.com,S=2476,W=2553) dovecot: dsync-remote(a...@aaa.com): Warning: Maildir /var/mail/virtual/aaa.com/alex/.INBOX.System: Expunged message reappeared, giving a new UID (old uid=3653, file=1380157264.M261921P17392.mail2.aaa.com,S=3119,W=3175) dovecot: dsync-remote(a...@aaa.com): Warning: Maildir /var/mail/virtual/aaa.com/alex/.INBOX.System: Expunged message reappeared, giving a new UID (old uid=3654, file=1380157263.M819006P25260.mail2.aaa.com,S=2476,W=2553:2,) dovecot: dsync-remote(a...@aaa.com): Warning: Maildir /var/mail/virtual/aaa.com/alex/.INBOX.System: Expunged message reappeared, giving a new UID (old uid=3655, file=1380157264.M261922P17392.mail2.aaa.com,S=3119,W=3175:2,) As a result, synchronization was, but there were duplicate emails. After this synchronization is working fine, no more errors. dovecot --version 2.2.5 dovecot --build-options Build options: ioloop=kqueue notify=kqueue ipv6 openssl io_block_size=8192 Mail storages: shared mdbox sdbox maildir mbox cydir imapc pop3c raw fail SQL drivers: mysql Passdb: checkpassword pam passwd passwd-file sql Userdb: checkpassword nss passwd prefetch passwd-file sql Thanks! -- Best regards, Aleksey Tsvetkov System Administrator Company Grand Vision tel. +7(495)933-39-79, ext. 184
[Dovecot] Doveadm with a 2nd Instance
Hi Guys, I am trying to use 2 instances of Dovecot on the same server so I can have a Director managing my connections, everything appears to be working, but I can not use doveadm to control my 2nd instance, but doveconf seems to work fine. [user@server logs]$ doveconf -i Director | grep logs debug_log_path = /home/user/apps/logs/director/director_debug.log info_log_path = /home/user/apps/logs/director/director_info.log log_path = /home/user/apps/logs/director/director.log info_log_path = /home/user/apps/logs/director/director_lmtp.log [user@server logs]$ doveadm -i Director log find Debug: /home/user/apps/logs/dovecot_debug.log Info: /home/user/apps/logs/dovecot_info.log Warning: /home/user/apps/logs/dovecot.log Error: /home/user/apps/logs/dovecot.log Fatal: /home/user/apps/logs/dovecot.log I have stopped and started both my instances so the config running is what is in the config file, but when I use -i Director with doveadm it uses the other instances config. [user@server logs]$ doveadm instance list path name last used running /home/user/apps/dovecot/var/run/dovecot Dovecot 2013-09-26 00:39:14 yes /home/user/apps/dovecot/var/run/director Director 2013-09-26 00:32:31 yes Any ideas, or does anyone have any experience with the Dovecot instance feature? Chris
Re: [Dovecot] Passing info from mail process to mail_filter plugin script?
Timo Sirainen wrote: > On 25.9.2013, at 3.06, Charles Cazabon wrote: > > > > I hacked an additional %variable (I used %q) into a copy of > > mail-user.c:mail_user_var_expand_table () [...] > Better to not give a one character name, but only the long name so it won't > conflict with any future Dovecot additions. That was my plan. I added the single character key when I was trying to debug why it wasn't working. > > The %q does not appear to be getting replaced; it's just skipped over. > > It's not even passing an empty string in its place. [...] > It looks like this should be correct. The plugin settings expansion i done > by mail-user.c:mail_user_expand_plugins_envs(). Aha, thanks. My code to set this information was still not being called quite early enough, so the table didn't contain a value for my variable when mail_user_expand_plugins_envs() was called. I've rejigged it some more, and now it is indeed working. Thanks very much for your help with this. > The other possibility would be that you just modify mail-filter plugin and > add the extra parameter without any %variable changes. Probably better since > then you don't need to patch Dovecot core itself. Ah, perhaps that wasn't clear - this isn't a constant or anything like that. The extra argument getting passed to mail_filter is taken from data the client sends to the IMAP server -- so I needed to be able to pull it out of the IMAP session and pass it to the mail_filter script. Charles -- --- Charles Cazabon GPL'ed software available at: http://pyropus.ca/software/ ---
[Dovecot] recipient_delimiter
Can I enable $recipient_delimiter = ‘+’ for only the virtual sql users?
$ doveconf -n
# 2.2.5: /usr/local/etc/dovecot/dovecot.conf
# OS: FreeBSD 9.1-RELEASE i386
auth_mechanisms = PLAIN LOGIN
disable_plaintext_auth = no
first_valid_uid = 89
login_log_format_elements = user=<%u> %r %m %c
mail_location = maildir:~/Maildir
mail_max_userip_connections = 90
managesieve_notify_capability = mailto
managesieve_sieve_capability = fileinto reject envelope encoded-character
vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy
include variables body enotify environment mailbox date ihave
namespace inbox {
inbox = yes
location =
mailbox Drafts {
special_use = \Drafts
}
mailbox Junk {
auto = subscribe
special_use = \Junk
}
mailbox NotJunk {
auto = subscribe
}
mailbox Sent {
special_use = \Sent
}
mailbox "Sent Messages" {
special_use = \Sent
}
mailbox Trash {
special_use = \Trash
}
prefix =
}
passdb {
driver = pam
}
passdb {
args = /etc/dovecot/dovecot-sql.conf.ext
driver = sql
}
protocols = imap sieve
service auth {
unix_listener /var/spool/postfix/private/auth {
mode = 0666
}
}
service imap-login {
inet_listener imaps {
port = 993
ssl = yes
}
}
ssl_cert =
Re: [Dovecot] Dovecot extremely slow!
-- Computerisms Bob Miller 867-334-7117 / 867-633-3760 http://computerisms.ca On Wed, 2013-09-25 at 16:15 -0600, LuKreme wrote: > On 25 Sep 2013, at 16:05 , Patricio Rojo wrote: > > > I attach the 10-master configuration > > That’s not that useful. > > doveconf -n is useful > > As are the server logs, as opposed to the strace output...
Re: [Dovecot] Dovecot extremely slow!
On 25 Sep 2013, at 16:05 , Patricio Rojo wrote: > I attach the 10-master configuration That’s not that useful. doveconf -n is useful
[Dovecot] Dovecot extremely slow!
Please help,
Dovecot is running extremely slow for the last couple of weeks and it
seems to be getting worse (or my patience running short).
I attach the 10-master configuration and the log file after running
strace according to: http://wiki.dovecot.org/Debugging/ProcessTracing
I can click on an email and wait for a minute or more before receiving a
connection dropped or no error at all. I use many clients (thunderbird,
windows 8 mail, maildroid for android, squirrelmail) and they all have
similar behavior. It happens both in the inbox and on imap subfolders.
Sometimes it helps changing subfolders back and forth.
I have many imap folders organized in up to 3 levels of subfolders and
use postfix for delivery.
Let me know any other info you require. Thanks!
Patricio
#default_process_limit = 100
#default_client_limit = 1000
# Default VSZ (virtual memory size) limit for service processes. This is mainly
# intended to catch and kill processes that leak memory before they eat up
# everything.
#default_vsz_limit = 256M
# Login user is internally used by login processes. This is the most untrusted
# user in Dovecot system. It shouldn't have access to anything at all.
#default_login_user = dovenull
# Internal user is used by unprivileged processes. It should be separate from
# login user, so that login processes can't disturb other processes.
#default_internal_user = dovecot
service imap-login {
inet_listener imap {
#port = 143
}
inet_listener imaps {
#port = 993
#ssl = yes
}
# Number of connections to handle before starting a new process. Typically
# the only useful values are 0 (unlimited) or 1. 1 is more secure, but 0
# is faster.
#service_count = 1
# Number of processes to always keep waiting for more connections.
#process_min_avail = 0
# If you set service_count=0, you probably need to grow this.
#vsz_limit = $default_vsz_limit
}
service pop3-login {
inet_listener pop3 {
#port = 110
}
inet_listener pop3s {
#port = 995
#ssl = yes
}
}
service lmtp {
unix_listener lmtp {
#mode = 0666
}
# Create inet listener only if you can't use the above UNIX socket
#inet_listener lmtp {
# Avoid making LMTP visible for the entire internet
#address =
#port =
#}
}
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 = $default_vsz_limit
# Max. number of IMAP processes (connections)
#process_limit = 1024
}
service pop3 {
# Max. number of POP3 processes (connections)
#process_limit = 1024
}
service auth {
# auth_socket_path points to this userdb socket by default. It's typically
# used by dovecot-lda, doveadm, possibly imap process, etc. Users that have
# full permissions to this socket are able to get a list of all usernames and
# get the results of everyone's userdb lookups.
#
# The default 0666 mode allows anyone to connect to the socket, but the
# userdb lookups will succeed only if the userdb returns an "uid" field that
# matches the caller process's UID. Also if caller's uid or gid matches the
# socket's uid or gid the lookup succeeds. Anything else causes a failure.
#
# To give the caller full permissions to lookup all users, set the mode to
# something else than 0666 and Dovecot lets the kernel enforce the
# permissions (e.g. 0777 allows everyone full permissions).
unix_listener auth-userdb {
#mode = 0666
#user =
#group =
}
# Postfix smtp-auth
unix_listener /var/spool/postfix/private/auth {
user = postfix
group = postfix
mode = 0666
}
inet_listener {
port = 12345
}
# Auth process is run as this user.
#user = $default_internal_user
}
service auth-worker {
# Auth worker process is run as root by default, so that it can access
# /etc/shadow. If this isn't necessary, the user should be changed to
# $default_internal_user.
#user = root
}
service dict {
# If dict proxy is used, mail processes should have access to its socket.
# For example: mode=0660, group=vmail and global mail_access_groups=vmail
unix_listener dict {
#mode = 0600
#user =
#group =
}
}
18:29:13.833120 epoll_wait(9, {}, 6, 23980) = 0
18:29:37.837451 stat("/home/pato/mail/Astro/conferences",
{st_mode=S_IFREG|0644, st_size=112122083, ...}) = 0
18:29:37.838261 epoll_wait(9, {}, 6, 2) = 0
18:30:07.867721 stat("/home/pato/mail/Astro/conferences",
{st_mode=S_IFREG|0644, st_size=112122083, ...}) = 0
18:30:07.868340 epoll_wait(9, {}, 6, 28917) = 0
18:30:36.814608 write(11, "* OK Still here\r\n", 17) = 17
18:30:36.832177 time(NULL) = 1380144636
18:30:36.833279 epoll_wait(9, {{EPOLLIN, {u32=1413012688,
u64=139759648824528}}}, 6, 1034) = 1
18:30:37.065994 read(11, "DONE\r\n", 8030) = 6
18:30:37.066289 epoll_ctl(9, EPOLL_CTL_DEL, 11, {0, {u32=1413012688,
u64=139759648824528}}) = 0
18:30:37.066574 inotify_rm_watch(13, 2) = 0
18:30:
Re: [Dovecot] "service_count = 0" for "service dict" (High-performance mode)
On 25.9.2013, at 17.48, Alessio Cecchi wrote:
> I'm running dovecot 2.1.17 with "Login processes" in "High-performance mode"
> as explained here:
>
> service imap-login {
> service_count = 1
>
> http://wiki2.dovecot.org/LoginProcess
>
> but i thinks I should also set "service dict" in high-performance mode since
> sometimes the number of dict processes reach the limit of 100 (from
> default_process_limit=100) and I find these errors in the logs:
>
> Sep 25 15:32:24 imap(info@), session=: Error:
> read(/usr/local/dovecot-2.1/var/run/dovecot/dict) failed: Connection reset by
> peer
> Sep 25 15:32:24 imap(service@), session=: Error:
> read(/usr/local/dovecot-2.1/var/run/dovecot/dict) failed: Connection reset by
> peer
dict lookups are synchronous. There can never be more than 1 client handled
simultaneously, so it's not a good idea to set dict's client_limit above 1.
> Do you think will be better set:
>
> service dict {
> service_count = 0
This is already 0 by default. The limiting factor is the client_limit, which is
1.
> or default_process_limit=200 (instead of 100)
Not necessary either to do such a global change. I'd set:
service dict {
process_limit = 200 # or more
}
[Dovecot] "service_count = 0" for "service dict" (High-performance mode)
Hi,
I'm running dovecot 2.1.17 with "Login processes" in "High-performance
mode" as explained here:
service imap-login {
service_count = 1
http://wiki2.dovecot.org/LoginProcess
but i thinks I should also set "service dict" in high-performance mode
since sometimes the number of dict processes reach the limit of 100
(from default_process_limit=100) and I find these errors in the logs:
Sep 25 15:32:24 imap(info@), session=: Error:
read(/usr/local/dovecot-2.1/var/run/dovecot/dict) failed: Connection
reset by peer
Sep 25 15:32:24 imap(service@), session=: Error:
read(/usr/local/dovecot-2.1/var/run/dovecot/dict) failed: Connection
reset by peer
or
Sep 25 15:33:48 imap(info@), session=: Warning:
read(/usr/local/dovecot-2.1/var/run/dovecot/dict): dict lookup took 5
seconds
Sep 25 15:33:48 imap(editoria@), session=<3LpHZTTnDgBdJwmm>:
Warning: read(/usr/local/dovecot-2.1/var/run/dovecot/dict): dict lookup
took 5 seconds
Do you think will be better set:
service dict {
service_count = 0
or default_process_limit=200 (instead of 100)
Thanks
--
Alessio Cecchi is:
@ ILS -> http://www.linux.it/~alessice/
on LinkedIn -> http://www.linkedin.com/in/alessice
Assistenza Sistemi GNU/Linux -> http://www.cecchi.biz/
@ PLUG -> ex-Presidente, adesso senatore a vita, http://www.prato.linux.it
Re: [Dovecot] proxy: get rid of redundant log-informations
Hi
Am 22.09.2013 03:13, schrieb Reindl Harald:
> Am 22.09.2013 02:20, schrieb Timo Sirainen:
>> %$ is the status, so you're asking for another status variable. Something
>> like in the attached patch, where you can replace %$ with %{login_status}?
>
> *exactly* that's it - many thanks!
>
> %{login_status} -> ab[2].value = client->login_success ? "OK" : "Failed";
> in case of deeper debugging one can always set "%$" temporary
>
> when we can get rid of "TLSv1 with cipher" and only have the cipher the log
> would become
> really tiny and easy to follow without too much linebreaking - not to forget
> the logsize
> in case of a lot of POP3 users every few minutes
nearly perfect
___
2.2.6 with the patch:
Sep 25 12:22:26 testserver dovecot: pop3-login: OK: p...@testserver.rhsoft.net,
91.118.73.100, DIGEST-MD5, TLSv1
with cipher RC4-SHA (128/128 bits)
Sep 25 12:22:26 testserver dovecot: pop3-login: OK: p...@testserver.rhsoft.net,
91.118.73.100, DIGEST-MD5, TLSv1
with cipher RC4-SHA (128/128 bits)
___
my dream:
Sep 25 12:22:26 testserver dovecot: pop3-login: OK: p...@testserver.rhsoft.net,
91.118.73.100, DIGEST-MD5, RC4-SHA
(128/128 bits)
Sep 25 12:22:26 testserver dovecot: pop3-login: OK (disconnecting):
p...@testserver.rhsoft.net, 91.118.73.100,
DIGEST-MD5, RC4-SHA (128/128 bits)
___
would allow rsyslog to skip the disconnect lines in case of OK and shorten the
cipher output
:msg, contains, "OK (disconnecting)" ~
diff -r d400c1a673cf src/login-common/client-common.c
--- a/src/login-common/client-common.c Sun Sep 22 03:17:12 2013 +0300
+++ b/src/login-common/client-common.c Sun Sep 22 03:17:44 2013 +0300
@@ -561,9 +561,10 @@
static const char *
client_get_log_str(struct client *client, const char *msg)
{
- static struct var_expand_table static_tab[3] = {
+ static struct var_expand_table static_tab[] = {
{ 's', NULL, NULL },
{ '$', NULL, NULL },
+ { '\0', NULL, "login_status" },
{ '\0', NULL, NULL }
};
const struct var_expand_table *var_expand_table;
@@ -603,6 +604,7 @@
tab[0].value = t_strdup(str_c(str));
tab[1].value = msg;
+ tab[2].value = client->login_success ? "OK" : "Failed";
str_truncate(str, 0);
var_expand(str, client->set->login_log_format, tab);
signature.asc
Description: OpenPGP digital signature
Re: [Dovecot] unable to lock for exclusive access: Resource temporarily unavailable
Am 25.09.2013 11:17, schrieb n...@ecs.gr: > Could you please provide more information about what you mean with > Maildir format? I am not so familiar. > Is it a quick and stable solution? > > Best Regards, > > Nikos > > Quoting Timo Sirainen : > >> On 25.9.2013, at 10.27, Nikos Papadopoulos wrote: >> >>> We have a mail server (RHEL 6.0, Postfix and Dovecot 1.0.7). >>> >>> mail_location: mbox:~/mail:INBOX=/var/mail/%u >>> >>> There is great delay in the delivery of the emails. Some seem to not be >>> delivered at all. Issuing the mailq command we get the following >>> message for >>> almost all the email accounts: >>> >>> (cannot update mailbox /var/mail/xyz for user xyz. unable to lock for >>> exclusive access: Resource temporarily unavailable) >> >> mbox format is problematic in this way. Newer Dovecot versions (v2.x) >> do some extra work to unlock the mbox earlier with POP3. That might >> help you. Or you could switch to Maildir format where this isn't a >> problem. I'm not sure why it started happening only now and not >> earlier. Perhaps the POP3 clients are downloading mails more slowly, >> perhaps you're getting more mail and things are running slower than >> before. >> >> > > Maildir is a standard specification http://wiki.dovecot.org/MailboxFormat/Maildir http://wiki.dovecot.org/MailboxFormat/ there is no easy answer what might be better to use at your side , this depends on your setup ( how many mailboxes, how many mails , how big are mailboxes etc , storagekind etc, traffic , how many pop3 vs imap logins ) your dovecot version is very old , you should upgrade or migrate in any case Best Regards MfG Robert Schetterer -- [*] sys4 AG http://sys4.de, +49 (89) 30 90 46 64 Franziskanerstraße 15, 81669 München Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263 Vorstand: Patrick Ben Koetter, Axel von der Ohe, Marc Schiffbauer Aufsichtsratsvorsitzender: Florian Kirstein
Re: [Dovecot] unable to lock for exclusive access: Resource temporarily unavailable
Could you please provide more information about what you mean with Maildir format? I am not so familiar. Is it a quick and stable solution? Best Regards, Nikos Quoting Timo Sirainen : On 25.9.2013, at 10.27, Nikos Papadopoulos wrote: We have a mail server (RHEL 6.0, Postfix and Dovecot 1.0.7). mail_location: mbox:~/mail:INBOX=/var/mail/%u There is great delay in the delivery of the emails. Some seem to not be delivered at all. Issuing the mailq command we get the following message for almost all the email accounts: (cannot update mailbox /var/mail/xyz for user xyz. unable to lock for exclusive access: Resource temporarily unavailable) mbox format is problematic in this way. Newer Dovecot versions (v2.x) do some extra work to unlock the mbox earlier with POP3. That might help you. Or you could switch to Maildir format where this isn't a problem. I'm not sure why it started happening only now and not earlier. Perhaps the POP3 clients are downloading mails more slowly, perhaps you're getting more mail and things are running slower than before.
Re: [Dovecot] v2.2.6 released
* Timo Sirainen : > http://dovecot.org/releases/2.2/dovecot-2.2.6.tar.gz > http://dovecot.org/releases/2.2/dovecot-2.2.6.tar.gz.sig Works like a charm here. Tinkering with ciphers & ssl_prefer_server_ciphers now. -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebra...@charite.de | http://www.charite.de
Re: [Dovecot] unable to lock for exclusive access: Resource temporarily unavailable
On 25.9.2013, at 10.27, Nikos Papadopoulos wrote: > We have a mail server (RHEL 6.0, Postfix and Dovecot 1.0.7). > > mail_location: mbox:~/mail:INBOX=/var/mail/%u > > There is great delay in the delivery of the emails. Some seem to not be > delivered at all. Issuing the mailq command we get the following message for > almost all the email accounts: > > (cannot update mailbox /var/mail/xyz for user xyz. unable to lock for > exclusive access: Resource temporarily unavailable) mbox format is problematic in this way. Newer Dovecot versions (v2.x) do some extra work to unlock the mbox earlier with POP3. That might help you. Or you could switch to Maildir format where this isn't a problem. I'm not sure why it started happening only now and not earlier. Perhaps the POP3 clients are downloading mails more slowly, perhaps you're getting more mail and things are running slower than before.
[Dovecot] unable to lock for exclusive access: Resource temporarily unavailable
Dears, We have a mail server (RHEL 6.0, Postfix and Dovecot 1.0.7). The output of dovecot -n is the following: # 1.0.7: /etc/dovecot.conf protocols: pop3 login_dir: /var/run/dovecot/login login_executable: /usr/libexec/dovecot/pop3-login mail_location: mbox:~/mail:INBOX=/var/mail/%u mail_executable: /usr/libexec/dovecot/pop3 mail_plugin_dir: /usr/lib/dovecot/pop3 pop3_client_workarounds: outlook-no-nuls oe-ns-eoh auth default: passdb: driver: pam userdb: driver: passwd During the last days we face the following problem: There is great delay in the delivery of the emails. Some seem to not be delivered at all. Issuing the mailq command we get the following message for almost all the email accounts: (cannot update mailbox /var/mail/xyz for user xyz. unable to lock for exclusive access: Resource temporarily unavailable) Please send to me any suggestions, because I cannot resolve it and I receive a lot of pressure. Best Regards, Nikos
[Dovecot] v2.2.6 released
http://dovecot.org/releases/2.2/dovecot-2.2.6.tar.gz
http://dovecot.org/releases/2.2/dovecot-2.2.6.tar.gz.sig
I didn't have time to look into the latest reported dsync replication bugs, but
this release should have been done a long time ago already and I'm busy for
next few days, so no more waiting. Things seem to be working quite well in
general though.
* acl: If public/shared namespace has a shared subscriptions file for
all users, don't list subscription entries that are not visible to
the user accessing it.
+ doveadm: Added "auth lookup" command for doing passdb lookup.
+ login_log_format_elements: Added %{orig_user}, %{orig_username}
and %{orig_domain} expanding to the username exactly as sent by
the client (before any changes auth process made).
+ Added ssl_prefer_server_ciphers setting.
+ auth_verbose_passwords: Log the password also for unknown users.
+ Linux: Added optional support for SO_REUSEPORT with
inet_listener { reuse_port=yes }
- director: v2.2.5 changes caused "SYNC lost" errors
- dsync: Many fixes and error handling improvements
- doveadm -A: Don't waste CPU by doing a separate config lookup
for each user
- Long-running ssl-params process no longer prevents Dovecot restart
- mbox: Fixed mailbox_list_index=yes to work correctly
