- dovecot - dovecot.org

mail location change results in various errors
by Cliff Hayes 07 Nov '14

07 Nov '14

I have a sendmail/dovecot imap/pop3 system that has been running with the following mail_location: mail_location = mbox:/var/empty:INBOX=/var/spool/mail/%u:INDEX=/var/indexes/%u In order to reduce errors and simplify operation I removed imap and am now only responding to pop3. I'd like to also simplify the mail_location to get rid of index errors since I don't need indexes: mail_location = mbox:/var/spool/mail:INBOX=/var/spool/mail/%n But when I applied the new mail_location I began to get the following five errors: Nov 6 23:17:24 sendmail dovecot: pop3(chayes): Warning: UIDVALIDITY changed (1132434125 -> 1205169149) in mbox file /var/spool/mail/chayes Nov 6 23:17:26 sendmail dovecot: pop3(chayes): Panic: Message unexpectedly expunged from index Nov 6 23:17:26 sendmail dovecot: pop3(chayes): Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0() [0x3340045e2a] -> /usr/lib64/dovecot/libdovecot.so.0() [0x3340045e6e] -> /usr/lib64/dovecot/libdovecot.so.0(i_fatal+0) [0x3340019eb3] -> /usr/lib64/dovecot/libdovecot-storage.so.0() [0x3ef62567ed] -> /usr/lib64/dovecot/libdovecot-storage.so.0() [0x3ef6256e75] -> /usr/lib64/dovecot/libdovecot-storage.so.0() [0x3ef62928ed] -> /usr/lib64/dovecot/libdovecot-storage.so.0(index_mail_set_seq+0x76) [0x3ef6294ae6] -> /usr/lib64/dovecot/libdovecot-storage.so.0() [0x3ef625698c] -> dovecot/pop3() [0x405ec7] -> dovecot/pop3(client_command_execute+0x6d7) [0x4071c7] -> dovecot/pop3(client_handle_input+0x78) [0x405618] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_call_io+0x36) [0x3340052c36] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run+0xa7) [0x3340053a57] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_run+0x28) [0x3340052778] -> /usr/lib64/dovecot/libdovecot.so.0(master_service_run+0x13) [0x334003e3c3] -> dovecot/pop3(main+0x283) [0x403cc3] -> /lib64/libc.so.6(__libc_start_main+0xf5) [0x359f821a05] -> dovecot/pop3() [0x403e2d] Nov 6 23:17:26 sendmail dovecot: pop3(chayes): Fatal: master: service(pop3): child 3358 killed with signal 6 (core dumps disabled) Nov 6 23:18:00 sendmail dovecot: pop3(jbkirk): Error: open(/var/spool/mail/.imap/INBOX/dovecot.index.log) failed: Permission denied (euid=2151(jbkirk) egid=12(mail) missing +r perm: /var/spool/mail/.imap/INBOX/dovecot.index.log, dir owned by 3575:12 mode=0770) dovecot -n output # 2.1.16: /etc/dovecot/dovecot.conf # OS: Linux 3.9.2-200.fc18.x86_64 x86_64 Fedora release 18 (Spherical Cow) ext4 auth_mechanisms = plain login auth_verbose = yes auth_verbose_passwords = plain disable_plaintext_auth = no mail_location = mbox:/var/empty:INBOX=/var/spool/mail/%u:INDEX=/var/indexes/%u mbox_write_locks = fcntl 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 } protocols = pop3 ssl = no ssl_cert = </etc/pki/dovecot/certs/dovecot.pem ssl_key = </etc/pki/dovecot/private/dovecot.pem userdb { driver = passwd } What do I need to do to transition to the new mail_location without the errors? Thanks in advance.

1 0

building latest stable for ubuntu 14.04
by Eduardo Casarero 07 Nov '14

07 Nov '14

Hi list, Does anybody have some notes/blog post/etc about building dovecot deb packages?

3 2

mail location change generates various errors
by Cliff Hayes 07 Nov '14

07 Nov '14

