- dovecot - dovecot.org

[Dovecot] Imap Error
by Jason Liedtke 20 Jan '11

20 Jan '11

This morning I have a Outlook 2007 user who getting the error and I am unsure how to fix it. Cannot open this item. The server responded: "Error in IMAP command UID FETCH: Invalid uidset' DoveCot v 1.2.9 # 1.2.9: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-27-generic-pae i686 Ubuntu 10.04.1 LTS log_timestamp: %Y-%m-%d %H:%M:%S protocols: imap imaps pop3 pop3s managesieve listen(default): * listen(imap): * listen(pop3): * listen(managesieve): *:2000 disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable(default): /usr/lib/dovecot/imap-login login_executable(imap): /usr/lib/dovecot/imap-login login_executable(pop3): /usr/lib/dovecot/pop3-login login_executable(managesieve): /usr/lib/dovecot/managesieve-login mail_privileged_group: mail mail_location: maildir:~/ mmap_disable: yes mail_nfs_storage: yes mail_nfs_index: yes mbox_write_locks: fcntl dotlock mail_executable(default): /usr/lib/dovecot/imap mail_executable(imap): /usr/lib/dovecot/imap mail_executable(pop3): /usr/lib/dovecot/pop3 mail_executable(managesieve): /usr/lib/dovecot/managesieve mail_plugins(default): quota imap_quota mail_plugins(imap): quota imap_quota mail_plugins(pop3): quota mail_plugins(managesieve): mail_plugin_dir(default): /usr/lib/dovecot/modules/imap mail_plugin_dir(imap): /usr/lib/dovecot/modules/imap mail_plugin_dir(pop3): /usr/lib/dovecot/modules/pop3 mail_plugin_dir(managesieve): /usr/lib/dovecot/modules/managesieve imap_client_workarounds(default): tb-extra-mailbox-sep imap_client_workarounds(imap): tb-extra-mailbox-sep imap_client_workarounds(pop3): imap_client_workarounds(managesieve): pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh pop3_client_workarounds(managesieve): managesieve_logout_format(default): bytes=%i/%o managesieve_logout_format(imap): bytes=%i/%o managesieve_logout_format(pop3): bytes=%i/%o managesieve_logout_format(managesieve): bytes ( in=%i : out=%o ) namespace: type: private separator: / inbox: yes list: yes subscriptions: yes lda: postmaster_address: hostname: auth_socket_path: /var/run/dovecot/auth-master mail_plugins: quota sieve log_path: info_log_path: syslog_facility: mail auth default: username_format: %Lu passdb: driver: ldap args: /etc/dovecot/dovecot-ldap.conf passdb: driver: sql args: /etc/dovecot/dovecot-sql.conf passdb: driver: ldap args: /etc/dovecot/dovecot-ldap.conf passdb: driver: ldap args: /etc/dovecot/dovecot-ldap.conf userdb: driver: ldap args: /etc/dovecot/dovecot-ldap.conf userdb: driver: sql args: /etc/dovecot/dovecot-sql.conf userdb: driver: ldap args: /etc/dovecot/dovecot-ldap.conf userdb: driver: ldap args: /etc/dovecot/dovecot-ldap.conf socket: type: listen master: path: /var/run/dovecot/auth-master mode: 432 user: vmail group: vmail plugin: quota: maildir quota_rule: *:bytes=20M sieve: ~/sieve/.dovecot.sieve sieve_dir: ~/sieve sieve_global_path: /var/mail/default.sieve sieve_before: /var/mail/sieve/global sieve_extensions: +imapflags

2 1

[Dovecot] ldap auth error
by pch0317 20 Jan '11

20 Jan '11

