Re: Calendar function ?

2018-10-22 Thread María Arrea


    We use sabredav for caldav+cardav and roundcube+agendav for nice 
web ui :)


    Regards

El 21/10/18 a las 15:04, Erwan David escribió:

Le 10/21/18 à 12:29, m...@caloro.ch a écrit :


Hello

I running no long time with me Email System Postfix/Dovecot/mysql and 
i’am whery happy


the feature to synchroize Calendar, or view the calender entry from 
me workpartner i will miss


this feature, how do you handle this ? isn’t possible to insert this 
to Dovecot or Postfix?


Are this question out of topic ? or how do you implement this in our 
envirement ?


Regards

Mauri


I use the caldav features of nextcloud for tjis





Re: Error: stat no such file or directory with 2.2.33.2

2017-12-13 Thread María Arrea


    Hello Timo, this is the content of path 
/indices_dovecot/indices/11/21/espi/mailboxes/CURSOS/ACCION SOCIAL



-rw--- 1 entrega entrega 304 dic 13 08:41 dovecot.index
-rw--- 1 entrega entrega  40 dic 13 08:41 dovecot.index.log
-rw--- 1 entrega entrega 392 dic 13 08:41 dovecot.index.log.2


    In today logs I have not found any "No such file or directory" so 
far.  If I can do something to help you debug this, ask for in in this 
thread.


    Regards

    María.

El 13/12/17 a las 20:09, Timo Sirainen escribió:

On 13 Dec 2017, at 9.55, María Arrea <maria.ar...@gmx.com> wrote:


 We have upgraded today from Dovecot 2.2.31 to Dovecot 2.2.33.2 and 
modified our config to include ITERINDEX in mail_location and we are detecting 
some errors like this:


/Dec 13 08:17:31 buzon_rhel7 dovecot: imap(rboloix): Error: 
stat(/buzones/location/18/48/rboloix/mailboxes/SIT - Pra 
2014/dbox-Mails) failed: No such file or directory//
//Dec 13 08:40:24 buzon_rhel7 dovecot: imap(espi): Error: 
stat(/buzones/location/11/21/espi/mailboxes/CURSOS/ACCION SOCIAL/dbox-Mails) 
failed: No such file or directory//
//Dec 13 08:40:25 buzon_rhel7 dovecot: imap(espi: Error: 
stat(/buzones/location/11/21/espi/mailboxes/CURSOS/ACCION SOCIAL/dbox-Mails) 
failed: No such file or directory//
//Dec 13 08:41:59 buzon_rhel7 dovecot: imap(espi): Error: 
stat(/buzones/location/11/21/espi/mailboxes/CURSOS/ACCION SOCIAL/dbox-Mails) 
failed: No such file or directory/

I think /indices_dovecot/indices/11/21/espi/mailboxes/CURSOS/ACCION 
SOCIAL/dbox-Mails exists, but this one doesn't? So it's a desync between what 
exists and what doesn't. A fix would be to either delete the folder from the 
indices_dovecot or mkdir this missing directory back. I guess it would be nice 
if Dovecot would mkdir it back automatically. Although I don't know where the 
stat() errors are coming from exactly - I tried a few tests and I could get a 
different error by trying to APPEND to the folder, but couldn't figure out how 
to trigger a stat() error.





Re: New Dovecot service: SMTP Submission (RFC6409)

2017-12-13 Thread María Arrea


    Stephan, thank you very much for your hard work. I want to ask your 