I have a sendmail/dovecot imap/pop3 system that has been running with the following mail_location: mail_location = mbox:/var/empty:INBOX=/var/spool/mail/%u:INDEX=/var/indexes/%u In order to reduce errors and simplify operation I removed imap and am now only responding to pop3. I'd like to also simplify the mail_location to get rid of index errors since I don't need indexes: mail_location = mbox:/var/spool/mail:INBOX=/var/spool/mail/%n But when I applied the new mail_location I began to get the following five errors: Nov 6 23:17:24 sendmail dovecot: pop3(chayes): Warning: UIDVALIDITY changed (1132434125 -> 1205169149) in mbox file /var/spool/mail/chayes Nov 6 23:17:26 sendmail dovecot: pop3(chayes): Panic: Message unexpectedly expunged from index Nov 6 23:17:26 sendmail dovecot: pop3(chayes): Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0() [0x3340045e2a] -> /usr/lib64/dovecot/libdovecot.so.0() [0x3340045e6e] -> /usr/lib64/dovecot/libdovecot.so.0(i_fatal+0) [0x3340019eb3] -> /usr/lib64/dovecot/libdovecot-storage.so.0() [0x3ef62567ed] -> /usr/lib64/dovecot/libdovecot-storage.so.0() [0x3ef6256e75] -> /usr/lib64/dovecot/libdovecot-storage.so.0() [0x3ef62928ed] -> /usr/lib64/dovecot/libdovecot-storage.so.0(index_mail_set_seq+0x76) [0x3ef6294ae6] -> /usr/lib64/dovecot/libdovecot-storage.so.0() [0x3ef625698c] -> dovecot/pop3() [0x405ec7] -> dovecot/pop3(client_command_execute+0x6d7) [0x4071c7] -> dovecot/pop3(client_handle_input+0x78) [0x405618] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_call_io+0x36) [0x3340052c36] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run+0xa7) [0x3340053a57] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_run+0x28) [0x3340052778] -> /usr/lib64/dovecot/libdovecot.so.0(master_service_run+0x13) [0x334003e3c3] -> dovecot/pop3(main+0x283) [0x403cc3] -> /lib64/libc.so.6(__libc_start_main+0xf5) [0x359f821a05] -> dovecot/pop3() [0x403e2d] Nov 6 23:17:26 sendmail dovecot: pop3(chayes): Fatal: master: service(pop3): child 3358 killed with signal 6 (core dumps disabled) Nov 6 23:18:00 sendmail dovecot: pop3(jbkirk): Error: open(/var/spool/mail/.imap/INBOX/dovecot.index.log) failed: Permission denied (euid=2151(jbkirk) egid=12(mail) missing +r perm: /var/spool/mail/.imap/INBOX/dovecot.index.log, dir owned by 3575:12 mode=0770) dovecot -n output # 2.1.16: /etc/dovecot/dovecot.conf # OS: Linux 3.9.2-200.fc18.x86_64 x86_64 Fedora release 18 (Spherical Cow) ext4 auth_mechanisms = plain login auth_verbose = yes auth_verbose_passwords = plain disable_plaintext_auth = no mail_location = mbox:/var/empty:INBOX=/var/spool/mail/%u:INDEX=/var/indexes/%u mbox_write_locks = fcntl 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 } protocols = pop3 ssl = no ssl_cert = </etc/pki/dovecot/certs/dovecot.pem ssl_key = </etc/pki/dovecot/private/dovecot.pem userdb { driver = passwd } What do I need to do to transition to the new mail_location without the errors? Thanks in advance.

2 1

Dovecot replication causing deleted emails to reappear
by Asai 06 Nov '14

06 Nov '14

Greetings, I've set up replication successfully on two Dovecot servers. I had fully synced the servers but then took one offline for 2 weeks. When I restored it, the servers synced but ended up replacing deleted emails in random people's inboxes. I'm using maildir. Does anyone have any insights as to correcting this issue? Asai -- --Asai

1 0

Dovecot-lda permission errors or maybe authentication errors?
by Robert Kryger 06 Nov '14

06 Nov '14