Hi, I have dovecot 2.0.beta6 and I'm newbie with dovecot. I try authenticate user via LDAP (MS ActiveDirectory). I have errors in log: mail dovecot: auth: Error: LDAP: binding failed (dn cn=administrator,ou=users,dc=my,dc=domain): Invalid credentials, 80090308: LdapErr: DSID-0C090334, comment: AcceptSecurityContext error, data 525, vece This is my dovecot.conf file: protocols = imap disable_plaintext_auth = no listen = * ssl = no auth_mechanisms = plain base_dir = /var/run/dovecot/ mail_location = mbox:/home/vmail/%n/ passdb { driver = ldap args =/etc/dovecot/dovecot-ldap.conf } userdb { driver = ldap args = /etc/dovecot/dovecot-ldap.conf } And this is my dovecot-ldap.conf: hosts = 192.168.0.19 dn = cn=administrator,ou=users,dc=my,dc=domain dnpass = password base = ou=myuser,dc=my,dc=domain scope = subtree ldap_version = 3 auth_bind = yes auth_bind_userdn = ou=myuser,dc=my,dc=domain user_attrs = homeDirectory=home,uidNumber=uid,gidNumber=gid user_filter = (&(objectClass=posixAccount)(uid=%u)) pass_attrs = uid=user,userPassword=password pass_filter = (&(objectClass=posixAccount)(uid=%u)) Should I have any file in /etc/pam.d ? Thanks

3 4

[Dovecot] domain stripping
by PA 20 Jan '11

20 Jan '11

Hi, using dovecot 2.0 and I'm using a couple of user DBs, sql/prefetch and pam. Currently if the user logins with username@domain it authenticates off the sql DB and works fine. If the user logins with username with no @domain it fails on the sql lookup and succeeds on the pam user DB. However I was wondering if I can have another sql DB lookup that says when the user logins and fails against the first two user DBs, sql/pam db, to try this last sql user DB and appends a default domain to it, because the sql DB lists username with the domain. Currently I have all users login in with no realm on the older mail server and I wanted to migrate these users to dovecot 2.x with minimal impact and wanted to have the ability for these virtual users to login with and without a realm. Thanks paul.

2 2

[Dovecot] Problems with Upgrade from Courier
by Aaron Pettitt 20 Jan '11

20 Jan '11

I inherited a server from a previous employee. The server crashed so it was time to move everything over to another server. We have a web mail site and I installed everything running dovecot, postfix and roundcube. After I installed it, everything worked great when I created a new user. The new user could send and receive emails with no issues. I then copied the home directory over from the other server and ran the courier-dovecot migration script. It created the subscription files and the dovecot-uidlist files in each user (about 1000 total users). When I login as one of the existing users, it says that there is no mail in the mailbox. However, if I look at the user's cur and new folders, there is mail in those folders. If I send a new mail to the user, it does not show up in their inbox. If I look in their new folder, the new mail that I sent was delivered to that folder but it does not show up in their inbox. I've tried going to dovecot directly through telnet with the same results. I've been stuck for 2 days now so any help is greatly appreciated. Below is my dovecot.conf with all the comments removed. Thanks all! protocols = imap imaps disable_plaintext_auth = no log_path = '/var/log/dovecot/error.log' info_log_path = '/var/log/dovecot/info.log' log_timestamp = "%m/%d/%Y %H:%M:%S " #mail_location = maildir:~/ mail_location = maildir:/home/vmail/%d/%n/ mail_privileged_group = mail mail_debug = yes protocol imap { } protocol pop3 { } protocol managesieve { sieve_storage=~/sieve } protocol lda { log_path = /home/vmail/dovecot-deliver.log auth_socket_path = /var/run/dovecot/auth-master postmaster_address = postmaster(a)mybridemal.com mail_plugins = cmusieve global_script_path = /home/vmail/globalsieverc } auth_verbose = yes auth_debug = no auth_debug_passwords = no auth default { passdb sql { args = /etc/dovecot/dovecot-sql.conf } args = uid=5000 gid=5000 home=/home/vmail/%d/%n allow_all_users=yes } user = root path = /var/run/dovecot/auth-master mode = 0600 user = vmail #group = } client { path = /var/spool/postfix/private/auth mode = 0660 user = postfix group = postfix } } } }

1 0

[Dovecot] Bug found, assertion failed
by Tobias Daucher 20 Jan '11

