- dovecot - dovecot.org

[Dovecot] v2.0.9 -segfault in lib21_fts_solr_plugin.so
by G.Nau 16 Jan '11

16 Jan '11

After installing dovecot 2.0.8 (just updated to 2.0.9) I installed the fts plugin 2.0.9 and get several seconds after reloading dovecot segfaults. Jan 16 12:43:04 lin kernel: [601979.190764] imap[13313]: segfault at 18 ip 00007f5094cd99d6 sp 00007fffb10e96a0 error 4 in lib21_fts_solr_plugin.so[7f5094cd6000+7000] Jan 16 12:43:04 lin kernel: [601979.404712] imap[13315]: segfault at 18 ip 00007ff1f248a9d6 sp 00007fff500b0a90 error 4 in lib21_fts_solr_plugin.so[7ff1f2487000+7000] Jan 16 12:43:04 lin kernel: [601979.628830] imap[13317]: segfault at 18 ip 00007f4b5a2809d6 sp 00007fff8d012260 error 4 in lib21_fts_solr_plugin.so[7f4b5a27d000+7000] Jan 16 12:45:30 lin kernel: [602124.948358] show_signal_msg: 6 callbacks suppressed Jan 16 12:45:30 lin kernel: [602124.948369] imap[13960]: segfault at 18 ip 00007fa4f92ea9d6 sp 00007fff65212ee0 error 4 in lib21_fts_solr_plugin.so[7fa4f92e7000+7000] Jan 16 12:45:30 lin kernel: [602125.167202] imap[13962]: segfault at 18 ip 00007f07a1a8d9d6 sp 00007fff3183cb10 error 4 in lib21_fts_solr_plugin.so[7f07a1a8a000+7000] Regards Gunther

1 0

[Dovecot] fts squat: Disabled with in-memory indexes question
by Robert Schetterer 15 Jan '11

15 Jan '11