opinion about jmap ( http://jmap.io/ ) , do you think is a viable 
alternative to current IMAP + MSA ?


    Regards

    María

El 12/12/17 a las 00:14, Stephan Bosch escribió:

Hi,

As some of you know, I started implementing the SMTP submission proxy a
few years ago. It acts as a front-end for any MTA, adding the necessary
functionality for an SMTP submission service, also known as a Mail
Submission Agent (MSA) (https://tools.ietf.org/html/rfc6409). The main
reason I created this, back then, was implementing the BURL capability
(https://tools.ietf.org/html/rfc4468). The main application of that
capability -- together with IMAP URLAUTH -- is avoiding a duplicate
upload of submitted e-mail messages; normally the message is both sent
through SMTP and uploaded to the "Sent" folder through IMAP. Using BURL,
the client can first upload the message to IMAP and then use BURL to
make the SMTP server fetch the message from IMAP for submission, thereby
avoiding a second upload. Apart from BURL, the submission proxy service
also adds the required AUTH support, avoiding the need to configure the
MTA for SASL authentication. More SMTP capabilities like CHUNKING and
SIZE are supported, without requiring the backend MTA supporting these
extensions. Other capabilities like DSN currently require support from
the backend/relay MTA.

At this point, the submission proxy is still pretty basic. However, it
will provide a basis for adding all kinds of functionality in the (not
so distant) future. For the first time, it will be possible to act upon
message submission, rather than only message retrieval; e.g. plugins can
be devised that process outgoing messages somehow. Examples of the
things we could do are adding Sieve filtering support for outgoing
messages, or implicitly storing submitted messages to the Sent folder.
Once a plugin API is devised, you can create your own plugins.

The reason I send this message now, is that this code is finally merged
into the Dovecot master repository. This means that it is part of the
upcoming 2.3 release. Now that it is merged, you can install and test it
from Github if you like. Feedback is of course appreciated. The
documentation is still pretty sparse, but there is currently not much to
configure. Just add "submission" to the protocols and configure the
relay MTA server. The configuration is currently only documented in the
example configuration in doc/example-config/conf.d/20-submission.conf.
The submission service is a login service, just like IMAP, POP3 and
ManageSieve, so clients are required to authenticate. The same
authentication configuration will also apply to submission, unless
you're doing protocol-specific things, in which case you may need to
amend your configuration for the new protocol. BURL support requires a
working IMAP URLAUTH implementation.

I've updated the automated Xi Debian package builder to create an
additional dovecot-submissiond package. So, if you're using the Xi
packages, you only need to install that package and configure the relay MTA.

Regards,

Stephan.









Error: stat no such file or directory with 2.2.33.2

2017-12-12 Thread María Arrea


    We have upgraded today from Dovecot 2.2.31 to Dovecot 2.2.33.2 and 
modified our config to include ITERINDEX in mail_location and we are 
detecting some errors like this:



/Dec 13 08:17:31 buzon_rhel7 dovecot: imap(rboloix): Error: 
stat(/buzones/location/18/48/rboloix/mailboxes/SIT - Pra 
2014/dbox-Mails) failed: No such file or directory//
//Dec 13 08:40:24 buzon_rhel7 dovecot: imap(espi): Error: 
stat(/buzones/location/11/21/espi/mailboxes/CURSOS/ACCION 
SOCIAL/dbox-Mails) failed: No such file or directory//
//Dec 13 08:40:25 buzon_rhel7 dovecot: imap(espi: Error: 
stat(/buzones/location/11/21/espi/mailboxes/CURSOS/ACCION 
SOCIAL/dbox-Mails) failed: No such file or directory//
//Dec 13 08:41:59 buzon_rhel7 dovecot: imap(espi): Error: 
stat(/buzones/location/11/21/espi/mailboxes/CURSOS/ACCION 
SOCIAL/dbox-Mails) failed: No such file or directory/


    I have grepped logs of past 4 weeks and have not found this errors 
with Dovecot 2.2.31. Any idea of what is going on?



    Full doveconf -n output below:


/# 2.2.33.2 (d6601f4ec): /etc/dovecot/dovecot.conf
# Pigeonhole version 0.4.21 (92477967)
# OS: Linux 3.10.0-693.11.1.el7.x86_64 x86_64 Red Hat Enterprise Linux 
Server release 7.4 (Maipo) xfs

auth_cache_negative_ttl = 10 secs
auth_cache_size = 10 M
auth_cache_ttl = 2 mins
auth_master_user_separator = *
auth_mechanisms = plain login
auth_worker_max_count = 5500
base_dir = /var/run/dovecot/
default_client_limit = 5000
default_process_limit = 6500
disable_plaintext_auth = no
imap_capability = +XLIST
imap_client_workarounds = tb-extra-mailbox-sep delay-newmail tb-lsub-flags
lda_mailbox_autocreate = yes
lda_mailbox_autosubscribe = yes
mail_fsync = never
mail_gid = entrega
mail_home = /buzones/location/%2.26Hn/%2.200Hn/%n/home_usuario/
mail_location = 
mdbox:/buzoneslocation//%2.26Hn/%2.200Hn/%n:ITERINDEX:INDEX=/indices_dovecot/indices/%2.26Hn/%2.200Hn/%n:ALT=/buzones/alternativolocation//%2.26Hn/%2.200Hn/%n

mail_max_userip_connections = 15000
mail_plugins = " zlib acl quota virtual mail_log notify"
mail_uid = entrega
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

mdbox_purge_preserve_alt = yes
mdbox_rotate_interval = 1 days
mdbox_rotate_size = 60 M
namespace {
  inbox = yes
  location =
  mailbox Drafts {
    auto = subscribe
    special_use = \Drafts
  }
  mailbox SPAM {
    auto = subscribe
    special_use = \Junk
  }
  mailbox Sent {
    auto = subscribe
    special_use = \Sent
  }
  mailbox Trash {
    auto = subscribe
    special_use = \Trash
  }
  prefix =
  type = private
}
namespace {
  list = yes
  location = 
mdbox:/buzoneslocation//%%2.26Hn/%%2.200Hn/%%n:ALT=/buzones/alternativolocation//%%2.26Hn/%%2.200Hn/%%n:INDEX=/indices_dovecot/indices/%%2.26Hn/%%2.200Hn/%%n:INDEXPVT=~/mdbox/carpeta_compartida/%%u

  prefix = carpeta_compartida/%%u/
  separator = /
  subscriptions = no
  type = shared
}
namespace {
  list = yes
  location = 
virtual:/etc/dovecot/virtual:INDEX=~/mdbox/virtual:CONTROL=~/mdbox/virtual

  prefix = Carpetas_virtuales/
  separator = /
}
passdb {
  args = /etc/dovecot/deny
  deny = yes
  driver = passwd-file
}
passdb {
  args = /etc/dovecot/dovecot-ldap.conf
  driver = ldap
}
passdb {
  args = /etc/dovecot/dovecot-ldap.conf
  driver = ldap
}
plugin {
  acl = vfile
  acl_shared_dict = file:/buzoneslocation//acls_compartidas.db
  lda_mailbox_autosubscribe = yes
  mail_log_events = delete undelete expunge copy mailbox_delete 
mailbox_rename

  mail_log_fields = uid box msgid size subject from
  quota = dict:Cuota de usuario::file:/buzones/cuotas/%n
  quota_rule2 = Trash:storage=+10%%
  quota_warning = storage=90%% aviso_cuota 90 %u
  sieve = 
/buzoneslocation//%2.26Hn/%2.200Hn/%n/home_usuario/dovecot.sieve

  sieve_dir = /buzoneslocation//%2.26Hn/%2.200Hn/%n/home_usuario/sieve/
  zlib_save = gz
  zlib_save_level = 9
}
pop3_no_flag_updates = yes
protocols = pop3 imap sieve
service anvil {
  client_limit = 25000
}
service auth {
  client_limit = 32000
  unix_listener auth-master {
    user = entrega
  }
  unix_listener auth-userdb {
    user = entrega
  }
  user = root
}
service aviso_cuota {
  executable = script /usr/local/bin/quota-warning.sh
  unix_listener aviso_cuota {
    mode = 0666
  }
  user = entrega
}
service config {
  process_min_avail = 4
}
service imap-login {
  executable = /usr/libexec/dovecot/imap-login
  group = dovenull
  process_min_avail = 2
  service_count = 0
  vsz_limit = 1 G
}
service imap {
  executable = /usr/libexec/dovecot/imap
  process_limit = 8000
  process_min_avail = 12
  vsz_limit = 1 G
}
service managesieve-login {
  executable = /usr/libexec/dovecot/managesieve-login
  inet_listener sieve {
    port = 2000
  }
  process_limit = 2000
  vsz_limit = 1 G
}
service managesieve {
  

Re: Recommended tool for migrating IMAP servers

2017-12-05 Thread María Arrea
    We migrated 36 TB of mail (65K users) from Sun Messaging to Dovecot 
using Imapsync, worked like a charm.


    Regards

    María


Re: How to limit Apple Mail (desktop)?

2017-11-02 Thread María Arrea

El 31/10/17 a las 15:30, Robert Schetterer escribió:

Am 31.10.2017 um 14:06 schrieb María Arrea:

    If you use Linux you can use netfilter (iptables) mark feature to
track individual connections from a given IP, and above a threshold you
can shape the bandwitdh based on those iptables mark. For example, if an
IMAP connection from ip X exceed 100 megabytes of data, bandwitdh for
that ip would be limited to 100 KB/sec (or whatever number). First 100
megabytes, top speed, above that they get slower.

dont think this will work
tons of cons can come from a nat ip
so you would punish everyone behind that ip ,not only apple mail


Not true. You set a connection tracking using ip+port, not only IP.



i see no real solution for the problem, cause if the server works out
some slow down this would only lead to longer download times, but will
no solve the orig wanted task. It will all be workarounds for a "buggy"
client



    Original post talked about "unbearable server load". Shapping 
network traffic will definitely help with that.



    María.


Re: How to limit Apple Mail (desktop)?

2017-10-31 Thread María Arrea


   If you use Linux you can use netfilter (iptables) mark feature to 
track individual connections from a given IP, and above a threshold you 
can shape the bandwitdh based on those iptables mark. For example, if an 
IMAP connection from ip X exceed 100 megabytes of data, bandwitdh for 
that ip would be limited to 100 KB/sec (or whatever number). First 100 
megabytes, top speed, above that they get slower.


    Regards

    María


El 30/10/17 a las 10:38, Rupert Gallagher escribió:

By default, Apple Mail downloads all e-mails from  server's account. Previous 
versions of this client allowed to opt-out. The latest two versions? however, 
only allow to opt-out from downloading the attachments.

The stress on the server is unbearable. We cannot ask users to be considerate: 
this is the default behaviour of Apple Mail.

We need a server-side solution to the problem.

Please share your ideas.


Re: Question about ITERINDEX in 2.2.32

2017-10-16 Thread María Arrea


Thank you Mr. Aki

    Should this info about ITERINDEX be present in 
https://wiki.dovecot.org/MailLocation ? Bit confusing now.


El 16/10/17 a las 12:35, Aki Tuomi escribió:


On 16.10.2017 13:30, María Arrea wrote:

El 16/10/17 a las 12:25, Aki Tuomi escribió:

ITERINDEX is a flag, it's not supposed to have any value.

Aki

So ITERINDEX=yes should be the right value? This is the right
mail_location settings?

mail_location=mdbox:/buzones/domain/%2.26Hn/%2.200Hn/%n:ITERINDEX=yes:INDEX=/indices_dovecot/indices/%2.26Hn/%2.200Hn/%n:ALT=/buzones/alternativo/domain/%2.26Hn/%2.200Hn/%n




Precisely correct value is just INTERINDEX. No yes or no.

Aki





On 16.10.2017 13:22, María Arrea wrote:

  I have tested putting the same value in ITERINDEX & INDEX, is this
the expected?

  Regards

  María

El 07/09/17 a las 08:44, María Arrea escribió:

Hello

  I have a question about the new setting ITERINDEX. This is my
filesystem layout

  /indices_dovecot : 8 x Fast SSD drives
  /buzones : 32x SAS 10k rpm disks
  /buzones/alternativo : 24 x SAS 7.2k rpm slow disks

  This is my mail_location:

mail_location =
mdbox:/buzones/domain/%2.26Hn/%2.200Hn/%n:INDEX=/indices_dovecot/indices/%2.26Hn/%2.200Hn/%n:ALT=/buzones/alternativo/domain/%2.26Hn/%2.200Hn/%n




  What should I write in mail_location with the new ITERINDEX
setting?

  Regards

  María


Re: Question about ITERINDEX in 2.2.32

2017-10-16 Thread María Arrea

El 16/10/17 a las 12:25, Aki Tuomi escribió:

ITERINDEX is a flag, it's not supposed to have any value.

Aki
So ITERINDEX=yes should be the right value? This is the right 
mail_location settings?


mail_location=mdbox:/buzones/domain/%2.26Hn/%2.200Hn/%n:ITERINDEX=yes:INDEX=/indices_dovecot/indices/%2.26Hn/%2.200Hn/%n:ALT=/buzones/alternativo/domain/%2.26Hn/%2.200Hn/%n







On 16.10.2017 13:22, María Arrea wrote:

     I have tested putting the same value in ITERINDEX & INDEX, is this
the expected?

     Regards

     María

El 07/09/17 a las 08:44, María Arrea escribió:

Hello

     I have a question about the new setting ITERINDEX. This is my
filesystem layout

     /indices_dovecot : 8 x Fast SSD drives
     /buzones : 32x SAS 10k rpm disks
     /buzones/alternativo : 24 x SAS 7.2k rpm slow disks

     This is my mail_location:

mail_location =
mdbox:/buzones/domain/%2.26Hn/%2.200Hn/%n:INDEX=/indices_dovecot/indices/%2.26Hn/%2.200Hn/%n:ALT=/buzones/alternativo/domain/%2.26Hn/%2.200Hn/%n



     What should I write in mail_location with the new ITERINDEX setting?

     Regards

     María


Re: Question about ITERINDEX in 2.2.32

2017-10-16 Thread María Arrea


    I have tested putting the same value in ITERINDEX & INDEX, is this 
the expected?


    Regards

    María

El 07/09/17 a las 08:44, María Arrea escribió:

Hello

    I have a question about the new setting ITERINDEX. This is my 
filesystem layout


    /indices_dovecot : 8 x Fast SSD drives
    /buzones : 32x SAS 10k rpm disks
    /buzones/alternativo : 24 x SAS 7.2k rpm slow disks

    This is my mail_location:

mail_location = 
mdbox:/buzones/domain/%2.26Hn/%2.200Hn/%n:INDEX=/indices_dovecot/indices/%2.26Hn/%2.200Hn/%n:ALT=/buzones/alternativo/domain/%2.26Hn/%2.200Hn/%n 




    What should I write in mail_location with the new ITERINDEX setting?

    Regards

    María


Question about ITERINDEX in 2.2.32

2017-09-07 Thread María Arrea

Hello

I have a question about the new setting ITERINDEX. This is my 
filesystem layout


/indices_dovecot : 8 x Fast SSD drives
/buzones : 32x SAS 10k rpm disks
/buzones/alternativo : 24 x SAS 7.2k rpm slow disks

This is my mail_location:

mail_location = 
mdbox:/buzones/domain/%2.26Hn/%2.200Hn/%n:INDEX=/indices_dovecot/indices/%2.26Hn/%2.200Hn/%n:ALT=/buzones/alternativo/domain/%2.26Hn/%2.200Hn/%n 




What should I write in mail_location with the new ITERINDEX setting?

Regards

María


Re: v2.2.32 released

2017-09-04 Thread María Arrea

Hello

I have a question about the new setting ITERINDEX. This is my 
filesystem layout


/indices_dovecot : 8 x Fast SSD drives
/buzones : 32x SAS 10k rpm disks
/buzones/alternativo : 24 x SAS 7.2k rpm slow disks

This is my mail_location:

mail_location = 
mdbox:/buzones/domain/%2.26Hn/%2.200Hn/%n:INDEX=/indices_dovecot/indices/%2.26Hn/%2.200Hn/%n:ALT=/buzones/alternativo/domain/%2.26Hn/%2.200Hn/%n



What should I write in mail_location with the new ITERINDEX setting?

Regards

María


El 24/08/17 a las 16:08, Timo Sirainen escribió:

https://dovecot.org/releases/2.2/dovecot-2.2.32.tar.gz
https://dovecot.org/releases/2.2/dovecot-2.2.32.tar.gz.sig

Two more fixes since rc2. And repeating:

There are various changes in this release that can be used to significantly 
reduce disk IO with:
1) NFS storage especially, but I guess also other remote filesystems and even 
some with local disks
2) When mail storage and INDEX storage are separated

  * imapc: Info-level line is logged every time when successfully
connected to the remote server. This includes local/remote IP/port,
which can be useful for matching against external logs.
  * config: Log a warning if plugin { key=no } is used explicitly.
v2.3 will support "no" properly in plugin settings, but for now
any value at all for a boolean plugin setting is treated as "yes",
even if it's written as explicit "no". This change will now warn
that it most likely won't work as intended.

  + Various optimizations to avoid accessing files/directories when it's
not necessary. Especially avoid accessing mail root directories when
INDEX directories point to a different filesystem.
  + mail_location can now include ITERINDEX parameter. This tells Dovecot
to perform mailbox listing from the INDEX path instead of from the
mail root path. It's mainly useful when the INDEX storage is on a
faster storage.
  + mail_location can now include VOLATILEDIR= parameter. This
is used for creating lock files and in future potentially other
files that don't need to exist permanently. The path could point to
tmpfs for example. This is especially useful to avoid creating lock
files to NFS or other remote filesystems. For example:
mail_location=sdbox:~/sdbox:VOLATILEDIR=/tmp/volatile/%2.256Nu/%u
  + mail_location's LISTINDEX= can now contain a full path.
This allows storing mailbox list index to a different storage
than the rest of the indexes, for example to tmpfs.
  + mail_location can now include NO-NOSELECT parameter. This
automatically deletes any \NoSelect mailboxes that have no children.
These mailboxes are sometimes confusing to users.
  + mail_location can now include BROKENCHAR= parameter. This can
be useful with imapc to access mailbox names that aren't valid mUTF-7
charset from remote servers.
  + If mailbox_list_index_very_dirty_syncs=yes, the list index is no
longer refreshed against filesystem when listing mailboxes. This
allows the mailbox listing to be done entirely by only reading the
mailbox list index.
  + Added mailbox_list_index_include_inbox setting to control whether
INBOX's STATUS information should be cached in the mailbox list
index. The default is "no", but it may be useful to change it to
"yes", especially if LISTINDEX points to tmpfs.
  + userdb can return chdir=, which override mail_home for the
chdir location. This can be useful to avoid accessing home directory
on login.
  + userdb can return postlogin= to specify per-user imap/pop3
postlogin socket path.
  + cassandra: Add support for result paging by adding page_size=
parameter to the connect setting.
  + dsync/imapc, pop3-migration plugin: Strip also trailing tabs from
headers when matching mails. This helps with migrations from Zimbra.
  + imap_logout_format supports now %{appended} and %{autoexpunged}
  + virtual plugin: Optimize IDLE to use mailbox list index for finding
out when something has changed.
  + Added apparmor plugin. See https://wiki2.dovecot.org/Plugins/Apparmor
  - virtual plugin: A lot of fixes. In many cases it was also working
very inefficiently or even incorrectly.
  - imap: NOTIFY parameter parsing was incorrectly "fixed" in v2.2.31.
It was actually (mostly) working in previous versions, but broken
in v2.2.31.
  - Modseq tracking didn't always work correctly. This could have caused
imap unhibernation to fail or IMAP QRESYNC/CONDSTORE extensions to
not work perfectly.
  - mdbox: "Inconsistency in map index" wasn't fixed automatically
  - dict-ldap: %variable values used in the LDAP filter weren't escaped.
  - quota=count: quota_warning = -storage=.. was never executed (try #2).
v2.2.31 fixed it for -messages, but not for -storage.
  - imapc: >= 32 kB mail bodies were supposed to be cached for subsequent
FETCHes, but weren't.
  - quota-status service didn't support recipient_delimiter
  

Dovecot + SAN with dedup+compression

2016-10-04 Thread María Arrea

Hello

We have a big Dovecot Server (over 20 TB of mail, 40K users, over 
30K iops) and we are evaluating a new SAN Array. We have competitive 
proposals from Pure Storage (All Flash) , HP 3Par (Hybrid), NetApp FaaS 
(Hybrid) & EMC Unity (Hybrid). We rely in mdbox+zlib for main storage 
and mdbox+lzma for secondary storage, does anybody in the list have 
experience with SAN-based deduplication/compression?

Regards
Maria.