[Dovecot] 2.0.12 Coredump under Solaris 10

2011-04-27 Thread Denny Schierz
hi,

I've installed a testversion from 2.0.12 and getting coredumps after
login via IMAP/POP3. I don't know, if it is a simple config error or
something else.

==
dovecot: [ID 583609 local7.error] master: Error: service(imap): child
29333 killed with signal 11 (core dumped)

[ID 583609 local7.error] master: Error: service(imap): child 29335
killed with signal 11 (core dumped)
==

my configure:

CPPFLAGS="-D_POSIX_PTHREAD_SEMANTICS"  LDFLAGS="-L/opt/csw/lib
-L/usr/lib -R/opt/csw/lib/"  ./configure
--prefix=/usr/local/dovecot/2.0.12-testinstanz --with-ssl=openssl
--with-rundir=/var/run/dovecot-testinstanz
--with-storages=maildir,mbox,sdbox,mdbox  --with-ldap=yes
--sysconfdir=/usr/local/dovecot/etc-testinstanz


2.0.9 works.

The gdb coredump shows:

gdb ../../dovecot2-testinstanz/libexec/dovecot/imap 
/var/run/dovecot-testinstanz/core 

GNU gdb 6.6
Copyright (C) 2006 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 "i386-pc-solaris2.8"...
Reading symbols
from 
/usr/local/dovecot/2.0.12-testinstanz/lib/dovecot/libdovecot-storage.so.0...done.
Loaded symbols
for /usr/local/dovecot/2.0.12-testinstanz/lib/dovecot/libdovecot-storage.so.0
Reading symbols
from /usr/local/dovecot/2.0.12-testinstanz/lib/dovecot/libdovecot.so.0...done.
Loaded symbols
for /usr/local/dovecot/2.0.12-testinstanz/lib/dovecot/libdovecot.so.0
Reading symbols from /opt/csw/lib/libiconv.so.2...done.
Loaded symbols for /opt/csw/lib//libiconv.so.2
Reading symbols from /lib/libnsl.so.1...done.
Loaded symbols for /lib/libnsl.so.1
Reading symbols from /lib/libsocket.so.1...done.
Loaded symbols for /lib/libsocket.so.1
Reading symbols from /lib/librt.so.1...done.
Loaded symbols for /lib/librt.so.1
Reading symbols from /lib/libsendfile.so.1...done.
Loaded symbols for /lib/libsendfile.so.1
Reading symbols from /lib/libc.so.1...done.
Loaded symbols for /lib/libc.so.1
Reading symbols from /usr/sfw/lib/libgcc_s.so.1...done.
Loaded symbols for /usr/sfw/lib/libgcc_s.so.1
Reading symbols from /lib/libaio.so.1...done.
Loaded symbols for /lib/libaio.so.1
Reading symbols from /lib/libmd.so.1...done.
Loaded symbols for /lib/libmd.so.1
Reading symbols
from 
/usr/local/dovecot/2.0.12-testinstanz/lib/dovecot/lib01_acl_plugin.so...done.
Loaded symbols
for /usr/local/dovecot/dovecot2-testinstanz/lib/dovecot//lib01_acl_plugin.so
Reading symbols from /lib/libscf.so.1...done.
Loaded symbols for /lib/libscf.so.1
Reading symbols from /lib/libdoor.so.1...done.
Loaded symbols for /lib/libdoor.so.1
Reading symbols from /lib/libuutil.so.1...done.
Loaded symbols for /lib/libuutil.so.1
Reading symbols from /lib/libgen.so.1...done.
Loaded symbols for /lib/libgen.so.1
Reading symbols from /lib/libmp.so.2...done.
Loaded symbols for /lib/libmp.so.2
Reading symbols
from 
/usr/local/dovecot/2.0.12-testinstanz/lib/dovecot/lib02_imap_acl_plugin.so...done.
Loaded symbols
for 
/usr/local/dovecot/dovecot2-testinstanz/lib/dovecot//lib02_imap_acl_plugin.so
Reading symbols
from 
/usr/local/dovecot/2.0.12-testinstanz/lib/dovecot/lib10_quota_plugin.so...done.
Loaded symbols
for /usr/local/dovecot/dovecot2-testinstanz/lib/dovecot//lib10_quota_plugin.so
Reading symbols
from 
/usr/local/dovecot/2.0.12-testinstanz/lib/dovecot/lib11_imap_quota_plugin.so...done.
Loaded symbols
for 
/usr/local/dovecot/dovecot2-testinstanz/lib/dovecot//lib11_imap_quota_plugin.so
Reading symbols
from 
/usr/local/dovecot/2.0.12-testinstanz/lib/dovecot/lib11_trash_plugin.so...done.
Loaded symbols
for /usr/local/dovecot/dovecot2-testinstanz/lib/dovecot//lib11_trash_plugin.so
Reading symbols
from 
/usr/local/dovecot/2.0.12-testinstanz/lib/dovecot/lib15_notify_plugin.so...done.
Loaded symbols
for /usr/local/dovecot/dovecot2-testinstanz/lib/dovecot//lib15_notify_plugin.so
Reading symbols
from 
/usr/local/dovecot/2.0.12-testinstanz/lib/dovecot/lib20_autocreate_plugin.so...done.
Loaded symbols
for 
/usr/local/dovecot/dovecot2-testinstanz/lib/dovecot//lib20_autocreate_plugin.so
Reading symbols
from 
/usr/local/dovecot/2.0.12-testinstanz/lib/dovecot/lib20_fts_plugin.so...done.
Loaded symbols
for /usr/local/dovecot/dovecot2-testinstanz/lib/dovecot//lib20_fts_plugin.so
Reading symbols
from 
/usr/local/dovecot/2.0.12-testinstanz/lib/dovecot/lib20_listescape_plugin.so...done.
Loaded symbols
for 
/usr/local/dovecot/dovecot2-testinstanz/lib/dovecot//lib20_listescape_plugin.so
Reading symbols
from 
/usr/local/dovecot/2.0.12-testinstanz/lib/dovecot/lib20_mail_log_plugin.so...done.
Loaded symbols
for 
/usr/local/dovecot/dovecot2-testinstanz/lib/dovecot//lib20_mail_log_plugin.so
Reading symbols
from 
/usr/local/dovecot/2.0.12-testinstanz/lib/dovecot/lib20_zlib_plugin.so...done.
Loaded symbols
for /usr/local/dovecot/dovecot2-testinstanz/lib/dovecot//lib20

