Re: Timeout when opening folder

[infoomatic via dovecot]

My guess is that this is a kubernetes specific issue and not a dovecot
issue.

Please provide kubernetes logs. Also: how is your storage implemented?
Any chance more than one dovecot instance are accessing that storage? Is
the storage available on the node where the container runs?

Regards,
Robert


On 24.06.24 23:52, Entrepreneur AJ via dovecot wrote:

Hi all, I'm stuck with an issue.

Migrating everything to a k0s kubernetes cluster, trying to migrate
dovecot and all so far seems to be well with PVC for mail storage, ssl
working great, authentication vis PostgreSQL working great.

Issue is when trying to look at another folder say Deleted or Spam etc
folder I am getting a timeout error with no logs.

___
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-le...@dovecot.org

Re: Which DKIM application for postfix 3.9.0

[infoomatic via dovecot]

Just for completeness sake I will throw some in:

*) https://launchpad.net/dkimpy-milter
*) https://lib.rs/crates/dkim-milter
*) https://github.com/fastmail/authentication_milter

I have not yet had time to look at them, so no comment on their usability.

regards,
Robert


On 24.04.24 00:06, Joseph Tam via dovecot wrote:

On Tue, Apr 23, 2024 at 7:33 AM  wrote:


I am upgrading to postfix 3.9.0. I have not used DKIM in previous postfix 
installs, but I
would like to start now with the new google rules. I have done some research 
and opendkim
  is the most recommended, however, other research states the opendkim has been
abandoned by it's maintainers. So I am looking for a good alternative dkim 
software
that will work with postfix that I can compile myself. I do not run on any linux
version, so therefore I can not just apt-get a new dkim application.
I run Solaris and therefore need to compile my applications, postfix and dkim.
Any good suggestions will be appreciated.


I just rolled out a locally compiled opendkim on my mail server. It
works, but there
are a few gotchas.

Although it seems like a moribund project, there is a late beta
version that includes
some important patches, most notably the "Header:\n LongHeaderValue" bug that
needs fixing.  You can look at

 https://sourceforge.net/p/opendkim/patches/

to find that patch, as well as others you deem important.  As DKIM standards
are not going to change soon, having end-of-line software is not as
bad as it seems
unless you need particular enhancements to make it work better in your
circumstances.
Once you get your setup dialed, you can probably set it and forget it.

Most of the headaches have actually been internal: local mail
injection via sendmail
would skip miltering, From header canonicalization by the MTA would not be
seen by the opendkim milter thereby creating messages with missing or invalid
signatures, and mailing list/auto reply/forwarder software mangling messages.

I think Postfix does a better job in this regard, so these issues may
not present itself.
(I did a Postfix/opendkim milter on an Ubuntu system and it was much
less hassle.)

You should look at *lots* of DMARC RUA reports.  People are doing crazy batsh*t
stuff with your mail domain.

Joseph Tam 
___
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-le...@dovecot.org

___
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-le...@dovecot.org

Re: Backing up m(d)box - rsync?

[infoomatic]

https://github.com/tachtler/dovecot-backup


On 16.08.23 16:45, Gareth Evans wrote:

Thanks Sven but I get a 404 from that link.
Gareth


On 16 Aug 2023, at 15:21, sven_roellig via dovecot  wrote:

i use https://github.com/tachtler/dovecot-backupregards sven
 Ursprüngliche Nachricht Von: donots...@fastmail.fm Datum: 16.08.23  15:29  
(GMT+01:00) An: dovecot@dovecot.org Betreff: Backing up m(d)box - rsync? Hello,I manage a small 
number of email accounts for a voluntary organisation on a shared hosting platform.$ dovecot 
--version2.3.13 (89f716dc2)I would like to keep automated local backups, but do not have access to 
doveadm.I have seen a couple of forum posts where users have have suggested that using rsync to 
backup m(d)box folders can corrupt dovecot's indexes, but there is no further explanation, and this 
is apparently not a problem for maildir.  Our host seems to use mdbox.Does doveadm provide some 
sort of transaction/locking mechanism to prevent consistency problems?  Others seem to recommend 
using tar but I don't see what difference that should make.Given that cpanel backups (provided as 
tar.gz archives of the home directory) include mail/ and seem to be copies of the filesystem at a 
particular time (though not true "snapshots" as such), aren't these just as 
"safe" as an rsync-ed backup?Can anyone confirm/deny/shed any light on the issue(s), if 
indeed any?Many thanks,Gareth___dovecot mailing list -- 
dovecot@dovecot.orgTo unsubscribe send an email to dovecot-le...@dovecot.org
___
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-le...@dovecot.org


___
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-le...@dovecot.org

___
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-le...@dovecot.org

Re: adding caldav/carddav next to dovecot

[infoomatic]

On 14.10.22 16:13, Marc wrote:

I also do not want any other other 'crap' just the cal (and card) dav solution.


sorry about my suggestion, but I am just a big fan of SOGo (no
affiliation with) from sogo.nu ... it may not be a solution for you
because it offers caldav, carddav, webmail, but performance is top
notch, maybe you want to have a look anyway

Re: FTS config - cannot search substrings

[infoomatic]

sometimes ignoring the problem for a few moments and then starting over
again helps ...

the solution was already solved here in a mail over 10 years ago -
https://dovecot.org/list/dovecot/2011-May/059338.html

Thanks Daniel Miller!


On 18.11.21 23:58, infoomatic wrote:

Hi,

I have an issue with FTS, maybe someone here can help me out.

Basically my setup is working with solr + tika enabled, however, it
seems my search is not configured the way I expect it. Eg when I receive
a pdf document containing the word "myfoobar" I cannot search for
"myfoo" or "foobar", but searching for "myfoobar" shows the right result.

Any ideas? Thanks!

FTS config - cannot search substrings

[infoomatic]

Hi,

I have an issue with FTS, maybe someone here can help me out.

Basically my setup is working with solr + tika enabled, however, it
seems my search is not configured the way I expect it. Eg when I receive
a pdf document containing the word "myfoobar" I cannot search for
"myfoo" or "foobar", but searching for "myfoobar" shows the right result.

Any ideas? Thanks!

Re: ZFS storage and backup

[infoomatic]

On 15.11.21 11:04, James wrote:


I will use native ZFS encryption soon.  I see no performance issues in
test.

Don't get hung up on ZFS tuning, mostly ZFS just works.


yes I know, I love working with it, I have used it for > 10 years now,
but it happened that none of my mailserver projects used ZFS. Regarding
storage I tend to use sdbox, from what I have read it seems to be the
better option when using a COW filesystem compared to mdbox. One more
question is: compression at file system level or in dovecot storage?

The reason I am not sure to switch to ssds is that most servers are for
non-profit organisations, sports clubs etc. - they also need some
storage for pictures, their budget is quite low (so performance testing
would only be done out of my interest), and if spinning rust with
optimized settings suffices why not.

Thanks for your input so far, hope more will come ;-)

ZFS storage and backup

[infoomatic]

Hi listmembers,

I am about to migrate our mailservices to FreeBSD + ZFS. Thus, before
entering the sheer endless  stage of performance testing, I thought I
would ask here kindly for all kinds of information.

My setups are nothing special with few users, however, I would like to
have a nice setup, maybe some of you could contribute to this thread. We
are using slow spinning disks, but we may consider using ssds in a
not-so-distant future.

*) storages: any infos on ZFS options or whether to use mdbox or sdbox,
and what configs/options regarding compression etc.

*) backup: what is a best practice regarding backups? - using only the
dovecot tools or leveraging the great features of ZFS (or both) with
snapshots etc.?

Thanks for all sorts of infos, probably saving me quite some time
evaluating different options!

Robert

Re: Strategies for protecting IMAP (e.g. MFA)

[infoomatic]

I will throw in a few interesting projects which have kept my small
servers safe:

*) firehol.org

*) crowdsec.net

*) www.fail2ban.org

Have a look at those interesting projects!


On 13.11.21 22:16, Tyler Montney wrote:

With the world of ransomware as it is today (aka attacks seem more
vicious and commonplace), anything I expose to WAN must have
additional protection. I've seen a few posts to this list on it. The
only thing that helped was that Dovecot supports OAuth. Through OAuth
I figure I could implement MFA. However, I'd have to host my own
identity server. From there, Thunderbird supports OAuth so that should
work.

Since this is getting increasingly complicated, I wanted to ask before
going further. What do you all do? Any recommendations?

Re: dsync-trouble

[infoomatic]

On 05.11.21 08:39, Aki Tuomi wrote:

Not sure how this is done in FreeBSD but can you try getting debug symbols 
somehow?

Aki


@Hanns: can you compile from ports and use
https://wiki.freebsd.org/BenWoods/DebuggingPorts or just 'make
WITH_DEBUG=yes DEBUG_FLAGS="-g -O0"' in /usr/local/mail/dovecot

Re: dsync-trouble

[infoomatic]

On 04.11.21 09:11, Hanns Mattes wrote:

chown -R 1777 /var/coredumps


that should probably be "chmod -R 1777 /var/coredumps"

Re: Auth-Trouble

[infoomatic]

please inform the mailing list if problems persist, thank you!

I am about to migrate to FreeBSD ...


On 01.11.21 13:53, Hanns Mattes wrote:

Hi,

Am 01.11.21 um 00:51 schrieb Hanns Mattes:

Hi,

Am 01.11.21 um 00:27 schrieb infoomatic:

does 2.3.17_1 from ports fix the problem?

I'm building own packages with poudriere and "pkg info dovecot" says
it's 2.3.17_1

Given the fact that this version is dated 2021-10-28 I'm not sure, if
its part of the problem or the solution.