20 Jan '11

Hi there, We're running dovecot 2.06, with mdbox. Following message was in our syslog: Jan 20 09:26:48 servername dovecot: [ID 583609 mail.crit] imap(user): Panic: file istream-limit.c: line 79: assertion failed: (v_offset <= lstream->v_size) The problem could be solved on client side, by just deleting the ImapMail-Folder in Thunderbird. Why? Thunderbird tried to move a message, that obviously wasn't there. Dovecot got killed and the message above was in the syslog. Connection was closed and Thunderbird told me the server is dead. Thunderbird tried this every few seconds, and there was no way to say thunderbird "stop try moving". So the only way was to delete thunderbirds mail cache. I think it would be very nice, if dovecot doesn't die, just because the client tries to move a message, which isn't there. Thanks, Tobias Daucher -- Dr. Nagler & Company GmbH Hauptstraße 9 92253 Schnaittenbach Tel : 09622-7197-38 Fax : 09622-7197-50 Web : http://www.nagler-company.com E-Mail : tobias.daucher(a)nagler-company.com Hauptsitz: Schnaittenbach Handelregister: Amberg HRB 4653 Gerichtsstand: Amberg Steuernummer: 201/118/51825 USt.-ID-Nummer: DE 273143997 Geschäftsführer: Dr. Martin Nagler, Dr. Dr. Karl-Kuno Kunze

1 0

Re: [Dovecot] dovecot Digest, Vol 93, Issue 41
by Alan Brown 20 Jan '11

20 Jan '11

> From: Stan Hoeppner <stan(a)hardwarefreak.com> > Subject: Re: [Dovecot] SSD drives are really fast running Dovecot > > > Yes. Go with a cluster filesystem such as OCFS or GFS2 and an inexpensive SAN > storage unit that supports mixed SSD and spinning storage such as the Nexsan > SATABoy with 2GB cache: http://www.nexsan.com/sataboy.php I can't speak for OCFS2, but after several years' experience with the filesystem I strongly recommend NOT using GFS/GFS2. Its locking model is incredibly slow (500 locks/second on a filesystem mounted with quotas enabled and noatime) and results in dire performance - plus there's a known crash vulnerability if files are repeatedly renamed in large directories (this bites us regularly...) GFS2 isn't an "enterprise" filesystem by any stretch of the imagination, despite what a number of enthusiastic salespeople might try to convince you of. We're lucky to keep the GFS servers up for more than a week at a time.

3 2

[Dovecot] Upgrading from 1.2 to 2.0
by list＠airstreamcomm.net 20 Jan '11

20 Jan '11

Greetings Dovecot mailing list! We are an ISP that recently migrated from Courier to Dovecot, and are looking at the next round of upgrades. Hoping that we could get pointed to some documentation or get a general list of best practices for an upgrade from 1.2.13 to 2.0.9. Our current environment consists of four Dovecot machines that share an NFS backend hosting POP and IMAP. Our biggest question is whether we can support a rolling upgrade from 1.2.13 to 2.0.9, or if it would need to be an all for one cut. Thanks in advance.

3 2

Re: [Dovecot] Duplicate mail for forwards (dovecot+postfix+postfixadmin)
by Darek M 19 Jan '11

19 Jan '11

Cool, thank you Patrick! Must have missed that somehow. I put the setting in main.cf, "receive_override_options = no_address_mappings", right after 'content_filter' (running amavisd on a separate port) and it seems to have fixed the problem. -- Darek On Tue, Jan 18, 2011 at 7:05 PM, Patrick Westenberg <pw(a)wk-serv.de> wrote: > Darek M schrieb: > >> Anyone have an idea of what I should be looking at in a situation like >> this? Does the 'goto' field look fine? > > You have to set > -o receive_override_options=no_address_mappings > in your master.cf > > Patrick >

1 0

[Dovecot] Pigeonhole 2.2 build issue on arm
by Tom Talpey 19 Jan '11

19 Jan '11

