Re: [Dovecot] Dovecot stops with "Fatal: kevent(): Invalid argument"
On 05/21/2011 17:54, Timo Sirainen wrote: > On 21.5.2011, at 2.51, Henrik Larsson wrote: > >> >>>> That patch doesn't fix anything. It only changes the error message to be >>>> more informative so I could figure out what is causing it. If you haven't >>>> seen any more errors, it's just a coincidence. >>> >>> I have for some reason not seen the error since applying the above patch. >>> But wouldn't it make sense to include the patch in the stable release so >>> others can give input in the rare case they experience the same issue? At >>> least until the issue has been resolved. >>> >>> I don't say that this is a Dovecot issue, and I admit that it have to be a >>> rare case, but when two independent people experience the same error, there >>> have to be a problem somewhere. >> >> Is there a problem adding a patch like this to the stable code? > > Annoying to add ugly debug code for a problem that happens so rarely.. > >> Should I ask the FreeBSD dovecot2 port maintainer to add it to the FreeBSD >> port instead? > > I wouldn't mind them adding it. > I just saw it (~1500 users affected, dovecot disappeared) dovecot: master: Panic: kevent() failed: Invalid argument FreeBSD 11-RELEASE-p10, dovecot 2.2.29 (.1_2 package revision) This thread was the only exact match on search engines… No other match in last 60 days's logs of our two dovecot 'backends' (nor in last 10 years from my head) Not sure if this can help… a least for stats … @Timo: kudos for ~15 years of not experiencing this kind of bugs :) -- *geoffroy desvernay* C.R.I - Administration systèmes et réseaux Ecole Centrale de Marseille signature.asc Description: OpenPGP digital signature
Re: [Dovecot] auth_cache multiple passwords ?
Timo Sirainen a écrit : > On Jun 12, 2009, at 9:45 AM, Geoffroy Desvernay wrote: > >> For a single webmail connection per login, it work, thanks to cache_key >> using client's IP. >> >> But for multiple use of the same login in the webmail, there are more >> than one 'password' valid at a time… >> >> What may be the 'correct' solution: > > The only usable solution I see is to disable negative auth caching and > use this patch from v1.2: > http://hg.dovecot.org/dovecot-1.2/rev/8a23ab43132a > Thank you ! I compiled 1.1.16 with this patch (applied manually). If I understand what it does (I'm not sure at all), It just allow disabling negative caching of wrong passwords, but it doesn't allow to cache multiple passwords for one 'cache_key', am I right ? In my test-case, this patch allows the webmail to work, getting a new ticket for each IMAP connection (1 login failure then login success with a new ticket) in case of concurrent connections with a same login. (the last who clicks kicks out others from the cache) I think dovecot understands this as a 'password change', and this behaviour seems correct for all but this case :( How difficult would it be to keep cached more than one password by key ? -- *Geoffroy Desvernay* C.R.I - Administration systèmes et réseaux Ecole Centrale de Marseille Tel: (+33|0)4 91 05 45 24 Fax: (+33|0)4 91 05 45 98 d...@centrale-marseille.fr signature.asc Description: OpenPGP digital signature
Re: [Dovecot] auth_cache multiple passwords ?
Timo Sirainen a écrit : > On Jun 12, 2009, at 9:45 AM, Geoffroy Desvernay wrote: > >> For a single webmail connection par login, it work, thanks to cache_key >> using client's IP. >> >> But for multiple use of the same login in the webmail, there are more >> than one 'password' valid at a time… >> >> What may be the 'correct' solution: > > The only usable solution I see is to disable negative auth caching and > use this patch from v1.2: > http://hg.dovecot.org/dovecot-1.2/rev/8a23ab43132a > I'll try to patch 1.1.16 with this patch and report here, thanks ! signature.asc Description: OpenPGP digital signature
[Dovecot] auth_cache multiple passwords ?
Hi, First, thanks Timo and Stefan for this great IMAP/Sieve implementation... We are using 1.1.16+cmu_sieve/managesieve additions for now (following releases since ~ 1.0.1). We have a specific problem here with auth-cache: We use direct imap/sieve connection from different clients, using LDAP password: everything is fine. The problem appears with our webmail access using a web-SSO system (jasig's CAS), using one-time-tickets as password for imap connections (checked by pam_cas module for now). For a single webmail connection par login, it work, thanks to cache_key using client's IP. But for multiple use of the same login in the webmail, there are more than one 'password' valid at a time… What may be the 'correct' solution: - patching auth-cache.c (auth_cache_lookup function ?) - writing a different login backend ? - ??? Hope I'm clear enough… -- geoffroy desvernay Ecole Centrale de Marseille signature.asc Description: OpenPGP digital signature
Re: [Dovecot] Sieve per virtual mailbox
Joan a écrit : > the client side does not just convert the "Rules" defined in Thuderbird > into a sieve script ? > Yes, but it 'talks' to a managesieve server, not IMAP, and to make dovecot act as a managesieve server you need Stefan's patch in dovecot + Stefan's Managesieve server compiled against dovecot (+ dovecot.conf 'managesieve' part). If I understand well, you actually have sieve plugin working, but not managesieve. If your users have access to sieve scripts (and knowledge to write them), they can also use any editor on their account, without need of managesieve server... HTH -- geoffroy desvernay signature.asc Description: OpenPGP digital signature
Re: [Dovecot] Sieve per virtual mailbox
Nikolay Shopik a écrit : > On 10.06.2009 19:02, Joan wrote: >> Not sure I understand all: >> I have dovecot-libsieve from Stefan installed (with a script for all >> virtual mailboxes installed and correctly running) >> So: >> I need to install another software on the server side ? which one ? >> I need to install another software on the client side ? which one ? >> […] >> > You probably need managesieve patch as well from Stefan to make this > work. After that user can connect to server using addon showed here > before and edit sieve file on fly. Only problem user have to know syntax. > You need all of this *only if* you want your clients to be able to edit their own rules… Just to make it more clear ;) -- *Geoffroy Desvernay* signature.asc Description: OpenPGP digital signature
Re: [Dovecot] Managesieve
Thomas E. Deutsch a écrit : > Hi > > I've a problem. I've built a new mailserver for our company based on > dovecot (1.1.15). At the same time, our company's name has changed. The > old mail addresses are forwarded to the new addresses. > > But I've a problem with sieve. It looks like the sieve filters are only > working for the new addresses. But due to the change of the name was not > long ago, most of the mails are still sent to the old addresses. > > What can I do to get filters also working for the old addresses? > > Configuration of managesieve: > Isn't the problem in the sieve rules more than in the server's config ? My 2 cents... -- Geoffroy Desvernay signature.asc Description: OpenPGP digital signature
Re: [Dovecot] Dovecot + FreeBSD-7.2 + ZFS ?
Frank Bonnet a écrit : > Hello > > Anyons has tested this configuration with success ? > > I'll test it in few days and I am wondering if I am alone :-) > Not ZFS, but various combinations of dovecot 1.1.15+FreeBSD(7.1 and 7.2)+(NFS and UFS). No problem for us® ;) -- Geoffroy Desvernay signature.asc Description: OpenPGP digital signature
Re: [Dovecot] Quota over NFS
Flavio Costa a écrit : > Hey, Hi, > I've been strugling to get quota working on my enviroment. > > I have one storage server that exports the 'home' dir. > My mail server mounts the exported 'home' server at '/home' We have something like that > > # dovecot --version >> 1.1.14 1.1.11 for us > > > I'm also running Postfix and using Dovecot/LDA as MDA so that we can use the > Dovecot's Quota plugin. Here, from 'dovecot -n': mail_plugins(imap): quota imap_quota quota: fs:user:noenforcing > > The thing is that if the user has exceeded it's quota the LDA detects it and > I get a response from postmaster warning me that the INBOX is full. > But through IMAP, if I issue : > >> C: 1 GETQUOTAROOT INBOX >> S: * QUOTAROOT INBOX "" >> S: 1 OK Getquota complete >> >> There's no: > >> * QUOTA "" (STORAGE 10 512) >> Here: . OK Logged in. . GETQUOTAROOT INBOX * QUOTAROOT "INBOX" "user" * QUOTA "user" (STORAGE 46752 2355200) . OK Getquotaroot completed. I'll try with 1.1.14 this week (if I manage to get time for that …) I'll be back here if there is some regression. -- *Geoffroy Desvernay* C.R.I - Administration systèmes et réseaux Ecole Centrale de Marseille signature.asc Description: OpenPGP digital signature
Re: [Dovecot] behavior of dovecot with Openldap
Masaharu Kawada a écrit : >> I'm pretty sure that configuration will simply use both the servers >> all the time more or less randomly. Unless OpenLDAP library has some >> code that does something similar to what you're talking about, but >> somehow I doubt that. Here we use "uris" parameter instead of "hosts", and we seems to have expected behaviour: dovecot is always using the first listed uri except if it doesn't respond (switch to the second) We can check it simply: first listed server have more than 200 simultaneous connexions daily, 2nd have only one per slave (replication thread) (we use the slave as first uri) Hope this helps. -- Geoffroy Desvernay signature.asc Description: OpenPGP digital signature
Re: [Dovecot] imap dump-capability fails Dovecot 1.1.6
Timo Sirainen a =E9crit : > On Fri, 2008-10-31 at 08:32 +0100, Thorsten Vollmer wrote: >> Hi Timo, >> >> Dovecot fails to start after upgrading from 1.1.4 to 1.1.6: >> >> Fatal: userdb didn't return a home directory, but mail location used i= t >> (%h): %h/mail:CONTROL=3D%h/control:INDEX=3D%h/index >> Error: imap dump-capability process returned 89 >> Fatal: Invalid configuration in /etc/dovecot/dovecot.conf >> >> Adding a fake home directory to args in >> master-settings.c:get_imap_capability solved the problem for me, but >> there may be a more correct fix. >=20 > Yes, that's the correct fix: > http://hg.dovecot.org/dovecot-1.1/rev/2fbd36039526 >=20 > One workaround is to use ~ instead of %h. It'll log errors, but it stil= l > works. >=20 > Wonder how many people will have this problem.. Perhaps I'll have to > release 1.1.7 just because of it. >=20 I did too... (but found the workaround at first try) --=20 ___ / Geoffroy DESVERNAY |\ /\`Service info`| Tel: (+33|0)4 91 05 45 24 /\ \/ Ecole Centrale de Marseille | Fax: (+33|0)4 91 05 45 98 \/ \ (ex-EGIM)| Mail: [EMAIL PROTECTED] / --- signature.asc Description: OpenPGP digital signature
Re: [Dovecot] Dovecot+PostfixAdmin+PostgreSQL on FreeBSD 7
Erdenebat Gantumur a écrit : > Hi dear, Timo > > When I execute dovecot -F then it doesn't exiting. During this time when > try to telnet 110 port it shows > > Escape character is '^]'. > +OK Dovecot ready. > ^] > telnet> quit > > Also i've set log and log_info path. In dovecot_info.log it's showing: > > dovecot: 2008-10-23 01:23:39 Info: Dovecot v1.1.3 starting up > dovecot: 2008-10-23 01:23:39 Info: auth(default): pgsql: Connected to > postfix > dovecot: 2008-10-23 01:25:09 Info: pop3-login: Disconnected (no auth > attempts): rip=x.x.x.x, lip=x.x.x.x, secured > dovecot: 2008-10-23 01:25:27 Info: imap-login: Disconnected (no auth > attempts): rip=x.x.x.x, lip=x.x.x.x, secured > dovecot: 2008-10-23 01:25:51 Info: pop3-login: Disconnected (no auth > attempts): rip=x.x.x.x, lip=x.x.x.x, secured > > What does it mean? How can I run dovecot just like common way > /usr/local/etc/rc.d/dovecot start? When I execute that command it > doesn't start. Thank you. > Hi, Are you sure there is smething like 'dovecot_enable="YES"' in /etc/rc.conf ? tip: try /usr/local/etc/rc.d/dovecot rcvar Hope this helps Geoffroy signature.asc Description: OpenPGP digital signature
[Dovecot] dovecot 1.1.4 managesieve patch
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I'm maintainer of managesieve's FreeBSD port. (cc to dovecot's port maintainer) Stephan, do you plan to make available a 1.1.4 specific patch ? Dovecot's port assume that managesieve patch include dovecot's version number: so it may help the port's upgrade process. (seems that 1.1.3's patch is applying smoothly) Another question: I didn't found anything about managesieve support in dovecot 1.2x: - is the patch still required ? - should managesieve server work with dovecot 1.2 in actual state (0.10.3) I'll soon try it on a small setup (FreeBSD+Maildir+fs quotas+managesieve) - -- Geoffroy Desvernay -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.9 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkjp79sACgkQGbFYzwF8gKrubACfYBDeX88iGNAePPfeut/YksJ4 6zgAoJAmOTvx6fKjNQ4Vs7VWkxFHjMCp =8G2x -END PGP SIGNATURE-
Re: [Dovecot] v1.1.1 released
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Timo Sirainen a écrit : > http://dovecot.org/releases/1.1/dovecot-1.1.1.tar.gz > http://dovecot.org/releases/1.1/dovecot-1.1.1.tar.gz.sig > > Hopefully this release lives a bit longer than v1.1.0. > > - Maildir: When migrating from v1.0 with old format dovecot-uidlist > files, Dovecot may have appended lines to it using the new format and > later broken with "UID larger than next_uid" error. > updated freebsd ports for dovecot, sieve plugin and managesieve here: http://dgeo.perso.ec-marseille.fr/dovecot Not very well tested, but 'it works for us'™ Thank you Timo ! - -- _______ /*Geoffroy DESVERNAY* |\ /\`Service info`| Tel: (+33|0)4 91 05 45 24 /\ \/ | Fax: (+33|0)4 91 05 45 98 \/ \ Ecole Centrale de Marseille | Mail: dgeo ec-marseille.fr / --- -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.9 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkhjadMACgkQGbFYzwF8gKpi2ACfW0MiIX8ekUoWCmFOZBnZPAIl QSgAniVblppvCgCwhdEN4SfACLPGu8q2 =+tzg -END PGP SIGNATURE-
Re: [Dovecot] quotactl bug?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 JOHN ROMAN a écrit : > more on the strange quota errorthis is in BSD, with quotas referenced on > an NFS, and users provided by YP/NIS > > quotactl(Q_GETQUOTA, /.amd_mnt/crock/vol/v_user1/jdoe) failed: Operation not > supported > > this looks strange to me, as the specification for quotactl states the > function Q_GETQUOTA: > > Q_GETQUOTAGet disk quota limits and current usage for the user or >group (as determined by the command type) with identifier >id. The addr argument is a pointer to a struct dqblk >structure (defined in ). > > > this directory path is not a valid UID...rather, its my user home directory > path! > For us (whith FreeBSD 6.x and 7.0), this (quota over NFS) only works since 1.1. I had the same error with dovecot-1.0x. With 1.1, we still need: - rquotad in /etc/inetd.conf in both server and client (and of cource inetd_enable="YES" in /etc/rc.conf ;) to check this, "# rpcinfo -p server | grep rquota" - quota enable on this filesystem... I think there was a patch somewhere to enable this on 1.0x too... check the archives. - -- ___ /*Geoffroy DESVERNAY* |\ /\`Service info`| Tel: (+33|0)4 91 05 45 24 /\ \/ Ecole Centrale de Marseille | Fax: (+33|0)4 91 05 45 98 \/ \ (ex-EGIM)| Mail: [EMAIL PROTECTED] / --- -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.9 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkhIAQ8ACgkQGbFYzwF8gKqGzACgnFNWOJCnEaSv78105RyXa1j2 eSoAnRSwFGJLQrBFz6e1dQ/S5TCiIFdh =ROXg -END PGP SIGNATURE-
[Dovecot] FreeBSD port for 1.1, some bits more...
I did (re-)compile dovecot (1.1rc8) today, with managesieve (0.10.2) and
sieve-plugin (1.1.5).
I did modify the existing dovecot-devel port, adding managesieve patch
as an OPTION, and I added a 'dovecot-managesieve-devel' port, and a
'dovecot-sieve-devel' one to be complete...
Not sure everything is very complete, but at least it works for me=E2=84=A2=
, and
if it can help anybody to save some time... The tree ports are there:
http://dgeo.perso.ec-marseille.fr/dovecot
Not sure I used the very good way of building FreeBSD ports...
Cheers,
Geoffroy
--=20
___
/ Geoffroy DESVERNAY |\
/\`Service info`| Tel: (+33|0)4 91 05 45 24 /\
\/ Ecole Centrale de Marseille | Fax: (+33|0)4 91 05 45 98 \/
\ (ex-EGIM)| Mail: dgeo ec-marseille.fr /
---
signature.asc
Description: OpenPGP digital signature
[Dovecot] FreeBSD port: port's patch for 1.1rc3
For those who wants testing 1.1rc3 on FreeBSD, this is a simple patch
against /usr/ports/mail/dovecot.
To apply:
# cd /usr/ports/mail/dovecot
# patch -p1 < /tmp/patch_dovecot_1.0.13-1.1.rc3.diff
Hope I did not forget something important... This is an adaptation of
the existing port.
PS: for port's maintainer: Which way will take 1.0 vs 1.1 upgrade ? a
new mail/dovecot10 port or ?
Hope this helps
--
Geoffroy Desvernay
diff -bruN dovecot-1.0.13/Makefile dovecot/Makefile
--- dovecot-1.0.13/Makefile 2008-04-01 14:41:12.0 +0200
+++ dovecot/Makefile2008-04-01 14:29:33.0 +0200
@@ -7,9 +7,9 @@
#
PORTNAME= dovecot
-DISTVERSION= 1.0.13
+DISTVERSION= 1.1.rc3
CATEGORIES=mail ipv6
-MASTER_SITES= http://www.dovecot.org/releases/1.0/
+MASTER_SITES= http://www.dovecot.org/releases/1.1/rc/
MAINTAINER=[EMAIL PROTECTED]
COMMENT= Secure and compact IMAP and POP3 servers
diff -bruN dovecot-1.0.13/distinfo dovecot/distinfo
--- dovecot-1.0.13/distinfo 2008-04-01 14:41:12.0 +0200
+++ dovecot/distinfo2008-04-01 14:43:56.0 +0200
@@ -1,3 +1,3 @@
-MD5 (dovecot-1.0.13.tar.gz) = 281bd9dee8d6c1674977257acc80ce64
-SHA256 (dovecot-1.0.13.tar.gz) =
16da29b2bc08d0178a09323bf0787a2a0e953075655566a7b4b6b148c87ac25f
-SIZE (dovecot-1.0.13.tar.gz) = 1774025
+MD5 (dovecot-1.1.rc3.tar.gz) = eed10a2f5142ebdf88276c0a82f548e1
+SHA256 (dovecot-1.1.rc3.tar.gz) =
5a72318a6f4d12a1da7104de94b439a8523142c0f54af1f1ff64966820ef9460
+SIZE (dovecot-1.1.rc3.tar.gz) = 329
diff -bruN dovecot-1.0.13/files/patch-dovecot-example.conf
dovecot/files/patch-dovecot-example.conf
--- dovecot-1.0.13/files/patch-dovecot-example.conf 2008-04-01
14:41:12.0 +0200
+++ dovecot/files/patch-dovecot-example.conf2008-04-01 14:38:52.0
+0200
@@ -1,5 +1,5 @@
dovecot-example.conf.orig 2008-03-04 05:48:12.0 +
-+++ dovecot-example.conf 2008-03-05 22:49:08.554336095 +
+--- dovecot-example.conf.orig 2008-04-01 14:30:50.0 +0200
dovecot-example.conf 2008-04-01 14:38:28.0 +0200
@@ -12,7 +12,7 @@
# Default values are shown for each setting, it's not required to uncomment
# any of the lines. Exception to this are paths, they're just examples with
@@ -15,9 +15,9 @@
#protocols = imap imaps
+protocols = %%PROTOCOLS%%
- # IP or host address where to listen in for connections. It's not currently
- # possible to specify multiple addresses. "*" listens in all IPv4 interfaces.
-@@ -210,6 +212,7 @@
+ # A space separated list of IP or host addresses where to listen in for
+ # connections. "*" listens in all IPv4 interfaces. "[::]" listens in all IPv6
+@@ -213,6 +214,7 @@
#
#
#mail_location =
@@ -25,7 +25,7 @@
# If you need to set multiple mailbox locations or want to change default
# namespace settings, you can do it by defining namespace sections.
-@@ -256,6 +259,7 @@
+@@ -273,6 +275,7 @@
# used only for creating mbox dotlock files when creation fails for INBOX.
# Typically this is set to "mail" to give access to /var/mail.
#mail_privileged_group =
@@ -33,7 +33,7 @@
# Grant access to these supplementary groups for mail processes. Typically
# these are used to set up access to shared mailboxes. Note that it may be
-@@ -320,6 +324,7 @@
+@@ -339,6 +342,7 @@
# IP address. Useful for seeing who are actually using the IMAP processes
# (eg. shared mailboxes or if same uid is used for multiple accounts).
#verbose_proctitle = no
@@ -41,7 +41,7 @@
# Valid UID range for users, defaults to 500 and above. This is mostly
# to make sure that users can't log in as daemons or other system users.
-@@ -333,6 +338,7 @@
+@@ -352,6 +356,7 @@
# belongs to supplementary groups with non-valid GIDs, those groups are
# not set.
#first_valid_gid = 1
@@ -49,7 +49,7 @@
#last_valid_gid = 0
# Maximum number of running mail processes. When this limit is reached,
-@@ -506,19 +512,19 @@
+@@ -501,19 +506,19 @@
protocol imap {
# Login executable location.
@@ -73,7 +73,7 @@
# Maximum IMAP command line length in bytes. Some clients generate very long
# command lines with huge mailboxes, so you may need to raise this if you
get
-@@ -528,7 +534,7 @@
+@@ -527,7 +532,7 @@
# Support for dynamically loadable plugins. mail_plugins is a space
separated
# list of plugins to load.
#mail_plugins =
@@ -82,15 +82,15 @@
# Send IMAP capabilities in greeting message. This makes it unnecessary for
# clients to request it with CAPABILITY command, so it saves one round-trip.
-@@ -563,6 +569,7 @@
+@@ -562,6 +567,7 @@
# accept '/' suffix in mailbox names in subscriptions list.
# The list is space-separated.
- #imap_client_workarounds = outlook-idle
-+ imap_client_workarounds = delay-newmail outlook-idle netscape-eoh
tb-extra-mailbox-sep
+ #imap_client_workarounds =
[Dovecot] Index corruption ?
Hi,
We are using dovecot for some times (a little before 1.0), for IMAP and
(a little for the moment) deliver.
We have ~2 logins/day, Maildirs are over NFS (with indexes too, for
the moment...)
Up to 1.0.5, we sometime have this error in maillog:
Nov 1 13:55:41 tic dovecot: IMAP(login): file mail-index-view-sync.c:
line 666 (mail_index_view_sync_end): assertion failed:
(view->log_file_offset >= view->map->hdr.log_file_int_offset)
I didn't find any bits on google, nor on this list's archive...
# gdb (without debug, I may do it if required)
Program terminated with signal 6, Aborted.
Reading symbols from /usr/local/lib/libiconv.so.3...(no debugging
symbols found)...done.
Loaded symbols for /usr/local/lib/libiconv.so.3
Reading symbols from /lib/libc.so.6...(no debugging symbols found)...done.
Loaded symbols for /lib/libc.so.6
Reading symbols from /libexec/ld-elf.so.1...(no debugging symbols
found)...done.
Loaded symbols for /libexec/ld-elf.so.1
#0 0x182ad51f in kill () from /lib/libc.so.6
(gdb) bt
#0 0x182ad51f in kill () from /lib/libc.so.6
#1 0x182ad4be in raise () from /lib/libc.so.6
#2 0x182ac0e8 in abort () from /lib/libc.so.6
#3 0x080a85da in i_set_failure_syslog ()
#4 0x080a80e1 in data_stack_deinit ()
#5 0x08092c97 in mail_index_view_sync_end ()
#6 0x0808229e in index_mailbox_sync_next ()
#7 0x001c in ?? ()
#8 0xbfbfe7e8 in ?? ()
#9 0x080d3140 in ?? ()
#10 0x080d8044 in ?? ()
#11 0x001c in ?? ()
#12 0xbfbfe828 in ?? ()
#13 0x08060761 in imap_sync_deinit ()
Previous frame inner to this frame (corrupt stack?)
dovecot -n
# 1.0.5: /usr/local/etc/dovecot.conf
ssl_ca_file: /etc/ssl/cacert.pem
ssl_cert_file: /etc/ssl/private/imaps.ec-marseille.fr.pem
ssl_key_file: /etc/ssl/private/imaps.ec-marseille.fr.key
disable_plaintext_auth: no
login_dir: /var/run/dovecot/login
login_executable: /usr/local/libexec/dovecot/imap-login
login_greeting: IMAP Centrale ready.
login_greeting_capability: yes
login_process_size: 64
login_processes_count: 20
login_max_processes_count: 512
valid_chroot_dirs: /users:/home
max_mail_processes: 2048
verbose_proctitle: yes
first_valid_uid: 1000
last_valid_uid: 55000
first_valid_gid: 999
last_valid_gid: 55000
mail_extra_groups: mail
mail_location: maildir:%h/Maildir/
mmap_disable: yes
lock_method: flock
maildir_stat_dirs: yes
maildir_copy_with_hardlinks: yes
mail_drop_priv_before_exec: yes
mail_executable: /usr/local/libexec/dovecot/imap_convert
imap_client_workarounds: delay-newmail outlook-idle netscape-eoh
tb-extra-mailbox-sep
auth default:
verbose: yes
worker_max_count: 60
passdb:
driver: pam
args: imap
passdb:
driver: ldap
args: /usr/local/etc/dovecot-ldap.conf
userdb:
driver: passwd
userdb:
driver: ldap
args: /usr/local/etc/dovecot-uldap.conf
socket:
type: listen
client:
path: /var/spool/postfix/private/auth
mode: 432
user: postfix
group: postfix
master:
path: /var/run/dovecot/auth-master
mode: 384
plugin:
quota: fs
___
# dovecot-ldap.conf (dovecot-uldap.conf is a symlink)
___
hosts = ldapr.serv.int:389 ldap:389
dn =
dnpass =
auth_bind = yes
ldap_version = 3
base = ou=People,
deref = never
scope = onelevel
user_attrs = homeDirectory=home,uidNumber=uid,gidNumber=gid,uid=system_user
user_filter =
(&(objectClass=inetLocalMailRecipient)(|(uid=%u)(mail=%u)(mail=%n@)))
pass_attrs = uid=user
pass_filter =
(&(objectClass=inetLocalMailRecipient)(|(uid=%u)(mail=%u)(mail=%n@)))
--
___
/ Geoffroy DESVERNAY |\
/\`Service info`| Tel: (+33|0)4 91 05 45 24 /\
\/ Ecole Centrale de Marseille | Fax: (+33|0)4 91 05 45 98 \/
\ (ex-EGIM)| Mail: [EMAIL PROTECTED] /
---
signature.asc
Description: OpenPGP digital signature
Re: [Dovecot] FreeBSD NFS file locking mechanism
Timo Sirainen a écrit : > On Thu, 2007-06-28 at 15:18 +0200, Geoffroy Desvernay wrote: >> Tony Tsang a écrit : >>> Hi all, >>> >>> I have some machines running FreeBSD and dovecot deployed. User's home >>> dir is on NFS mount and I've found that dovecot only works with >>> dotlock file locking mechanism, fcntl and flock failed. Now it causes >>> problem with thunderbird (thunderbird is cachine connections) waiting >>> forever and I noticed that dovecot is trying to acquire a lock but >>> unsuccessful since the lock file is in place. Is it possible to use >>> file locking other than dotlock on FreeBSD NFS mounted homedir? How do >>> I achieve this? >>> >>> Thanks a lot. >>> >>> Tony Tsang. >> We have the same setup, working with >> lock_method: flock > > lock_method affects only index files. Are they also in NFS? > Oups... Sorry, next time I'll read a bit more before answer... >> We have rpc.lockd running (rpc_lockd_enable="YES" in rc.conf) in both >> nfs servers and clients(dovecot server). > > flock locks files only locally, they aren't visible to other computers. > Only fcntl locks are. (Except with Linux 2.6.5+, AFAIK no other OSes do > this). > so I'll double-check my config... -- ___ / Geoffroy DESVERNAY |\ /\`Service info`| Tel: (+33|0)4 91 05 45 24 /\ \/ Ecole Centrale de Marseille | Fax: (+33|0)4 91 05 45 98 \/ \ (ex-EGIM)| Mail: [EMAIL PROTECTED] / --- signature.asc Description: OpenPGP digital signature
Re: [Dovecot] FreeBSD NFS file locking mechanism
Tony Tsang a écrit : > Hi all, > > I have some machines running FreeBSD and dovecot deployed. User's home > dir is on NFS mount and I've found that dovecot only works with > dotlock file locking mechanism, fcntl and flock failed. Now it causes > problem with thunderbird (thunderbird is cachine connections) waiting > forever and I noticed that dovecot is trying to acquire a lock but > unsuccessful since the lock file is in place. Is it possible to use > file locking other than dotlock on FreeBSD NFS mounted homedir? How do > I achieve this? > > Thanks a lot. > > Tony Tsang. We have the same setup, working with lock_method: flock We have rpc.lockd running (rpc_lockd_enable="YES" in rc.conf) in both nfs servers and clients(dovecot server). FreeBSD 6.2 -- ___ / Geoffroy DESVERNAY |\ /\`Service info`| Tel: (+33|0)4 91 05 45 24 /\ \/ Ecole Centrale de Marseille | Fax: (+33|0)4 91 05 45 98 \/ \ | Mail: [EMAIL PROTECTED] / --- signature.asc Description: OpenPGP digital signature