I'll do a complete reinstallation of the server, there are obviously
more problems. For example: I can ssh to both servers (and i can connect
from them to my server at home) but they refuse to talk to each other.
Same with telnet etc. No idea why, so I'll start over and recheck things.

Regards Hanns

Re: Auth-Trouble

[infoomatic]

does 2.3.17_1 from ports fix the problem?


On 01.11.21 00:01, Hanns Mattes wrote:

Hi,

Am 31.10.21 um 18:30 schrieb Hanns Mattes:

Hi, me again,
Hanns Mattes  schrieb:
I stand corrected and forgot to remove

things are working, except replication.

no, they don't.

okay, imap logins are working again.

Replication still failing. My guess is, that my master-user
configuration is the culprit.

Any Ideas?

Regards

Re: reconsidering my (your?) current setup

[Infoomatic]

On 07.10.21 13:49, dove...@ptld.com wrote:

https://www.oracle.com/linux/

Im surprised at how little people are aware of this.


probably people are aware ... it's just that it is oracle *cough*cough*
*scnr*. As RHEL clone there is also alma linux, rocky linux  and
eurolinux ... and various migration scripts [1]. However, with Linux
distros it is up to your requirements, we do prefer Debian based distros
and have had dovecot running on Ubuntu for a long time but have recently
migrated to FreeBSD.


[1] https://github.com/AlmaLinux/almalinux-deploy

https://github.com/rocky-linux/rocky-tools/tree/main/migrate2rocky

Re: migration from 2.0.16

[infoomatic]

On 17.12.20 15:56, Barbara M. wrote:
>
> We own the servers and use CT (LXC).
> The IBM move is clear, but going to C7 today seems to me not a good
> choice. It is in its descending stage and in a couple of years
> packages are going to became very outdated.
> If RH8 remain "open source" I suppose the community or some interested
> medium level company that use CentOS for their business can became a
> new CentOS and switch to a different named distro is supposed to be
> only a question of replace repositories.
> That seems to me a smoother path (IMHO).
> Debian 10 is EOL on 2022
> Ubuntu LTS seems a solution, but I hadn't ever used it (I may be
> wrong, but in the past Canonical don't inspire me to much trust).
>
Maybe Rocky Linux will become a drop-in replacement for CentOS, see
https://rockylinux.org/ - it is led by the founder of CentOS and was
initated after the recent news concerning CentOS.


If it does not have to be Linux I'll throw in FreeBSD + jails (= system
level containers) as a recommendation. After quite some problems with
major upgrades on Ubuntu I moved some of the servers to FreeBSD and now
I am happy. (Going from one Debian stable to the next Debian stable also
turned out to work much better than going from one Ubuntu LTS to the
next Ubuntu LTS version ... but that is just my personal experience on <
50 servers)

Re: quota-status for outgoing mail (Dovecot/Postfix)

[infoomatic]

If you are not restricted to using dovecot and postfix only, I suggest
having a look at policyd "cluebringer" - from https://wiki.policyd.org/

Works great to set quotas per user or per domain.


On 06.12.20 21:13, Peter Folta wrote:
> [Dovecot version 2.3.11.3 (502c39af9)]
>
> Hi all,
>
> I’m using Dovecot’s quota-status service to let Postfix check the
> recipient’s quota before accepting emails following the guide
> here: https://blog.sys4.de/postfix-dovecot-mailbox-quota-en.html
> . This
> works well for inbound emails.
>
> I would like to set up something similar for outbound email, i.e. if a
> user is over quota, they should not be allowed to send new emails. At
> the moment, the setup is in a bit of an inconsistent state: Users that
> have exceeded their quota are still able to send outbound emails but
> saving them in their Sent folder will fail leaving them without a copy.
>
> I have tried using Dovecot’s quota-status in Postfix’s
> smtpd_send_restrictions but didn’t get this to work. A quick look at
> the Dovecot source code seems to suggest that the quota-status plugin
> is only checking the recipient
> address: 
> https://github.com/dovecot/core/blob/master/src/plugins/quota/quota-status.c#L135-L146
> 
>  and 
> https://github.com/dovecot/core/blob/master/src/plugins/quota/quota-status.c#L109-L111
> .
>
> I suspect it’s not possible to use the quota-status service to control
> outbound email but thought I’d ask to confirm. I’m wondering if
> there’s a different way to achieve this?
>
> Thanks
> Peter

Re: A user's last access time

[infoomatic]

On 21.10.20 18:27, @lbutlr wrote:
> How is SQLite different from MySQL? I have both on my system. They are both 
> on-disk database files.
>

sqlite is accessed through a library, data is stored in a file. whereas
mysql needs a running service/daemon (which takes care of storing the
data into files)

Re: Feature request.

[infoomatic]

so if you have a new certificate it is valid vor 89.something days, you
could do a:

openssl x509 -in file.crt -checkend 7689600 -noout > /dev/null &&
/usr/bin/systemctl reload dovecot

Re: Urgent Help required

[infoomatic]

On 08.07.20 20:28, Kishore Potnuru wrote:
>
> I have another question. I understand redhat 6.10 will go out of
> support in november 2020. But this is a test environment. Am i able to
> install dovecot 2.3 version on redhat 6.10? For the Live support, I
> will be doing it on redhat 7.7 version. 
>
> For testing, I am trying redhat 6.10 version, if it is successful, i
> will be trying the Live one's on redhat 7.7 version.


Testing with version 6.10 and then running on 7.7 is probably not a good
idea. I highly recommend the same versions of software for testing and
production - so better start your tests on 7.7

Re: Is it possible to enable push notifications for iOS/macOS mail clients on a stock dovecot?

[infoomatic]

I have no idea about that Mac proprietary stuff ... however,
https://doc.dovecot.org/configuration_manual/push_notification/ might be
a solution/workaround for you.

regards,

infoomatic


Am 08.01.20 um 22:33 schrieb Gerben Wierda:

Now that Apple has abandoned mail server capabilities in macOS Server.app we 
have to move to an open source solution. I have done this using Macports and it 
works well (no thanks to Apple as it never published the in 2018 promised 
migration info for mail services).

The MacPorts Apple Push Notification variant based on a patch written a few 
years ago for dovecot supports APNS but it requires you to export a certificate 
form your old High Sierra Server.app. With the patch and that certificate, 
dovecot tells an email client it supports XAPPLEPUSHSERVICE and that makes 
Apple mail clients think they are talking to macOS Server and they switch to 
push notifications for updates. Now, that certificate needs to be renewed 
yearly by Server.app and imported by hand etc. At some point this will stop 
working (apart from that you need to keep an old macOS Server around to renew)

Is there another way to get this working with an open source dovecot, outside 
of using Apple’s push notification service? Some other standard? Some other 
service? Probably not, right?

G

Aw: Re: dsync panic

[Infoomatic]

thanks, the fix worked for me, too (on 2.3.2.1)!
 

Gesendet: Freitag, 13. Juli 2018 um 22:43 Uhr
Von: "Timo Sirainen" 
An: "Wolfgang Rosenauer" 
Cc: dovecot 
Betreff: Re: dsync panic



On 13 Jul 2018, at 21.39, Wolfgang Rosenauer  wrote:


 


I think I get pretty much the same issue:

 

dsync(support): Panic: file mailbox-attribute.c: line 360 (mailbox_attribute_get_stream): assertion failed: (value_r->value != NULL || value_r->value_stream != NULL)
dsync(support): Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(+0xc9e06) [0x7fba8a348e06] -> /usr/lib64/dovecot/libdovecot.so.0(default_fatal_handler+0x2a) [0x7fba8a348e4a] -> /usr/lib64/dovecot/libdovecot.so.0(i_fatal+0) [0x7fba8a2bd813] -> /usr/lib64/dovecot/libdovecot-storage.so.0(+0x597fc) [0x7fba8a64f7fc] -> dsync(dsync_mailbox_import_attribute+0x3a) [0x55d72a8ac37a] -> dsync(dsync_brain_sync_mails+0x2ef) [0x55d72a8a7e9f] -> dsync(dsync_brain_run+0x2b0) [0x55d72a8a3690] -> dsync(+0x29f5c) [0x55d72a88af5c] -> dsync(+0x2bd97) [0x55d72a88cd97] -> dsync(+0x2c878) [0x55d72a88d878] -> dsync(doveadm_mail_try_run+0x205) [0x55d72a88e1f5] -> dsync(main+0x475) [0x55d72a87de85] -> /lib64/libc.so.6(__libc_start_main+0xf5) [0x7fba89c8d725] -> dsync(_start+0x29) [0x55d72a87e009]





Already fixed, but was scheduled for v2.3.3: https://github.com/dovecot/core/commit/4ff4bd024a9b6e7973b76b186ce085c2ca669d3e

 

As a workaround, you could disable ACL when running dsync: doveadm -o plugin/acl= ...

 

Aw: Re: dsync panic

[Infoomatic]

thanks for taking the time to answer. Unfortunately, I get the same error with the right command (without the -1)

 

infoomatic

 

 

Gesendet: Donnerstag, 12. Juli 2018 um 19:57 Uhr
Von: "Sami Ketola" 
An: dovecot 
Cc: Infoomatic 
Betreff: Re: dsync panic


 
 

On 7 Jul 2018, at 4.31, Infoomatic <infooma...@gmx.at> wrote:
 


Hi,
I just upgraded from dovecot 2.2.19 to 2.3.2. "doveadm backup" worked fine in v 2.2.19, but now panics (user with shared folder):
/opt/dovecot/bin/doveadm backup -u testuser -1 sdbox:/tmp/testuser



 
Not sure why it panics, but at least your command line looks incorrect. 

 

please try: doveadm backup -u testuser sdbox:/tmp/testuser

 

your options are:

 

