Nabble - Dovecot

Re: Thinderbird+delete+move to Trash folder

2009-12-22T02:08:39Z

On Tue, Dec 22, 2009 at 12:32:00AM +0100, Papp Tamás wrote:
> It's like when a messages is deleted from TB, the message get moved
> to the Trash folder, and it's expunged(?) at the same time. Is it
> possible?

Do you use TB2? And do you have two trash folders? Like:
- INBOX.Trash
- Trash

Then have a look at this bugreport:
https://bugzilla.mozilla.org/show_bug.cgi?id=479226

TB3 behaves differently, but still wrong.

So long,
Aiko
--
:wq ✉

Re: Dovecot Deliver CPU usage

2009-12-21T20:33:00Z

> On Tue, 2009-12-15 at 15:08 -0500, Timo Sirainen wrote:
>> > Dec 14 12:46:04 server01 postfix/pipe[1870]: 57489E913:
>> > to=<user1@...>, orig_to=<user2@...>, relay=dovecot,
>> > delay=1703, delays=1369/328/0/5.9, dsn=5.7.0, status=bounced
>> (permission
>> > denied. Command output: Not enough disk space )
>>
>> Can you get a strace from this kind of a failed delivery? The strace
>> should contain ENOSPC string.
>
> Looking at the code .. I think that can happen with both EDQUOT and
> ENOSPC errors from a write, but nothing else..

Strace with ENOSPC

09:57:39.782569 write(10, "T5vfloaIeSOsJdT6IXB146wSWLNKqK\n4v"..., 28672)
= -1 ENOSPC (No space left on device)
09:57:40.695074 fstat(10, {st_mode=S_IFREG|0644, st_size=2068480, ...}) = 0
09:57:40.707778 munmap(0x7fa35c97b000, 2101248) = 0
09:57:40.708119 close(10) = 0
09:57:40.708162
unlink("/home/vmail/example.com/user1/tmp/1261456056.M913860P17478.node01")
= 0
09:57:40.711774 sendto(6, "<22>Dec 22 09:57:40 dovecot: deli"..., 201,
MSG_NOSIGNAL, NULL, 0) = 201
09:57:40.712087 munmap(0x7fa35dc47000, 200704) = 0
09:57:40.712148 write(2, "Not enough disk space\n"..., 22) = 22
09:57:40.712235 sendto(6, "<22>Dec 22 09:57:40 dovecot: deli"..., 189,
MSG_NOSIGNAL, NULL, 0) = 189
09:57:40.712353 exit_group(77)

Re: Thinderbird+delete+move to Trash folder

2009-12-21T15:57:28Z

Papp Tamás wrote, On 2009. 12. 22. 0:32:

> hi All,
>
> I have a problem, which makes me headache. I can't find out, what is
> the problem.
>
> I have a mail szerver, which works just fine as expected, TB move
> messages to trash folder after I delete it, and they are moved.
>
> I have an other server. If I delete a message, it doesn't move to the
> Trash folder. As deleted_to_trash plugin is installed, if I only mark
> messages as deleted, they are moved to thee Trash folder and also with
> Outlook works well.
>
>
> It's like when a messages is deleted from TB, the message get moved to
> the Trash folder, and it's expunged(?) at the same time. Is it possible?
>
> Could you help me?
>
> The system is Ubuntu 9.04 with docecot 1.2.5-0~auto+0 from
> http://xi.rename-it.nl/debian/, but builded by myself for x86_64.

I've just tried 1.2.9-0~auto+21 and I see the same.

But(!) if I press SHIFT+DELETE, than it's working as it should work with
the pure DELETE. Probably SHIFT+DEL set only the delete flag, it does
not move the message?

Thank you,

tamas

Thinderbird+delete+move to Trash folder

2009-12-21T15:32:00Z

hi All,

I have a problem, which makes me headache. I can't find out, what is the
problem.

I have a mail szerver, which works just fine as expected, TB move
messages to trash folder after I delete it, and they are moved.

I have an other server. If I delete a message, it doesn't move to the
Trash folder. As deleted_to_trash plugin is installed, if I only mark
messages as deleted, they are moved to thee Trash folder and also with
Outlook works well.

It's like when a messages is deleted from TB, the message get moved to
the Trash folder, and it's expunged(?) at the same time. Is it possible?

Could you help me?

The system is Ubuntu 9.04 with docecot 1.2.5-0~auto+0 from
http://xi.rename-it.nl/debian/, but builded by myself for x86_64.

Thank you,

tamas

Remove From Server When Deleted From Deleted Items

2009-12-21T10:05:30Z

In Windows Live Mail I have this setting enabled: "Remove From Server
When Deleted From Deleted Items". It does not seem to remove them
even when the trash is emptied though. Am using POP3 access. Anyone
else see this?

Matt

Re: Dovecot v2.0 wiki

2009-12-21T10:02:35Z

On 20.12.2009, at 1.01, Pascal Volk wrote:

> Does this mean, all the mentions of v1.x could be removed when a page is
> updated?
> Some v1.x specific pages (e.g. /LDA/Sieve/CMU) can be deleted?

Yes.

Re: dovecot-1.2.8 imap crash (with backtrace)

2009-12-21T09:43:52Z

Just wanted to update you that I just upgraded all of our servers to
1.2.9 and I'm still seeing the array_delete panic:

Dec 21 12:10:16 gehenna11.rutgers.edu dovecot: IMAP(user1): Panic: file
maildir-uidlist.c: line 403 (maildir_uidlist_records_array_delete):
assertion failed: (pos != NULL)
Dec 21 12:15:12 gehenna19.rutgers.edu dovecot: IMAP(user2): Panic: file
maildir-uidlist.c: line 403 (maildir_uidlist_records_array_delete):
assertion failed: (pos != NULL)

I also started receiving a good deal of these, but only from one user so
far:

Dec 21 12:16:42 gehenna14.rutgers.edu dovecot: IMAP(user3): Panic: file
cmd-list.c: line 242 (ns_get_listed_prefix): assertion failed: (match ==
IMAP_MATCH_YES)
Dec 21 12:18:20 gehenna14.rutgers.edu dovecot: IMAP(user3): Panic: file
cmd-list.c: line 242 (ns_get_listed_prefix): assertion failed: (match ==
IMAP_MATCH_YES)
Dec 21 12:18:20 gehenna14.rutgers.edu dovecot: IMAP(user3): Panic: file
cmd-list.c: line 242 (ns_get_listed_prefix): assertion failed: (match ==
IMAP_MATCH_YES)
Dec 21 12:19:57 gehenna14.rutgers.edu dovecot: IMAP(user3): Panic: file
cmd-list.c: line 242 (ns_get_listed_prefix): assertion failed: (match ==
IMAP_MATCH_YES)

Let me know if you need full backtraces from the core dump.

On 12/17/2009 02:06 PM, David Halik wrote:

> On 12/17/2009 01:07 PM, Timo Sirainen wrote:
>> On Thu, 2009-12-17 at 12:49 -0500, David Halik wrote:
>>
>>> I applied those patches to my 1.2.8 installation before 1.2.9 was
>>> released and that immediately fixed the expunge crash, but the
>>> array_delete bug is still there.
>> Do you also see the "duplicate file entry" before the crash?
>>
>
> Yes, the duplicate file entry is always reported immediately before
> the crash, just as Ralf reported too. You can see it in this example
> pastebin I took from one of our users:
>
> http://pastebin.com/f29c55de5
>
>
>>> maildir:~/Maildir:INDEX=/rci/nqu%h/dovecot:CONTROL=/rci/nqu%h/dovecot
>> Are the index/control files on NFS? Are there multiple different servers
>> accessing mail data?
>>
>
> Correct. All index, control files, amd mail storage are located on NFS
> and there are multiple load balanced servers accessing the NFS data.
> We're currently running with:
>
> mmap_disable = yes
> dotlock_use_excl = yes
> fsync_disable = no
> mail_nfs_storage = yes
> mail_nfs_index = yes
>

--
================================
David Halik
System Administrator
OIT-CSS Rutgers University
dhalik@...
================================

Re: [exim] Exim + Dovecot deliver overquota problems

2009-12-21T07:48:21Z

On Mon, 21 Dec 2009 13:44:42 +0100
Joan <aseques@...> wrote:

> >
> > You need to check user's quota on routing stage, not transport.
> >
> It'd be much better, because I would allow me to mix overquota and
> no-overquota recipients.
> But the problem in my case is that I am using some hashing to
> distribute the users' mailboxes, dovecot can handle this easily
> because it supports some interesting stuff
> (http://wiki.dovecot.org/Variables)

Exim have much more variables and functions http://exim.org/exim-html-4.69/doc/html/spec_html/ch11.html#SECTexpvar, so if you don't use any special dovecot variable data, than it shouldn't be a problem.

> With a perl script I could also do that, I would like only if it's the
> last resort (too much overhead I would think)
> >
Parsing file and counting quota value - is trivial stuff. The main disadvantage of this way is executing external aplication on every RCPT TO command. If you'll decide to use perl consider using option perl_at_start to minimize aplication starting time.

Re: Released Pigeonhole Sieve v0.1.14 and ManageSieve v0.11.10 for Dovecot v1.2.9

2009-12-21T06:05:05Z

Seth Mattinen wrote:
> Stephan Bosch wrote:
>> Seth Mattinen wrote:
>>> Is there any plan to add quota enforcement to managesieve?
>>>
>> Yes, it's on the TODO list.
>>
> Yes, it's been on the TODO for a long time, but how much of a priority
> is it?
>
As a matter of fact, it no longer has a priority, simply because it is
implemented in the tip revision of the mercurial repository (v1.2).

Regards,

Stephan.

Re: Dovecot vs Exim file locking

2009-12-21T00:52:04Z

Hi,

I am trying to deploy large e-mail system but I will use qmail-ldap on Linux
and maildir will be mounted by all backends from Netapp via NFS.

In LDAP, there will be only one mailhost entry. All qmail-ldap backends will
have same name and will run dovecot instance. So, all users can access to
mailbox from any server in the pool. If I distribute users with different
mailhosts and if one mailhost server is down,
the users will not able to access their mailbox until fix the problem or
change mailhost entry with working one.

But I don't know the NFS issues in my planned setup. Do you think that I
will face
same NFS locks/problem(OS based) with Netapp NFS?

Thanks in advance.

On Mon, Dec 21, 2009 at 9:15 AM, Daniel Campos <dcampos@...> wrote:

> Hi Ecuardo,Timo, thanks for your answers!
>
> -----Mensaje original-----
> De: Timo Sirainen [mailto:tss@...]
> Enviado el: viernes, 18 de diciembre de 2009 15:30
> Para: Daniel Campos
> CC: dovecot@...
> Asunto: Re: [Dovecot] Dovecot vs Exim file locking
>
> On Dec 18, 2009, at 8:41 AM, Daniel Campos wrote:
>
> > We're planning to deploy a large e-mail system storing maildirs in a NAS
> > system through NFS. One of the options we're thinking on is using
> > Dovecot+EXIM.
> >
> > As far as I've read in both project's documentation, both services
> implement
> > locking allowing multiple servers to access the same maildirs in order to
> > distribute the service load.
>
> Mail deliveries don't require any locks with maildir. But for Dovecot, be
> sure to read http://wiki.dovecot.org/NFS
>
>
> __________ Informacisn de NOD32, revisisn 4704 (20091220) __________
>
> Este mensaje ha sido analizado con NOD32 antivirus system
> http://www.nod32.com
>
>
>

qpopper to dovecot migration

2009-12-21T00:15:46Z

Heya,

We are in the process of migrating from qpopper to dovecot as POP3 server (and IMAP as well) and we hit the UIDL issue with dovecot. Qpopper uses its own algorithm to create UIDL values and if you set it up to write them down in the mbox file as X-UIDL, then dovecot can use them (pop_uidl_reuse = yes).

But if you don't use that feature from qpopper, than X-UIDLs are missing and there is no way to create the same UIDL values. So, I was wondering if anyone else hit that issue and maybe knows how to address it (writing an extension or something)?

Thanks in advance,

regards, Jernej

Re: Dovecot vs Exim file locking

2009-12-20T23:15:01Z

Hi Ecuardo,Timo, thanks for your answers!

-----Mensaje original-----
De: Timo Sirainen [mailto:tss@...]
Enviado el: viernes, 18 de diciembre de 2009 15:30
Para: Daniel Campos
CC: dovecot@...
Asunto: Re: [Dovecot] Dovecot vs Exim file locking

On Dec 18, 2009, at 8:41 AM, Daniel Campos wrote:

> We're planning to deploy a large e-mail system storing maildirs in a NAS
> system through NFS. One of the options we're thinking on is using
> Dovecot+EXIM.
>
> As far as I've read in both project's documentation, both services
implement
> locking allowing multiple servers to access the same maildirs in order to
> distribute the service load.

Mail deliveries don't require any locks with maildir. But for Dovecot, be
sure to read http://wiki.dovecot.org/NFS

__________ Informacisn de NOD32, revisisn 4704 (20091220) __________

Este mensaje ha sido analizado con NOD32 antivirus system
http://www.nod32.com

Re: Released Pigeonhole Sieve v0.1.14 and ManageSieve v0.11.10 for Dovecot v1.2.9

2009-12-20T01:37:56Z

Stephan Bosch wrote:

> Seth Mattinen wrote:
>> Stephan Bosch wrote:
>>> Hello Dovecot users,
>>>
>>> Due to personal matters I haven't had time to do anything in the last
>>> few weeks. Before that I provided some pre-releases and since nobody
>>> indicated problems with those, I release them definitively now. I hope
>>> the shit storm has blown over, so that I can dedicate more of my time
>>> towards Pigeonhole development.
>>>
>>> The Sieve release involves a large architectural change, but also fixes
>>> quite a few small problems. The ManageSieve release is necessary to
>>> match Sieve API changes.
>>>
>>
>> Is there any plan to add quota enforcement to managesieve?
>>
> Yes, it's on the TODO list.
>

Yes, it's been on the TODO for a long time, but how much of a priority
is it?

~Seth

Re: Released Pigeonhole Sieve v0.1.14 and ManageSieve v0.11.10 for Dovecot v1.2.9

2009-12-20T00:37:01Z

Seth Mattinen wrote:

> Stephan Bosch wrote:
>> Hello Dovecot users,
>>
>> Due to personal matters I haven't had time to do anything in the last
>> few weeks. Before that I provided some pre-releases and since nobody
>> indicated problems with those, I release them definitively now. I hope
>> the shit storm has blown over, so that I can dedicate more of my time
>> towards Pigeonhole development.
>>
>> The Sieve release involves a large architectural change, but also fixes
>> quite a few small problems. The ManageSieve release is necessary to
>> match Sieve API changes.
>>
>
> Is there any plan to add quota enforcement to managesieve?
>

Yes, it's on the TODO list.

Regards,

--
Stephan Bosch
stephan@...

Re: Dovecot v2.0 wiki

2009-12-19T22:01:40Z

On 12/18/2009 12:44 AM Timo Sirainen wrote:
>
> The main reason for wiki2 is to be able to describe Dovecot v2.0's
> actual behavior everywhere and get rid of all the old v1.x specific
> settings. The wiki1 is already annoyingly bloated and confusing with
> information about v1.0 and then v1.1 and maybe even how it's still
> different in v1.2..

Does this mean, all the mentions of v1.x could be removed when a page is
updated?
Some v1.x specific pages (e.g. /LDA/Sieve/CMU) can be deleted?

The result would be a clearly wiki for v2.0

Regards,
Pascal
--
The trapper recommends today: c01dcofe.0935406@...

Re: deliver panics when handling mails bigger than some kByte

2009-12-19T10:31:33Z

On Tue, Dec 15, 2009 at 03:04:07PM -0500, Timo Sirainen wrote:

> On Mon, 2009-12-14 at 20:55 +0100, Leon Meßner wrote:
> > Hi,
> >
> > i've just upgraded to dovecot-1.2.8 (from 1.2.4) and do now get the
> > following errors when deliver gets hands on mails with some attachments.
> >
> > # tail -n 1 /var/log/messages
> > Dec 14 19:00:36 mail3 dovecot: deliver(user): Panic: file istream.c:
> > line 96 (i_stream_read): assertion failed: (stream->eof)
>
> Can you reproduce this easily? Can you get it to dump core?

Happens everytime one tries to send mails which are slightly bigger
(around 100k).

> kern.corefile and kern.sugid_coredump sysctls probably help. I'd like to
> get at least gdb backtrace and also a few other variables..
> http://dovecot.org/bugreport.html

Here's the backtrace and the output of `dovecot -n`. This is still 1.2.8,
I will upgrade as soon as the new FreeBSD port is out there. The
configuration is basically postfix with deliver as LDA and dovecot-sieve
inside a FreeBSD 7.2 jail and maildir's on NFS.

thanks and happy holidays to everyone,
Leon

18:19_root@mail3:/root# gdb /usr/local/libexec/dovecot/deliver
deliver.core
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you
are
welcome to change it and/or distribute copies of it under certain
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for
details.
This GDB was configured as "amd64-marcel-freebsd"...(no debugging
symbols found)...
Core was generated by `deliver'.
Program terminated with signal 6, Aborted.
Reading symbols from /usr/local/lib/libiconv.so.3...done.
Loaded symbols for /usr/local/lib/libiconv.so.3
Reading symbols from /usr/lib/librt.so.1...done.
Loaded symbols for /usr/lib/librt.so.1
Reading symbols from /lib/libc.so.7...done.
Loaded symbols for /lib/libc.so.7
Reading symbols from
/usr/local/lib/dovecot/lda/lib90_sieve_plugin.so...done.
Loaded symbols for /usr/local/lib/dovecot/lda/lib90_sieve_plugin.so
Reading symbols from /libexec/ld-elf.so.1...done.
Loaded symbols for /libexec/ld-elf.so.1
#0 0x0000000800b2fa1c in kill () from /lib/libc.so.7
(gdb) bt full
#0 0x0000000800b2fa1c in kill () from /lib/libc.so.7
No symbol table info available.
#1 0x0000000800b2e83b in abort () from /lib/libc.so.7
No symbol table info available.
#2 0x00000000004c7795 in failure_exit ()
No symbol table info available.
#3 0x00000000004c8147 in i_syslog_fatal_handler ()
No symbol table info available.
#4 0x00000000004c7a7a in i_panic ()
No symbol table info available.
#5 0x00000000004ce84c in i_stream_read ()
No symbol table info available.
#6 0x00000000004d1c52 in i_stream_create_fd ()
No symbol table info available.
#7 0x00000000004ce778 in i_stream_read ()
No symbol table info available.
#8 0x00000000004d0925 in i_stream_create_concat ()
No symbol table info available.
#9 0x00000000004d0c2d in i_stream_create_concat ()
No symbol table info available.
#10 0x00000000004ce778 in i_stream_read ()
No symbol table info available.
#11 0x00000000004d35fa in i_stream_create_seekable ()
No symbol table info available.
#12 0x00000000004ce778 in i_stream_read ()
No symbol table info available.
#13 0x00000000004cf3cd in i_stream_read_data ()
No symbol table info available.
#14 0x00000000004bd6df in message_id_get_next ()
No symbol table info available.
#15 0x00000000004bdee9 in message_id_get_next ()
No symbol table info available.
#16 0x00000000004bf018 in message_parser_parse_next_block ()
No symbol table info available.
#17 0x000000000045eb1d in index_mail_cache_parse_continue ()
No symbol table info available.
#18 0x00000000004442ac in maildir_save_continue ()
No symbol table info available.
#19 0x00000000004787a3 in mailbox_save_continue ()
No symbol table info available.
#20 0x0000000000471105 in mail_storage_copy ()
No symbol table info available.
#21 0x0000000000441f6c in maildir_copy ()
No symbol table info available.
#22 0x0000000000478871 in mailbox_copy ()
No symbol table info available.
#23 0x0000000800e2f881 in act_store_execute () from
/usr/local/lib/dovecot/lda/lib90_sieve_plugin.so
No symbol table info available.
#24 0x0000000800e29707 in _sieve_result_implicit_keep () from
/usr/local/lib/dovecot/lda/lib90_sieve_plugin.so
No symbol table info available.
#25 0x0000000800e29bff in sieve_result_execute () from
/usr/local/lib/dovecot/lda/lib90_sieve_plugin.so
No symbol table info available.
#26 0x0000000800e35ac7 in sieve_execute () from
/usr/local/lib/dovecot/lda/lib90_sieve_plugin.so
No symbol table info available.
#27 0x0000000800e1b58e in lda_sieve_deliver_mail () from
/usr/local/lib/dovecot/lda/lib90_sieve_plugin.so
No symbol table info available.
#28 0x000000000041b247 in main ()
No symbol table info available.

18:23_root@mail3:/root# dovecot -n
# 1.2.8: /usr/local/etc/dovecot.conf
# OS: FreeBSD 7.2-STABLE amd64
log_path: /var/log/dovecot.log
protocols: imaps pop3s managesieve
listen: mail3.physik.tu-berlin.de
ssl_cert_file: /etc/private/mail3.physik.tu-berlin.de.pem
ssl_key_file: /etc/private/physik.tu-berlin.de_privatekey.pem
login_dir: /var/run/dovecot/login
login_executable(default): /usr/local/libexec/dovecot/imap-login
login_executable(imap): /usr/local/libexec/dovecot/imap-login
login_executable(pop3): /usr/local/libexec/dovecot/pop3-login
login_executable(managesieve):
/usr/local/libexec/dovecot/managesieve-login
login_processes_count: 6
login_max_processes_count: 256
verbose_proctitle: yes
first_valid_uid: 200
first_valid_gid: 300
mail_privileged_group: mail
mail_location: maildir:~/maildir
mmap_disable: yes
mail_nfs_storage: yes
mail_nfs_index: yes
mail_executable(default): /usr/local/libexec/dovecot/imap
mail_executable(imap): /usr/local/libexec/dovecot/imap
mail_executable(pop3): /usr/local/libexec/dovecot/pop3
mail_executable(managesieve): /usr/local/libexec/dovecot/managesieve
mail_plugin_dir(default): /usr/local/lib/dovecot/imap
mail_plugin_dir(imap): /usr/local/lib/dovecot/imap
mail_plugin_dir(pop3): /usr/local/lib/dovecot/pop3
mail_plugin_dir(managesieve): /usr/local/lib/dovecot/managesieve
imap_client_workarounds(default): delay-newmail netscape-eoh
tb-extra-mailbox-sep
imap_client_workarounds(imap): delay-newmail netscape-eoh
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):
namespace:
type: private
separator: /
inbox: yes
list: yes
subscriptions: yes
namespace:
type: private
separator: /
prefix: mail/
location: mbox:~/mail
list: yes
subscriptions: yes
lda:
postmaster_address: postmaster@...
log_path:
info_log_path:
mail_plugins: sieve
quota_full_tempfail: yes
sendmail_path: /usr/sbin/sendmail
auth default:
mechanisms: gssapi plain login
username_format: %Lu
krb5_keytab: /etc/mail3.krb5.keytab
gssapi_hostname: mail3.physik-pool.tu-berlin.de
worker_max_count: 120
passdb:
driver: pam
args: session=yes failure_show_msg=yes max_requests=100 dovecot
userdb:
driver: passwd
args: blocking=yes
socket:
type: listen
client:
path: /var/run/dovecot/auth-client
mode: 432
master:
path: /var/run/dovecot/auth-master
mode: 384
plugin:
sieve: ~/.dovecot.sieve
sieve_dir: ~/.sieve

attachment0 (202 bytes) Download Attachment

Re: Released Pigeonhole Sieve v0.1.14 and ManageSieve v0.11.10 for Dovecot v1.2.9

2009-12-19T09:30:37Z

Stephan Bosch wrote:

> Hello Dovecot users,
>
> Due to personal matters I haven't had time to do anything in the last
> few weeks. Before that I provided some pre-releases and since nobody
> indicated problems with those, I release them definitively now. I hope
> the shit storm has blown over, so that I can dedicate more of my time
> towards Pigeonhole development.
>
> The Sieve release involves a large architectural change, but also fixes
> quite a few small problems. The ManageSieve release is necessary to
> match Sieve API changes.
>

Is there any plan to add quota enforcement to managesieve?

~Seth

trouble with expire

2009-12-19T09:21:44Z

we've got the expire plugin configured, and it's properly inserting rows
to the db. But something's slightly wrong with runing the actual
expire-tool(.sh) job. It seems to want to find the maildirs in a directory
inside our maildirs called Maildir (which we don't have.) It's no biggie
if we need to just wait for v2 to get expire working ;)
::::

# /usr/local/sbin/dovecot --exec-mail ext /usr/local/libexec/dovecot/expire-tool.sh --test

Info: Loading modules from directory: /usr/local/lib/dovecot/imap
Info: Module loaded: /usr/local/lib/dovecot/imap/lib10_quota_plugin.so
Info: Module loaded: /usr/local/lib/dovecot/imap/lib20_expire_plugin.so
Info: Quota root: name=user backend=dict args=:proxy::quotadict
Info: Quota warning: bytes=0 (95%) messages=0
command=/usr/local/ee/quota-warning.sh 95
Info: Quota warning: bytes=0 (80%) messages=0
command=/usr/local/ee/quota-warning.sh 80
Info: expire: pattern=*.Trash type=expunge secs=86400
Info: expire: pattern=*.Spam type=expunge secs=86400
Info: expire: pattern=*.Virus type=expunge secs=86400
Info: auth input: home=/home/npomail/virt.monopod.net/a@.../
Info: auth input: uid=1003
Info: auth input: gid=1003
Info: auth input:
mail=maildir:/home/npomail/virt.monopod.net/a@.../
Info: auth input: quota_rule=*:storage=1024000000B
Info: auth input:
sieve=/home/npomail/virt.monopod.net/a@.../sieve-filterfile
Info: auth input:
sieve_dir=/home/npomail/virt.monopod.net/a@.../
Info: dict quota: user=a@..., uri=proxy::quotadict,
noenforcing=0
Info: Namespace: type=private, prefix=INBOX., sep=., inbox=yes, hidden=no,
list=yes, subscriptions=yes
Info: cydir: mailbox location not given
Info: cydir: Couldn't create mail storage : Root mail directory not given
Info: dbox: mailbox location not given
Info: dbox: Couldn't create mail storage : Root mail directory not given
Info: maildir:
access(/home/npomail/virt.monopod.net/a@...//Maildir, rwx):
failed: No such file or directory
Info: maildir: couldn't find root dir
Info: maildir: Couldn't create mail storage : Root mail directory not
given
Info: mbox: root:
access(/home/npomail/virt.monopod.net/a@...//mail, rwx)
failed: No such file or directory
Info: mbox: root:
access(/home/npomail/virt.monopod.net/a@...//Mail, rwx)
failed: No such file or directory
Info: mbox: checking if we are chrooted:
Info: mbox autodetect: data=
Info: mbox autodetect: has .imap/: stat(/.imap) failed: No such file or
directory
Info: mbox autodetect: has inbox: stat(/inbox) failed: No such file or
directory
Info: mbox autodetect: has mbox: stat(/mbox) failed: No such file or
directory
Info: mbox: root mail directory not found
Info: mbox: Couldn't create mail storage : Autodetection failed
Info: raw: mailbox location not given
Info: raw: Couldn't create mail storage : Root mail directory not given
Info: shared: Couldn't create mail storage : Shared mailbox location not
prefixed with driver
Error: Namespace 'INBOX.': Mail storage autodetection failed with
home=/home/npomail/virt.monopod.net/a@.../
Info: User lookup failed: a@...
Info: a@.../INBOX.Trash: stop, expire time in future: Sat Dec
19 19:12:43 2009

Re: "Filename keeps changing" issue

2009-12-19T04:19:17Z

Le 07/12/2009 13:42, Steffen Kaiser a écrit :
> [...]
> If so, I would:
>
> a) check for dangling symlinks,
> b) check for funny characters in the name ".Travail.Linux.Arch Linux",
> e.g. line break, tab, ...
> c) umount / mount the file system if remote, to reset the internal cache
> d) make a file system check
> [...]
Thanks for your help, a filesystem check solved the problem.

Paul

Released Pigeonhole Sieve v0.1.14 and ManageSieve v0.11.10 for Dovecot v1.2.9

2009-12-19T03:19:38Z

Hello Dovecot users,

Due to personal matters I haven't had time to do anything in the last
few weeks. Before that I provided some pre-releases and since nobody
indicated problems with those, I release them definitively now. I hope
the shit storm has blown over, so that I can dedicate more of my time
towards Pigeonhole development.

The Sieve release involves a large architectural change, but also fixes
quite a few small problems. The ManageSieve release is necessary to
match Sieve API changes.

Changelog Sieve v0.1.14:

* Made the imposed limits on the number of redirects and the number
of actions configurable. The settings are called sieve_max_actions
and sieve_max_redirects.
* Did a major rework of extension handling, making sure that no global
state is maintained. This change was triggered by problems that
global state info would cause for Dovecot v2.0, but it is also
important for v1.2 as it significantly cleans up the library
implementation.
+ Made LDA Sieve plugin recognize the deliver_log_format setting.
+ Message headers produced from user-supplied data are now
RFC2047-encoded if necessary for outgoing messages. This is for
example important for the :subject argument of the vacation action.
+ Added support for the $text$ substitution in the deprecated notify
extension.
+ The subaddress extension now also accepts recipient_delimiter
setting as an alias for sieve_subaddress_sep setting. This
anticipates the recipient_delimiter setting in v2.0.
- Fixed logging of mailbox names. It logged the converted mUTF7
version in stead of the original UTF8 version supplied by the user.
- Fixed a minor memory leak in the multiscript support.
- Fixed a bug in the recompilation of Sieve scripts. Made sure that
scripts are only recompiled when the script file - or the symlink
pointing to it - is strictly newer.

Changelog ManageSieve v0.11.10:

* This release contains adjustments to match changes in the Sieve API.
This means that this release will only compile against Pigeonhole
Sieve v0.1.14.
- Fixed compilation of ManageSieve against CMUSieve.

The releases are available as follows:

Sieve:

http://www.rename-it.nl/dovecot/1.2/dovecot-1.2-sieve-0.1.14.tar.gz
http://www.rename-it.nl/dovecot/1.2/dovecot-1.2-sieve-0.1.14.tar.gz.sig

ManageSieve (package + patch):

http://www.rename-it.nl/dovecot/1.2/dovecot-1.2-managesieve-0.11.10.tar.gz
http://www.rename-it.nl/dovecot/1.2/dovecot-1.2-managesieve-0.11.10.tar.gz.sig

http://www.rename-it.nl/dovecot/1.2/dovecot-1.2.9-managesieve-0.11.10.diff.gz
http://www.rename-it.nl/dovecot/1.2/dovecot-1.2.9-managesieve-0.11.10.diff.gz.sig

Refer to http://pigeonhole.dovecot.org for more information. Have fun
testing the new releases and don't hesitate to notify me when there are
problems.

Releases for Dovecot v2.0 are still under development...

Regards,

--
Stephan Bosch
stephan@...

Re: dovecot: pipe() failed: Too many open files

2009-12-18T15:58:33Z

On Fre, 2009-12-18 at 18:32 -0500, Charles Marcus wrote:
> On 12/18/2009, JW (jw@...) wrote:
> > I'm sorry, I forgot to specify that I was using Debian Linux:
>
> You also forgot the bare neceesities, like dovecot version, dovecot -n
> output and log entries exhibiting the problem.
And for the current case looking into /proc/$(pidof dovecot)/fd should
show all open fds (and $(ls -1 /proc/$(pidof dovecot)/fd | wc -l) should
be somewhat near the limit).

> I'm actually amazed at how many people post on support lists and say
> 'Help! Its not working!! What did I do wrong?!' - do they really expect
> meaningful help?
>
> Even more amazing, on this list Timo can often divine the answer anyway...
He has probably am extremely good crystal ball;-)

Bernd
--
mobil: +43 664 4416156 http://bernd.petrovitsch.priv.at/
Linux Software Entwicklung, Beratung und Dienstleistungen

Re: Release candidates for Sieve v0.1.14 and ManageSieve v0.11.10 for Dovecot v1.2.8

2009-12-18T15:40:50Z

-------- Original-Nachricht --------
> Datum: Fri, 18 Dec 2009 22:31:02 +0100
> Von: Stephan Bosch <stephan@...>
> An: Dovecot Mailing List <dovecot@...>
> Betreff: Re: [Dovecot] Release candidates for Sieve v0.1.14 and ManageSieve v0.11.10 for Dovecot v1.2.8

> Steve wrote:
>
> >> Well, I got sued, so that took some of my attention.
> >>
> > How did it end for you? I hope, I wish it ended good for you?
> >
> Yes, for some reason the lawsuit was withdrawn the day before, probably
> due to our written defense. I don't know. At least it's gone for now.
>
I don't know about what it was but I hope they don't try again. Just continue your normal life and don't care about them. My daddy used to say (he passed away this year in February): Dear son. Don't touch shit. It will only stink more!

So don't care about the ones that have tried to sue you. The less you care about them the better for you (I guess).

> Regards,
>
> Stephan.
>
Steve
--
Jetzt kostenlos herunterladen: Internet Explorer 8 und Mozilla Firefox 3.5 -
sicherer, schneller und einfacher! http://portal.gmx.net/de/go/atbrowser

Re: dovecot: pipe() failed: Too many open files

2009-12-18T15:32:32Z

On 12/18/2009, JW (jw@...) wrote:
> I'm sorry, I forgot to specify that I was using Debian Linux:

You also forgot the bare neceesities, like dovecot version, dovecot -n
output and log entries exhibiting the problem.

I'm actually amazed at how many people post on support lists and say
'Help! Its not working!! What did I do wrong?!' - do they really expect
meaningful help?

Even more amazing, on this list Timo can often divine the answer anyway...

Re: dovecot: pipe() failed: Too many open files

2009-12-18T15:17:41Z

On Dec 18, 2009, at 6:12 PM, Mario Antonio wrote:

> JW wrote:You could try:
> /etc/security/limits.conf
>
>
>
> your_dovecot_user soft nofile 524288
> your_dovecot_user hard nofile 524288

I think these are read by PAM when user logs in. Dovecot never uses them. I'm not sure if even setting root's limits here will affect software started by init.d scripts at system startup.

Re: expire db(s)?

2009-12-18T15:15:42Z

On Dec 18, 2009, at 5:57 PM, ben@... wrote:

> with two separate dovecot/backend servers accessing one central mysql server, will it be ok to have them both use the same expires table? Or will that confuse the actual
> dovecot --exec-mail ext /usr/local/libexec/dovecot/expire-tool.sh
> cronjob since some of the entries mailboxes won't exist locally?

It'll break. If userdb lookup fails, expire-tool thinks that the user no longer exists and deletes the row from database. If it succeeds but the mail directory doesn't exist, it'll think the mailbox was deleted and deletes the row from database.

Re: dovecot: pipe() failed: Too many open files

2009-12-18T15:12:59Z

JW wrote:

> On Friday 18 December 2009 16:00:48 Timo Sirainen wrote:
>
>> On Dec 18, 2009, at 4:47 PM, JW wrote:
>>
>>> I've researched this problem a number of times, usually I see suggestions
>>> to increase ulimit.
>>>
>>> I've done this a number of times, all the way up to:
>>>
>>> ulimit -n 8192
>>>
>>> I've put that in the init script right above the daemon start line.
>>>
>> What exactly is the "daemon start line"
>>
>
> I'm sorry, I forgot to specify that I was using Debian Linux:
>
>
> case "$1" in
> start)
> if grep protocols /etc/dovecot/dovecot.conf | sed 's/#.*$//' | tr -d '"' |
> \
> egrep -q '[^#]*(\bpop3s?\b|\bimaps?\b)';
> then
> if [ -x /usr/lib/dovecot/imap-login -a -x /usr/lib/dovecot/imap ] \
> || [ -x /usr/lib/dovecot/pop3-login -a -x /usr/lib/dovecot/pop3 ];
> then
> echo -n "Starting $DESC: $NAME"
> ulimit -n 8192
> start-stop-daemon --start --quiet --oknodo --exec $DAEMON
> echo "."
> fi
> fi
> ;;
> stop)
> echo -n "Stopping $DESC: $NAME "
> start-stop-daemon --stop --quiet --oknodo --exec $DAEMON
> echo "."
> ;;
>
>
>
>> ? Many Linux distros override ulimit
>> in their internal scripts. If you're using Linux, you could check if
>> dovecot process really has 8192 limit:
>>
>> cat /proc/`pidof dovecot`/limits | grep 'Max open'
>>
>
>
> I've seen this suggestion on the web a few times, but there's no such
> directory, /proc/`pidof dovecot`/limits or /proc/*/limits for that matter
>
> pidof dovecot
>
> shows the pid for:
>
> /usr/sbin/dovecot
>
> I've tried "grep -i max" and grep -i open in the /proc/$pid/* directory for
> every pid of every dovecot process on the system, none of the files in there
> contain either word.
>
> mail:/var/log# ps auxw | grep dove
> root 23299 0.0 0.0 1948 648 ? Ss 00:41
> 0:07 /usr/sbin/dovecot
> root 23300 0.0 0.2 8752 2700 ? S 00:41 0:05 dovecot-auth
>
> mail:/var/log# ls /proc/23299
> attr cmdline cwd exe maps mounts oom_adj root stat status
> wchan
> auxv cpuset environ fd mem mountstats oom_score smaps statm task
>
>
> Is there a different place I should put the ulimit?
>
> JW
>
>

You could try:
/etc/security/limits.conf

your_dovecot_user soft nofile 524288
your_dovecot_user hard nofile 524288

Not sure if instead of your_dovecot_user, you should increase the limits
for the root user .... ??

Regards,
Mario Antonio

Re: dovecot: pipe() failed: Too many open files

2009-12-18T15:10:38Z

On Dec 18, 2009, at 5:46 PM, JW wrote:

> I'm sorry, I forgot to specify that I was using Debian Linux:
>
>
> echo -n "Starting $DESC: $NAME"
> ulimit -n 8192
> start-stop-daemon --start --quiet --oknodo --exec $DAEMON

Well, this seemed to work in Debian unstable.. So maybe the problem is that something just causes Dovecot to eat all available file descriptors. When it happens again you should get the lsof output of dovecot and save it.

Also you never mentioned your Dovecot version. It's possible it's already been fixed in recent versions.

>> ? Many Linux distros override ulimit
>> in their internal scripts. If you're using Linux, you could check if
>> dovecot process really has 8192 limit:
>>
>> cat /proc/`pidof dovecot`/limits | grep 'Max open'
>
>
> I've seen this suggestion on the web a few times, but there's no such
> directory, /proc/`pidof dovecot`/limits or /proc/*/limits for that matter

I guess you've old enough kernel that it doesn't support it.

expire db(s)?

2009-12-18T14:57:08Z

with two separate dovecot/backend servers accessing one central mysql
server, will it be ok to have them both use the same expires table? Or
will that confuse the actual
dovecot --exec-mail ext /usr/local/libexec/dovecot/expire-tool.sh
cronjob since some of the entries mailboxes won't exist locally?

Ben

Re: dovecot: pipe() failed: Too many open files

2009-12-18T14:46:53Z

On Friday 18 December 2009 16:00:48 Timo Sirainen wrote:

> On Dec 18, 2009, at 4:47 PM, JW wrote:
> > I've researched this problem a number of times, usually I see suggestions
> > to increase ulimit.
> >
> > I've done this a number of times, all the way up to:
> >
> > ulimit -n 8192
> >
> > I've put that in the init script right above the daemon start line.
>
> What exactly is the "daemon start line"

I'm sorry, I forgot to specify that I was using Debian Linux:

case "$1" in
start)
if grep protocols /etc/dovecot/dovecot.conf | sed 's/#.*$//' | tr -d '"' |
\
egrep -q '[^#]*(\bpop3s?\b|\bimaps?\b)';
then
if [ -x /usr/lib/dovecot/imap-login -a -x /usr/lib/dovecot/imap ] \
|| [ -x /usr/lib/dovecot/pop3-login -a -x /usr/lib/dovecot/pop3 ];
then
echo -n "Starting $DESC: $NAME"
ulimit -n 8192
start-stop-daemon --start --quiet --oknodo --exec $DAEMON
echo "."
fi
fi
;;
stop)
echo -n "Stopping $DESC: $NAME "
start-stop-daemon --stop --quiet --oknodo --exec $DAEMON
echo "."
;;

> ? Many Linux distros override ulimit
> in their internal scripts. If you're using Linux, you could check if
> dovecot process really has 8192 limit:
>
> cat /proc/`pidof dovecot`/limits | grep 'Max open'

I've seen this suggestion on the web a few times, but there's no such
directory, /proc/`pidof dovecot`/limits or /proc/*/limits for that matter

pidof dovecot

shows the pid for:

/usr/sbin/dovecot

I've tried "grep -i max" and grep -i open in the /proc/$pid/* directory for
every pid of every dovecot process on the system, none of the files in there
contain either word.

mail:/var/log# ps auxw | grep dove
root 23299 0.0 0.0 1948 648 ? Ss 00:41
0:07 /usr/sbin/dovecot
root 23300 0.0 0.2 8752 2700 ? S 00:41 0:05 dovecot-auth

mail:/var/log# ls /proc/23299
attr cmdline cwd exe maps mounts oom_adj root stat status
wchan
auxv cpuset environ fd mem mountstats oom_score smaps statm task

Is there a different place I should put the ulimit?

JW

--

----------------------
System Administrator - Cedar Creek Software
http://www.cedarcreeksoftware.com

Re: dovecot: pipe() failed: Too many open files

2009-12-18T14:00:48Z

On Dec 18, 2009, at 4:47 PM, JW wrote:
> I've researched this problem a number of times, usually I see suggestions to
> increase ulimit.
>
> I've done this a number of times, all the way up to:
>
> ulimit -n 8192
>
> I've put that in the init script right above the daemon start line.

What exactly is the "daemon start line"? Many Linux distros override ulimit in their internal scripts. If you're using Linux, you could check if dovecot process really has 8192 limit:

cat /proc/`pidof dovecot`/limits | grep 'Max open'

Re: Maildir on NFS - attribute caching question

2009-12-18T13:58:18Z

On Dec 18, 2009, at 4:42 PM, Brandon Davidson wrote:

> The Wiki article on NFS states that 1.1 and newer will flush attribute
> caches if necessary with mail_nfs_storage=yes. We're running 1.2.8 with
> that set, as well as mail_nfs_index=yes, mmap_disable=yes and
> fsync_disable=no. We have a pool of POP/IMAP and SMTP machines that are
> accessing the maildirs, and can't guarantee any sort of user session
> affinity to a particular host.
>
> We also mount our NFS shares with 'noac', which is what I'm writing to
> ask about. I'd like to stop doing that for performance reasons. Do you
> see any issues with taking that out of the mount options, given our
> environment?

Dovecot's NFS cache flushing doesn't work perfectly. But I think some/most/all of those conditions exist also when attribute cache is disabled. Or maybe not. I can't really remember anymore what I read in the kernel code :) And that was only for Linux and FreeBSD, don't know about other OSes. The issue was about directory entry caching, I don't remember if attribute cache also disabled it.

Anyway.. I think you should just try enabling attribute cache and if things start breaking more, disable it again.

dovecot: pipe() failed: Too many open files

2009-12-18T13:47:14Z

In the past few months we've been having increasing problems with dovecot
timing out pop3 logins.

As best I can tell it gets to the point where it won't accept any new pop3
logins.

The error in the mail log is:

dovecot: pipe() failed: Too many open files

I've researched this problem a number of times, usually I see suggestions to
increase ulimit.

I've done this a number of times, all the way up to:

ulimit -n 8192

I've put that in the init script right above the daemon start line.

So far it hasn't helped.

In addition, when looking at lsof, it doesn't seem like we're anywhere near
the actual limit. for example, last time dovecot only had 1032 files open.

Does anyone have any idea what could be causing the error? Or what else I can
try to figure this out?

Thank you,

JW

--

----------------------
System Administrator - Cedar Creek Software
http://www.cedarcreeksoftware.com

Maildir on NFS - attribute caching question

2009-12-18T13:42:44Z

Hi Timo,

We've been running Dovecot with Maildir on NFS for quite a while - since
back in the 1.0 days I believe. I'm somewhat new here. Anyway...

The Wiki article on NFS states that 1.1 and newer will flush attribute
caches if necessary with mail_nfs_storage=yes. We're running 1.2.8 with
that set, as well as mail_nfs_index=yes, mmap_disable=yes and
fsync_disable=no. We have a pool of POP/IMAP and SMTP machines that are
accessing the maildirs, and can't guarantee any sort of user session
affinity to a particular host.

We also mount our NFS shares with 'noac', which is what I'm writing to
ask about. I'd like to stop doing that for performance reasons. Do you
see any issues with taking that out of the mount options, given our
environment?

Thanks,

-Brad

Re: Release candidates for Sieve v0.1.14 and ManageSieve v0.11.10 for Dovecot v1.2.8

2009-12-18T13:31:02Z

Steve wrote:

>> Well, I got sued, so that took some of my attention.
>>
> How did it end for you? I hope, I wish it ended good for you?
>
Yes, for some reason the lawsuit was withdrawn the day before, probably
due to our written defense. I don't know. At least it's gone for now.

Regards,

Stephan.

Re: Release candidates for Sieve v0.1.14 and ManageSieve v0.11.10 for Dovecot v1.2.8

2009-12-18T13:26:13Z

-------- Original-Nachricht --------
> Datum: Fri, 18 Dec 2009 22:21:21 +0100
> Von: Stephan Bosch <stephan@...>
> An: Bruce Bodger <bbodger@...>
> CC: Dovecot Mailing List <dovecot@...>
> Betreff: Re: [Dovecot] Release candidates for Sieve v0.1.14 and ManageSieve v0.11.10 for Dovecot v1.2.8

> Bruce Bodger wrote:
> >
> > On Nov 25, 2009, at 4:51 PM, Stephan Bosch wrote:
> >
> >> Hello Dovecot users,
> >>
> >> I am getting closer to new releases for Sieve and ManageSieve for
> >> Dovecot v1.2.8. However, the release for Sieve includes a large
> >> restructuring of the sources to improve extension handling and to
> >> remove global state. That is why I first provide a few pre-releases
> >> for you to check first:
> >>
> >> Sieve
> >>
> >> http://www.rename-it.nl/dovecot/1.2/dovecot-1.2-sieve-0.1.14pre.tar.gz
> >>
> http://www.rename-it.nl/dovecot/1.2/dovecot-1.2-sieve-0.1.14pre.tar.gz.sig
> >>
> >
> >> Feel free to test these release candidates and please notify me when
> >> you incur any problems. The real releases will follow this weekend.
> >
> > Stephen,
> >
> > How are you doing regarding the real releases, specifically
> > dovecot-1.2-sieve-0.1.14 ? The pre release is/was a bit confusing as
> > it contains a dovecot-1.2-sieve-0.1.13 folder within the
> > dovecot-1.2-sieve-0.1.14pre.tar.gz archive.
> >
> Well, I got sued, so that took some of my attention.
>

How did it end for you? I hope, I wish it ended good for you?

> I'll tend to this
> tomorrow morning.
>
> Regards,
>
> Stephan.
>
Steve
--
Jetzt kostenlos herunterladen: Internet Explorer 8 und Mozilla Firefox 3.5 -
sicherer, schneller und einfacher! http://portal.gmx.net/de/go/chbrowser