Re: [Dovecot] dovecot & OCFS2 Cluster

2011-04-27 Thread Robert Schetterer
Am 27.04.2011 00:50, schrieb Joseph Tam:
> Robert Schetterer  writes:
> 
>>> Anyway, why use lmtp over lda ?
>>
>> i.e avoid backscatter by overquota
> 
> A clarification on this: backscatter (or rather, ambiguous NDR notices
> that claim many users are over quota rather than just one) is a result
> of a local mailer that support multiple recipient delivery in one
> invocation, but can only return one result code to the MTA.
> 
> Since Dovecot's deliver-lda does not support  multiple recipient delivery,
> this is not a problem.


> 
> LMTP can support multiple deliveries of the same message per invocation,
> but replies with individual SMTP codes to avoid the above problem.
> It can take advantage of this to efficiently implement single instance
> storage if it is enabled.

in my understanding lmtp acts more like a mta
so overquota  "reject" can be send during smtp income stage i.e with
postfix, to the sender client

with lda this isnt possible cause the the mta does give the whole mail
to lda which and mta send "recieved" to the sender client
( so the bounce must be send later by binary sendmail etc )

whatever this is the behavior i ve tested in my setups,
may Timo correct me if i fail here

> 
>> performance should better too
> 
> Apart from multiple deliveries or SIS, I'm not sure this is true, or
> significant if it were.