doveadm backup

doveadm sync

doveadm sync -1

 

https://wiki2.dovecot.org/Tools/Doveadm/Sync

 

Sami

Aw: dsync panic

[Infoomatic]

Hi,

Any info on this one? btw, did a c error (standl2 is the username, of course)

Regards,
infoomatic


> Gesendet: Samstag, 07. Juli 2018 um 03:31 Uhr
> Von: Infoomatic 
> An: dovecot@dovecot.org
> Betreff: dsync panic
>
> Hi,
> I just upgraded from dovecot 2.2.19 to 2.3.2. "doveadm backup" worked fine in 
> v 2.2.19, but now panics (user with shared folder):
> /opt/dovecot/bin/doveadm backup -u testuser -1 sdbox:/tmp/testuser
> 
> dsync(standl2): Panic: file mailbox-attribute.c: line 360 
> (mailbox_attribute_get_stream): assertion failed: (value_r->value != NULL || 
> value_r->value_stream != NULL)
> dsync(standl2): Error: Raw backtrace: 
> /opt/dovecot/lib/dovecot/libdovecot.so.0(+0xcb6fa) [0x7f43679986fa] -> 
> /opt/dovecot/lib/dovecot/libdovecot.so.0(+0xcb769) [0x7f4367998769] -> 
> /opt/dovecot/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7f43679069c1] -> 
> /opt/dovecot/lib/dovecot/libdovecot-storage.so.0(+0x568ff) [0x7f4367c9d8ff] 
> -> /opt/dovecot/bin/doveadm(dsync_mailbox_import_attribute+0x4d) 
> [0x56234f7b68dd] -> /opt/dovecot/bin/doveadm(dsync_brain_sync_mails+0x2fd) 
> [0x56234f7b217d] -> /opt/dovecot/bin/doveadm(dsync_brain_run+0x538) 
> [0x56234f7adb28] -> /opt/dovecot/bin/doveadm(+0x27fec) [0x56234f793fec] -> 
> /opt/dovecot/bin/doveadm(+0x2a0e7) [0x56234f7960e7] -> 
> /opt/dovecot/bin/doveadm(+0x2ad7b) [0x56234f796d7b] -> 
> /opt/dovecot/bin/doveadm(doveadm_mail_try_run+0x1fa) [0x56234f79769a] -> 
> /opt/dovecot/bin/doveadm(main+0x45b) [0x56234f786b2b] -> 
> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0) [0x7f4367523830] -> 
> /opt/dovecot/bin/doveadm(_start+0x29) [0x56234f786ca9]
> 
> regards,
> infoomatic
> 

dsync panic

[Infoomatic]

Hi,
I just upgraded from dovecot 2.2.19 to 2.3.2. "doveadm backup" worked fine in v 
2.2.19, but now panics (user with shared folder):
/opt/dovecot/bin/doveadm backup -u testuser -1 sdbox:/tmp/testuser

dsync(standl2): Panic: file mailbox-attribute.c: line 360 
(mailbox_attribute_get_stream): assertion failed: (value_r->value != NULL || 
value_r->value_stream != NULL)
dsync(standl2): Error: Raw backtrace: 
/opt/dovecot/lib/dovecot/libdovecot.so.0(+0xcb6fa) [0x7f43679986fa] -> 
/opt/dovecot/lib/dovecot/libdovecot.so.0(+0xcb769) [0x7f4367998769] -> 
/opt/dovecot/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7f43679069c1] -> 
/opt/dovecot/lib/dovecot/libdovecot-storage.so.0(+0x568ff) [0x7f4367c9d8ff] -> 
/opt/dovecot/bin/doveadm(dsync_mailbox_import_attribute+0x4d) [0x56234f7b68dd] 
-> /opt/dovecot/bin/doveadm(dsync_brain_sync_mails+0x2fd) [0x56234f7b217d] -> 
/opt/dovecot/bin/doveadm(dsync_brain_run+0x538) [0x56234f7adb28] -> 
/opt/dovecot/bin/doveadm(+0x27fec) [0x56234f793fec] -> 
/opt/dovecot/bin/doveadm(+0x2a0e7) [0x56234f7960e7] -> 
/opt/dovecot/bin/doveadm(+0x2ad7b) [0x56234f796d7b] -> 
/opt/dovecot/bin/doveadm(doveadm_mail_try_run+0x1fa) [0x56234f79769a] -> 
/opt/dovecot/bin/doveadm(main+0x45b) [0x56234f786b2b] -> 
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0) [0x7f4367523830] -> 
/opt/dovecot/bin/doveadm(_start+0x29) [0x56234f786ca9]

regards,
infoomatic

Aw: Re: 2 panics, 1 segmentation fault in dovecot 2.3.0 (fts)

[Infoomatic]

Thanks Aki! The fix works! Will give you the debug stuff of the other error 
next week.

Regards,
Infoomatic

> Gesendet: Samstag, 27. Januar 2018 um 20:38 Uhr
> Von: "Aki Tuomi" <aki.tu...@dovecot.fi>
> An: "Dovecot ML" <dovecot@dovecot.org>, Infoomatic <infooma...@gmx.at>
> Betreff: Re: 2 panics, 1 segmentation fault in dovecot 2.3.0 (fts)
>
> 
> > On January 27, 2018 at 4:19 PM Infoomatic <infooma...@gmx.at> wrote:
> > 
> > 
> > Hi,
> > 
> > While testing our migration to dovecot 2.3.0, we encountered 2 panics, 1 
> > segmentation fault while we wanted to rebuild the solr indizes. Problem [1] 
> > was encountered while rebuilding the indizes, and now I don't know how many 
> > mails/documents are indexed or where it got stuck. [2] and [3] encountered 
> > while just playing around, since I did not know of "tokenize" and did not 
> > find a lot of information about it.
> > 
> > This is a ubuntu 16.04 machine, dovecot 2.3.0 compiled from source ( + the 
> > patch for the recent zlib problem). "doveadm index" runs on a ~ 4GB 
> > mdbox-zipped-mailbox for about 3-4 minutes before aborting with the message 
> > above, beforehand I did a "/opt/dovecot/bin/doveadm fts rescan -A". When I 
> > repeat "doveadm index" it aborts after about 4 seconds, after a 
> > "/opt/dovecot/bin/doveadm fts rescan -A" it runs again for 3-4 minutes.
> > 
> > Apache tika logs, but those are probably not related to the problem, 
> > however, the devs might want investigate the last line:
> > WARN  Parse exception Expected ';', got "," determining content disposition
> > javax.mail.internet.ParseException: Expected ';', got ","
> > and
> > org.apache.tika.exception.ZeroByteFileException: InputStream must have > 0 
> > bytes
> > 
> > 
> > I would be happy if you could have a look at this, please, and of course 
> > just tell me what further information you need.
> > 
> > Thanks,
> > infoomatic
> > 
> > 
> > [1] /opt/dovecot/bin/doveadm index -u user1 '*'
> > doveadm(user1): Panic: file unichar.c: line 160 (uni_ucs4_to_utf8_c): 
> > assertion failed: (uni_is_valid_ucs4(chr))
> > doveadm(user1): Error: Raw backtrace: 
> > /opt/dovecot/lib/dovecot/libdovecot.so.0(+0xc5eea) [0x7ff27755beea] -> 
> > /opt/dovecot/lib/dovecot/libdovecot.so.0(+0xc5f59) [0x7ff27755bf59] -> 
> > /opt/dovecot/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7ff2774ce5e1] -> 
> > /opt/dovecot/lib/dovecot/libdovecot.so.0(uni_ucs4_to_utf8_c+0xa0) 
> > [0x7ff277593300] -> /opt/dovecot/lib/dovecot/libdovecot.so.0(+0xa74f9) 
> > [0x7ff27753d4f9] -> 
> > /opt/dovecot/lib/dovecot/libdovecot.so.0(mail_html2text_more+0xc5) 
> > [0x7ff27753d705] -> /opt/dovecot/lib/dovecot/lib20_fts_plugin.so(+0xcf5c) 
> > [0x7ff276460f5c] -> 
> > /opt/dovecot/lib/dovecot/lib20_fts_plugin.so(fts_parser_more+0x27) 
> > [0x7ff276460c37] -> 
> > /opt/dovecot/lib/dovecot/lib20_fts_plugin.so(fts_build_mail+0x511) 
> > [0x7ff27645eb51] -> /opt/dovecot/lib/dovecot/lib20_fts_plugin.so(+0x110a6) 
> > [0x7ff2764650a6] -> 
> > /opt/dovecot/lib/dovecot/libdovecot-storage.so.0(mail_precache+0x2e) 
> > [0x7ff27784618e] -> /opt/dovecot/bin/doveadm(+0x2f697) [0x55dd2f912697] -> 
> > /opt/dovecot/bin/doveadm(+0x29827) [0x55dd2f90c827] -> 
> > /opt/dovecot/bin/doveadm(+0x2a4bb) [0x55dd2f90d4bb] -> 
> > /opt/dovecot/bin/doveadm(doveadm_cmd_ver2_to_mail_cmd_wrapper+0x21d) 
> > [0x55dd2f90e2cd] -> /opt/dovecot/bin/doveadm(doveadm_cmd_run_ver2+0x575) 
> > [0x55dd2f91deb5] -> /opt/dovecot/bin/doveadm(doveadm_cmd_try_run_ver2+0x37) 
> > [0x55dd2f91df07] -> /opt/dovecot/bin/doveadm(main+0x1d2) [0x55dd2f8fd032] 
> > -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0) [0x7ff2770ec830] 
> > -> /opt/dovecot/bin/doveadm(_start+0x29) [0x55dd2f8fd439]
> > Aborted (core dumped)
> > 
> > 
> 
> You can fix this with 
> https://github.com/dovecot/core/commit/5c1837529e6957da3e389683c43bd006859395e5.patch
> 
> > [2] This was just about my curiosity since I haven't used "tokenize" and 
> > did not find too much info about it: 
> > /opt/dovecot/bin/doveadm fts tokenize -A '*'
> > Panic: file doveadm-print.c: line 142: unreached
> > Error: Raw backtrace: /opt/dovecot/lib/dovecot/libdovecot.so.0(+0xc5eea) 
> > [0x7f38ac5c2eea] -> /opt/dovecot/lib/dovecot/libdovecot.so.0(+0xc5f59) 
> > [0x7f38ac5c2f59] -> /opt/dovecot/lib/dovecot/libdovecot.so.0(i_fatal+0) 
> > 

