Re: Remove "Duplicate" emails (and documentation update)

2018-02-23 Thread @lbutlr 
On 2018-02-23 (16:47 MST), Joseph Tam  wrote:
> 
> On Fri, 23 Feb 2018, @lbutlr wrote:
> 
>> $ doveadm -f table fetch -u kremels 'hdr.message-id guid uid
>> hdr.x-listname' mailbox "Archive" | sort| awk 'cnt[$1]++{if
>> (cnt[$1]==2) print prev[$1]; print} {prev[$1]=$0}' |grep -E "[0-9] +$"
>> |awk '{print "doveadm expunge -u kremels MAILBOX-GUID "$2" UID "$3}?
> 
> I was unaware of the syntax "hdr.{header}" -- all the reference materials
> I've seen only refers to "hdr" which returns the entire header block.

the error message from doveadm if you specify an invalid field is:

Available fetch fields: hdr. body. binary. user mailbox 
mailbox-guid seq uid guid flags modseq hdr body body.snippet text text.utf8 
size.physical size.virtual date.received date.sent date.saved 
date.received.unixtime date.sent.unixtime date.saved.unixtime imap.envelope 
imap.body imap.bodystructure pop3.uidl pop3.order refcount storageid

>> First, even after expunging a message and running doveadm index -u
>> kremels ?Archive?, subsequent runs still show the same duplicate
>> messages.
> 
> I suspect client side caching.

No, there is no client side involved. I am executing all of these these 
commands on the mail server. I expunge the messages, I index (or even 
force-resync) and the next search shows the same messages even though they are 
not in the Maildir anymore.

> If {count} is what you expected, then dovecot has the correct information
> and it's likely some client-side caching issue.

I would have needed to check the count before doing this, and I did not.

>> Second, what I really want to do is run this over ALL the mailboxes,
>> except for Junk and Sent but if that is possible I can?t find the right
>> syntax.
> 
> You mean to remove duplicates from any 2 mailboxes, or remove duplicates
> in mailboxes also found in Archive?

I want to find any duplicates (based on msg ID) across all mailboxes, except 
Sent

>   doveadm -f table fetch -u kremels \
>   'hdr.message-id guid uid' \
>   NOT mailbox Archive \
>   NOT mailbox Junk \
>   NOT mailbox Sent \
>   | sort -b >list1

Aha! Didn't know you could use NOT mailbox. That probably solves my issue on 
that score.

-- 
"It's unacceptable to think" - George W Bush 15/Sep/2006

Re: Remove "Duplicate" emails (and documentation update)

2018-02-23 Thread Joseph Tam 


On Fri, 23 Feb 2018, @lbutlr wrote:


$ doveadm -f table fetch -u kremels 'hdr.message-id guid uid
hdr.x-listname' mailbox "Archive" | sort| awk 'cnt[$1]++{if
(cnt[$1]==2) print prev[$1]; print} {prev[$1]=$0}' |grep -E "[0-9] +$"
|awk '{print "doveadm expunge -u kremels MAILBOX-GUID "$2" UID "$3}?


I was unaware of the syntax "hdr.{header}" -- all the reference materials
I've seen only refers to "hdr" which returns the entire header block.
This is handy to know because up to now, I've been filtering "hdr"
fetches through grep.  I've tried updating the Wiki, but it's immutable,
so would someone update the documentation:

https://wiki.dovecot.org/Tools/Doveadm/Fetch
(and man page in distribution)

hdr[.{x}]
Header {x} of message.  If missing, the
entire header is fetched.


First, even after expunging a message and running doveadm index -u
kremels ?Archive?, subsequent runs still show the same duplicate
messages.


I suspect client side caching.  If you query IMAP directly, does
it report the correct number of messages?

(Using openssl s_client, or netcat or telnet, or whatever)
x1 LOGIN kremels yourpassword
x2 SELECT INBOX
... look for "* {count} EXISTS" ...
x3 LOGOUT

If {count} is what you expected, then dovecot has the correct information
and it's likely some client-side caching issue.


Second, what I really want to do is run this over ALL the mailboxes,
except for Junk and Sent but if that is possible I can?t find the right
syntax.


You mean to remove duplicates from any 2 mailboxes, or remove duplicates
in mailboxes also found in Archive?

If the latter, try

doveadm -f table fetch -u kremels \
hdr.message-id \
mailbox Archive \
| sort -b >list0

doveadm -f table fetch -u kremels \
'hdr.message-id guid uid' \
NOT mailbox Archive \
NOT mailbox Junk \
NOT mailbox Sent \
| sort -b >list1

The list of duplicate message-id, guid and uid will then be ...

join -j1 list0 list1

You can process it via awk with one invocation of doveadm (2nd form
without exclusion of Archive) but you'll need to know the guid of
Archive beforehand.

Joseph Tam

dovecot auth and horde webmail

2018-02-23 Thread David Mehler 
Hello,

I'm not sure if this is a Dovecot-specific question, or Postfix or
Horde webmail. As Dovecot is used for authenticating both Postfix as
well as horde I thought i'd start here.

I've got a new horde webmail install going on a FreeBSD 11.1 jail.
I've got Dovecot set up so that it appends a domain name if one is not
given, so that user and u...@example.com can both log in.

When I logged in with horde webmail I used for the first attempt
username with no @example.com suffix. I logged in ok, but couldn't
send an email, gave me a weird error no address associated with host.
I logged out, logged back in using u...@example.com the full address,
and this time the message sending went through.

Any ideas or if this is not a Dovecot question let me know, as that
means I'll have two other places to try.

Thanks.
Dave.

