[Dovecot] Dsync converting dbox-Maildir
Hi! I've changed my mailbox format from dbox to Maildir. The problem is maildir message filename extension has no S=/W= field after migration. Using dovecot 2.1.15.
Re: [Dovecot] backing up maildir dovecot files
Am 13.02.2013 08:20, schrieb Steffen Kaiser: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, 12 Feb 2013, David Mehler wrote: Thanks, if I did: rsync --force --delete-after -tPrlHpogEAXz /folder/ /backups/newmailstore/ could I then tar up the newmailstore folder with something like tar zcf without messing anything up? keep in mind, that the backup of the Maildir with rsync is no 100% consistent snapshot, because of the filename renames; otherwise: yes who would rename them and why? signature.asc Description: OpenPGP digital signature
Re: [Dovecot] Is there any way to mask or hide the INBOX label for Dovecot 1.2.x Shared Mailboxes?
On 13.2.2013, at 0.12, Jason Discount dovecot@practiceofcode.com wrote: I'm setting up a new Dovecot sever to replace an old Cyrus server, and need to keep things as consistent as possible. I have a couple local accounts, like junkmail and notjunkmail that users get shared access to, and can drop things in to train sa-update. However, when users share over junkmail's inbox, it's displayed in the hierarchy: • Other Users • junkmail • INBOX Is there any way to get junkmail's INBOX to just show up at Other Users/junkmail and not require that extra depth? • Other Users • junkmail mail_shared_explicit_inbox=no I'm running Debian Squeeze and the standard dovecot package available therein: # uname -a Linux internet.digitalquay.com.au 2.6.32-5-xen-amd64 #1 SMP Sun Sep 23 13:49:30 UTC 2012 x86_64 GNU/Linux #dovecot --version 1.2.15 You need v2.1.6 or newer. Debian backports has 2.1.7.
Re: [Dovecot] Imap process crash: assertion failed: (full_fs_access)
On 11.2.2013, at 12.20, Joseph Tam jtam.h...@gmail.com wrote:
Timo Sirainen t...@iki.fi writes:
Any guess at what would cause this?
Feb 7 21:20:53 server dovecot: imap(user): Panic: file
mailbox-list-fs-iter.c: line 447 (fs_list_get_roots): assertion
failed: (full_fs_access)
LIST command that had invalid parameters that somehow got through the
first validity check. What namespace config do you have?
namespace {
alias_for =
hidden = yes
list = no
location =
prefix = /
separator = /
}
This one causes these crashes. Fixed in v2.2 now:
http://hg.dovecot.org/dovecot-2.2/rev/fb367a977077
Re: [Dovecot] dsync 2.1.10 does not correctly handle renames of mailbox subtrees
On 12.2.2013, at 11.19, Karol Jurak karol.ju...@gmail.com wrote: It seems that dsync 2.1.10 does not correctly handle renames of mailbox subtrees. The scenario is as follows. I'm hoping I won't have to fix this in v2.1. v2.2 has a redesigned dsync where rename syncing should work much better.
Re: [Dovecot] dsync 2.1.10 does not correctly handle renames of mailbox subtrees
On 13 February 2013 11:46, Timo Sirainen t...@iki.fi wrote:
On 12.2.2013, at 11.19, Karol Jurak karol.ju...@gmail.com wrote:
It seems that dsync 2.1.10 does not correctly handle renames of mailbox
subtrees. The scenario is as follows.
I'm hoping I won't have to fix this in v2.1. v2.2 has a redesigned dsync
where rename syncing should work much better.
Would you mind taking a look at the following patch? It appends to
dovecot.mailbox.log records describing
renames of all mailboxes in a subtree, not just the top level one. My basic
tests showed that this indeed allows
dsync to correctly replicate the renames, but I'm not familiar with dovecot
internals enough to be confident that this
doesn't break something else.
diff --git a/src/lib-storage/index/index-storage.c
b/src/lib-storage/index/index-storage.c
index 6d0771c..292c0fa 100644
--- a/src/lib-storage/index/index-storage.c
+++ b/src/lib-storage/index/index-storage.c
@@ -584,6 +584,9 @@ int index_storage_mailbox_rename(struct mailbox *src,
struct mailbox *dest,
bool rename_children)
{
guid_128_t guid;
+ struct mailbox_list_iterate_context *iter;
+ const char *pattern;
+ const struct mailbox_info *info;
if (src-list-v.rename_mailbox(src-list, src-name,
dest-list, dest-name,
@@ -596,6 +599,23 @@ int index_storage_mailbox_rename(struct mailbox *src,
struct mailbox *dest,
non-selectable mailbox (directory), which doesn't even have a
GUID */
mailbox_name_get_sha128(dest-name, guid);
mailbox_list_add_change(src-list, MAILBOX_LOG_RECORD_RENAME, guid);
+
+ if (rename_children) {
+ pattern = t_strdup_printf(%s%c*, dest-name,
+ mail_namespace_get_sep(dest-list-ns));
+
+ iter = mailbox_list_iter_init(dest-list, pattern,
+ MAILBOX_LIST_ITER_RETURN_NO_FLAGS);
+
+ while ((info = mailbox_list_iter_next(iter)) != NULL) {
+ mailbox_name_get_sha128(info-name, guid);
+ mailbox_list_add_change(src-list,
MAILBOX_LOG_RECORD_RENAME,
+ guid);
+ }
+
+ mailbox_list_iter_deinit(iter);
+ }
+
return 0;
}
Re: [Dovecot] Broken physical size caching in Dovecot 2.1.10
On 05/02/13 02:06, Timo Sirainen wrote: On Tue, 2013-01-29 at 19:58 +, Rob Redpath wrote: I'm encountering two, probably related, errors in my Dovecot 2.1.10 install. The issue relates to compressed email stored in Maildir format directories. In some cases, a mailbox will become inaccessible, and the following will be logged from a doveadm fetch:- doveadm(i...@example.com): Error: Corrupted index cache file /var/spool/virtual_mail/info_example.com_d/dovecot.index.cache: Broken physical size for mail UID 2777 doveadm(i...@example.com): Error: Cached message size smaller than expected (18996 64624) doveadm(i...@example.com): Error: Maildir filename has wrong S value, renamed the file from /var/spool/virtual_mail/info_example.com_d/cur/1277451630.H877760P14612.mailserver.example.com,S=18996:2,Z to /var/spool/virtual_mail/info_example.com_d/cur/1277451630.H877760P14612.mailserver.example.com,S=18996:2,Z Interestingly, the file mentioned in the error ( /var/spool/virtual_mail/info_example.com_d/dovecot.index.cache ) doesn't exist. The uncompressed size of the file is 64624 bytes, the compressed size is 18996. Dovecot's zlib plugin requires that the maildir filenames have ,S=uncompressed size. Otherwise you get those errors. http://dovecot.org/tools/maildir-size-check.sh can be used to fix the filenames. Thanks for this. The problem I'm encountering is that Dovecot renames files, and does so to their size on disk rather than their uncompressed size, undoing any corrective action that's been taken. For example:- [root@mailserver ~]# ls /var/spool/virtual_mail/info_example.com_d/cur/1287153356.H12P6490.mailserver.example.net,S=4580:2,SZ /var/spool/virtual_mail/info_example.com_d/cur/1287153356.H12P6490.mailserver.example.net,S=4580:2,SZ [root@mailserver ~]# zcat /var/spool/virtual_mail/info_example.com_d/cur/1287153356.H12P6490.mailserver.example.net,S=4580:2,SZ | wc 3451530 24587 [root@mailserver ~]# mv /var/spool/virtual_mail/info_example.com_d/cur/1287153356.H12P6490.mailserver.example.net,S=4580:2,SZ /var/spool/virtual_mail/info_example.com_d/cur/1287153356.H12P6490.mailserver.example.net,S=24587:2,SZ [root@mailserver ~]# doveadm fetch -u i...@example.com text all /dev/null snip doveadm(i...@example.com): Error: Maildir filename has wrong S value, renamed the file from /var/spool/virtual_mail/info_example.com_d/cur/1287153356.H12P6490.mailserver.example.net,S=24587:2,SZ to /var/spool/virtual_mail/info_example.com_d/cur/1287153356.H12P6490.mailserver.example.net,S=4580:2,SZ /snip
[Dovecot] dovecot-uidlist crashing and re retriving messages by pop3 clients
Hello, I have issue with dovecot (v. 2.1.13)configuration after implementation dovecot-lda (I used maildrop earlier). Now i have 9 servers with storage by NFS v3. My problem is frequently dovecot-uidlist crashing. 2013-02-13T13:34:02.447969+01:00 k1 dovecot: imap(u...@domain.com): Error: Broken file /path_to_mailbox/dovecot-uidlist line 3170: Invalid data: 2013-02-13T13:34:34.527715+01:00 k1 dovecot: pop3(u...@domain.com): Error: Broken file /path_to_mailbox/dovecot-uidlist line 367: Invalid data: It happens few time in minute for diferent users and has effect to re retriving messages by pop3 clients. This my NFS mount options: (rw,tcp,vers=3,actimeo=0) 10-mail.conf options: mmap_disable = yes dotlock_use_excl = yes mail_fsync=always mail_nfs_storage = yes mail_nfs_index = yes lock_method = dotlock I do not know what I did wrong and how solve this issue. Maybe NFS v4 or fcntl locks or migration to pop3_uidl_format = %g will by solution. Please some hint. Please any help for solve this issue and sorry my english.
Re: [Dovecot] backing up maildir dovecot files
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wed, 13 Feb 2013, Reindl Harald wrote: Thanks, if I did: rsync --force --delete-after -tPrlHpogEAXz /folder/ /backups/newmailstore/ could I then tar up the newmailstore folder with something like tar zcf without messing anything up? keep in mind, that the backup of the Maildir with rsync is no 100% consistent snapshot, because of the filename renames; otherwise: yes who would rename them and why? /folder/ would be a Maildir on a production mail server. If rsync runs (without help from other funtionality, such as LVM or ZFS snapshots) and at the same time someone accesses the Maildir and: a) sees a message, which lets Dovecot rename the message file from ***/new/ to ***/cur b) tags a message with a keyword, which lets Dovecot rename the file to have some lower-case letter c) untags a keyword - remove that letter from the filename d) changes Deleted, Read, Answered status -- add/remove an upper-case letter from filename rsync might have cached a message with an old filename no longer physically present on disk. You will see a XYZ vanished message and that particular message is not backuped, but removed from backup. Some scripts use rsync in a loop in assumption, that no Maildir is accessed that often, that you get a clean run of rsync eventually. Maybe, if you tag a message with a new keyword, rsync already copied dovecot-keywords without the new keyword, but copy the message, when its filename has the keyword-letter. In fact, if I want to make 100% sure I get an exact copy, I do this: rsync /from /to rsync /from /to mv /from /from_locked sleep 1 rsync /from_locked /to mv /from_locked /from /from is the base directory of the Maildir. In my environment that causes tempfails on delivery and internal server errors on IMAP/POP3 access. But the time between the two mv's is very small, because the main differences are handled with the first two rsync's. As you seen, I copy one user after another, which breaks hardlinks between users, but keeps memory footprint of rsync low and as well as the downtime. I do make my usual daily backups without the loop and the mv's, because it is very seldom I get the vanished messages. I suppose, because the script runs two hours after midnight. - -- Steffen Kaiser -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iQEVAwUBURuQIF3r2wJMiz2NAQKgjgf8CtyeO6pONFU038x8O2wggcntdvGyeg8Z Uq8KR0QFVg1n0HNDaa33OYN4IxSHX8zNvElf+wc0ejQ3NUOPVDl2mdm4iEihyOYv Veb/p2iK671Nrs8nB7USwx7OE9vY8IYoB/ZSXrXGWowqOqRQIcJWHAfZ9Ewj3Rg/ iRGMUNCn7UfEDfWl+F5yWpdp/+3xJGxoWeWaegW/yfTzlJ5nKffS/SAfJlUm7zuV u31JL4fjk25uGG7alzrCxOq0z4A3PvcpGag2nkfIRbrLLmo4Wzr+09Bd2zqmSn74 /PaHlxFS6a2uy7ugqdd5kxfiZHnOS2/d6JgV428I8qS0CWugEPuFbg== =mw5e -END PGP SIGNATURE-
Re: [Dovecot] Authentication with many Windows AD
El 12/02/13 11:36, Antonio Alberola escribió: Dear All, I'm a new user of Dovecot and I need support with the authentication process. I use Dovecot 2.0.9 and Postfix 2.6.6 on host x86_64-redhat-linux-gnu 2.6.32-279.14.1.el6.x86_64 CentOS release 6.3 (Final) I need to select the validation method depending on the user. I have users that have to be authenticate with UNIX account, and I have others thats have to be authenticate with Windows AD. For example, some sysadmins and special accounts needs validate with Unix accounts. Other normal users have to authenticate with Windows AD, I have many Windows controllers. Some users authenticate to a specific Windows AD and other users are validated in another one. How I can do this? You can set as many databases as you want. Check this: http://wiki2.dovecot.org/PasswordDatabase http://wiki2.dovecot.org/Authentication/MultipleDatabases HTH
Re: [Dovecot] dovecot-uidlist crashing and re retriving messages by pop3 clients
On 13.2.2013, at 13.57, Piotr Rotter piotr.rot...@active24.pl wrote: I have issue with dovecot (v. 2.1.13)configuration after implementation dovecot-lda (I used maildrop earlier). Now i have 9 servers with storage by NFS v3. My problem is frequently dovecot-uidlist crashing. 2013-02-13T13:34:02.447969+01:00 k1 dovecot: imap(u...@domain.com): Error: Broken file /path_to_mailbox/dovecot-uidlist line 3170: Invalid data: 2013-02-13T13:34:34.527715+01:00 k1 dovecot: pop3(u...@domain.com): Error: Broken file /path_to_mailbox/dovecot-uidlist line 367: Invalid data: It happens few time in minute for diferent users and has effect to re retriving messages by pop3 clients. Use director: http://wiki2.dovecot.org/Director
Re: [Dovecot] FreeBSD, Dovecot and ZFS
WAG would be similar issues you can face when using NFS with multiple
servers accessing it (file locking issues).
The solution would be to use Director to make sure users are always directed
to the same server.
http://wiki2.dovecot.org/Director
If that isn't the problem, then much more info would be needed (ie, doveconf
-n output, logs exhibiting the problem, etc)...
--
Best regards,
*/Charles /*
Thank you for your reply. To further expand the problem does not happen with
any regularity, we went over 30 days with no issue after two weeks of sporadic
occurrences. It usually only appears, if at all, any time after 2:00 PM (i.e.
14:30, 15:20, 16:10). And not every day (has not happened on a weekend). The
number of POP3 and IMAP processes increase dramatically when the issue occurs.
Here is a copy of the dovecot -n output
# 1.2.17: /usr/local/etc/dovecot.conf
# OS: FreeBSD 8.1-RELEASE-p5 i386 nfs
protocols: imap imaps pop3 pop3s
ssl_cert_file: /mail/shared/etc/ssl/certs/dovecot.pem
ssl_key_file: /mail/shared/etc/ssl/private/dovecot.pem
disable_plaintext_auth: no
login_dir: /var/run/dovecot/login
login_executable(default): /usr/local/libexec/dovecot/imap-login
login_executable(imap): /usr/local/libexec/dovecot/imap-login
login_executable(pop3): /usr/local/libexec/dovecot/pop3-login
login_greeting: Hello there, who might you be?
max_mail_processes: 4096
verbose_proctitle: yes
first_valid_uid: 26
first_valid_gid: 0
mail_privileged_group: mail
mail_location: maildir:/mail/store/%d/%n
mmap_disable: yes
dotlock_use_excl: no
mail_nfs_storage: yes
mail_nfs_index: yes
lock_method: dotlock
mail_executable(default): /usr/local/libexec/dovecot/imap
mail_executable(imap): /usr/local/libexec/dovecot/imap
mail_executable(pop3): /usr/local/libexec/dovecot/pop3
mail_plugin_dir(default): /usr/local/lib/dovecot/imap
mail_plugin_dir(imap): /usr/local/lib/dovecot/imap
mail_plugin_dir(pop3): /usr/local/lib/dovecot/pop3
imap_client_workarounds(default): delay-newmail outlook-idle netscape-eoh
tb-extra-mailbox-sep
imap_client_workarounds(imap): delay-newmail outlook-idle netscape-eoh
tb-extra-mailbox-sep
imap_client_workarounds(pop3):
pop3_client_workarounds(default):
pop3_client_workarounds(imap):
pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh
lda:
postmaster_address: {REMOVED}
sendmail_path: /usr/local/sbin/exim
auth default:
default_realm: {REMOVED}
username_format: %Lu
passdb:
driver: sql
args: /mail/shared/etc/dovecot-sql.conf
userdb:
driver: passwd
userdb:
driver: static
args: uid=26 gid=6 home=/mail/store/%d/%n
Re: [Dovecot] FreeBSD, Dovecot and ZFS
At 9PM + on 12/02/13 you (Jason Lock) wrote: Mail Issues - FreeBSD Hello, my apologies if this may be the wrong forum but hoping that maybe someone might be able to provide some insight. This may turn out to be something better addressed on freebsd-stable, but this is a perfectly good place to start. Thank you for your reply. Have a very sporadic and strange issue with our mail servers running Dovecot on FreeBSD. There are three servers hosting Dovecot with FreeBSD as the underlying operating system. All three connect to a NAS server, again running FreeBSD and ZFS. Over NFS, I assume? What version, what mount options, and what type of authentication? Yes, using NFSv3 to attach the share from the NAS to each of the POP3/IMAP servers. Only mount options set are RW. Not authentication in place, NAS and POP3/IMAP Servers share VLAN just for the NAS connections. What locking strategies is Dovecot using? In dovecot using the following: dotlock_use_excl: no mail_nfs_storage: yes mail_nfs_index: yes lock_method: dotlock Are there any suspicious messages in syslog on either machine? Nothing specific. When the specific issue occurs, clients connecting to check mail via POP3 or IMAP experience long delays and timeouts. To the point where POP3 Logins fail due to the timeouts. The issue is further compounded by clients increasing the number of attempts to check mail. Are the delays happening before or after login? Delays appear during login, username gets passed but then timeouts after the password is sent. If you can provoke this and get a 'procstat -k' for the relevant dovecot process this might be helpful. If 'long' delays means several minutes, running something along the lines of 'procstat -k $(pgrep -U dovecot -U doveauth)' every minute or so for a while might be one way to catch this, though this will collect a lot of data rather fast so you will need some way to locate the relevant entry. Will look to capture that information if possible, have not been able to re-create the situation in which the issue occurs. Ben
Re: [Dovecot] Broken physical size caching in Dovecot 2.1.10
On 05/02/13 02:06, Timo Sirainen wrote: On Tue, 2013-01-29 at 19:58 +, Rob Redpath wrote: I'm encountering two, probably related, errors in my Dovecot 2.1.10 install. The issue relates to compressed email stored in Maildir format directories. In some cases, a mailbox will become inaccessible, and the following will be logged from a doveadm fetch:- doveadm(i...@example.com): Error: Corrupted index cache file /var/spool/virtual_mail/info_example.com_d/dovecot.index.cache: Broken physical size for mail UID 2777 doveadm(i...@example.com): Error: Cached message size smaller than expected (18996 64624) doveadm(i...@example.com): Error: Maildir filename has wrong S value, renamed the file from /var/spool/virtual_mail/info_example.com_d/cur/1277451630.H877760P14612.mailserver.example.com,S=18996:2,Z to /var/spool/virtual_mail/info_example.com_d/cur/1277451630.H877760P14612.mailserver.example.com,S=18996:2,Z Interestingly, the file mentioned in the error ( /var/spool/virtual_mail/info_example.com_d/dovecot.index.cache ) doesn't exist. The uncompressed size of the file is 64624 bytes, the compressed size is 18996. Dovecot's zlib plugin requires that the maildir filenames have ,S=uncompressed size. Otherwise you get those errors. http://dovecot.org/tools/maildir-size-check.sh can be used to fix the filenames. Thanks for this. The problem I'm encountering is that Dovecot renames files, and does so to their size on disk rather than their uncompressed size, undoing any corrective action that's been taken. For example:- [root@mailserver ~]# ls /var/spool/virtual_mail/info_example.com_d/cur/1287153356.H12P6490.mailserver.example.net,S=4580:2,SZ /var/spool/virtual_mail/info_example.com_d/cur/1287153356.H12P6490.mailserver.example.net,S=4580:2,SZ [root@mailserver ~]# zcat /var/spool/virtual_mail/info_example.com_d/cur/1287153356.H12P6490.mailserver.example.net,S=4580:2,SZ | wc 3451530 24587 [root@mailserver ~]# mv /var/spool/virtual_mail/info_example.com_d/cur/1287153356.H12P6490.mailserver.example.net,S=4580:2,SZ /var/spool/virtual_mail/info_example.com_d/cur/1287153356.H12P6490.mailserver.example.net,S=24587:2,SZ [root@mailserver ~]# doveadm fetch -u i...@example.com text all /dev/null snip doveadm(i...@example.com): Error: Maildir filename has wrong S value, renamed the file from /var/spool/virtual_mail/info_example.com_d/cur/1287153356.H12P6490.mailserver.example.net,S=24587:2,SZ to /var/spool/virtual_mail/info_example.com_d/cur/1287153356.H12P6490.mailserver.example.net,S=4580:2,SZ /snip
[Dovecot] Renaming not supported across conflicting directory permissions
Is it possible to disable this check in 2.1.7? (without a patch and re-compile?)
[Dovecot] Requested xxxx scheme, but we have a NULL password after upgrade
I'm having an issue I can't seem to work around after upgrading from Dovecot
1.0.7 to 1.2.17.
After getting Dovecot 1.07 working on CentOS 5.9, I decided that it might be
wise to upgrade to a later version, so I stuck with 1.x and went with
1.2.17, which I had to compile from source. CentOS was originally using
/etc as the starting path for Dovecot files but the source distribution puts
most of the stuff under /usr/local/etc. After the usual configmakemake
install dance I made the necessary changes to point to the new libraries,
modules, etc. and the imap-login: Fatal: Dovecot version mismatch: Master
is v1.2.17, login is v1.0.7 messages went away.
After doing this though I cannot login, I get the following error messages:
Feb 13 15:50:40 auth(default): Info: client in: AUTH7 NTLM
service=imaplip=192.168.2.102 rip=192.168.2.100 lport=143
rport=1470
Feb 13 15:50:40 auth(default): Info: client out: CONT 7
Feb 13 15:50:40 auth(default): Info: client in: CONT7
TlRMTVNTUAABB4IIogAFASgKDw==
Feb 13 15:50:40 auth(default): Info: client out: CONT 7
TlRMTVNTUAACMAAwADAFAooATj7XW6ve2hwAADgAOABgUwBlAHIAdgBlAHIAMQAuAGgAZQByAHMAYwBoAGwAYQB1AHIAZQBuAC4AYwBvAG0AAwAwAFMAZQByAHYAZQByADEALgBoAGUAcgBzAGMAaABsAGEAdQByAGUAbgAuAGMAbwBtAAA=
Feb 13 15:50:40 auth(default): Info: client in: CONT7
TlRMTVNTUAADGAAYAGoAAABoAGgAggBIEAAQAEgSABIAWADqBQKIAgUBKAoP*CENSORED*bgBiAFEAUwBFAC0AVwBJAE4AWABQAEXO6p/WuopqQ02x1kzJGW3NoQELKw32N88JqkbMOYOVErhiS492elwBAQAAA*CENSORED*ysN9jcAAwAwAFMAZQByAHYAZQByADEALgBoAGUAcgBzAGMAaABsAGEAdQByAGUAbgAuAGMAbwBt
Feb 13 15:50:40 auth(default): Info: cache(pquesinb,192.168.2.100): miss
Feb 13 15:50:40 auth(default): Info: passwd-file(pquesinb,192.168.2.100):
lookup: user=pquesinb file=/etc/dovecot.users
Feb 13 15:50:40 auth(default): Info: password(pquesinb,192.168.2.100):
Requested NTLM scheme, but we have a NULL password
Feb 13 15:50:40 auth(default): Info: cache(pquesinb,192.168.2.100): miss
Feb 13 15:50:40 auth(default): Info: password(pquesinb,192.168.2.100):
passdb doesn't support credential lookups
Feb 13 15:50:40 auth(default): Info: cache(pquesinb,192.168.2.100): miss
Feb 13 15:50:40 auth(default): Info: password(pquesinb,192.168.2.100):
passdb doesn't support credential lookups
Feb 13 15:50:40 auth(default): Info: cache(pquesinb,192.168.2.100): miss
Feb 13 15:50:40 auth(default): Info: password(pquesinb,192.168.2.100):
passdb doesn't support credential lookups
Feb 13 15:50:40 auth(default): Info: cache(pquesinb,192.168.2.100): miss
Feb 13 15:50:40 auth(default): Info: password(pquesinb,192.168.2.100):
passdb doesn't support credential lookups
Feb 13 15:50:42 auth(default): Info: client out: FAIL 7
user=pquesinb
Looking at the log from the old version while it was working, I was getting
messages like the following:
dovecot: Feb 04 14:14:21 Info: imap-login: Login: user=pquesinb,
method=NTLM, rip=192.168.2.100, lip=192.168.2.102
dovecot: Feb 04 14:14:21 Info: imap-login: Login: user=pquesinb,
method=NTLM, rip=192.168.2.100, lip=192.168.2.102
dovecot: Feb 04 14:15:03 Info: IMAP(pquesinb): Disconnected: Logged out
dovecot: Feb 04 14:15:03 Info: IMAP(pquesinb): Disconnected: Logged out
dovecot: Feb 04 14:15:23 Info: imap-login: Login: user=pquesinb,
method=NTLM, rip=192.168.2.100, lip=192.168.2.102
dovecot: Feb 04 14:15:23 Info: imap-login: Login: user=pquesinb,
method=NTLM, rip=192.168.2.100, lip=192.168.2.102
dovecot: Feb 04 14:16:05 Info: IMAP(pquesinb): Disconnected: Logged out
dovecot: Feb 04 14:16:05 Info: IMAP(pquesinb): Disconnected: Logged out
/etc/dovecot.users contains a list of usernames.
Is this error the result of additional security which has been incorporated
into the later version of Dovecot, or is it because my installation of the
later version from source is broken, somehow incompatible, etc? Dovecot was
configured to use PAM and it appeared to know the password of my account,
failing when it was entered incorrectly so I'm assuming that it was
successfully using PAM. I kept the same syntax in the later config file.
From dovecot.conf:
passdb pam {
# [session=yes] [setcred=yes] [failure_show_msg=yes] [max_requests=n]
# [cache_key=key] [service name]
#
# session=yes makes Dovecot open and immediately close PAM session. Some
# PAM plugins need this to work, such as pam_mkhomedir.
#
# setcred=yes makes Dovecot establish PAM credentials if some PAM
plugins
# need that. They aren't ever deleted though, so this isn't enabled by
# default.
#
# max_requests specifies how many PAM lookups to do in one process
before
# recreating the process. The default is 100, because many PAM plugins
# leak memory.
#
# cache_key can be used to enable authentication caching for PAM
# (auth_cache_size also needs to be set). It isn't enabled by default
Re: [Dovecot] Authentication with many Windows AD
Am 2013-02-13 15:19, schrieb Joseba Torre: You can set as many databases as you want. Beware that databases are processed sequentially and that failed lookups may incur a timeout. -- peter
Re: [Dovecot] dovecot-uidlist crashing and re retriving messages by pop3 clients
I configure director temporary in some tricky way because I have to
serve md5 and ntlm authentication method and I do not want reconfigure
pop/imap servers.
Can you confirm I done all ok becouse I have that issue:
# doveadm director map
doveadm(root): Error: User listing returned failure
doveadm(root): Error: user listing failed
user
mail server ip expire
time
unknown
192.168.111.24
2013-02-14 00:57:34
unknown
192.168.111.21
2013-02-14 00:57:46
yet everything else works ok
My password_query:
password_query = SELECT clear AS password, 'Y' as proxy, '%u' AS
destuser, clear AS pass FROM postfix_users WHERE email = '%u'
My director server config (dovecot -n):
# dovecot -n
# 2.1.13: /etc/dovecot/dovecot.conf
# OS: Linux 3.7.1-hardened-r2 x86_64 Gentoo Base System release 2.1
auth_mechanisms = plain login digest-md5 cram-md5 ntlm apop
auth_verbose = yes
default_client_limit = 1
default_process_limit = 1
default_vsz_limit = 512 M
deliver_log_format = from=%f, msgid=%m, psize=%p: %$
director_mail_servers = 192.168.111.21 192.168.111.22 192.168.111.23
192.168.111.24 192.168.111.25 192.168.111.26
director_servers = 195.78.67.29
director_user_expire = 2 hours
disable_plaintext_auth = no
passdb {
args = /etc/dovecot/dovecot-sql.conf.ext
driver = sql
}
plugin {
mail_log_events = delete undelete expunge copy mailbox_delete
mailbox_rename
mail_log_fields = box msgid from size
}
protocols = imap pop3
service auth {
client_limit = 1
unix_listener auth-userdb {
group = vmail
mode = 0600
user = vmail
}
}
service director {
inet_listener {
port = 9090
}
unix_listener login/director {
mode = 0666
}
}
service imap-login {
executable = imap-login director
}
service pop3-login {
executable = pop3-login director
}
ssl_ca = /etc/ssl/dovecot.ca
ssl_cert = /etc/ssl/dovecot.crt
ssl_key = /etc/ssl/dovecot.key
Re: [Dovecot] dovecot-uidlist crashing and re retriving messages by pop3 clients
I apologize for asking a question too fast without checking , I forgot look at logs. Of course missing iterate_query iterate_query = SELECT email AS user FROM postfix_users
Re: [Dovecot] Imap process crash: assertion failed: (full_fs_access)
On Wed, 13 Feb 2013, dovecot-requ...@dovecot.org wrote:
Timo Sirainen t...@iki.fi writes:
Any guess at what would cause this?
Feb 7 21:20:53 server dovecot: imap(user): Panic: file
mailbox-list-fs-iter.c: line 447 (fs_list_get_roots): assertion
failed: (full_fs_access)
LIST command that had invalid parameters that somehow got through the
first validity check. What namespace config do you have?
namespace {
alias_for =
hidden = yes
list = no
location =
prefix = /
separator = /
}
This one causes these crashes. Fixed in v2.2 now:
http://hg.dovecot.org/dovecot-2.2/rev/fb367a977077
Thanks for diagnosing this. I'll probably remove this namespace or limp
along until 2.2 becomes the latest stable release.
I added this namespace alias in an abundance of caution: this was to
prevent users from trying to peruse the entire file space e.g. /etc.
A poor man's chroot. I didn't test this thoroughly to see if it actually
did what it was supposed to.
Joseph Tam jtam.h...@gmail.com