2 panics, 1 segmentation fault in dovecot 2.3.0 (fts)

[Infoomatic]

Hi,

While testing our migration to dovecot 2.3.0, we encountered 2 panics, 1 
segmentation fault while we wanted to rebuild the solr indizes. Problem [1] was 
encountered while rebuilding the indizes, and now I don't know how many 
mails/documents are indexed or where it got stuck. [2] and [3] encountered 
while just playing around, since I did not know of "tokenize" and did not find 
a lot of information about it.

This is a ubuntu 16.04 machine, dovecot 2.3.0 compiled from source ( + the 
patch for the recent zlib problem). "doveadm index" runs on a ~ 4GB 
mdbox-zipped-mailbox for about 3-4 minutes before aborting with the message 
above, beforehand I did a "/opt/dovecot/bin/doveadm fts rescan -A". When I 
repeat "doveadm index" it aborts after about 4 seconds, after a 
"/opt/dovecot/bin/doveadm fts rescan -A" it runs again for 3-4 minutes.

Apache tika logs, but those are probably not related to the problem, however, 
the devs might want investigate the last line:
WARN  Parse exception Expected ';', got "," determining content disposition
javax.mail.internet.ParseException: Expected ';', got ","
and
org.apache.tika.exception.ZeroByteFileException: InputStream must have > 0 bytes


I would be happy if you could have a look at this, please, and of course just 
tell me what further information you need.

Thanks,
infoomatic


[1] /opt/dovecot/bin/doveadm index -u user1 '*'
doveadm(user1): Panic: file unichar.c: line 160 (uni_ucs4_to_utf8_c): assertion 
failed: (uni_is_valid_ucs4(chr))
doveadm(user1): Error: Raw backtrace: 
/opt/dovecot/lib/dovecot/libdovecot.so.0(+0xc5eea) [0x7ff27755beea] -> 
/opt/dovecot/lib/dovecot/libdovecot.so.0(+0xc5f59) [0x7ff27755bf59] -> 
/opt/dovecot/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7ff2774ce5e1] -> 
/opt/dovecot/lib/dovecot/libdovecot.so.0(uni_ucs4_to_utf8_c+0xa0) 
[0x7ff277593300] -> /opt/dovecot/lib/dovecot/libdovecot.so.0(+0xa74f9) 
[0x7ff27753d4f9] -> 
/opt/dovecot/lib/dovecot/libdovecot.so.0(mail_html2text_more+0xc5) 
[0x7ff27753d705] -> /opt/dovecot/lib/dovecot/lib20_fts_plugin.so(+0xcf5c) 
[0x7ff276460f5c] -> 
/opt/dovecot/lib/dovecot/lib20_fts_plugin.so(fts_parser_more+0x27) 
[0x7ff276460c37] -> 
/opt/dovecot/lib/dovecot/lib20_fts_plugin.so(fts_build_mail+0x511) 
[0x7ff27645eb51] -> /opt/dovecot/lib/dovecot/lib20_fts_plugin.so(+0x110a6) 
[0x7ff2764650a6] -> 
/opt/dovecot/lib/dovecot/libdovecot-storage.so.0(mail_precache+0x2e) 
[0x7ff27784618e] -> /opt/dovecot/bin/doveadm(+0x2f697) [0x55dd2f912697] -> 
/opt/dovecot/bin/doveadm(+0x29827) [0x55dd2f90c827] -> 
/opt/dovecot/bin/doveadm(+0x2a4bb) [0x55dd2f90d4bb] -> 
/opt/dovecot/bin/doveadm(doveadm_cmd_ver2_to_mail_cmd_wrapper+0x21d) 
[0x55dd2f90e2cd] -> /opt/dovecot/bin/doveadm(doveadm_cmd_run_ver2+0x575) 
[0x55dd2f91deb5] -> /opt/dovecot/bin/doveadm(doveadm_cmd_try_run_ver2+0x37) 
[0x55dd2f91df07] -> /opt/dovecot/bin/doveadm(main+0x1d2) [0x55dd2f8fd032] -> 
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0) [0x7ff2770ec830] -> 
/opt/dovecot/bin/doveadm(_start+0x29) [0x55dd2f8fd439]
Aborted (core dumped)


[2] This was just about my curiosity since I haven't used "tokenize" and did 
not find too much info about it: 
/opt/dovecot/bin/doveadm fts tokenize -A '*'
Panic: file doveadm-print.c: line 142: unreached
Error: Raw backtrace: /opt/dovecot/lib/dovecot/libdovecot.so.0(+0xc5eea) 
[0x7f38ac5c2eea] -> /opt/dovecot/lib/dovecot/libdovecot.so.0(+0xc5f59) 
[0x7f38ac5c2f59] -> /opt/dovecot/lib/dovecot/libdovecot.so.0(i_fatal+0) 
[0x7f38ac5355e1] -> /opt/dovecot/bin/doveadm(+0x3b3d3) [0x55c728e8b3d3] -> 
/opt/dovecot/bin/doveadm(+0x2a63a) [0x55c728e7a63a] -> 
/opt/dovecot/bin/doveadm(doveadm_cmd_ver2_to_mail_cmd_wrapper+0x21d) 
[0x55c728e7b2cd] -> /opt/dovecot/bin/doveadm(doveadm_cmd_run_ver2+0x575) 
[0x55c728e8aeb5] -> /opt/dovecot/bin/doveadm(doveadm_cmd_try_run_ver2+0x37) 
[0x55c728e8af07] -> /opt/dovecot/bin/doveadm(main+0x1d2) [0x55c728e6a032] -> 
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0) [0x7f38ac153830] -> 
/opt/dovecot/bin/doveadm(_start+0x29) [0x55c728e6a439]
Aborted (core dumped)


[3] /opt/dovecot/bin/doveadm fts tokenize -u user1 "@"
Segmentation fault (core dumped)

Aw: Re: problem with lda

[Infoomatic]

My workaround for this issue was to use lmtp which now works flawlessly.

Regards,
infoomatic