doveconf -n
# 2.2.33.2 (d6601f4ec): /usr/local/etc/dovecot/dovecot.conf
# Pigeonhole version 0.4.21 (92477967)
# OS: FreeBSD 11.1-RELEASE-p4 amd64
auth_cache_size = 16 k
auth_default_realm = example.com
auth_mechanisms = plain login
auth_realms = example.com example2.com
dict {
  acl = mysql:/usr/local/etc/dovecot/shared-folders.conf
  sqlquota = mysql:/usr/local/etc/dovecot/quota.conf
}
first_valid_gid = 999
first_valid_uid = 999
hostname = mail.example.com
imap_client_workarounds = delay-newmail tb-extra-mailbox-sep tb-lsub-flags
last_valid_gid = 999
last_valid_uid = 999
lda_mailbox_autocreate = yes
lda_mailbox_autosubscribe = yes
listen = 127.0.0.1 xxx.xxx.xxx.xxx
lmtp_rcpt_check_quota = yes
mail_access_groups = vmail
mail_fsync = never
mail_gid = vmail
mail_home = /home/vmail/%d/%n
mail_location = maildir:~/mail/:LAYOUT=fs:INDEX=~/mail/
mail_plugins = acl mail_log notify quota quota_clone trash virtual welcome zlib
mail_server_admin = mailto:postmas...@example.com
mail_uid = vmail
mailbox_list_index = yes
managesieve_notify_capability = mailto
managesieve_sieve_capability = fileinto reject envelope
encoded-character vacation subaddress comparator-i;ascii-numeric
relational regex imap4flags copy include variables body enotify
environment mailbox date index ihave duplicate mime foreverypart
extracttext imapflags notify imapsieve vnd.dovecot.imapsieve
namespace {
  hidden = no
  list = yes
  location = 
maildir:/home/vmail/public/:LAYOUT=fs:CONTROL=~/mail/public:INDEXPVT=~/mail/public:INDEX=~/mail/public
  mailbox TestFolder {
auto = subscribe
comment = Public Folder for message sharing
  }
  prefix = public/
  separator = /
  subscriptions = yes
  type = public
}
namespace {
  list = yes
  location = maildir:~/mail/:INDEX=~/mail/shared/%%Ld/%%Ln
  prefix = shared/%%u/
  separator = /
  subscriptions = yes
  type = shared
}
namespace {
  location = virtual:/usr/local/etc/dovecot/virtual
  mailbox All {
auto = subscribe
comment = All my messages
special_use = \All
  }
  prefix = virtual/
  separator = /
}
namespace inbox {
  inbox = yes
  location =
  mailbox Archive {
auto = no
special_use = \Archive
  }
  mailbox Archives {
auto = subscribe
special_use = \Archive
  }
  mailbox "Deleted Messages" {
auto = no
autoexpunge = 30 days
special_use = \Trash
  }
  mailbox Drafts {
auto = subscribe
special_use = \Drafts
  }
  mailbox Junk {
auto = no
autoexpunge = 30 days
special_use = \Junk
  }
  mailbox "Junk E-mail" {
auto = no
autoexpunge = 30 days
special_use = \Junk
  }
  mailbox Sent {
auto = subscribe
special_use = \Sent
  }
  mailbox "Sent Items" {
auto = no
special_use = \Sent
  }
  mailbox "Sent Messages" {
auto = no
special_use = \Sent
  }
  mailbox Spam {
auto = subscribe
autoexpunge = 30 days
special_use = \Junk
  }
  mailbox Trash {
auto = subscribe
autoexpunge = 30 days
special_use = \Trash
  }
  prefix =
  separator = /
  type = private
}
passdb {
  args = /usr/local/etc/dovecot/dovecot-sql.conf.ext
  driver = sql
}
plugin {
  acl = vfile:/usr/local/etc/dovecot/global-acls:cache_secs=300
  acl_anyone = allow
  acl_globals_only = yes
  acl_shared_dict = proxy::acl
  imapsieve_mailbox1_before =
file:/usr/local/lib/dovecot/sieve/report-spam.sieve
  imapsieve_mailbox1_causes = COPY
  imapsieve_mailbox1_name = Spam
  imapsieve_mailbox2_before = file:/usr/local/lib/dovecot/sieve/report-ham.sieve
  imapsieve_mailbox2_causes = COPY
  imapsieve_mailbox2_from = Spam
  imapsieve_mailbox2_name = *
  mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename
  mail_log_fields = uid box msgid size
  quota = count:User quota
  quota_clone_dict = proxy::sqlquota
  quota_exceeded_message = Storage quota for this account has been
exceeded, please try again later.
  quota_grace = 10%%
  quota_status_nouser = DUNNO
  quota_status_overquota = 552 5.2.2 Mailbox is full
  quota_status_success = DUNNO
  quota_vsizes = true
  quota_warning = storage=100%% quota-exceeded 100 %u
  quota_warning2 = storage=95%% quota-warning 95 %u
  quota_warning3 = storage=90%% quota-w

Re: Remove "Duplicate" emails

2018-02-23 Thread @lbutlr 
OK, perhaps I tried to cover too much, so let's just look at this:

If I run this command, I get no errors:

doveadm expunge -u kremels MAILBOX-GUID 1488800748.47633_1.mail.covisp.net UID 
22908

But, if I search again 

doveadm -f table fetch -u kremels 'hdr.message-id guid uid hdr.x-listname' 
mailbox 'Archive' | sort| awk 'cnt[$1]++{if (cnt[$1]==2) print prev[$1]; print} 
{prev[$1]=$0}' |grep -E "[0-9]  +$" |awk '{print "doveadm expunge -u kremels 
MAILBOX-GUID "$2" UID "$3}' | grep 22908
hdr.message-id guiduid hdr.x-listname
doveadm expunge -u kremels MAILBOX-GUID 1488800748.47633_1.mail.covisp.net UID 
22908

The message is still listed.

Am i misunderstanding something about how expunge works or what it does?

How do i remove the messages in such a way that they will not show up in 
subsequent searches (as far as I can tell, assuming the 1488800748.47633_1 is 
the first part of the file name in the maildir, the message is actually 
deleted).

 $ find Maildir -name "1488800*"
Maildir/.Archive/cur/1488800350.46962_1.mail.covisp.net:2,S
Maildir/.Archive/cur/1488800633.47337_1.mail.covisp.net:2,S
Maildir/.Sent/cur/1488800118.M2833P43167.mail.covisp.net,S=1221,W=1251:2,Sad


-- 
Tragic heroes always moan when the gods take an interest in them, but
it's the people the gods ignore who get the really tough deals. --Mort

Re: Sieve

2018-02-23 Thread Stephan Bosch 
Op 2/19/2018 om 7:14 PM schreef IT:
>
> Hello,
>
> Im newbie at sieve. I have a nice script running on my boxes,
>
> and I have the following question:
>
> Using Sieve,
>
> is there a RULE to find out if String "MYTESTSTRING"
>
> is ANYWHERE inside the Email, or ANYWHERE inside the HEADER at least --
>
> in order to trigger actions like "discard;" consequently ?
>

I am seeing that question a lot lately. For the top-level message, the
answer is unfortunately: no.

You could hack something ugly using the extprograms plugin, but standard
Sieve has no such capability.

Regards,

Stephan.



>
> Thank you so much in advance
>
> best Regards
>
> Florian
>
>
>
>
> -- 
>
> Mit freundlichen Grüßen / best regards
>
> Florian Bojack
>
> i...@u-eitner.de 
>
>
>
> logoEitner
>
> U.Eitner
>
> Formenbau, Erodier-& Kunststofftechnik GmbH
>
> Benzstraße 7
>
> D-64807 Dieburg
>
>
> Geschäftsführer Ulrich und Lars Eitner
>
> Tel: +49 (0) 6071 23262
>
> Fax: +49 (0) 6071 5562
>
> Web: www.i...@u-eitner.de
>
> Der Inhalt dieser Email und etwaiger Anhänge ist vertraulich und
> ausschließlich für den bezeichneten Adressaten bestimmt.
>
> Jede unbefugte Kenntnisnahme, Veröffentlichung,Vervielfältigung oder
> Weitergabe ist unzulässig.
>
> Sollten Sie nicht der vorgesehene Empfänger sein, bitten wir Sie, sich
> mit uns in Verbindung zu setzen und die Email zu löschen sowie alle
> Kopien zu vernichten.
>
> This e-mail is intended solely for the addressee and may contain
> confidential and/or privileged information.
>
> If you are not the intended recipient, please notify the sender
> immediately and destroy this e-mail.
>
> In this case any form of reproduction, disclosure, distribution or any
> action taken or refrained from in reliance on it, is strictly prohibited.
>

Re: Assertion during dsync receive

2018-02-23 Thread Tanstaafl 
On Fri Feb 23 2018 14:53:53 GMT-0500 (Eastern Standard Time), Aki Tuomi
 wrote:
> It is problem for any mailbox

Ok, so, I'm still unclear...

what cache are we talking about? Are you saying that there is a limit to
how many emails dovecot can store in a single... 'folder'?

Re: Assertion during dsync receive

2018-02-23 Thread Aki Tuomi 
It is problem for any mailbox


---Aki TuomiDovecot oy
 Original message From: Tanstaafl  
Date: 23/02/2018  21:36  (GMT+02:00) To: dovecot@dovecot.org Subject: Re: 
Assertion during dsync receive 
On Fri Feb 23 2018 13:53:27 GMT-0500 (Eastern Standard Time), Aki Tuomi
 wrote:
> Once you cache grows bigger than 0x400 you have problems

This is for a single mailbox? IS this only a problem for mbox and maybe
sdbox?

Re: Assertion during dsync receive

2018-02-23 Thread Tanstaafl 
On Fri Feb 23 2018 13:53:27 GMT-0500 (Eastern Standard Time), Aki Tuomi
 wrote:
> Once you cache grows bigger than 0x400 you have problems

This is for a single mailbox? IS this only a problem for mbox and maybe
sdbox?

Re: Optimizing search performance for mobile devices / web mailer / general - solr plugin config

2018-02-23 Thread Tanstaafl 
On Fri Feb 23 2018 03:51:37 GMT-0500 (Eastern Standard Time), Peter
Chiochetti  wrote:
> There is a trick to have messages indexed on arrival, instead of at 
> mailbox access, "fts_autoindex = yes" in the plugin section. This is not 
> mentioned in the dovecot wiki page but might be useful.

Not sure why you would say that...

That setting is mentioned specifically twice...

https://wiki.dovecot.org/Plugins/FTS

Re: Assertion during dsync receive

2018-02-23 Thread Aki Tuomi 
Once you cache grows bigger than 0x400 you have problems


---Aki TuomiDovecot oy
 Original message From: Ian Bobbitt  
Date: 23/02/2018  20:33  (GMT+02:00) To: dovecot@dovecot.org Subject: Re: 
Assertion during dsync receive 

Thanks. I've had the user clear out that mailbox, and replication is
working fine for them again.



Is there a better way to catch this than watch for crashes and read
the backtrace to find what mailbox needs to be shrunk?



Where is the threshold for "too big"?



-- Ian



On 2/23/18 11:33 AM, Aki Tuomi wrote:


  
  The mailbox is too big.
  

  
  

  
  

  
  

---
Aki Tuomi
Dovecot oy
  
  

  
  
 Original message 
From: Ian Bobbitt  
Date: 23/02/2018 17:52 (GMT+02:00) 
To: dovecot@dovecot.org 
Subject: Assertion during dsync receive 



  
  Hi,

  

  I'm getting an assertion failed on the receiving side, causing
  syncs to fail for one user. The servers are setup so that

  only one is receiving any traffic other than replication at any
  time. The one that's only receiving replications is the

  one that's failing.

  

  I've tried deleting the user's home on the receiving server, but
  it still crashes during the sync. Oddly, the user's

  home is 7.4G on the sending server, but ends up at 42G on the
  receiving side, even after deleting and trying a fresh sync.

  

  The mailbox implicated in the backtrace ("Spam") does have a very
  large number of messages in it.

  On sender:

  Spam messages=1217764 recent=0 uidnext=1218103
  uidvalidity=1379509105 unseen=16 highestmodseq=744588
  vsize=34468460093

  guid=090ed93a7a09abf10200fdf6807a firstsaved=1498744186

  On receiver:

  Spam messages=1217766 recent=352 uidnext=1218105
  uidvalidity=1379509105 unseen=16 highestmodseq=744589
  vsize=34468496809

  guid=090ed93a7a09abf10200fdf6807a firstsaved=1519396172

  

  Feb 23 14:57:20 dovecot: dsync-local(bgeels): Warning: fscking
  index file

  /gnoc/mail/home/bgeels/mail/storage/dovecot.map.index

  Feb 23 14:57:20 dovecot: dsync-local(bgeels): Warning: mdbox
  /gnoc/mail/home/bgeels/mail/storage: rebuilding indexes

  Feb 23 14:57:33 dovecot: dsync-local(bgeels): Panic: file
  mail-index-util.c: line 10 (mail_index_uint32_to_offset):

  assertion failed: (offset < 0x4000)

  Feb 23 14:57:33 dovecot: dsync-local(bgeels): Error: Raw
  backtrace: /usr/lib64/dovecot/libdovecot.so.0(+0x9f3de)

  [0x7feb584143de] ->
  /usr/lib64/dovecot/libdovecot.so.0(+0x9f4be) [0x7feb584144be]
  ->

  /usr/lib64/dovecot/libdovecot.so.0(i_fatal+0) [0x7feb583a577c]
  ->

/usr/lib64/dovecot/libdovecot-storage.so.0(mail_index_uint32_to_offset+0xa0)
  [0x7feb587906d0] ->

/usr/lib64/dovecot/libdovecot-storage.so.0(mail_cache_compress+0x854)
  [0x7feb58774f34] ->

/usr/lib64/dovecot/libdovecot-storage.so.0(mail_index_sync_commit+0x25f)
  [0x7feb587884ff] ->

/usr/lib64/dovecot/libdovecot-storage.so.0(mdbox_storage_rebuild_in_context+0x10de)
  [0x7feb5870b3ae] ->

  /usr/lib64/dovecot/libdovecot-storage.so.0(mdbox_sync_begin+0x858)
  [0x7feb5870ccd8] ->

  /usr/lib64/dovecot/libdovecot-storage.so.0(mdbox_sync+0x4c)
  [0x7feb5870ce7c] ->

/usr/lib64/dovecot/libdovecot-storage.so.0(mdbox_storage_sync_init+0x4b)
  [0x7feb5870cf3b] ->

  /usr/lib64/dovecot/libdovecot-storage.so.0(mailbox_sync_init+0x44)
  [0x7feb586f2834] ->

  /usr/lib64/dovecot/libdovecot-storage.so.0(mailbox_sync+0x37)
  [0x7feb586f28d7] ->

  dovecot/doveadm-server(dsync_mailbox_import_deinit+0x475)
  [0x445495] -> dovecot/doveadm-server() [0x43edc0] ->

  dovecot/doveadm-server(dsync_brain_sync_mails+0x743) [0x43f653]
  -> dovecot/doveadm-server(dsync_brain_run+0x541)

  [0x43acf1] -> dovecot/doveadm-server() [0x43b070] ->
  dovecot/doveadm-server() [0x44fe5f] ->

  /usr/lib64/dovecot/libdovecot.so.0(io_loop_call_io+0x52)
  [0x7feb58429cd2] ->

/usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x10f)
  [0x7feb5842b3bf] ->

  /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run+0x3c)
  [0x7feb58429d6c] ->

  /usr/lib64/dovecot/libdovecot.so.0(io_loop_run+0x38)
  [0x7feb58429f28] -> dovecot/doveadm-server() [0x4209c5] ->

  dovecot/doveadm-server() [0x422df6] -> dovecot/doveadm-server()
  [0x4377f4] ->

  /usr/lib64/dovecot/libdovecot.so.0(io_loop_call_io+0x52)
  [0x7feb58429cd2] ->

/usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x10f)
  [0x7feb5842b3bf] ->

  /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run+0x3c)
  [0x7feb58429d6c]

  Feb 23 14:57:33 dsync

Re: Assertion during dsync receive

2018-02-23 Thread Ian Bobbitt 
Thanks. I've had the user clear out that mailbox, and replication is working 
fine for them again.

Is there a better way to catch this than watch for crashes and read the 
backtrace to find what mailbox needs to be shrunk?

Where is the threshold for "too big"?

-- Ian

On 2/23/18 11:33 AM, Aki Tuomi wrote:
> The mailbox is too big.
>
>
>
> ---
> Aki Tuomi
> Dovecot oy
>
>  Original message 
> From: Ian Bobbitt 
> Date: 23/02/2018 17:52 (GMT+02:00)
> To: dovecot@dovecot.org
> Subject: Assertion during dsync receive
>
> Hi,
>
> I'm getting an assertion failed on the receiving side, causing syncs to fail 
> for one user. The servers are setup so that
> only one is receiving any traffic other than replication at any time. The one 
> that's only receiving replications is the
> one that's failing.
>
> I've tried deleting the user's home on the receiving server, but it still 
> crashes during the sync. Oddly, the user's
> home is 7.4G on the sending server, but ends up at 42G on the receiving side, 
> even after deleting and trying a fresh sync.
>
> The mailbox implicated in the backtrace ("Spam") does have a very large 
> number of messages in it.
> On sender:
> Spam messages=1217764 recent=0 uidnext=1218103 uidvalidity=1379509105 
> unseen=16 highestmodseq=744588 vsize=34468460093
> guid=090ed93a7a09abf10200fdf6807a firstsaved=1498744186
> On receiver:
> Spam messages=1217766 recent=352 uidnext=1218105 uidvalidity=1379509105 
> unseen=16 highestmodseq=744589 vsize=34468496809
> guid=090ed93a7a09abf10200fdf6807a firstsaved=1519396172
>
> Feb 23 14:57:20 dovecot: dsync-local(bgeels): Warning: fscking index file
> /gnoc/mail/home/bgeels/mail/storage/dovecot.map.index
> Feb 23 14:57:20 dovecot: dsync-local(bgeels): Warning: mdbox 
> /gnoc/mail/home/bgeels/mail/storage: rebuilding indexes
> Feb 23 14:57:33 dovecot: dsync-local(bgeels): Panic: file mail-index-util.c: 
> line 10 (mail_index_uint32_to_offset):
> assertion failed: (offset < 0x4000)
> Feb 23 14:57:33 dovecot: dsync-local(bgeels): Error: Raw backtrace: 
> /usr/lib64/dovecot/libdovecot.so.0(+0x9f3de)
> [0x7feb584143de] -> /usr/lib64/dovecot/libdovecot.so.0(+0x9f4be) 
> [0x7feb584144be] ->
> /usr/lib64/dovecot/libdovecot.so.0(i_fatal+0) [0x7feb583a577c] ->
> /usr/lib64/dovecot/libdovecot-storage.so.0(mail_index_uint32_to_offset+0xa0) 
> [0x7feb587906d0] ->
> /usr/lib64/dovecot/libdovecot-storage.so.0(mail_cache_compress+0x854) 
> [0x7feb58774f34] ->
> /usr/lib64/dovecot/libdovecot-storage.so.0(mail_index_sync_commit+0x25f) 
> [0x7feb587884ff] ->
> /usr/lib64/dovecot/libdovecot-storage.so.0(mdbox_storage_rebuild_in_context+0x10de)
>  [0x7feb5870b3ae] ->
> /usr/lib64/dovecot/libdovecot-storage.so.0(mdbox_sync_begin+0x858) 
> [0x7feb5870ccd8] ->
> /usr/lib64/dovecot/libdovecot-storage.so.0(mdbox_sync+0x4c) [0x7feb5870ce7c] 
> ->
> /usr/lib64/dovecot/libdovecot-storage.so.0(mdbox_storage_sync_init+0x4b) 
> [0x7feb5870cf3b] ->
> /usr/lib64/dovecot/libdovecot-storage.so.0(mailbox_sync_init+0x44) 
> [0x7feb586f2834] ->
> /usr/lib64/dovecot/libdovecot-storage.so.0(mailbox_sync+0x37) 
> [0x7feb586f28d7] ->
> dovecot/doveadm-server(dsync_mailbox_import_deinit+0x475) [0x445495] -> 
> dovecot/doveadm-server() [0x43edc0] ->
> dovecot/doveadm-server(dsync_brain_sync_mails+0x743) [0x43f653] -> 
> dovecot/doveadm-server(dsync_brain_run+0x541)
> [0x43acf1] -> dovecot/doveadm-server() [0x43b070] -> dovecot/doveadm-server() 
> [0x44fe5f] ->
> /usr/lib64/dovecot/libdovecot.so.0(io_loop_call_io+0x52) [0x7feb58429cd2] ->
> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x10f) 
> [0x7feb5842b3bf] ->
> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run+0x3c) [0x7feb58429d6c] 
> ->
> /usr/lib64/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7feb58429f28] -> 
> dovecot/doveadm-server() [0x4209c5] ->
> dovecot/doveadm-server() [0x422df6] -> dovecot/doveadm-server() [0x4377f4] ->
> /usr/lib64/dovecot/libdovecot.so.0(io_loop_call_io+0x52) [0x7feb58429cd2] ->
> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x10f) 
> [0x7feb5842b3bf] ->
> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run+0x3c) [0x7feb58429d6c]
> Feb 23 14:57:33 dsync-local(bgeels): Fatal: master: service(doveadm): child 
> 82098 killed with signal 6 (core dumped)
>
> I've attached the output of `doveconf -n` and the full backtrace from a core 
> dump.
>
> Dovecot 2.2.33.2 (GhettoForge package)
> CentOS 7 x86_64
> XFS, no NFS.
>
>
> -- Ian