When building Pigeonhole 2.2 for ARM, the following warnings are produced: uri-mailto.c: In function '_parse_hex_value': uri-mailto.c:139: warning: comparison is always false due to limited range of data type uri-mailto.c:145: warning: comparison is always false due to limited range of data type The problem is a test assuming that char is a signed type : static inline int _decode_hex_digit(char digit) { ... static bool _parse_hex_value(const char **in, char *out) { char value; // <<--- change to "int". if ( **in == '\0' || (value=_decode_hex_digit(**in)) < 0 ) return FALSE; *out = value << 4; (*in)++; if ( **in == '\0' || (value=_decode_hex_digit(**in)) < 0 ) return FALSE; This is untested, but I changed the "char value" to "int value" to correct the signed comparisons. There are no warnings when building for x86 in either case, btw. Also, the two tests for "**in == '\0'" seem to be unnecessary? [/share/Public/XDove/dovecot-2.0-pigeonhole-0.2.2/src] # gcc -v Using built-in specs. Target: arm-none-linux-gnueabi Configured with: ../gcc-4.2/configure --build=i386-pc-linux-gnu --host=arm-none-linux-gnueabi --target=arm-none-linux-gnueabi --prefix=/opt --disable-nls --disable-static --with-as=/home/slug/optware/cs08q1armel/toolchain/arm-2008q1/bin/arm-none-linux-gnueabi-as --with-ld=/home/slug/optware/cs08q1armel/toolchain/arm-2008q1/bin/arm-none-linux-gnueabi-ld --enable-languages=c,c++ --disable-multilib --enable-threads --disable-libmudflap --disable-libssp --disable-libgomp --disable-libstdcxx-pch --enable-shared --enable-symvers=gnu --enable-__cxa_atexit Thread model: posix gcc version 4.2.3 [/share/Public/XDove/dovecot-2.0-pigeonhole-0.2.2/src] # make ... libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../../../../.. -I./.. -I./../../.. -I/share/Public/XDove/dovecot-2.0.9 -I/share/Public/XDove/dovecot-2.0.9/src/lib -I/share/Public/XDove/dovecot-2.0.9/src/lib-dict -I/share/Public/XDove/dovecot-2.0.9/src/lib-mail -I/share/Public/XDove/dovecot-2.0.9/src/lib-imap -I/share/Public/XDove/dovecot-2.0.9/src/lib-charset -I/share/Public/XDove/dovecot-2.0.9/src/lib-index -I/share/Public/XDove/dovecot-2.0.9/src/lib-storage -I/share/Public/XDove/dovecot-2.0.9/src/lib-storage/index -I/share/Public/XDove/dovecot-2.0.9/src/lib-storage/index/raw -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -Wstrict-aliasing=2 -MT ntfy-mailto.lo -MD -MP -MF .deps/ntfy-mailto.Tpo -c ntfy-mailto.c -fPIC -DPIC -o .libs/ntfy-mailto.o uri-mailto.c: In function '_parse_hex_value': uri-mailto.c:139: warning: comparison is always false due to limited range of data type uri-mailto.c:145: warning: comparison is always false due to limited range of data type

2 1

[Dovecot] Problem with seeing mail after Upgrade from Courier
by apettitt 19 Jan '11

19 Jan '11

I created a new server for a webmail system because the old server crashed. When I created the server, I installed Dovecot and the old server had Courier. On the new server, I'm doing virtual users where the old one created system users. I moved all the folders over for all the users on to the new server and ran the Courier-Dovecot migration script. The files were created successfully with no issues. The issue I'm having now is that Dovecot is not seeing any mail in the user's directory. If I create a new user, it can send and receive mail with no problems. If I send an email to an existing user, it gets delivered to the new folder but dovecot does not see anything in the new folder. There is also mail in the curr folder that dovecot does not see. I'm using Roundcube as a webmail client but I've also tried using Telnet with the same results. Any ideas? -- View this message in context: http://old.nabble.com/Problem-with-seeing-mail-after-Upgrade-from-Courier-t… Sent from the Dovecot mailing list archive at Nabble.com.

2 1