> Gesendet: Donnerstag, 25. Januar 2018 um 14:07 Uhr
> Von: Infoomatic <infooma...@gmx.at>
> An: "Stephan Bosch" <step...@rename-it.nl>, "Dovecot ML" <dovecot@dovecot.org>
> Betreff: Aw: Re: problem with lda
>
> thanks for your input.
> 
> Bill: deliver is just a symlink to dovecot-lda
> Stephan: I don't know, and and it even does not work when I use deliver -f 
> "postmaster@ourdomain.internal" - I get the same error message.
> 
> A part of the mail I got when using 2.2.23:
> 
> Return-Path: 
> Delivered-To: user1@ourdomain.internal
> Received: from localhost (localhost [127.0.0.1])
>   by hosting.ourdomain.internal (Postfix) with ESMTP id 8E985424C7
>   for <user1@ourdomain.internal>; Thu, 25 Jan 2018 12:36:59 +0100 (CET)
> Content-Type: multipart/report; report-type=delivery-status;
> 
> That's strange. Any ideas, anyone?
> 
> Regards,
> infoomatic
> 
> 
> > Gesendet: Donnerstag, 25. Januar 2018 um 09:35 Uhr
> > Von: "Stephan Bosch" <step...@rename-it.nl>
> > An: Infoomatic <infooma...@gmx.at>, dovecot@dovecot.org
> > Betreff: Re: problem with lda
> >
> > Op 1/24/2018 om 5:30 PM schreef Infoomatic:
> > > Hello,
> > >
> > > I am currently testing the upgrade from our dovecot v2.2.23 to 2.3.0. I 
> > > have a strange problem with lda.
> > > We use bounce mails for internal users if they try to send 
> > > virus/spammails. The exact same config works with 2.2.23, but not with 
> > > 2.3.0.
> > >
> > > The relevant postfix/master.cf part:
> > > dovecot   unix  -   n   n   -   -   pipe
> > >   flags=DRhu user=vmail:vmail argv=/opt/dovecot/libexec/dovecot/deliver 
> > > -d ${recipient} -f ${sender}
> > >
> > > On the same machine, with 2.2.23 I get a bounce mail when trying to send 
> > > a virus, with the subject "VIRUS in message apparently from you 
> > > (Eicar-Test-Signature)", to both the users inbox as well as to the 
> > > mailbox of virusalert@ourdomain.internal
> > >
> > > With 2.3.0, in the logs I get an error:
> > >
> > > relay=dovecot, delay=0.01, delays=0/0/0/0, dsn=5.3.0, status=bounced 
> > > (command line usage error. Command output: lda: Fatal: Invalid -f 
> > > parameter: Missing domain 
> > >
> > > and the alert message is only sent to virusalert@ourdomain.internal, but 
> > > not to the user who tried to send the mail.
> > >
> > > The relevant part of our dovecot.conf:
> > > protocol lda {
> > >   mail_plugins = " quota zlib sieve acl mail_log notify"
> > >   postmaster_address = postmaster@ourdomain.internal
> > > }
> > >
> > > Does anyone know how to solve this problem? Or is there a workaround via 
> > > postfix/amavis/spamassassin? Any hints are highly appreciated, thanks!
> > 
> > Apparently, the ${sender} has no @domain part. Why?
> > 
> > Regards,
> > 
> > Stephan.
> > 
> 

Aw: Re: problem with lda

[Infoomatic]

thanks for your input.

Bill: deliver is just a symlink to dovecot-lda
Stephan: I don't know, and and it even does not work when I use deliver -f 
"postmaster@ourdomain.internal" - I get the same error message.

A part of the mail I got when using 2.2.23:

Return-Path: 
Delivered-To: user1@ourdomain.internal
Received: from localhost (localhost [127.0.0.1])
by hosting.ourdomain.internal (Postfix) with ESMTP id 8E985424C7
for <user1@ourdomain.internal>; Thu, 25 Jan 2018 12:36:59 +0100 (CET)
Content-Type: multipart/report; report-type=delivery-status;

That's strange. Any ideas, anyone?

Regards,
infoomatic


> Gesendet: Donnerstag, 25. Januar 2018 um 09:35 Uhr
> Von: "Stephan Bosch" <step...@rename-it.nl>
> An: Infoomatic <infooma...@gmx.at>, dovecot@dovecot.org
> Betreff: Re: problem with lda
>
> Op 1/24/2018 om 5:30 PM schreef Infoomatic:
> > Hello,
> >
> > I am currently testing the upgrade from our dovecot v2.2.23 to 2.3.0. I 
> > have a strange problem with lda.
> > We use bounce mails for internal users if they try to send virus/spammails. 
> > The exact same config works with 2.2.23, but not with 2.3.0.
> >
> > The relevant postfix/master.cf part:
> > dovecot   unix  -   n   n   -   -   pipe
> >   flags=DRhu user=vmail:vmail argv=/opt/dovecot/libexec/dovecot/deliver -d 
> > ${recipient} -f ${sender}
> >
> > On the same machine, with 2.2.23 I get a bounce mail when trying to send a 
> > virus, with the subject "VIRUS in message apparently from you 
> > (Eicar-Test-Signature)", to both the users inbox as well as to the mailbox 
> > of virusalert@ourdomain.internal
> >
> > With 2.3.0, in the logs I get an error:
> >
> > relay=dovecot, delay=0.01, delays=0/0/0/0, dsn=5.3.0, status=bounced 
> > (command line usage error. Command output: lda: Fatal: Invalid -f 
> > parameter: Missing domain 
> >
> > and the alert message is only sent to virusalert@ourdomain.internal, but 
> > not to the user who tried to send the mail.
> >
> > The relevant part of our dovecot.conf:
> > protocol lda {
> >   mail_plugins = " quota zlib sieve acl mail_log notify"
> >   postmaster_address = postmaster@ourdomain.internal
> > }
> >
> > Does anyone know how to solve this problem? Or is there a workaround via 
> > postfix/amavis/spamassassin? Any hints are highly appreciated, thanks!
> 
> Apparently, the ${sender} has no @domain part. Why?
> 
> Regards,
> 
> Stephan.
> 

problem with lda

[Infoomatic]

Hello,

I am currently testing the upgrade from our dovecot v2.2.23 to 2.3.0. I have a 
strange problem with lda.
We use bounce mails for internal users if they try to send virus/spammails. The 
exact same config works with 2.2.23, but not with 2.3.0.

The relevant postfix/master.cf part:
dovecot   unix  -   n   n   -   -   pipe
  flags=DRhu user=vmail:vmail argv=/opt/dovecot/libexec/dovecot/deliver -d 
${recipient} -f ${sender}

On the same machine, with 2.2.23 I get a bounce mail when trying to send a 
virus, with the subject "VIRUS in message apparently from you 
(Eicar-Test-Signature)", to both the users inbox as well as to the mailbox of 
virusalert@ourdomain.internal

With 2.3.0, in the logs I get an error:

relay=dovecot, delay=0.01, delays=0/0/0/0, dsn=5.3.0, status=bounced (command 
line usage error. Command output: lda: Fatal: Invalid -f parameter: Missing 
domain 

and the alert message is only sent to virusalert@ourdomain.internal, but not to 
the user who tried to send the mail.

The relevant part of our dovecot.conf:
protocol lda {
  mail_plugins = " quota zlib sieve acl mail_log notify"
  postmaster_address = postmaster@ourdomain.internal
}

Does anyone know how to solve this problem? Or is there a workaround via 
postfix/amavis/spamassassin? Any hints are highly appreciated, thanks!

Regards,
infoomatic

Aw: Dovecot - Postfix Calender Synchronisation

[Infoomatic]

Hello,

> Please witch add-on possibilities exist to synchronize the Calednar with
> Dovecot and Postfix.
> 
> Can give me here any a possible direction ?

Postfix and Dovecot are responsible for mailing. If you want a calendar, you 
probably want
a CalDav server or a Microsoft ActiveSync compatible server.

There are various solutions out there, I know of caldav servers and libraries 
from sabredav.io, calendarserver.org, agendav.org, davical.org, radicale.org 
and bedework at apereo.org

If you want a more integrated solution there is open-xchange (dovecot company 
is part of), sogo.nu, kolab.org, obm.org, horde, citadel, zimbra, zarafa

While I have not tried all of those, I can recommend sogo.nu. I have not tried 
all of the above, and when I evaluated some of them (back then in 2012/13), 
some did not meet our 
expectations concerning speed, ease of setup/administration and stability. But 
things might have changed of course.

Hope this helps,
infoomatic

Aw: How to filter spam with same to: and from: adress

[Infoomatic]

This is usually solved within your mta. In most simple setups, the MX server 
receiving the mails should not accept mails for which it is responsible itself, 
so your mailserver phyto.qc.ca should not accept mails with "from: 
a...@phyto.qc.ca" from other servers than what you defined (e.g. in 
"mynetworks" if you are using postfix).
On the other hand, you should make sure that your users cannot send their mails 
other than that linked to their accounts, so make sure j...@phyto.qc.ca cannot 
send as ma...@phyto.qc.ca ... if you are using postfix, you might have a look 
at reject_sender_login_mismatch.

hope this helps,

infoomatic

> Gesendet: Donnerstag, 14. April 2016 um 13:32 Uhr
> Von: Claude <cla...@phyto.qc.ca>
> An: "dovecot@dovecot.org >> dovecot dovecot.org" <dovecot@dovecot.org>
> Betreff: How to filter spam with same to: and from: adress
>
> Is it possible to create a filter somewhere to delete email that have same 
> to: and from: adress. All these email are forged using my domain name with 
> always different fictif user name. The only common point is that they have 
> the same user name in the from: and to: adress
> 
> Claude Gelinas agr.
> Phyto Ressources Inc.

Aw: bug in indexer/indexer-worker

[Infoomatic]

I guess this is the same issue: 
http://www.dovecot.org/list/dovecot/2015-June/101029.html


 Gesendet: Dienstag, 16. Juni 2015 um 14:07 Uhr
 Von: Infoomatic infooma...@gmx.at
 An: Dovecot ML dovecot@dovecot.org
 Betreff: bug in indexer/indexer-worker

 Hi,
 
 I have already mentioned this in 
 http://www.dovecot.org/pipermail/dovecot/2014-November/098592.html
 
 I could reproduce the errors above in a self-compiled v2.2.18 and the 
 prebuilt packages from xi.rename-it.nl (in addition to version 2.2.15 
 mentioned in the link)
 
 The problem occurs when enabling fts_tika in the plugins (tried tika 1.6, 1.7 
 and 1.8). I tried to move a folder of my mailbox with about 2000 mails to my 
 server (no users, modern hardware).
 At some point I get an error and from this time on dovecot keeps repeating 
 the last lines with every mail that comes in ... see [1]
 I then get kernel syslog messages like in [2]. when I try to index all users 
 (had another testuser) mailboxes with doveadm index I get the errors of [3].
 
 The mailfolder does contain mails with attachments of all sorts, videos, 
 office documents etc. When disabling fts_tika it works. dovecot -n output is 
 [4]
 
 Could someone of the devs please have a look?
 
 best regards,
 infoomatic
 
 
 [1] Then comes the panic which produces loads of errormessages below the Raw 
 backtrace part:
 Jun 16 10:11:08 testhost dovecot: indexer-worker(user1): Warning: I/O leak: 
 0x7f40b55c39d0 (line 411, fd 20)
 Jun 16 10:11:08 testhost dovecot: indexer-worker(user1): Warning: Timeout 
 leak: 0x7f40b55c3780 (line 325)
 Jun 16 10:11:08 testhost dovecot: indexer-worker(user1): Panic: file 
 ioloop.c: line 39 (io_add_file): assertion failed: (callback != NULL)
 Jun 16 10:11:08 testhost dovecot: indexer-worker(user1): Error: Raw 
 backtrace: /opt/dovecot/lib/dovecot/libdovecot.so.0(+0x78320) 
 [0x7f40b55f4320] - /opt/dovecot/lib/dovecot/libdovecot.so.0(+0x783fe) 
 [0x7f40b55f43fe] - /opt/dovecot/lib/dovecot/libdovecot.so.0(i_fatal+0) 
 [0x7f40b55a3b25] - /opt/dovecot/lib/dovecot/libdovecot.so.0(+0x897d0) 
 [0x7f40b56057d0] - 
 /opt/dovecot/lib/dovecot/libdovecot.so.0(io_loop_move_io+0x3e) 
 [0x7f40b560643e] - 
 /opt/dovecot/lib/dovecot/libdovecot.so.0(connection_switch_ioloop+0x14) 
 [0x7f40b55f21d4] - 
 /opt/dovecot/lib/dovecot/libdovecot.so.0(http_client_switch_ioloop+0x28) 
 [0x7f40b55c8148] - /opt/dovecot/lib/dovecot/libdovecot.so.0(+0x44536) 
 [0x7f40b55c0536] - 
 /opt/dovecot/lib/dovecot/lib21_fts_solr_plugin.so(solr_connection_post_more+0x49)
  [0x7f40b108d469] - 
 /opt/dovecot/lib/dovecot/lib21_fts_solr_plugin.so(+0x3ac9) [0x7f40b1089ac9] 
 - /opt/dovecot/lib/dovecot/lib21_fts_solr_plugin.so(+0x3b6d) 
 [0x7f40b1089b6d] - /opt/dovecot/lib/dovecot/lib20_fts_plugin.so(+0x86ec) 
 [0x7f40b495c6ec] - 
 /opt/dovecot/lib/dovecot/lib20_fts_plugin.so(fts_backend_update_deinit+0x23) 
 [0x7f40b495c723] - /opt/dovecot/lib/dovecot/lib20_fts_plugin.so(+0xe5cc) 
 [0x7f40b49625cc] - /opt/dovecot/lib/dovecot/lib20_fts_plugin.so(+0xf451) 
 [0x7f40b4963451] - /opt/dovecot/lib/dovecot/lib10_quota_plugin.so(+0xb454) 
 [0x7f40b4b97454] - /opt/dovecot/lib/dovecot/lib01_acl_plugin.so(+0xcfea) 
 [0x7f40b4daafea] - 
 /opt/dovecot/lib/dovecot/libdovecot-storage.so.0(mailbox_transaction_commit_get_changes+0x41)
  [0x7f40b58a64f1] - 
 /opt/dovecot/lib/dovecot/libdovecot-storage.so.0(mailbox_transaction_commit+0xe)
  [0x7f40b58a658e] - dovecot/indexer-worker() [0x40250c] - 
 /opt/dovecot/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x4c) 
 [0x7f40b560615c] - 
 /opt/dovecot/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0xbb) 
 [0x7f40b56070ab] - 
 /opt/dovecot/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x9) 
 [0x7f40b56061c9] - 
 /opt/dovecot/lib/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7f40b5606248] 
 - /opt/dovecot/lib/dovecot/libdovecot.so.0(master_service_run+0x13) 
 [0x7f40b55a9093] - dovecot/indexer-worker(main+0xe3) [0x401f03] - 
 /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) [0x7f40b51d8ec5] - 
 dovecot/indexer-worker() [0x401fc2]
 Jun 16 10:11:08 testhost dovecot: indexer: Error: Indexer worker 
 disconnected, discarding 2 requests for user1
 Jun 16 10:11:08 testhost dovecot: indexer-worker(user1): Fatal: master: 
 service(indexer-worker): child 2066 killed with signal 6 (core dumped)
 Jun 16 10:11:09 testhost dovecot: indexer-worker(user1): Warning: I/O leak: 
 0x7f25bc1689d0 (line 120, fd 23)
 Jun 16 10:11:09 testhost dovecot: indexer-worker(user1): Warning: Timeout 
 leak: 0x7f25bc168780 (line 325)
 Jun 16 10:11:09 testhost dovecot: indexer: Error: Indexer worker 
 disconnected, discarding 2 requests for user1
 Jun 16 10:11:09 testhost dovecot: indexer-worker(user1): Fatal: master: 
 service(indexer-worker): child 2124 killed with signal 11 (core dumped)
 Jun 16 10:11:09 testhost dovecot: indexer-worker(user1): Warning: I/O leak: 
 0x7f6cabb149d0 (line 120, fd 23)
 Jun 16 10:11:09 testhost dovecot: indexer-worker(user1): Warning: Timeout 
 leak