smime.p7s
Description: S/MIME Cryptographic Signature

Re: Assertion during dsync receive

2018-02-23 Thread Aki Tuomi 
The mailbox is too big.


---Aki TuomiDovecot oy
 Original message From: Ian Bobbitt  
Date: 23/02/2018  17:52  (GMT+02:00) To: dovecot@dovecot.org Subject: Assertion 
during dsync receive 
Hi,

I'm getting an assertion failed on the receiving side, causing syncs to fail 
for one user. The servers are setup so that
only one is receiving any traffic other than replication at any time. The one 
that's only receiving replications is the
one that's failing.

I've tried deleting the user's home on the receiving server, but it still 
crashes during the sync. Oddly, the user's
home is 7.4G on the sending server, but ends up at 42G on the receiving side, 
even after deleting and trying a fresh sync.

The mailbox implicated in the backtrace ("Spam") does have a very large number 
of messages in it.
On sender:
Spam messages=1217764 recent=0 uidnext=1218103 uidvalidity=1379509105 unseen=16 
highestmodseq=744588 vsize=34468460093
guid=090ed93a7a09abf10200fdf6807a firstsaved=1498744186
On receiver:
Spam messages=1217766 recent=352 uidnext=1218105 uidvalidity=1379509105 
unseen=16 highestmodseq=744589 vsize=34468496809
guid=090ed93a7a09abf10200fdf6807a firstsaved=1519396172