yes this should be meassured, youre right i dont know too if its really
performance relevant, but multiple deliver is nice to have anyway, why
should not use it

> 
> Joseph Tam 

however i see no reason to use lda longer in my setups as lmtp exits
youre right the backscatter case is really rare anyway
-- 
Best Regards

MfG Robert Schetterer

Germany/Munich/Bavaria


Re: [Dovecot] 2.0.12 Coredump under Solaris 10

2011-04-27 Thread Timo Sirainen
On Wed, 2011-04-27 at 10:24 +0200, Denny Schierz wrote:
> The gdb coredump shows:

Almost great bug report! Just:

> gdb ../../dovecot2-testinstanz/libexec/dovecot/imap 
> /var/run/dovecot-testinstanz/core 
> 
> Core was generated by `dovecot/imap'.
> Program terminated with signal 11, Segmentation fault.
> #0  0xfeb559f8 in strcmp () from /lib/libc.so.1

Give "bt full" command here and show the output.



Re: [Dovecot] 2.0.12 Coredump under Solaris 10

2011-04-27 Thread Denny Schierz
hi,

Am Mittwoch, den 27.04.2011, 12:37 +0300 schrieb Timo Sirainen:

> Give "bt full" command here and show the output.

lot of lines :-)


(gdb) bt full
#0  0xfeb559f8 in strcmp () from /lib/libc.so.1
No symbol table info available.
#1  0xfee73e7a in settings_find_key_nth (ctx=0x809bec0, key=0x807ab38
"plugin//imap", n=0x80477f0, def_r=0x80477f4, link_r=0x80477f8)
at settings-parser.c:699
parent_n = 1
parent_def = (const struct setting_define *) 0x0
parent_link = (struct setting_link *) 0x809bf40
def = (const struct setting_define *) 0x7ffb
link = (struct setting_link *) 0x807ab48
parent_key = 0x807ab48 "plugin/"
i = 134720328
__FUNCTION__ = "settings_find_key_nth"
#2  0xfee73e57 in settings_find_key_nth (ctx=0x809bec0, key=0x807ab20
"plugin//imap/spool", n=0x8047830, def_r=0x8047834, link_r=0x8047838)
at settings-parser.c:693
parent_n = 1
parent_def = (const struct setting_define *) 0x807ab20
parent_link = (struct setting_link *) 0x8047848
def = (const struct setting_define *) 0x7ffb
link = (struct setting_link *) 0x807ab48
parent_key = 0x807ab38 "plugin//imap"
i = 134720312
__FUNCTION__ = "settings_find_key_nth"
#3  0xfee73e57 in settings_find_key_nth (ctx=0x809bec0, key=0x807ab08
"plugin//imap/spool/%d", n=0x8047870, def_r=0x8047874, link_r=0x8047878)
at settings-parser.c:693
parent_n = 1
parent_def = (const struct setting_define *) 0x807ab08
parent_link = (struct setting_link *) 0x8047888
def = (const struct setting_define *) 0x7ffb
link = (struct setting_link *) 0x807ab48
parent_key = 0x807ab20 "plugin//imap/spool"
i = 134720288
__FUNCTION__ = "settings_find_key_nth"
#4  0xfee73e57 in settings_find_key_nth (ctx=0x809bec0, key=0x807aae8
"plugin//imap/spool/%d/%1n", n=0x80478b0, def_r=0x80478b4,
link_r=0x80478b8)
at settings-parser.c:693
parent_n = 1
parent_def = (const struct setting_define *) 0x807aae8
parent_link = (struct setting_link *) 0x80478c8
def = (const struct setting_define *) 0x7ffb
link = (struct setting_link *) 0x807ab48
parent_key = 0x807ab08 "plugin//imap/spool/%d"
i = 134720264
__FUNCTION__ = "settings_find_key_nth"
#5  0xfee73e57 in settings_find_key_nth (ctx=0x809bec0, key=0x807aac8
"plugin//imap/spool/%d/%1n/%n", n=0x8047930, def_r=0x8047934,
link_r=0x8047938)
at settings-parser.c:693
parent_n = 1
parent_def = (const struct setting_define *) 0x0
parent_link = (struct setting_link *) 0x1d
def = (const struct setting_define *) 0x7ffb
link = (struct setting_link *) 0x807ab48
parent_key = 0x807aae8 "plugin//imap/spool/%d/%1n"
i = 134720232
__FUNCTION__ = "settings_find_key_nth"
#6  0xfee73806 in settings_parse_keyvalue (ctx=0x809bec0, key=0x807aac8
"plugin//imap/spool/%d/%1n/%n", value=0x807aab5 "/home/testds")
at settings-parser.c:767
---Type  to continue, or q  to quit---
def = (const struct setting_define *) 0x807aa98
link = (struct setting_link *) 0x807aab4
n = 1
#7  0xfee74322 in settings_parse_line (ctx=0x809bec0, line=0x807aa98
"plugin//imap/spool/%d/%1n/%n=/home/testds") at settings-parser.c:869
_data_stack_cur_id = 4
key = 0x807aac8 "plugin//imap/spool/%d/%1n/%n"
ret = 134720200
#8  0xfef0b740 in mail_storage_service_lookup (ctx=0x80852f0,
input=0x8047b60, user_r=0x8047a98, error_r=0x8047b3c) at
mail-storage-service.c:134
_data_stack_cur_id = 3
flags = MAIL_STORAGE_SERVICE_FLAG_DISALLOW_ROOT
user = (struct mail_storage_service_user *) 0x8088988
username = 0x807a89b "tes...@domain.foo"
user_info = (const struct setting_parser_info *) 0x8089d80
user_set = (const struct mail_user_settings *) 0xfef7fc99
userdb_fields = (const char * const *) 0x807a908
error = 0xfeff0540 ""
reply = {uid = -1, gid = -1, home = 0x0, chroot = 0x0,
extra_fields = {arr = {buffer = 0x809b6b8, element_size = 4}, v =
0x809b6b8, 
v_modifiable = 0x809b6b8}}
set_parser = (struct setting_parser_context *) 0x8093d40
user_pool = (pool_t) 0x8088918
temp_pool = (pool_t) 0x809b6a8
ret = 1
#9  0xfef0be8f in mail_storage_service_lookup_next (ctx=0x80852f0,
input=0x8047b60, user_r=0x807ab48, mail_user_r=0x8047adc,
error_r=0x8047b3c)
at mail-storage-service.c:1001
user = (struct mail_storage_service_user *) 0x0
ret = 134768152
#10 0x080658cd in client_create_from_input (input=0x807ab48,
login_client=0x8086618, fd_in=10, fd_out=10, input_buf=0x8047b40,
error_r=0x8047b3c)
at main.c:202
user = (struct mail_storage_service_user *) 0x870
mail_user = (struct mail_user *) 0x1
client = (struct client *) 0x8047b40
set = (const struct 

[Dovecot] Segmentation Fault in doveadm move under Solaris 10

2011-04-27 Thread Jürgen Obermann

Hi all

I want to move mails from folder test-ein to another folder test-aus  
with the new "doveadm move" command in dovecot 2.0.12. When I try the  
following I get a "Segmentation Fault" after the mail was copied to  
the new folder:


# doveadm -v -f flow search -u g033  mailbox test-ein all
56779e33a911b84db2295451a966 1

# doveadm -v -f flow search -u g033  mailbox test-aus all

# doveadm -v -f flow move -u g033 test-aus mailbox test-ein all
Segmentation Fault

# doveadm -v -f flow search -u g033  mailbox test-aus all
57779e33a911b84db2295451a966 26

# doveadm -v -f flow search -u g033  mailbox test-ein all
56779e33a911b84db2295451a966 1

The mail now is in both the source folder and the destination folder.

With truss under Solaris 10 we can see what happens (only the last few  
lines are shown):

open64("/home/hrz/g033/Mail/test-ein", O_RDWR)  = 12
fstat64(12, 0xFFBFEBA0) = 0
time()  = 1303911414
alarm(5)= 0
fcntl(12, F_SETLKW64, 0xFFBFED38)   = 0
alarm(0)= 5
stat64("/home/hrz/g033/Mail/test-ein", 0xFFBFEF80) = 0
stat64("/home/hrz/g033/Mail/.imap/test-ein/dovecot.index.log", 0xFFBFEA28) = 0
pread64(11, 0x00083090, 8192, 4440) = 0
stat64("/home/hrz/g033/Mail/.imap/test-ein/dovecot.index.log", 0xFFBFEEC0) = 0
pread64(11, 0x00083090, 8192, 4440) = 0
fstat64(12, 0xFFBFF1F0) = 0
brk(0x00092498) = 0
brk(0x00094498) = 0
pread64(12, " F r o m   O l i v e r .".., 8192, 0) = 5135
open("/var/run/tzsync", O_RDONLY)   = 13
mmap(0x, 4, PROT_READ, MAP_SHARED, 13, 0) = 0xFF25
close(13)   = 0
brk(0x00094498) = 0
brk(0x00096498) = 0
open("/usr/share/lib/zoneinfo/MET", O_RDONLY)   = 13
fstat64(13, 0xFFBFEE68) = 0
read(13, " T Z i f\0\0\0\0\0\0\0\0".., 765) = 765
close(13)   = 0
stat64("/home/hrz/g033/Mail/.imap/test-ein/dovecot.index.log", 0xFFBFEE58) = 0
pread64(11, 0x00083090, 8192, 4440) = 0
brk(0x00096498) = 0
brk(0x00098498) = 0
open64("/home/hrz/g033/Mail/.imap/test-ein/dovecot.index.cache", O_RDWR) = 13
fstat64(13, 0xFFBFF060) = 0
mmap64(0x, 57344, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANON,  
-1, 0) = 0xFEC9

pread64(13, "01\b\0\0 MB811C2 MB811C2".., 8192, 0) = 8192
pread64(13, "808080D0\0\0011F\0\0\0\r", 12, 32) = 12
pread64(13, "80808998\0\001 8\0\0\00E", 12, 320) = 12
pread64(13, "80808DB6\0\001 N\0\0\00F", 12, 4704) = 12
pread64(13, "\0\0\0\0\0\002A1\0\0\01D", 12, 6872) = 12
pread64(13, "01\b\0\0 MB811C2 MB811C2".., 8192, 0) = 8192
pread64(13, " c h r i c h t "   " q u".., 8192, 24576) = 8192
pread64(13, "\0\0\0\0\0\0\0\0\0\0\0\0".., 8192, 32768) = 8192
pread64(13, " l e r "   < K a r l - H".., 8192, 8192) = 8192
time()  = 1303911414
time()  = 1303911414
time()  = 1303911414
lstat64("/home/hrz/g033/Mail/test-aus.lock", 0xFFBFED28) Err#2 ENOENT
open64("/home/hrz/g033/Mail/test-aus.lock", O_RDWR|O_CREAT|O_EXCL, 0666) = 14
write(14, " 8 8 2 2 : f t p s e r v", 12)   = 12
fdsync(14, FDSYNC)  = 0
fstat64(14, 0xFFBFEE68) = 0
close(14)   = 0
lstat64("/home/hrz/g033/Mail/test-aus.lock", 0xFFBFEFC8) = 0
open64("/home/hrz/g033/Mail/test-aus", O_RDWR)  = 14
fstat64(14, 0xFFBFEF40) = 0
time()  = 1303911414
alarm(5)= 0
fcntl(14, F_SETLKW64, 0xFFBFF120)   = 0
alarm(0)= 5
stat64("/home/hrz/g033/Mail/test-aus", 0xFFBFF208) = 0
stat64("/home/hrz/g033/Mail/.imap/test-aus/dovecot.index.log", 0xFFBFECF0) = 0
pread64(9, 0x0007622C, 8192, 8484)  = 0
stat64("/home/hrz/g033/Mail/test-aus", 0xFFBFEF38) = 0
stat64("/home/hrz/g033/Mail/.imap/test-aus/dovecot.index.log", 0xFFBFE9E0) = 0
pread64(9, 0x0007622C, 8192, 8484)  = 0
stat64("/home/hrz/g033/Mail/.imap/test-aus/dovecot.index.log.2",  
0xFFBFEBF8) Err#2 ENOENT

alarm(180)  = 0
fcntl(9, F_SETLKW64, 0xFFBFEBA0)= 0
alarm(0)= 180
time()  = 1303911414
rmdir("/home/hrz/g033/Mail/.imap/test-aus") Err#17 EEXIST
stat64("/home/hrz/g033/Mail/.imap/test-aus/dovecot.index.log", 0xFFBFECF8) = 0
pread64(9, 0x0007622C, 8192, 8484)  = 0
time()  = 13039114

Re: [Dovecot] Segmentation Fault in doveadm move under Solaris 10

2011-04-27 Thread Timo Sirainen
On 27.4.2011, at 17.03, Jürgen Obermann wrote:

> # doveadm -v -f flow move -u g033 test-aus mailbox test-ein all
> Segmentation Fault

Can you get gdb backtrace?

gdb --args doveadm -v ...
run
bt full

Or if that doesn't produce valid output:

ulimit -c unlimited
doveadm -v ...
gdb doveadm core
bt full

If you don't have gdb, I guess dbx backtrace works too, but I'm not entirely 
sure how that thing works.



Re: [Dovecot] Segmentation Fault in doveadm move under Solaris 10

2011-04-27 Thread Jürgen Obermann

Quoting Timo Sirainen :


On 27.4.2011, at 17.03, Jürgen Obermann wrote:


# doveadm -v -f flow move -u g033 test-aus mailbox test-ein all
Segmentation Fault


Can you get gdb backtrace?

gdb --args doveadm -v ...
run
bt full

Or if that doesn't produce valid output:

ulimit -c unlimited
doveadm -v ...
gdb doveadm core
bt full

If you don't have gdb, I guess dbx backtrace works too, but I'm not  
entirely sure how that thing works.




I compiled with Suns Studio compiler so there are no symbols, but I  
hope this helps a bit anyway:


# gdb --args doveadm -v -f flow move -u g033 test-aus mailbox test-ein all
GNU gdb 5.3
Copyright 2002 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 "sparc-sun-solaris2.8"...
(gdb) run
Starting program: /usr/local/etc/doveadm -v -f flow move -u g033  
test-aus mailbox test-ein all


Program received signal SIGSEGV, Segmentation fault.
0xfee32370 in strlen () from /lib/libc.so.1
(gdb) bt full
#0  0xfee32370 in strlen () from /lib/libc.so.1
No symbol table info available.
#1  0xff29a9a8 in mail_generate_guid_128_hash () from  
/opt/local/lib/dovecot/libdovecot-storage.so.0

No symbol table info available.
#2  0xff2c2088 in index_mail_expunge () from  
/opt/local/lib/dovecot/libdovecot-storage.so.0

No symbol table info available.
#3  0x0001af1c in cmd_move_run ()
No symbol table info available.
#4  0x00016778 in doveadm_mail_next_user ()
No symbol table info available.
#5  0x00016844 in doveadm_mail_single_user ()
No symbol table info available.
#6  0x00016c5c in doveadm_mail_cmd ()
No symbol table info available.
#7  0x000172b4 in doveadm_mail_try_run ()
No symbol table info available.
#8  0x0001db28 in main ()
No symbol table info available.
(gdb) quit
The program is running.  Exit anyway? (y or n) y

--
Hochschulrechenzentrum der | Mail: juergen.oberm...@hrz.uni-giessen.de
Justus-Liebig-Universitaet | WWW:  http://www.uni-giessen.de/obermann/
Heinrich-Buff-Ring 44  | Tel:  0641-99-13054 (0641-99-13001)
D-35392 Giessen, Germany   | Fax:  0641-99-13009



[Dovecot] What is the recommended way to move a message from one mailbox to another using CLI

2011-04-27 Thread Uffe Jakobsen

What is the recommended way to move a message from one mailbox to another
using CLI - serverside commands ?

Since IMAP does not support transactional moves between mailboxes - The only
thing that comes to my mind is this operation:

1) extract message from mailbox A using "doveadm fetch"
2) inject message into mailbox B using "dovecot-lda"
3) expunge message from mailbox A using "doveadm expunge"

it this the right solution ?

One problem with above approach is that injecting through "dovecot-lda" will
trigger the sieve script - which I'm not interested in since the message
have already been injected and processed once before - at delivery...

Any advice is much welcome

-- 
View this message in context: 
http://old.nabble.com/What-is-the-recommended-way-to-move-a-message-from-one-mailbox-to-another-using-CLI-tp31488298p31488298.html
Sent from the Dovecot mailing list archive at Nabble.com.



Re: [Dovecot] What is the recommended way to delete a message from a mailbox ?

2011-04-27 Thread Uffe Jakobsen



Andrew Lewis-10 wrote:
> 
>  On Wed, 20 Apr 2011 21:25:39 -0700 (PDT), Uffe Jakobsen wrote:
>> What is the recommended way to delete a message from a mailbox (from 
>> an
>> "external" server side program - such as a shell script) ?
>  doveadm expunge -u foo mailbox Outbox header message-id bar
> 

ah - thx :-)
-- 
View this message in context: 
http://old.nabble.com/What-is-the-recommended-way-to-delete-a-message-from-a-mailbox---tp31446701p31488306.html
Sent from the Dovecot mailing list archive at Nabble.com.



Re: [Dovecot] What is the recommended way to move a message from one mailbox to another using CLI

2011-04-27 Thread Eduardo M KALINOWSKI

On Qua, 27 Abr 2011, Uffe Jakobsen wrote:

What is the recommended way to move a message from one mailbox to another
using CLI - serverside commands ?


If you are using maildir, you can just mv the file.



--
BOFH excuse #392:

It's union rules. There's nothing we can do about it. Sorry.

Eduardo M KALINOWSKI
edua...@kalinowski.com.br



Re: [Dovecot] What is the recommended way to move a message from one mailbox to another using CLI

2011-04-27 Thread Timo Sirainen
On 27.4.2011, at 18.09, Uffe Jakobsen wrote:

> What is the recommended way to move a message from one mailbox to another
> using CLI - serverside commands ?

v2.0.12 has doveadm move command.



Re: [Dovecot] What is the recommended way to move a message from one mailbox to another using CLI

2011-04-27 Thread Uffe Jakobsen



Timo Sirainen wrote:
> 
> On 27.4.2011, at 18.09, Uffe Jakobsen wrote:
> 
>> What is the recommended way to move a message from one mailbox to another
>> using CLI - serverside commands ?
> 
> v2.0.12 has doveadm move command.
> 
> 

Damn I'm stuck on 2.0.11 until the FreeBSD port comes through...

What would be the recommended approach on 2.0.11 ?

Thanks in advance
-- 
View this message in context: 
http://old.nabble.com/What-is-the-recommended-way-to-move-a-message-from-one-mailbox-to-another-using-CLI-tp31488298p31489620.html
Sent from the Dovecot mailing list archive at Nabble.com.