- dovecot - dovecot.org

Re: [Dovecot] dovecot Digest, Vol 116, Issue 11
by Erik A Johnson 06 Dec '12

06 Dec '12

On December 5, 2012 2:07:14 AM PST, Ben Morrow <ben(a)morrow.me.uk> wrote: > At 1AM -0800 on 5/12/12 Erik A Johnson wrote: >> FYI, the tcpdump I sent previously was with one of our >> previously-discussed patches in place: >> >> if (!proxy->client_proxy && net_geterror(proxy->fd_ssl) == EBADF) { >> >> I'm attaching that dump again (as >> tcpdump_output_witholdpatch_headeronly.txt), as well as a dump without >> any of the patches (tcpdump_output_withoutpatches_headeronly.txt) in >> case there is any difference. > > Well, they're certainly different. Are you sure the second trace > (withoutpatches) was of a session which went into an infinite loop? > The only thing peculiar about that trace is that the server closes the > connection after receiving the first packet from the client, but it does > so perfectly properly: it ACKs the client's data packet, and does the > FIN-FIN/ACK exchance properly. You will notice there are no [R] packets, > which indicate something odd is happening at the server end. I'm pretty sure, but I've run it again, confirmed that the imap-login process is using 100% of a CPU until I kill it, and have attached the tcpdump. Looks like one packet from SERVER to CLIENT shifted slightly in chronology, but otherwise the same. >>> #ifdef SO_ISDEFUNCT >>> + if (getsockopt(proxy->fd_ssl, SOL_SOCKET, SO_ISDEFUNCT, >>> + (void *)&err, sizeof(err)) == 0 && err) { >>> + errstr = t_strdup_printf( >>> + "%s: socket is defunct", func_name); >>> + break; >>> + } >>> +#endif >> >> Nope, SO_ISDEFUNCT isn't defined. > > Oh, sorry, that needs > > #include <sys/socket.h> > > at the top. If that doesn't work, then which version of the OS are you > building for? AFAICT the DEFUNCT socket flag has been present since at > least 10.5, but the SO_ISDEFUNCT option was only introduced in 10.7. > This is irritating, actually: it means that to properly fix this on all > versions of Mac OS Dovecot would need to include the previous ENOTCONN > code #ifndef SO_ISDEFUNCT. I've got both 10.7 and 10.8 SDKs in Xcode and neither have SO_ISDEFUNCT defined in sys/socket.h (or anywhere else in the usr/include directories) -- there's a SS_DEFUNCT mask defined in sys/socketvar.h -- is that what you're looking for?

2 2

[Dovecot] Update configuration for separate mail directory
by eehmke 06 Dec '12

06 Dec '12

I have a small mail server with virtual users. In my /etc/dovecot/conf.d/10- mail.conf I have this setting: mail_location = maildir:/var/mail/vhosts/%d/%u which is also the home location of each user. Now I learned that this is not the prefered configuration, and in fact some of my sieve subdirectories are mistaken as mail directories. While I understand that I have to create separate mail subdirectories in each user folder, I am not sure where I have to adapt the dovecot configuration files. I could not find a guide, only some scattered hints and of course http://wiki2.dovecot.org/VirtualUsers/Home I guess I have to shut down the server for the reconfiguration, or is there a way to do it on a life system? Eggert -- View this message in context: http://dovecot.2317879.n4.nabble.com/Update-configuration-for-separate-mail… Sent from the Dovecot mailing list archive at Nabble.com.

1 0

[Dovecot] When are search indexes updated?
by David Abrahams 06 Dec '12

06 Dec '12

I noticed that occasionally searching in my huge archive mailbox can be really slow, so I tried doveadm index on it and it seemed to do a lot of work, which seemed strange given, for example, that dovecot-lda says it keeps Dovecot index files up-to-date. Then I thought, "maybe these are different files than the search indices." If so, that's not entirely clear from the docs and Wiki. So, questions: * When are search indexes updated? * Are they updated incrementally? * If not, why not? * If so, why would a mailbox's index drift out-of-date, as mine had? BTW, I'm using the clucene search backend. -- Dave Abrahams BoostPro Computing Software Development Training http://www.boostpro.com Clang/LLVM/EDG Compilers C++ Boost

6 16

[Dovecot] "no longer mounted" warnings
by Dave Abrahams 06 Dec '12

06 Dec '12

Dovecot seems to be warning about every volume it's ever seen in the past. Is this normal? Can I make it stop? --8<---------------cut here---------------start------------->8--- 12/4/12 12:33:38.148 PM dovecot[2658]: master: Warning: /Volumes/fs is no longer mounted. See http://wiki2.dovecot.org/Mountpoints 12/4/12 12:33:38.148 PM dovecot[2658]: master: Warning: /Volumes/dave is no longer mounted. See http://wiki2.dovecot.org/Mountpoints 12/4/12 12:33:38.149 PM dovecot[2658]: master: Warning: /Volumes/Groups is no longer mounted. See http://wiki2.dovecot.org/Mountpoints 12/4/12 12:33:38.149 PM dovecot[2658]: master: Warning: /Volumes/Public is no longer mounted. See http://wiki2.dovecot.org/Mountpoints 12/4/12 12:33:38.149 PM dovecot[2658]: master: Warning: /Volumes/Users is no longer mounted. See http://wiki2.dovecot.org/Mountpoints 12/4/12 12:33:38.149 PM dovecot[2658]: master: Warning: /Volumes/GPGTools is no longer mounted. See http://wiki2.dovecot.org/Mountpoints 12/4/12 12:33:38.149 PM dovecot[2658]: master: Warning: /private/tmp/ccc_dmg_mount.weHZmz is no longer mounted. See http://wiki2.dovecot.org/Mountpoints --8<---------------cut here---------------end--------------->8--- -- Dave Abrahams BoostPro Computing Software Development Training http://www.boostpro.com Clang/LLVM/EDG Compilers C++ Boost

4 4

Re: [Dovecot] imap-login hanging when firewall blocks ssl handshaking
by Erik A Johnson 06 Dec '12

06 Dec '12

On December 4, 2012 at 4:43:53 AM PST, Ben Morrow <ben(a)morrow.me.uk> wrote: > So, it looks to me as though you have a firewall problem. You may be > able to get more information by setting the kern.ipc.sodefunctlog sysctl > to 1: this should make the kernel log to syslog (or wherever the OSX > kernel logs go) when sockets are made DEFUNCT and when reads fail for > that reason. sudo sysctl -w kern.ipc.sodefunctlog=1 gives the following in the log: 12/5/12 9:10:00.000 PM kernel[0]: sosetdefunct[60169]: (target pid 60169 level 0) so 0xffffff803159c738 [2,1] marked as defunct 12/5/12 9:10:00.000 PM kernel[0]: sodefunct[60169]: (target pid 60169 level 0) so 0xffffff803159c738 [2,1] is now defunct [rcv_si 0x0, snd_si 0x0, rcv_fl 0x9400, snd_fl 0x1400] 12/5/12 9:10:00.000 PM kernel[0]: soreceive[60169]: defunct so 0xffffff803159c738 [2,1] (57) The last line is repeated about once every 4 microseconds until I kill it.

1 0

[Dovecot] log_path - expansion possible?
by Robert Blayzor 06 Dec '12

06 Dec '12

Does (or can) the ability to use expansion variables in Dovecot's log_path exist? ie: log_path = /var/log/dovecot/dovecot-%Y%m%d -- Robert Blayzor INOC, LLC rblayzor(a)inoc.net http://www.inoc.net/~rblayzor/

3 5

[Dovecot] dotlock error
by Muhammad Yousuf Khan 05 Dec '12

05 Dec '12

i finally manage to control access on public folder by File system permission. i have 3 test users. 1. tom 2. fmaster 3 . testmail tom and fmaster are a group called "news-own" and testmail user is a readonly one. here is my folder structure ill share dovecot -n output at the end of this email. drwxrwxr-t 2 tom news-own 4.0K Dec 4 19:08 tmp drwxrwxr-t 2 tom news-own 4.0K Dec 4 19:08 new -rwxrwxrwx 1 tom news-own 68 Dec 4 19:08 dovecot-uidlist -rw-rw-r-T 1 fmaster news-own 16K Dec 4 19:10 dovecot.index.cache drwxrwxr-t 2 tom news-own 4.0K Dec 4 19:15 cur -rw-rw-r-T 1 tom news-own 1.1K Dec 4 19:16 dovecot.index.log everything works fine as far as user fmaster and tom is concern as they are member of "news-own" and this group own the mailbox now the problem i face with readonly users. i am getting this error in /var/log/mail.info (against user testmail) file_dotlock_create(/public/.News/dovecot-uidlist) failed: Permission denied (euid=1002(testmail) egid=1002(testmail) missing +w perm: /public/.News at first point i saw this error and i could not subscribe to the folder. and the said log has been generated. now on second stage i change the dovecot-uidlist file permission to "1666" so that testmail user can also write to the file. now problem starts from here, i see two folder one is News and second one is News-1 and i don't know from where the second folder showed up. and when i click on any of the folder my /var/log/mail.info start to show below massage continuously. until i restart the dovecot service. file_dotlock_create(/public/.News/dovecot-uidlist) failed: Permission denied (euid=1002(testmail) egid=1002(testmail) missing +w perm: /public/.News i search google and i saw that people suggested to set stickey bit on which i already did or suggested to stop "dot locking" so i am here to ask is there any way to solve my said problem with out disabling dot locking? or if i stop dot locking what are the consequences? here i my dovcecot -n root@mailsrv:/public/.News# dovecot -n # 1.2.15: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-5-amd64 x86_64 Debian 6.0.6 log_timestamp: %Y-%m-%d %H:%M:%S ssl_cert_file: /etc/ssl/certs/postfix.pem ssl_key_file: /etc/ssl/private/postfix.key login_dir: /var/run/dovecot/login login_executable: /usr/lib/dovecot/imap-login mail_privileged_group: mail mail_location: maildir:~/Maildir:INBOX=~/Maildir/:INDEX=~/Maildir/index mail_debug: yes mbox_write_locks: fcntl dotlock namespace: type: private separator: / inbox: yes list: yes subscriptions: yes namespace: type: public separator: / prefix: Shared folders/ location: maildir:/public list: yes auth default: mechanisms: plain login passdb: driver: pam userdb: driver: passwd socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix Thanks in advance, any help or suggestion would be highly appreciated.

2 5

[Dovecot] dovecot backend on director ?
by Thomas Hummel 05 Dec '12

05 Dec '12

Hello Timo, The last time I checked my understanding about director was that : 1. backend/"real" imap servers should not be on the same host (or the same dovecot instance) to avoid proxying loops. Is it still the case with the latest 2.1 stable release ? Is there a plan to be able to run director and real server on the same host, thus requiring only 2 hosts instead of 4 to have load balancing and a redundant director ? 2. director itself was not able or meant to check if one of the real server was down (some script was pointed long time ago in this list). Same questions. 3. you'll have to use dovecot lmtp instead of let's say procmail. Would deliver be still a choice or is lmtp the only deliver compatible choice ? In what case would lmtp be more useful than deliver ? To have some sort of "remote LDA" ? By the way, what gets indexed on deposit on the mailbox since, by definition, the user has not done any request yet ? Thanks. -- Thomas Hummel | Institut Pasteur <hummel(a)pasteur.fr> | Groupe Exploitation et Infrastructure

2 2

Re: [Dovecot] imap-login hanging when firewall blocks ssl handshaking
by Erik A Johnson 05 Dec '12

05 Dec '12

FYI, the tcpdump I sent previously was with one of our previously-discussed patches in place: if (!proxy->client_proxy && net_geterror(proxy->fd_ssl) == EBADF) { I'm attaching that dump again (as tcpdump_output_witholdpatch_headeronly.txt), as well as a dump without any of the patches (tcpdump_output_withoutpatches_headeronly.txt) in case there is any difference. On December 4, 2012 6:18:23 AM PST, Ben Morrow <ben(a)morrow.me.uk> wrote: > At 12PM +0000 on 4/12/12 Ben Morrow wrote: >> Well, it looks to me as though xnu/bsd/kern/uipc_socket.c:soreceive will >> indeed return ENOTCONN for a socket which was once successfully >> connected but has now been disconnected. This happens when the socket is >> in the DEFUNCT state, which is a state that doesn't exist in FreeBSD; >> it's not completely clear but I suspect firewalls may be able to put >> arbitrary sockets into that state. > > Investigating a little further, it should be possible to test for this > situation directly. Assuming I'm correct about what's going on here, > this should be both cleaner and safer than mucking about looking for > ENOTCONN and guessing about what's happening. > > Erik, does this make the problem go away? I left out the > proxy->client_proxy test, since AFAICT this is just as likely to happen > on a client socket. > > Ben > > #ifdef SO_ISDEFUNCT > + if (getsockopt(proxy->fd_ssl, SOL_SOCKET, SO_ISDEFUNCT, > + (void *)&err, sizeof(err)) == 0 && err) { > + errstr = t_strdup_printf( > + "%s: socket is defunct", func_name); > + break; > + } > +#endif Nope, SO_ISDEFUNCT isn't defined.

2 1

[Dovecot] Quotas 2.1clarification
by Nick Edwards 05 Dec '12

05 Dec '12

Timo, I have much suspicion that our quota system is not working correctly since we migrate to 2.1 Currently using 2.1.10 Previously we had for issue of warnings quota_warning = storage=90%% /scripts/dqwarn-90.sh quota_warning2 = storage=75%% /scripts/dqwarn-75.sh worked great, these lines also migrated to new conf upon conversion. But quota conf example shows plugin { #quota_warning = storage=95%% quota-warning 95 %u #quota_warning2 = storage=80%% quota-warning 80 %u } # Example quota-warning service. The unix listener's permissions should be # set in a way that mail processes can connect to it. Below example assumes # that mail processes run as vmail user. If you use mode=0666, all system users # can generate quota warnings to anyone. #service quota-warning { # executable = script /usr/local/bin/quota-warning.sh # user = dovecot # unix_listener quota-warning { # user = vmail # } #} So this seems to indicate /scripts/dqwarn-75.sh should be a service name, which then calls the service quota-warning with that script in it etc etc etc surely this old 4 line method has not been replaced into a 20 line mess? Is this old way still functioning as I suspect it is not, and we need to write up two separate new quota warning services given our warnings are worded differently, or should the old methods still be working as they did in 1.2 and we have an error elsewhere? Niki

2 2