Feb 23 14:57:20 dovecot: dsync-local(bgeels): Warning: fscking index file
/gnoc/mail/home/bgeels/mail/storage/dovecot.map.index
Feb 23 14:57:20 dovecot: dsync-local(bgeels): Warning: mdbox 
/gnoc/mail/home/bgeels/mail/storage: rebuilding indexes
Feb 23 14:57:33 dovecot: dsync-local(bgeels): Panic: file mail-index-util.c: 
line 10 (mail_index_uint32_to_offset):
assertion failed: (offset < 0x4000)
Feb 23 14:57:33 dovecot: dsync-local(bgeels): Error: Raw backtrace: 
/usr/lib64/dovecot/libdovecot.so.0(+0x9f3de)
[0x7feb584143de] -> /usr/lib64/dovecot/libdovecot.so.0(+0x9f4be) 
[0x7feb584144be] ->
/usr/lib64/dovecot/libdovecot.so.0(i_fatal+0) [0x7feb583a577c] ->
/usr/lib64/dovecot/libdovecot-storage.so.0(mail_index_uint32_to_offset+0xa0) 
[0x7feb587906d0] ->
/usr/lib64/dovecot/libdovecot-storage.so.0(mail_cache_compress+0x854) 
[0x7feb58774f34] ->
/usr/lib64/dovecot/libdovecot-storage.so.0(mail_index_sync_commit+0x25f) 
[0x7feb587884ff] ->
/usr/lib64/dovecot/libdovecot-storage.so.0(mdbox_storage_rebuild_in_context+0x10de)
 [0x7feb5870b3ae] ->
/usr/lib64/dovecot/libdovecot-storage.so.0(mdbox_sync_begin+0x858) 
[0x7feb5870ccd8] ->
/usr/lib64/dovecot/libdovecot-storage.so.0(mdbox_sync+0x4c) [0x7feb5870ce7c] ->
/usr/lib64/dovecot/libdovecot-storage.so.0(mdbox_storage_sync_init+0x4b) 
[0x7feb5870cf3b] ->
/usr/lib64/dovecot/libdovecot-storage.so.0(mailbox_sync_init+0x44) 
[0x7feb586f2834] ->
/usr/lib64/dovecot/libdovecot-storage.so.0(mailbox_sync+0x37) [0x7feb586f28d7] 
->
dovecot/doveadm-server(dsync_mailbox_import_deinit+0x475) [0x445495] -> 
dovecot/doveadm-server() [0x43edc0] ->
dovecot/doveadm-server(dsync_brain_sync_mails+0x743) [0x43f653] -> 
dovecot/doveadm-server(dsync_brain_run+0x541)
[0x43acf1] -> dovecot/doveadm-server() [0x43b070] -> dovecot/doveadm-server() 
[0x44fe5f] ->
/usr/lib64/dovecot/libdovecot.so.0(io_loop_call_io+0x52) [0x7feb58429cd2] ->
/usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x10f) 
[0x7feb5842b3bf] ->
/usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run+0x3c) [0x7feb58429d6c] ->
/usr/lib64/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7feb58429f28] -> 
dovecot/doveadm-server() [0x4209c5] ->
dovecot/doveadm-server() [0x422df6] -> dovecot/doveadm-server() [0x4377f4] ->
/usr/lib64/dovecot/libdovecot.so.0(io_loop_call_io+0x52) [0x7feb58429cd2] ->
/usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x10f) 
[0x7feb5842b3bf] ->
/usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run+0x3c) [0x7feb58429d6c]
Feb 23 14:57:33 dsync-local(bgeels): Fatal: master: service(doveadm): child 
82098 killed with signal 6 (core dumped)

I've attached the output of `doveconf -n` and the full backtrace from a core 
dump.

Dovecot 2.2.33.2 (GhettoForge package)
CentOS 7 x86_64
XFS, no NFS.


-- Ian

Assertion during dsync receive

2018-02-23 Thread Ian Bobbitt 
Hi,

I'm getting an assertion failed on the receiving side, causing syncs to fail 
for one user. The servers are setup so that
only one is receiving any traffic other than replication at any time. The one 
that's only receiving replications is the
one that's failing.

I've tried deleting the user's home on the receiving server, but it still 
crashes during the sync. Oddly, the user's
home is 7.4G on the sending server, but ends up at 42G on the receiving side, 
even after deleting and trying a fresh sync.

The mailbox implicated in the backtrace ("Spam") does have a very large number 
of messages in it.
On sender:
Spam messages=1217764 recent=0 uidnext=1218103 uidvalidity=1379509105 unseen=16 
highestmodseq=744588 vsize=34468460093
guid=090ed93a7a09abf10200fdf6807a firstsaved=1498744186
On receiver:
Spam messages=1217766 recent=352 uidnext=1218105 uidvalidity=1379509105 
unseen=16 highestmodseq=744589 vsize=34468496809
guid=090ed93a7a09abf10200fdf6807a firstsaved=1519396172