bug in indexer/indexer-worker

[Infoomatic]

Hi,

I have already mentioned this in 
http://www.dovecot.org/pipermail/dovecot/2014-November/098592.html

I could reproduce the errors above in a self-compiled v2.2.18 and the prebuilt 
packages from xi.rename-it.nl (in addition to version 2.2.15 mentioned in the 
link)

The problem occurs when enabling fts_tika in the plugins (tried tika 1.6, 1.7 
and 1.8). I tried to move a folder of my mailbox with about 2000 mails to my 
server (no users, modern hardware).
At some point I get an error and from this time on dovecot keeps repeating the 
last lines with every mail that comes in ... see [1]
I then get kernel syslog messages like in [2]. when I try to index all users 
(had another testuser) mailboxes with doveadm index I get the errors of [3].

The mailfolder does contain mails with attachments of all sorts, videos, office 
documents etc. When disabling fts_tika it works. dovecot -n output is [4]

Could someone of the devs please have a look?

best regards,
infoomatic


[1] Then comes the panic which produces loads of errormessages below the Raw 
backtrace part:
Jun 16 10:11:08 testhost dovecot: indexer-worker(user1): Warning: I/O leak: 
0x7f40b55c39d0 (line 411, fd 20)
Jun 16 10:11:08 testhost dovecot: indexer-worker(user1): Warning: Timeout leak: 
0x7f40b55c3780 (line 325)
Jun 16 10:11:08 testhost dovecot: indexer-worker(user1): Panic: file ioloop.c: 
line 39 (io_add_file): assertion failed: (callback != NULL)
Jun 16 10:11:08 testhost dovecot: indexer-worker(user1): Error: Raw backtrace: 
/opt/dovecot/lib/dovecot/libdovecot.so.0(+0x78320) [0x7f40b55f4320] - 
/opt/dovecot/lib/dovecot/libdovecot.so.0(+0x783fe) [0x7f40b55f43fe] - 
/opt/dovecot/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7f40b55a3b25] - 
/opt/dovecot/lib/dovecot/libdovecot.so.0(+0x897d0) [0x7f40b56057d0] - 
/opt/dovecot/lib/dovecot/libdovecot.so.0(io_loop_move_io+0x3e) [0x7f40b560643e] 
- /opt/dovecot/lib/dovecot/libdovecot.so.0(connection_switch_ioloop+0x14) 
[0x7f40b55f21d4] - 
/opt/dovecot/lib/dovecot/libdovecot.so.0(http_client_switch_ioloop+0x28) 
[0x7f40b55c8148] - /opt/dovecot/lib/dovecot/libdovecot.so.0(+0x44536) 
[0x7f40b55c0536] - 
/opt/dovecot/lib/dovecot/lib21_fts_solr_plugin.so(solr_connection_post_more+0x49)
 [0x7f40b108d469] - /opt/dovecot/lib/dovecot/lib21_fts_solr_plugin.so(+0x3ac9) 
[0x7f40b1089ac9] - /opt/dovecot/lib/dovecot/lib21_fts_solr_plugin.so(+0x3b6d) 
[0x7f40b1089b6d] - /opt/dovecot/lib/dovecot/lib20_fts_plugin.so(+0x86ec) 
[0x7f40b495c6ec] - 
/opt/dovecot/lib/dovecot/lib20_fts_plugin.so(fts_backend_update_deinit+0x23) 
[0x7f40b495c723] - /opt/dovecot/lib/dovecot/lib20_fts_plugin.so(+0xe5cc) 
[0x7f40b49625cc] - /opt/dovecot/lib/dovecot/lib20_fts_plugin.so(+0xf451) 
[0x7f40b4963451] - /opt/dovecot/lib/dovecot/lib10_quota_plugin.so(+0xb454) 
[0x7f40b4b97454] - /opt/dovecot/lib/dovecot/lib01_acl_plugin.so(+0xcfea) 
[0x7f40b4daafea] - 
/opt/dovecot/lib/dovecot/libdovecot-storage.so.0(mailbox_transaction_commit_get_changes+0x41)
 [0x7f40b58a64f1] - 
/opt/dovecot/lib/dovecot/libdovecot-storage.so.0(mailbox_transaction_commit+0xe)
 [0x7f40b58a658e] - dovecot/indexer-worker() [0x40250c] - 
/opt/dovecot/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x4c) [0x7f40b560615c] 
- /opt/dovecot/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0xbb) 
[0x7f40b56070ab] - 
/opt/dovecot/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x9) 
[0x7f40b56061c9] - /opt/dovecot/lib/dovecot/libdovecot.so.0(io_loop_run+0x38) 
[0x7f40b5606248] - 
/opt/dovecot/lib/dovecot/libdovecot.so.0(master_service_run+0x13) 
[0x7f40b55a9093] - dovecot/indexer-worker(main+0xe3) [0x401f03] - 
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) [0x7f40b51d8ec5] - 
dovecot/indexer-worker() [0x401fc2]
Jun 16 10:11:08 testhost dovecot: indexer: Error: Indexer worker disconnected, 
discarding 2 requests for user1
Jun 16 10:11:08 testhost dovecot: indexer-worker(user1): Fatal: master: 
service(indexer-worker): child 2066 killed with signal 6 (core dumped)
Jun 16 10:11:09 testhost dovecot: indexer-worker(user1): Warning: I/O leak: 
0x7f25bc1689d0 (line 120, fd 23)
Jun 16 10:11:09 testhost dovecot: indexer-worker(user1): Warning: Timeout leak: 
0x7f25bc168780 (line 325)
Jun 16 10:11:09 testhost dovecot: indexer: Error: Indexer worker disconnected, 
discarding 2 requests for user1
Jun 16 10:11:09 testhost dovecot: indexer-worker(user1): Fatal: master: 
service(indexer-worker): child 2124 killed with signal 11 (core dumped)
Jun 16 10:11:09 testhost dovecot: indexer-worker(user1): Warning: I/O leak: 
0x7f6cabb149d0 (line 120, fd 23)
Jun 16 10:11:09 testhost dovecot: indexer-worker(user1): Warning: Timeout leak: 
0x7f6cabb14780 (line 325)
Jun 16 10:11:09 testhost dovecot: indexer: Error: Indexer worker disconnected, 
discarding 2 requests for user1
Jun 16 10:11:09 testhost dovecot: indexer-worker(user1): Fatal: master: 
service(indexer-worker): child 2125 killed with signal 11 (core dumped)