I am a new dovecot user who recently transitioned my old mailserver to a new CentOS/Postfix/Dovecot system. I am running a simple configuration with about a dozen system users and Maildir folders. The e-mail setup seems to be running fine when I use the default local-delivery-agent in Postfix. However, I am trying to use the dovecot-lda instead so I can take advantage of the sieve functionality. I have tried to specify the dovecot-lda in two ways. First, in the /etc/postfix/main.cf file: mailbox_command = /usr/libexec/dovecot/dovecot-lda -f "$SENDER" -a "$RECIPIENT" or alternatively, I leave the mailbox_command blank and specify the following in the .forward file of a test user: | "/usr/libexec/dovecot/dovecot-lda" Either approach gives me the same error(s). When a mail message is sent to the test user USER1, the following errors appear in the dovecot-lda error file: Nov 04 08:47:29 lda(user1): Error: chdir(/home/user1/) failed: Permission denied (euid=524(user1) egid=524(user1) stat() failed: No such file or directory, euid is not dir owner) Nov 04 08:47:29 lda(user1): Error: chdir(/home/user1) failed: Permission denied Nov 04 08:47:29 lda(user1): Error: user user1: Initialization failed: Namespace 'INBOX.': stat(/home/user1/Maildir) failed: Permission denied (euid=524(user1) egid=524(user1) stat() failed: No such file or directory, euid is not dir owner) Nov 04 08:47:29 lda(user1): Fatal: Invalid user settings. Refer to server log for more information. Nov 04 08:47:29 lda(user1): Error: chdir(/home/user1/) failed: Permission denied (euid=524(user1) egid=524(user1) stat() failed: No such file or directory, euid is not dir owner) Nov 04 08:47:29 lda(user1): Error: chdir(/home/user1) failed: Permission denied Nov 04 08:47:29 lda(user1): Error: user user1: Initialization failed: Namespace 'INBOX.': stat(/home/user1/Maildir) failed: Permission denied (euid=524(user1) egid=524(user1) stat() failed: No such file or directory, euid is not dir owner) Nov 04 08:47:29 lda(user1): Fatal: Invalid user settings. Refer to server log for more information. At first, I interpreted this to mean the file permissions were not set correctly on the home directory or the Maildir folder. However, I have opened these up to full rwx access for everyone and I still get the same errors. Alternatively, perhaps this is related somehow to the dovecot-lda authentication process via the password or user databases, but I can't make any sense of the documentation. Can anyone suggest what might be wrong or how to better diagnose? For reference, I am running dovecot version 2.0.9. The dovecot-lda process also outputs the following messages (not errors) when a test message is sent to the USER1 account: Nov 04 08:47:29 lda: Debug: Loading modules from directory: /usr/lib64/dovecot Nov 04 08:47:29 lda: Debug: Module loaded: /usr/lib64/dovecot/lib90_sieve_plugin.so Nov 04 08:47:29 lda(user1): Debug: Effective uid=524, gid=524, home=/home/user1 Nov 04 08:47:29 lda(user1): Debug: Namespace : type=private, prefix=INBOX., sep=., inbox=yes, hidden=no, list=yes, subscriptions=yes location=maildir:~/Maildir Nov 04 08:47:29 lda(user1): Debug: maildir++: root=/home/user1/Maildir, index=, control=, inbox=/home/user1/Maildir Nov 04 08:47:29 lda: Debug: Loading modules from directory: /usr/lib64/dovecot Nov 04 08:47:29 lda: Debug: Module loaded: /usr/lib64/dovecot/lib90_sieve_plugin.so Nov 04 08:47:29 lda(user1): Debug: Effective uid=524, gid=524, home=/home/user1 Nov 04 08:47:29 lda(user1): Debug: Namespace : type=private, prefix=INBOX., sep=., inbox=yes, hidden=no, list=yes, subscriptions=yes location=maildir:~/Maildir Nov 04 08:47:29 lda(user1): Debug: maildir++: root=/home/user1/Maildir, index=, control=, inbox=/home/user1/Maildir The output of dovecot -n is: # 2.0.9: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-431.29.2.el6.x86_64 x86_64 CentOS release 6.5 (Final) auth_debug = yes auth_debug_passwords = yes auth_mechanisms = plain login disable_plaintext_auth = no login_trusted_networks = 71.xx.xx.xx 71.xx.xx.xy 71.xx.xx.xz 71.xx.xx.yx mail_debug = yes mail_location = maildir:~/Maildir 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 mbox_write_locks = fcntl namespace { inbox = yes location = prefix = INBOX. separator = . } passdb { driver = pam } plugin { sieve = ~/.dovecot.sieve sieve_dir = ~/sieve sieve_global_dir = home/sieve sieve_max_script_size = 1M } protocols = imap lmtp sieve service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } } service managesieve-login { inet_listener sieve { port = 4190 } } ssl_cert = </etc/pki/dovecot/certs/dovecot.pem ssl_key = </etc/pki/dovecot/private/dovecot.pem userdb { driver = passwd } protocol lda { info_log_path = /var/log/dovecot-lda.log log_path = /var/log/dovecot-lda-errors.log mail_plugins = sieve postmaster_address = postmaster(a)xxxxxxx.com }

3 7

Re: Dovecot-lda permission errors or maybe authentication errors?
by Alexander Dalloz 06 Nov '14

06 Nov '14