Hi Timo , should i care of that ? and what dous it mean Jan 15 09:23:15 mail02 dovecot: lmtp(6847): Debug: fts squat: Disabled with in-memory indexes Jan 15 09:23:15 mail02 dovecot: lmtp(6847): Debug: fts: No backends enabled by the fts setting i have protocol lmtp { # Space separated list of plugins to load (default is global mail_plugins). mail_plugins = quota sieve virtual acl fts fts_squat mail_log notify expire } so maybe having fts fts_squat here is not usefull ? -- Best Regards MfG Robert Schetterer Germany/Munich/Bavaria

1 0

Re: [Dovecot] Time jumped forwards
by Ian B 15 Jan '11

15 Jan '11

--- On Fri, 14/1/11, Tom Hendrikx <tom(a)whyscream.net> wrote: > > I had this problem too when I setup a VMware guest last > month (noticed > through strange spikes in munin's ntp monitoring, not > through dovecot > logs). After some research I found out that I had VMware > time > synchronisation (host to guest) enabled, and NTP in the > guest running. > The ESX host clock was some 90+ seconds behind, so VMware > stalled my > clock once in a while, after which NTP corrected it again. > > I asked the ESX admin to fix the clock, but disabled the > VMware > synchronisation and now use only ntp in the guest. Never > looked back. > > So in stead of 'ticking all the boxes', explain your setup. > You have NTP > enabled, but what does VMware do? Thanks for the post. I've checked my setup - the guest is not set to sync with the VMware host. NTP is running with local clock server commented out & 'tinker panic 0' set. It sounds like this is not a Dovecot issue so I'll stop posting to this list now and seek help elsewhere. What negative effects to Dovecot would I expect to see where the system clock is constantly changing?

3 2

[Dovecot] Check if a message has attachments
by Antoine Nguyen 14 Jan '11

14 Jan '11

Hi all, my question is not specific to Dovecot but to the IMAP protocol in general. I'm working on a web based software that provides a simple webmail ( http://modoboa.org/) I'm wondering what would an efficient way to detect if a message (or a group of messages) has attachments. I know it certainly consists in checking for specific MIME constructions but how to achieve that without fetching the whole body for each message? Thanks in advance, Antoine Nguyen

2 2

[Dovecot] Running two different versions of Dovecot (was: making folders unmovable)
by David Salisbury 14 Jan '11

14 Jan '11

OK, so I decided to go ahead and just upgrade to the latest 1 series Dovecot and see if that solves my ACL/config issues I've been having. (I tried compiling 2.0.9, but it errored out and I assume that's because it's a pretty old machine/compiler.) Anyway, 1.2.16 compiled fine, and I installed it in another location from the currently running 1.1 series install. I have this new install running (IMAP) on a non-standard port while I test it out, and it starts fine and all seems well. However, I'm wondering, is it OK to run it and have it look at the same Maildir mailboxes as the currently running 1.1 series install? Does that have the potential to mess with indexes or change anything in a bad way? (FWIW, I tried it briefly, and after changing the port number in and restarting my mail client [Thunderbird], it had trouble pulling up the mailbox I was trying to access.) David

1 0

Re: [Dovecot] Time jumped forwards
by Ian B 14 Jan '11

14 Jan '11

On Fri Jan 14 07:23:32 EET 2011, Eric Shubert wrote: >See >http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&docType… > > >In particular, see NTP Recommendations and VMware Tools bits at the bottom. Thanks, I've read through that document a couple of times now & I'm fairly sure my system 'ticks all the boxes' yet the warning messages continues. I can see no noticeable time discrepancy when I do periodic time checks from the command line comparing against another system's clock - certainly not 2 minute error margin Could this be a time mismatch between imap client & server? Ian.

3 4

[Dovecot] email addresses as usernames with Kerberos
by Peter Mogensen 14 Jan '11

14 Jan '11

Hi, I was trying out Kerberos authentication with som sample users for Dovecot and stumbled into this problem: The user names are of the form local-part@domain, so the Kerberos principal becomes "local-part\@domain@REALM". But it seems Dovecot (1.2.9) doesn't understand that syntax. Looking at the 2.0.8 sources I guess it's not supported. But isn't this a valid Kerberos principal? Is it a bug, or a missing feature or is there a special reason for not supporting it ? kind regards, Peter

1 0

[Dovecot] Time jumped forwards
by Ian B 14 Jan '11

14 Jan '11

Running Dovecot 2.0.8 on 32bit Centos5.5. The machine is a VMWare ESX VM. I'm seeing a lot of warning messages in syslog as follows: 2011-01-14T11:45:37.315917+08:00 imap4 dovecot: imap: Warning: Time jumped forwards 105 seconds 2011-01-14T11:46:00.598006+08:00 imap4 dovecot: imap: Warning: Time jumped forwards 106 seconds 2011-01-14T11:46:25.364405+08:00 imap4 dovecot: imap: Warning: Time jumped forwards 105 seconds 2011-01-14T11:46:27.030658+08:00 imap4 dovecot: imap: Warning: Time jumped forwards 106 seconds 2011-01-14T11:46:49.712202+08:00 imap4 dovecot: imap: Warning: Time jumped forwards 106 seconds 2011-01-14T11:48:07.600748+08:00 imap4 dovecot: imap: Warning: Time jumped forwards 106 seconds 2011-01-14T11:48:23.195587+08:00 imap4 dovecot: imap: Warning: Time jumped forwards 106 seconds 2011-01-14T11:48:37.342804+08:00 imap4 dovecot: imap: Warning: Time jumped forwards 106 seconds 2011-01-14T11:48:42.671037+08:00 imap4 dovecot: imap: Warning: Time jumped forwards 106 seconds 2011-01-14T11:48:45.903081+08:00 imap4 dovecot: imap: Warning: Time jumped forwards 105 seconds 2011-01-14T11:48:49.001119+08:00 imap4 dovecot: imap: Warning: Time jumped forwards 105 seconds 2011-01-14T11:48:58.935835+08:00 imap4 dovecot: imap: Warning: Time jumped forwards 105 seconds 2011-01-14T11:49:15.046253+08:00 imap4 dovecot: imap: Warning: Time jumped forwards 104 seconds 2011-01-14T11:49:16.842962+08:00 imap4 dovecot: imap: Warning: Time jumped forwards 106 seconds I've checked the clock settings in Centos and it all looks OK. NTP is running and not complaining about clock drift. Vmware recommend appending 'divider=10 clocksource=acpi_pm' kernel boot options to prevent timekeeping issues, which I've done. Has anyone else encountered this message? Is it something to be concerned about? Thanks, Ian.

2 1

Re: [Dovecot] Making shared folders "unmovable"
by Dave 13 Jan '11

13 Jan '11

Well, I just noticed this in my logs after I re-loaded the latest Dovecot config I tried: Jan 13 15:09:45 mail dovecot: SIGHUP received - reloading configuration Jan 13 15:09:45 mail dovecot: read(imap dump-capability process) failed: Interrupted system call Jan 13 15:09:45 mail dovecot: Invalid configuration, keeping old one Jan 13 15:09:45 mail dovecot: child 2085 (unknown) returned error 82 (Internal logging error) It's apparently been doing this every time I've reloaded the config, so this is probably why none of my changes with the ACLs are working. :/ Any thoughts on what could be causing this kind of error?? Does that error just basically mean something's set wrong somewhere in dovecot.conf? David

1 0

Re: [Dovecot] Best Cluster Storage
by Jonathan Tripathy 13 Jan '11

13 Jan '11

On 13/01/11 10:57, Stan Hoeppner wrote: > Jonathan Tripathy put forth on 1/13/2011 2:24 AM: > >> Ok so this is interesting. As long as I use Postfix native delivery, >> along with >> Dovecot director, NFS should work ok? > One has nothing to do with the other. Director doesn't touch smtp > (afaik), only > imap. The reason for having Postfix use its native local(8) delivery > agent for > writing into the maildir, instead of Dovecot deliver, is to avoid > Dovecot index > locking/corruption issues with a back end NFS mail store. So if you > want to do > sorting you'll have to use something other than sieve, such as > maildrop or > procmail. These don't touch Dovecot's index files, while Deliver > (LSA) does > write to them during message delivery into the maildir. Yes, I thought it had something to do with that >>> For any meaningful use of virtualized clusters with Xen, ESX, etc, a >>> prerequisite is shared storage. If you don't have it, get it. The >>> hypervisor >>> is what gives you fault tolerance. This requires shared storage. >>> If you do not >>> intend to install shared storage, and intend to use things like drbd >>> between >>> guests to get your storage redundancy, then you really need to >>> simply throw out >>> your hypervisor, in this case Xen, and do direct bare metal host >>> clustering with >>> drbd, gfs2, NFS, etc. >> Why is this the case? Apart from the fact that Virtualisation becomes >> "more >> useful" with shared storage (which I agree with), is there anything >> wrong with >> doing DR between guests? We don't have shared storage set up yet for the >> location this email system is going. We will get one in time though. > I argue that datacenter virtualization is useless without shared > storage. This > is easy to say for those of us who have done it both ways. You > haven't yet. > Your eyes will be opened after you do Xen or ESX atop a SAN. If > you're going to > do drbd replication between two guests on two physical Xen hosts then > you may as > well not use Xen at all. It's pointless. Where did I say I havn't done that yet? I have indeed worked with VM infrastructures using SAN storage, and yes, it's fantastic. Just this particular location doesn't have a SAN box installed. And we will have to agree to disagree as I personally do see the benefit of using VMs with local storage > What you need to do right now is build the justification case for > installing the > SAN storage as part of the initial build out and setup your virtual > architecture > around shared SAN storage. Don't waste your time on this other > nonsense of > replication from one guest to another, with an isolated storage pool > attached to > each physical Xen server. That's just nonsense. Do it right or don't > do it at all. > > Don't take my word for it. Hit Novell's website and VMWare's and pull > up the > recommended architecture and best practices docs. You don't need to tell me :) I already know how great it is > One last thing. I thought I read something quite some time ago about Xen > working on adding storage layer abstraction which would allow any Xen > server to > access directly connected storage on another Xen server, creating a > sort of > quasi shared SAN storage over ethernet without the cost of the FC > SAN. Did > anything ever come of that? > I haven't really been following how the 4.x branch is going as it wasn't stable enough for our needs. Random lockups would always occur. The 3.x branch is rock solid. There have been no crashes (yet!) Would DRBD + GFS2 work better than NFS? While NFS is simple, I don't mind experimenting with DRBD and GFS2 is it means fewer problems?

1 0