[2] kernel syslog:
[Tue Jun 16 09:51:15 2015] indexer-worker[7592

Aw: fts_solr Bad Request / BUG: Unknown internal error

[Infoomatic]

Hi,
I had the same experience. I used the current dovecot and SOLR 5.2. It works 
with 4.10, so my first wild guess would be that there is a bug in dovecots url 
encoding sending to solr (they possibly updated some stuff in url handling? - 
don't know).

In SOLR 5.2 i created a core mail3 and copied the config from my working 4.10 
installation. Indexing new messages seem to work, but searching gives a http 
400 error.

Firing up the query in solrs web interface works ... one of my test cases was 
select?fl=uid,scorerows=3sort=uid+ascq=subject:%22blubb%22fq=%2Bbox:b624920e60057c554e4adf211752+%2Buser:%22user%22

For further reference see 
http://mail-archives.apache.org/mod_mbox/lucene-solr-user/201506.mbox/browser

Could the devs please have a look at this, it might hopefully be just a small 
change.

regards,
infoomatic

 Gesendet: Freitag, 12. Juni 2015 um 11:19 Uhr
 Von: Nick Rosier nick+dove...@bunbun.be
 An: dovecot@dovecot.org
 Betreff: fts_solr Bad Request / BUG: Unknown internal error

 Hi,
 
 yesterday I created a new mailbox; ever since (and only for the new 
 mailbox) I am getting these errors:
 
 2015-06-12T00:00:29.808526+02:00 mail dovecot: 
 indexer-worker(x...@example.com): Error: fts_solr: Lookup failed: Bad 
 Request
 2015-06-12T00:00:29.808560+02:00 mail dovecot: 
 indexer-worker(x...@example.com): Error: Mailbox INBOX: Status lookup 
 failed: BUG: Unknown internal error
 
 Is this a known issue?
 Rgds,
 N.
 

Aw: fts_solr Bad Request / BUG: Unknown internal error

[Infoomatic]

oops, sorry, the reference is 
http://mail-archives.apache.org/mod_mbox/lucene-solr-user/201506.mbox/%3Ctrinity-f5cc6586-2f21-4028-a5f6-a0e523d7129a-1434194382936%403capp-gmx-bs50%3E

 Gesendet: Sonntag, 14. Juni 2015 um 13:09 Uhr
 Von: Infoomatic infooma...@gmx.at
 An: Dovecot ML dovecot@dovecot.org
 Betreff: Aw: fts_solr Bad Request / BUG: Unknown internal error

 Hi,
 I had the same experience. I used the current dovecot and SOLR 5.2. It works 
 with 4.10, so my first wild guess would be that there is a bug in dovecots 
 url encoding sending to solr (they possibly updated some stuff in url 
 handling? - don't know).
 
 In SOLR 5.2 i created a core mail3 and copied the config from my working 
 4.10 installation. Indexing new messages seem to work, but searching gives a 
 http 400 error.
 
 Firing up the query in solrs web interface works ... one of my test cases was 
 select?fl=uid,scorerows=3sort=uid+ascq=subject:%22blubb%22fq=%2Bbox:b624920e60057c554e4adf211752+%2Buser:%22user%22
 
 For further reference see 
 http://mail-archives.apache.org/mod_mbox/lucene-solr-user/201506.mbox/browser
 
 Could the devs please have a look at this, it might hopefully be just a small 
 change.
 
 regards,
 infoomatic
 
  Gesendet: Freitag, 12. Juni 2015 um 11:19 Uhr
  Von: Nick Rosier nick+dove...@bunbun.be
  An: dovecot@dovecot.org
  Betreff: fts_solr Bad Request / BUG: Unknown internal error
 
  Hi,
  
  yesterday I created a new mailbox; ever since (and only for the new 
  mailbox) I am getting these errors:
  
  2015-06-12T00:00:29.808526+02:00 mail dovecot: 
  indexer-worker(x...@example.com): Error: fts_solr: Lookup failed: Bad 
  Request
  2015-06-12T00:00:29.808560+02:00 mail dovecot: 
  indexer-worker(x...@example.com): Error: Mailbox INBOX: Status lookup 
  failed: BUG: Unknown internal error
  
  Is this a known issue?
  Rgds,
  N.
  
 

dovecot only partially indexing ... fts

[Infoomatic]

hi,
I have a setup using solr as fts, however it seems that when I move messages it 
does not automatically index the stuff. Also, when using sieve scripts to store 
messages in different folders I get:
dovecot: indexer-worker(user): Indexed 0 messages in testfolder

If I get a mail to normal INBOX I get 
dovecot: indexer-worker(user): Indexed 1 messages in INBOX

doveadm index -u user '*'
does the trick, however, I have set fts_autoindex = yes ... the relevant part 
of doveconf -n:

mail_plugins = fts fts_solr zlib acl quota zlib fts fts_solr acl
plugin {
  fts = solr
  fts_autoindex = yes
  fts_solr = url=http://localhost:8983/solr/ break-imap-search
  sieve = ~/.dovecot.sieve
  sieve_dir = ~/sieve
  sieve_extensions = +notify +imapflags
}
protocol lda {
  mail_plugins = fts fts_solr zlib sieve acl
}
protocol imap {
  mail_plugins = fts fts_solr zlib acl quota imap_acl imap_quota
}

is this normal behaviour or did I screw something up? 

TIA,
infoomatic

error using fts/tika

[Infoomatic]

Hi,

I played around a bit and tried to get tika to run with dovecot. In the end I 
was at least a bit successful.
However, when I tried to index my inbox with doveadm index -A '*'

I get:
doveadm(infoomatic): Error: fts_tika: PUT http://localhost:8081/tika failed: 
500 Server Error
doveadm(infoomatic): Warning: I/O leak: 0x7f4f697bb170 (line 127, fd 24)
doveadm(infoomatic): Panic: file ioloop-iolist.c: line 22: unreached
doveadm(infoomatic): Error: Raw backtrace: 
/usr/lib/dovecot/libdovecot.so.0(+0x67f30) [0x7f4f697e8f30] - 
/usr/lib/dovecot/libdovecot.so.0(default_fatal_handler+0x2a) [0x7f4f697e8f9a] 
- /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7f4f6979c515] - 
/usr/lib/dovecot/libdovecot.so.0(+0x79b0d) [0x7f4f697fab0d] - 
/usr/lib/dovecot/libdovecot.so.0(io_loop_handle_add+0x3b) [0x7f4f697fb2ab] - 
/usr/lib/dovecot/libdovecot.so.0(+0x78cf1) [0x7f4f697f9cf1] - 
/usr/lib/dovecot/libdovecot.so.0(io_loop_move_io+0x3e) [0x7f4f697fa93e] - 
/usr/lib/dovecot/libdovecot.so.0(connection_switch_ioloop+0x14) 
[0x7f4f697e6df4] - 
/usr/lib/dovecot/libdovecot.so.0(http_client_switch_ioloop+0x28) 
[0x7f4f697bf8e8] - /usr/lib/dovecot/libdovecot.so.0(+0x36a86) [0x7f4f697b7a86] 
- 
/usr/lib/dovecot/modules/lib21_fts_solr_plugin.so(solr_connection_post_more+0x29)
 [0x7f4f68d9f069] - /usr/lib/dovecot/modules/lib21_fts_solr_plugin.so(+0x3547) 
[0x7f4f68d9b547] - 
/usr/lib/dovecot/modules/lib20_fts_plugin.so(fts_build_mail+0x35c) 
[0x7f4f68faaffc] - /usr/lib/dovecot/modules/lib20_fts_plugin.so(+0xd3ee) 
[0x7f4f68fb03ee] - 
/usr/lib/dovecot/libdovecot-storage.so.0(mail_precache+0x19) [0x7f4f69ac3c39] 
- doveadm() [0x419501] - doveadm() [0x4153c3] - 
doveadm(doveadm_mail_try_run+0x48c) [0x4162ac] - doveadm(main+0x3d8) 
[0x412588] - /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) 
[0x7f4f693dcec5] - doveadm() [0x4127a4]
Aborted (core dumped)

The last messages of the tika-server:
Nov 04, 2014 10:18:17 PM org.apache.tika.server.TikaResource logRequest
INFO: tika (video/x-ms-wmv)
Nov 04, 2014 10:18:17 PM org.apache.tika.server.TikaResource$3 write
WARNING: tika: Text extraction failed
org.apache.tika.exception.TikaException: Unexpected RuntimeException from 
org.apache.tika.server.TikaResource$1@44742f73
Nov 04, 2014 10:18:17 PM org.apache.cxf.jaxrs.utils.JAXRSUtils 
logMessageHandlerProblem
SEVERE: Problem with writing the data, class 
org.apache.tika.server.TikaResource$3, ContentType: text/plain
Nov 04, 2014 10:18:17 PM 
org.apache.cxf.jaxrs.impl.WebApplicationExceptionMapper toResponse
WARNING: javax.ws.rs.WebApplicationException: HTTP 415 Unsupported Media Type

dovecot -n:
# 2.2.15: /etc/dovecot/dovecot.conf
# OS: Linux 3.13.0-39-generic x86_64 Ubuntu 14.04.1 LTS ext4
auth_username_format = %n
disable_plaintext_auth = no
mail_gid = vmail
mail_home = /var/lib/vmail/home/%u
mail_location = mdbox:/var/lib/vmail/mail/%u
mail_plugins = fts fts_solr
mail_uid = vmail
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 ihave duplicate 
imapflags
mdbox_rotate_size = 32 M
namespace inbox {
  inbox = yes
  location = 
  mailbox Drafts {
special_use = \Drafts
  }
  mailbox Junk {
special_use = \Junk
  }
  mailbox Sent {
special_use = \Sent
  }
  mailbox Sent Messages {
special_use = \Sent
  }
  mailbox Trash {
special_use = \Trash
  }
  prefix = 
}
passdb {
  args = /etc/dovecot/dovecot-ldap.conf.ext
  driver = ldap
}
plugin {
  fts = solr
  fts_autoindex = yes
  fts_solr = url=http://localhost:8080/solr/ break-imap-search
  fts_tika = http://localhost:8081/tika
  sieve = ~/.dovecot.sieve
  sieve_dir = ~/sieve
  sieve_extensions = +imapflags
}
protocols =  imap sieve
service auth {
  unix_listener /var/spool/postfix/private/auth {
group = postfix
mode = 0660
user = postfix
  }
  unix_listener auth-userdb {
group = vmail
user = vmail
  }
}
service managesieve-login {
  inet_listener sieve_deprecated {
port = 2000
  }
}
ssl_cert = /etc/dovecot/dovecot.pem
ssl_key = /etc/dovecot/private/dovecot.pem
userdb {
  args = /etc/dovecot/dovecot-ldap.conf.ext
  driver = ldap
}
protocol lda {
  mail_plugins = fts fts_solr sieve
}

Has anyone hints? Or do the devs want some more information for debugging?

best regards,

infoomatic

Aw: Re: OT - Finding/removing duplicate emails - WAS: Re: [Dovecot] dovecot/lmtp munmap()-ing a lot

[Infoomatic]

  On 6/9/2014 5:44 PM, Ralf Hildebrandt r...@sys4.de wrote:
  That's probably the problem here. The user had LOTS of (duplicate!)
  mails in his inbox.

I had the same problem with a corrupted IBM Domino mailfile which gave me lots 
of duplicates, however imapsync with the options --useheader Date --useheader 
Subject --skipheader X.* to eliminate headers according to date+subject did 
the trick.

Alternatively you could have a look at the Thunderbird Addon Remove Duplicate 
Message (alternate) 0.39 - havent used it on large IMAP folders but works also 
nicely.

hth,
infoomatic

Aw: Re: Mailboxes are in Maildir format. Any good backup tips? Had success with version control?

[Infoomatic]

 If you actually want to preserve those increments (as opposed to just keeping
 an rsync mirror up-to-date), I like rdiff-backup.  It handles maildirs well
 because of the one-message-per-file design.
Second that. It's great tool that keeps an actual sync
(rsync-based) of the data-directory and the metadata (delta) in a
seperate directory to restore data from any date.

Alternatively, you might want to take a look at bacula, which was faster
in most cases (development seems to have stalled, but there is a fork I
have not had time to take a look at: bareos). However, I liked the
rdiff-backup way because I can restore files via scp or rsync (most of
my requests were like please restore from yesterday) or if I want to
restore data from a certain date I can use rdiff-backup from command
line (bacula is much more complex, and you need the admin tool to
restore files - rdiff-backup works from command line locally or via ssh/keyauth)

hth,
Robert

Re: [Dovecot] acl, shared folders

[Infoomatic]

Hi,
Thanks a lot for the reply! A simple
location = mdbox:/var/lib/vmail/mail/%%u
was the solution. (my tests before with INDEX files obviously broke some stuff, 
so I just created empty users and it worked as it should with my initial config)
 
best regards,
infoomatic
 

Gesendet: Dienstag, 07. Januar 2014 um 08:19 Uhr
Von: Steffen Kaiser skdove...@smail.inf.fh-brs.de
An: Infoomatic infooma...@gmx.at
Cc: dovecot@dovecot.org
Betreff: Re: [Dovecot] acl, shared folders
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, 6 Jan 2014, Infoomatic 
wrote:  After spending quite some time to figure out how users can share 
folders I now hope someone of you could help me out. I am quite sure its just a 
stupid mistake/misunderstanding ... I am using Ubuntu 12.04 LTS with the 
shipped dovecot 2.0.19 I'm using v2.2, but it should apply to v2.0 as well.  
This seems fine. ACLs look fine.  However, there is nothing listed in the 
account of user2. I think the  mistake is in the namespace configuration of 
location or prefix     mail_home = /var/lib/vmail/home/%u  mail_location 
= mdbox:/var/lib/vmail/mail/%u  namespace {    inbox = yes    location =    
prefix =    separator = /    type = private  }  namespace {    list = 
children    location = mdbox:/var/lib/vmail/mail/%%n/mailboxes/shared/%n    
prefix = shared/%%n/    separator = /    subscriptions = no    type = shared 
 } First note, that you use %u in the default location, but %n in the shared 
namespace definition. IMHO, you must stick to one, as only one is correct in 
your setup. Second, reread http://wiki2.dovecot.org/SharedMailboxes/Shared Say 
user1 is sharing to user2, then your second namespace tells Dovecot to look for 
user1's mailboxes in /var/lib/vmail/mail/user1/mailboxes/shared/user2, you most 
likely need to replicate the default mail_location there with %'s doubled. Then 
you must decide, where each user's INDEX and CONTROL information is stored, or 
if flags are shared as well. - From your current definition I would say, you 
need: location = mdbox:/var/lib/vmail/mail/%%u:INDEX=~/shared/%%u First part 
points to the directory of the user sharing the mailboxes, INDEX= places 
user-specific files of the user accessing shared mailboxes into his/her own 
hierarchie. - -- Steffen Kaiser -BEGIN PGP SIGNATURE- Version: GnuPG 
v1.4.11 (GNU/Linux) 
iQEVAwUBUsuqhV3r2wJMiz2NAQK+lAgAu46HGrSz3h8JGGM7hJpLHsuDkypHD8Xr 
ThbicfUC5CVOBk1xs3FkXM1gDecb8820f6JrDSe24slg6Lf7WWPdZdGEzc4f0Dnr 
btL4+ePrRrI+UyuRXtmm7hZu6JaUwJj+h8AOmpzg+swJokHWUGkY73vcFri+O2bt 
Dfd+HbZqmuCjJ+aauLKclEEGCQ45JHKC/LavxnBFPix48PoCEOrfaVrC3R9mFjGD 
7CJbzgi2T2xJIdYzl+pvFRgEu8aT6AtgQo+4BE51PaLz/8XUE4NX5usV/kcLgu9O 
iz5VQcgKXFFoJ1HD37kcwNVkkAx67yDTVdDyLgvH9j0CYBpvnxDM4g== =WVlL -END PGP 
SIGNATURE-

[Dovecot] acl, shared folders

[Infoomatic]

Hi list,
 
After spending quite some time to figure out how users can share folders I now 
hope someone of you could help me out. I am quite sure its just a stupid 
mistake/misunderstanding ... I am using Ubuntu 12.04 LTS with the shipped 
dovecot 2.0.19
When I login via telnet as user1 I get the following:
1 create folder1
1 OK Create completed.
2 setacl folder1 user2 rli
2 OK Setacl complete.
3 getacl folder1
* ACL folder1 user2 ilr user1 lrwstipekxacd
3 OK Getacl completed.
 
This seems fine. However, there is nothing listed in the account of user2. I 
think the mistake is in the namespace configuration of location or prefix
 
Please help! Thanks!
 
infoomatic
 
# 2.0.19: /etc/dovecot/dovecot.conf
# OS: Linux 3.2.0-45-generic x86_64 Ubuntu 12.04.3 LTS ext4
auth_username_format = %n
disable_plaintext_auth = no
mail_debug = yes
mail_gid = vmail
mail_home = /var/lib/vmail/home/%u
mail_location = mdbox:/var/lib/vmail/mail/%u
mail_plugins =  acl zlib fts fts_solr acl
mail_uid = vmail
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 ihave imapflags
mdbox_rotate_size = 64 M
namespace {
  inbox = yes
  location =
  prefix =
  separator = /
  type = private
}
namespace {
  list = children
  location = mdbox:/var/lib/vmail/mail/%%n/mailboxes/shared/%n
  prefix = shared/%%n/
  separator = /
  subscriptions = no
  type = shared
}
passdb {
  args = /etc/dovecot/dovecot-ldap.conf.ext
  driver = ldap
}
plugin {
  acl = vfile
  acl_shared_dict = file:/var/lib/vmail/shared-mailboxes
  fts = solr
  fts_solr = break-imap-search url=http://localhost:8080/solr/
  sieve = ~/.dovecot.sieve
  sieve_dir = ~/sieve
  sieve_extensions = +imapflags
  zlib_save = bz2
  zlib_save_level = 6
}
protocols =  imap sieve pop3
service auth {
  unix_listener /var/spool/postfix/private/auth {
    group = postfix
    mode = 0660
    user = postfix
  }
  unix_listener auth-userdb {
    group = vmail
    user = vmail
  }
}
service managesieve-login {
  inet_listener sieve_deprecated {
    port = 2000
  }
}
ssl_cert = /etc/ssl/certs/dovecot.pem
ssl_key = /etc/ssl/private/dovecot.pem
userdb {
  args = /etc/dovecot/dovecot-ldap.conf.ext
  driver = ldap
}
protocol lda {
  mail_plugins =  sieve acl
}
protocol imap {
  mail_plugins =  acl imap_acl
}