Am 06.11.2014 um 09:01 schrieb Steffen Kaiser: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Wed, 5 Nov 2014, Alexander Dalloz wrote: > > Dear Alexander, > >> Run "sestatus" and you'll see. >> >> Run "grep -i AVC /var/log/audit/audit.log" to identify SELinux caused >> denials. > > because I saw this type of question quite too often, I added this info > to the Wiki2 (to be revised by Timo): > http://master.wiki2.dovecot.org/WhyDoesItNotWork > > I copy'n'pasted your sentences, if you don't mind. > > Kind regards, > > - -- Steffen Kaiser Hello Steffen, sure I am fine with that. Even better it would be to have a recipe for a custom SELinux policy to not be mislead switching off SELinux at all. Such a custom policy is necessary when storing mail in the user's homedir because files created there get a wrong SELinux context for that usecase by default. An general overview about this topic can be found on http://wiki.centos.org/HowTos/SELinux Kind regards Alexander

1 0

Can I take mail from Maildir mailbox and deliver it as new?
by James Pryor 06 Nov '14

06 Nov '14

Hello list, I have a need for someone to point me in the right direction. Our old email system (system A) had an account that acted as a mailing list accumulator/archiver. This account was a member of every list and mail would be sent to it's address. The strange part is that email was not delivered to system A because there was a . (dot) forward alias to another machine (system B) that runs sendmail. System B's sendmail then slurped up the incoming mail and processed it in some fashion which I do not care about. On our new mail server (system C (OS is RHEL6.5, dovecot-2.0.9-7.el6_5.1.x86_64, postfix-2.6.6-6.el6_5.x86_64)), I performed a bulk Linux account and mailbox migration from system A to system C using postfix/dovecot/imapsync. But I forgot to put the alias in place on system C to send all incoming that special account's mail on system B. So mail started to get delivered to local user ar_list on system C. So now I have a Maildir format mailbox on system C that has mail in it and I want to be able to manipulate and/or re-send those emails as new mail to system B. Once it is received by sendmail on system B, then I don't care about it any more. Is there a way to take mail sitting on disk in a mailbox and deliver it as if it was new mail to some other machine? Thanks, James -bash-4.1$ ls -l total 566 drwx------ 2 ar_list users 2048 Aug 7 21:29 cur -rw------- 1 ar_list users 12556 Oct 8 17:09 dovecot.index -rw------- 1 ar_list users 378880 Oct 9 14:41 dovecot.index.cache -rw------- 1 ar_list users 2580 Oct 9 14:41 dovecot.index.log -rw------- 1 ar_list users 65549 Oct 9 14:41 dovecot-uidlist -rw------- 1 ar_list users 8 Aug 7 19:38 dovecot-uidvalidity -r--r--r-- 1 ar_list users 0 Aug 7 19:38 dovecot-uidvalidity.53e40ddc drwx------ 2 ar_list users 100352 Oct 9 14:41 new drwx------ 2 ar_list users 2048 Oct 9 14:41 tmp -bash-4.1$ ls new/ | wc -l 1020 -bash-4.1$ ls cur | wc -l 25

3 3

Re: Dovecot-lda permission errors or maybe authentication errors?
by Robert Kryger 06 Nov '14

06 Nov '14

Alexander, You are absolutely right - I apologize for my confusion regarding SElinux. In fact, when I turn off SElinux in /etc/selinux/config (setting SELINUX=disabled, instead of =enforcing) then dovecot-lda starts working. Thanks for the advice - I have been fighting with this for several weeks without making headway! Robert

1 0

gssapi considered as PLAIN?
by Harry Schmalzbauer 05 Nov '14

05 Nov '14

Hello, as soon as I set "disable_plaintext_auth = yes", AUTH=GSSAPI vanishes from capabilities. ([CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE STARTTLS AUTH=GSSAPI AUTH=PLAIN AUTH=LOGIN] vs [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE STARTTLS LOGINDISABLED]) Why? I'm wondering especially because at http://wiki2.dovecot.org/Authentication/Mechanisms, GSSAPI is correctly listed under “Non-plaintext authentication“. Thanks, -Harry

3 7

ntlm_auth seems ok, initial auth failure with dovecot2 (and winbind 4.1.13)
by Harry Schmalzbauer 05 Nov '14

05 Nov '14

Hello, I've read quite often that there are problems with ntlm_auth helper (last one here http://www.dovecot.org/list/dovecot/2014-June/096561.html) But haven't found any confirmation, neither it's working for anybody else nor that it's known taht this issue needs debuging. Like for ohers, my authentication tests from the commandline with ntlm_auth exactly give expected results. But initial authentication (with Outlook) fail at first, but after entering the user's password, nevertheless succeeds with mech=NTLM. See the attached ntlm-log.txt Can't exactly tell when this regression occured, one year ago nobody had to enter his password, it worked like intended with Outlook (which still is version 2010). Any idea how to debug? It could be also a regression in samba, both highly appreciated applications were upgraded at the same time… Thanks, -Harry

1 0