Feb 23 14:57:20 dovecot: dsync-local(bgeels): Warning: fscking index file
/gnoc/mail/home/bgeels/mail/storage/dovecot.map.index
Feb 23 14:57:20 dovecot: dsync-local(bgeels): Warning: mdbox 
/gnoc/mail/home/bgeels/mail/storage: rebuilding indexes
Feb 23 14:57:33 dovecot: dsync-local(bgeels): Panic: file mail-index-util.c: 
line 10 (mail_index_uint32_to_offset):
assertion failed: (offset < 0x4000)
Feb 23 14:57:33 dovecot: dsync-local(bgeels): Error: Raw backtrace: 
/usr/lib64/dovecot/libdovecot.so.0(+0x9f3de)
[0x7feb584143de] -> /usr/lib64/dovecot/libdovecot.so.0(+0x9f4be) 
[0x7feb584144be] ->
/usr/lib64/dovecot/libdovecot.so.0(i_fatal+0) [0x7feb583a577c] ->
/usr/lib64/dovecot/libdovecot-storage.so.0(mail_index_uint32_to_offset+0xa0) 
[0x7feb587906d0] ->
/usr/lib64/dovecot/libdovecot-storage.so.0(mail_cache_compress+0x854) 
[0x7feb58774f34] ->
/usr/lib64/dovecot/libdovecot-storage.so.0(mail_index_sync_commit+0x25f) 
[0x7feb587884ff] ->
/usr/lib64/dovecot/libdovecot-storage.so.0(mdbox_storage_rebuild_in_context+0x10de)
 [0x7feb5870b3ae] ->
/usr/lib64/dovecot/libdovecot-storage.so.0(mdbox_sync_begin+0x858) 
[0x7feb5870ccd8] ->
/usr/lib64/dovecot/libdovecot-storage.so.0(mdbox_sync+0x4c) [0x7feb5870ce7c] ->
/usr/lib64/dovecot/libdovecot-storage.so.0(mdbox_storage_sync_init+0x4b) 
[0x7feb5870cf3b] ->
/usr/lib64/dovecot/libdovecot-storage.so.0(mailbox_sync_init+0x44) 
[0x7feb586f2834] ->
/usr/lib64/dovecot/libdovecot-storage.so.0(mailbox_sync+0x37) [0x7feb586f28d7] 
->
dovecot/doveadm-server(dsync_mailbox_import_deinit+0x475) [0x445495] -> 
dovecot/doveadm-server() [0x43edc0] ->
dovecot/doveadm-server(dsync_brain_sync_mails+0x743) [0x43f653] -> 
dovecot/doveadm-server(dsync_brain_run+0x541)
[0x43acf1] -> dovecot/doveadm-server() [0x43b070] -> dovecot/doveadm-server() 
[0x44fe5f] ->
/usr/lib64/dovecot/libdovecot.so.0(io_loop_call_io+0x52) [0x7feb58429cd2] ->
/usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x10f) 
[0x7feb5842b3bf] ->
/usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run+0x3c) [0x7feb58429d6c] ->
/usr/lib64/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7feb58429f28] -> 
dovecot/doveadm-server() [0x4209c5] ->
dovecot/doveadm-server() [0x422df6] -> dovecot/doveadm-server() [0x4377f4] ->
/usr/lib64/dovecot/libdovecot.so.0(io_loop_call_io+0x52) [0x7feb58429cd2] ->
/usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x10f) 
[0x7feb5842b3bf] ->
/usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run+0x3c) [0x7feb58429d6c]
Feb 23 14:57:33 dsync-local(bgeels): Fatal: master: service(doveadm): child 
82098 killed with signal 6 (core dumped)

I've attached the output of `doveconf -n` and the full backtrace from a core 
dump.

Dovecot 2.2.33.2 (GhettoForge package)
CentOS 7 x86_64
XFS, no NFS.


-- Ian
GNU gdb (GDB) Red Hat Enterprise Linux 7.6.1-100.el7_4.1
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu".
For bug reporting instructions, please see:
...
Reading symbols from /usr/bin/doveadm...(no debugging symbols found)...done.
[New LWP 146391]
Core was generated by `/usr/bin/doveadm dsync-server -ubgeels -U'.
Program terminated with signal 6, Aborted.
#0  0x7fc20bc531f7 in raise () from /lib64/libc.so.6
Missing separate debuginfos, use: debuginfo-install 
dovecot22-2.2.33.2-2.gf.el7.x86_64
(gdb) #0  0x7fc20bc531f7 in raise () from /lib64/libc.so.6
No symbol table info available.
#1  0x7fc20bc548e8 in abort () from /lib64/libc.so.6
No symbol table info available.
#2  0x7fc20c0803d6 in default_fatal_finish (type=, 
status=status@entry=0) at failures.c:201
backtrace = 0x1bcdfd0 "/usr/lib64/dovecot/libdovecot.so.0(+0x9f3de) 
[0x7fc20c0803de

Re: Stale mailbox lock file

2018-02-23 Thread Raffaele Gambelli 

So you don't know when this piece of code is executed:


case MAILBOX_LOCK_NOTIFY_MAILBOX_OVERRIDE:if (storage->callbacks->notify_ok == NULL)
break;str = t_strdup_printf("Stale mailbox lock file detected, "
  "will override in %u seconds", secs_left);
storage->callbacks->notify_ok(&ibox->box, str,
  storage->callback_context);
break;}

> Also do you have some other process(es) that touch the mailbox?

Without having access to this dovecot installation, I can't answer your question, but which could be the problem if there were some other processes?


I try to reformulate question, is it possible that when dovecot sends that notification, it blocks and don't send any other notifications like for example when the count of messages in a folder is changed?
Raffaele Gambelli

-"dovecot"  ha scritto: -


Per: Raffaele Gambelli , dovecot@dovecot.org
Da: Aki Tuomi Inviato da: "dovecot" 
Data: 23/02/2018 12.10PMOggetto: Re: Stale mailbox lock file

Yes. I am one of them.
---
Aki TuomiDovecot oy
 Original message 
From: Raffaele Gambelli  
Date: 23/02/2018  12:25  (GMT+02:00) To: dovecot@dovecot.org 
Subject: Re: Stale mailbox lock file 

Thanks Aki,do you know if this list is read by dovecot developers team too? Could you point me to the right list otherwise?
Raffaele Gambelli
-Aki Tuomi  ha scritto: -

Per: Raffaele Gambelli Da: Aki Tuomi 
Data: 23/02/2018 11.22AMCc: dovecot@dovecot.orgOggetto: Re: Stale mailbox lock file
  
I have no idea how you'd even get that error then.
AkiOn 23.02.2018 12:07, Raffaele Gambelli
  wrote:

Thanks but what answer it mean "
doveconf -n"? 
I have neither control noraccess in the dovecot installation to which I'm connecting.
I'm waiting to know the dovecot version but it could be
  that for legal reasons I will never receive it.
So please, if you know it obviously, why and when a dovecot
  server sends that notice?
Thanks, byeRaffaele Gambelli
  
-Aki Tuomi  
 ha scritto: -
  
Per: Raffaele Gambelli
,
dovecot@dovecot.orgDa: Aki Tuomi 
Data: 23/02/2018 10.54AM
Oggetto: Re: Stale mailbox lock file

On 23.02.2018 11:41, Raffaele  Gambelli wrote:

  
Hi  all,  I would like to understand the meaning of "Stale
  mailbox lock file detected"  In index-storage.c (
https://mis.dopa.go.th/atmail/server_source/dovecot/src/lib-storage/index/index-storage.c
  ) there is this notice "Stale mailbox lock file  detected" ...
I have a java application which connects via javamail
  to a dovecot server and I have some anomalies when  that message comes.
Thanks, bye  
  Raffaele Gambelli  
This is third email you've sent about this...
doveconf -nAlso do you have some other process(es) that touch the
mailbox?Aki

Re: Multiple SSL-Certificates/Domains setup not working | Solved!

2018-02-23 Thread Gabriel Kaufmann 

Could you write step by step how you reach the goal?

2018-02-22 15:55 GMT+01:00 Gabriel Kaufmann >:


I've tried to create an certbot SAN-Cert with multiple domain-names 
and this worked like a charm using one cert for all! Thanks!



Shure :)

At first you should have a working Certbot of course. Setup for this 
depends on your Server-Setup of course. Certbot requires access due to 
"standalone-http(s)" mode of certbot or access through 
apache/nginx/haproxy (works as well if setup correctly). I'm using each 
of these variants.


Assuming you have a working setup and certbot-services can access your 
certbot service (running as http/s while certbot is running) the SAN 
setup is quit easy:



$> certbot -d domain1.com -d domain2.com -d domain3.com


if running in non-standalone mode (running apache/nginx) you can tell 
Certbot where the auth-tokens are stored to for external domain-approval:



-w /var/www/my-web-root
With the syntax given above the SAN-Cert for all given domains is stored 
in /etc/letsencrypt/live/domain1/


standalone-mode and web-root also can be configured in 
/etc/letsencrypt/cli.ini

(https://community.letsencrypt.org/t/lestencrypt-standalone-cli-ini/43465)

Best regards

Gabriel Kaufmann

Re: Stale mailbox lock file

2018-02-23 Thread Aki Tuomi 
Yes. I am one of them.


---Aki TuomiDovecot oy
 Original message From: Raffaele Gambelli 
 Date: 23/02/2018  12:25  (GMT+02:00) To: 
dovecot@dovecot.org Subject: Re: Stale mailbox lock file 

Thanks Aki,
do you know if this list is read by dovecot developers team too? Could you 
point me to the right list otherwise?


Raffaele Gambelli




-Aki Tuomi  ha scritto: -

Per: Raffaele Gambelli 
Da: Aki Tuomi 

Data: 23/02/2018 11.22AM
Cc: dovecot@dovecot.org
Oggetto: Re: Stale mailbox lock file


  
I have no idea how you'd even get that error then.

Aki

On 23.02.2018 12:07, Raffaele Gambelli
  wrote:


Thanks but what answer it mean "
doveconf -n"? 
I have neither control noraccess in the dovecot installation to 
which I'm connecting.

I'm waiting to know the dovecot version but it could be
  that for legal reasons I will never receive it.

So please, if you know it obviously, why and when a dovecot
  server sends that notice?

Thanks, bye
  
  Raffaele Gambelli

  

-Aki Tuomi  
 ha scritto: -
  
Per: Raffaele Gambelli
,
dovecot@dovecot.org
Da: Aki Tuomi 

Data: 23/02/2018 10.54AM

Oggetto: Re: Stale mailbox lock file





On 23.02.2018 11:41, Raffaele  Gambelli wrote:


  
Hi  all,
  I would like to understand the meaning of "Stale
  mailbox lock file detected"
  In index-storage.c (
https://mis.dopa.go.th/atmail/server_source/dovecot/src/lib-storage/index/index-storage.c
  ) there is this notice "Stale mailbox lock file   
   detected" ...

  
  I have a java application which connects via javamail
  to a dovecot server and I have some anomalies when
  that message comes.

  
  Thanks, bye
  

  Raffaele Gambelli
  


This is third email you've sent about this...


doveconf -n

Also do you have some other process(es) that touch the
mailbox?

Aki

Re: Stale mailbox lock file

2018-02-23 Thread Raffaele Gambelli 

Thanks Aki,do you know if this list is read by dovecot developers team too? Could you point me to the right list otherwise?
Raffaele Gambelli
-Aki Tuomi  ha scritto: -

Per: Raffaele Gambelli Da: Aki Tuomi 
Data: 23/02/2018 11.22AMCc: dovecot@dovecot.orgOggetto: Re: Stale mailbox lock file
  
I have no idea how you'd even get that error then.
AkiOn 23.02.2018 12:07, Raffaele Gambelli
  wrote:

Thanks but what answer it mean "
doveconf -n"? 
I have neither control noraccess in the dovecot installation to which I'm connecting.
I'm waiting to know the dovecot version but it could be
  that for legal reasons I will never receive it.
So please, if you know it obviously, why and when a dovecot
  server sends that notice?
Thanks, byeRaffaele Gambelli
  
-Aki Tuomi  
 ha scritto: -
  
Per: Raffaele Gambelli
,
dovecot@dovecot.orgDa: Aki Tuomi 
Data: 23/02/2018 10.54AM
Oggetto: Re: Stale mailbox lock file

On 23.02.2018 11:41, Raffaele  Gambelli wrote:

  
Hi  all,  I would like to understand the meaning of "Stale
  mailbox lock file detected"  In index-storage.c (
https://mis.dopa.go.th/atmail/server_source/dovecot/src/lib-storage/index/index-storage.c
  ) there is this notice "Stale mailbox lock file  detected" ...
I have a java application which connects via javamail
  to a dovecot server and I have some anomalies when  that message comes.
Thanks, bye  
  Raffaele Gambelli  
This is third email you've sent about this...
doveconf -nAlso do you have some other process(es) that touch the
mailbox?Aki

Re: Stale mailbox lock file

2018-02-23 Thread Aki Tuomi 
I have no idea how you'd even get that error then.

Aki


On 23.02.2018 12:07, Raffaele Gambelli wrote:
> Thanks but what answer it mean "doveconf -n"? 
> I have neither control nor access in the dovecot installation to which
> I'm connecting.
>
> I'm waiting to know the dovecot version but it could be that for legal
> reasons I will never receive it.
>
> So please, if you know it obviously, why and when a dovecot server
> sends that notice?
>
> Thanks, bye
>
> Raffaele Gambelli
>
> -Aki Tuomi  ha scritto: -
> Per: Raffaele Gambelli ,
> dovecot@dovecot.org
> Da: Aki Tuomi 
> Data: 23/02/2018 10.54AM
> Oggetto: Re: Stale mailbox lock file
>
>
>
> On 23.02.2018 11:41, Raffaele Gambelli wrote:
>> Hi all,
>> I would like to understand the meaning of "Stale mailbox lock file
>> detected"
>> In index-storage.c
>> (https://mis.dopa.go.th/atmail/server_source/dovecot/src/lib-storage/index/index-storage.c
>> ) there is this notice "Stale mailbox lock file detected" ...
>>
>> I have a java application which connects via javamail to a dovecot
>> server and I have some anomalies when that message comes.
>>
>> Thanks, bye
>>
>> Raffaele Gambelli
>>
>
> This is third email you've sent about this...
>
> doveconf -n
>
> Also do you have some other process(es) that touch the mailbox?
>
> Aki

Re: Stale mailbox lock file

2018-02-23 Thread Raffaele Gambelli 

Thanks but what answer it mean "doveconf -n"? 
I have neither control nor access in the dovecot installation to which I'm connecting.
I'm waiting to know the dovecot version but it could be that for legal reasons I will never receive it.
So please, if you know it obviously, why and when a dovecot server sends that notice?
Thanks, byeRaffaele Gambelli
-Aki Tuomi  ha scritto: -

Per: Raffaele Gambelli , dovecot@dovecot.org
Da: Aki Tuomi Data: 23/02/2018 10.54AM
Oggetto: Re: Stale mailbox lock file  
On 23.02.2018 11:41, Raffaele Gambelli
  wrote:
  Hi all,
I would like to understand the meaning of "Stale mailbox lock file detected"
In index-storage.c (
https://mis.dopa.go.th/atmail/server_source/dovecot/src/lib-storage/index/index-storage.c
) there is this notice "Stale mailbox lock file detected" ...I have a java application which connects via javamail to a dovecot server and I have some anomalies when that message comes.
Thanks, byeRaffaele Gambelli
This is third email you've sent about this...doveconf -n
Also do you have some other process(es) that touch the mailbox?
Aki

Re: Stale mailbox lock file

2018-02-23 Thread Aki Tuomi 


On 23.02.2018 11:41, Raffaele Gambelli wrote:
> Hi all,
> I would like to understand the meaning of "Stale mailbox lock file detected"
> In index-storage.c 
> (https://mis.dopa.go.th/atmail/server_source/dovecot/src/lib-storage/index/index-storage.c)
>  there is this notice "Stale mailbox lock file detected" ...
>
> I have a java application which connects via javamail to a dovecot server and 
> I have some anomalies when that message comes.
>
> Thanks, bye
>
> Raffaele Gambelli
>

This is third email you've sent about this...

doveconf -n

Also do you have some other process(es) that touch the mailbox?

Aki

Stale mailbox lock file

2018-02-23 Thread Raffaele Gambelli 
Hi all,
I would like to understand the meaning of "Stale mailbox lock file detected"
In index-storage.c 
(https://mis.dopa.go.th/atmail/server_source/dovecot/src/lib-storage/index/index-storage.c)
 there is this notice "Stale mailbox lock file detected" ...

I have a java application which connects via javamail to a dovecot server and I 
have some anomalies when that message comes.

Thanks, bye

Raffaele Gambelli

Re: preferred way to move an imap folder

2018-02-23 Thread himbeere 


Thank you.

cheers
t.

On 2018-02-22 18:04, Aki Tuomi wrote:

On 22 February 2018 at 18:53 "@lbutlr" < krem...@kreme.com> wrote:

On 2018-02-22 (07:48 MST), himbe...@shinymail.de wrote:


Hello list.

What is the preferred way to move an imap folder. Lets say an
User has.

.maildir/.INBOX.Junk

I want to move this imap folder to:

.maildir/.Junk

Can i just use:

mv .maildir/.INBOX.Junk .maildir/.Junk

and be done with that?


Yes, but if the mailbox is defined as being under .INBOX it will
recreate it.

--
'But you ain't part of it, are you?' said Granny conversationally.
'You
try, but you always find yourself watchin' yourself watchin'
people, eh?
Never quite believin' anything? Thinkin' the wrong thoughts?'


 or you can use doveadm mailbox rename
 ---
Aki Tuomi

Re: Optimizing search performance for mobile devices / web mailer / general - solr plugin config

2018-02-23 Thread Peter Chiochetti 

Hello Götz,

As an intermediate skill level admin I found it not too hard. The 
dovecot part was easier than the solr one, mostly as I am stuck on an 
old system.


Solr indeed is blazingly fast. Searching several imap (sub)folders slows 
it down a bit, because imap only always searches a single one and then 
another one and so on. A proposed rfc to tackle that does not move forward.


There is a trick to have messages indexed on arrival, instead of at 
mailbox access, "fts_autoindex = yes" in the plugin section. This is not 
mentioned in the dovecot wiki page but might be useful.


In solr schema.xml I put some extra "copyField" stances, so from, to, 
and subject get indexed with body. My users are mostly on thunderbird, 
which only does body searches on the server.


Happy Hacking

Peter


Am 23.02.18 um 08:55 schrieb Götz Reinicke:

Hi all,

we run dovecot for a long time now with no complains from the users … 
until this week. Some users say, the search in mailfolders from iPhone 
(which only stores a few mails and search most on the server as I know) 
or our web mailer (SOGo, which I currently search also on the imap 
server) is „slow“.


As this is sort of individual experience, I was thinking of ways to 
speed up the search and came across the fts_solr plugin.


My question is, can I „just“ configure the its_solg plugin as described 
at the dovecot wiki? https://wiki.dovecot.org/Plugins/FTS/Solr


How difficult is is to set up a solr server for that purpose? As our 
current mail hardware is not busy at all, is it ok to install Solr on 
the same hardware/server?


May be someone using that setup can give me some hints?

And: How hard is it to switch back to the „build in“ default search if 
we don’t see any benefit from hosting a solr server too.



Thanks for feedback and suggestions . Regards . Götz

Optimizing search performance for mobile devices / web mailer / general - solr plugin config

2018-02-23 Thread Götz Reinicke 
Hi all,

we run dovecot for a long time now with no complains from the users … until 
this week. Some users say, the search in mailfolders from iPhone (which only 
stores a few mails and search most on the server as I know) or our web mailer 
(SOGo, which I currently search also on the imap server) is „slow“.

As this is sort of individual experience, I was thinking of ways to speed up 
the search and came across the fts_solr plugin.

My question is, can I „just“ configure the its_solg plugin as described at the 
dovecot wiki? https://wiki.dovecot.org/Plugins/FTS/Solr 


How difficult is is to set up a solr server for that purpose? As our current 
mail hardware is not busy at all, is it ok to install Solr on the same 
hardware/server?

May be someone using that setup can give me some hints?

And: How hard is it to switch back to the „build in“ default search if we don’t 
see any benefit from hosting a solr server too.


Thanks for feedback and suggestions . Regards . Götz




smime.p7s
Description: S/MIME cryptographic signature