Re: version conflict in freebsdports?

2018-01-23 Thread @lbutlr 


> On 23 Jan 2018, at 18:49, Vlad K.  wrote:
> 
> On 2018-01-24 02:22, @lbutlr wrote:
>> I have dovecot 2.2.33 installed. When trying to install
>> dovecot2-pigeonhole (v 0.4.19) I get the following when it tries to
>> install dovecot 2.2.31_1
> 
> 
> dovecot2 was renamed to dovecot back in August, so was dovecot2-pigeonhole to 
> dovecot-pigeonhole, as dovecot v1 was dropped, in FreeBSD ports. Read 
> /usr/ports/UPDATING for more info (20170807). Uninstall *2 and reinstall 
> packages without 2.

Ah, ok. You'd think someone would have marked the dovecot2 packages as old. 
Will recompile.

Thank you.

-- 
I CAN BE ROBBED BUT NEVER DENIED, I TOLD MYSELF. WHY WORRY?  'I too
cannot be cheated,' snapped Fate. SO I HAVE HEARD.

Out of memory on lmtp vsz_limit

2018-01-23 Thread Terence Lau 
Hi,

We've been getting these types or errors for quite a while now ...

Fatal: master: service(lmtp): child 63477 returned error 83 (Out of memory 
(service lmtp { vsz_limit=4096 MB }, you may need to increase it)

... and these errors have been decreasing in occurrence as we increased the 
default_vsz_limit.  Which is good but I would like to get some advice on how I 
could possibly eliminate the errors.

We have an internal smtp server (postfix 3.1.0) that has the config 
"always_bcc=arch...@company.com" over lmtp.  This mailbox is on a separate 
dovecot server with the following config (please let me know if the full config 
is required):

# 2.2.22 (fe789d2): /etc/dovecot/dovecot.conf
# Pigeonhole version 0.4.13 (7b14904)
# OS: Linux 4.4.0-109-generic x86_64 Ubuntu 16.04.1 LTS ext4
default_vsz_limit = 4 G
mail_location = maildir:/home/vmail/%d/%n
protocols = " imap lmtp pop3"
service lmtp {
  inet_listener lmtp {
port = 24
  }
}
userdb {
  args = username_format=%u /etc/dovecot/users
  default_fields = uid=vmail gid=vmail home=/home/vmail/%d/%n
  driver = passwd-file
}
protocol lmtp {
  mail_plugins =
}

Since we discovered the errors, we've been increasing the default_vsz_limit to 
1G, then 2G and now 4G (Server has 6GB of memory).  These errors occur whenever 
a large number of emails get sent around the same time to our smtp server.  
This causes the dovecot server to start crunching CPU and Memory.  Load average 
goes through the roof and takes some time to come back down as the smtp queue 
clears itself.

This mailbox is obviously very large but we have a script that runs daily to 
delete any emails older than a month:

find /home/vmail/company.com/archive/new/ -type f -mtime +30 -exec rm {} \;
find /home/vmail/company.com/archive/cur/ -type f -mtime +30 -exec rm {} \;

Still, the mailbox has on average of just under 300,000 emails.  No one 
accesses this mailbox with an email client, not until we need to dig something 
up.  And this has only happen once.  So the emails pretty much never get 
read/process by a user.

Now that we've increased the default_vsz_limit to 4G, the occurrence of these 
errors has reduced considerably.  But they still happen occasionally.  Short of 
increasing the memory further, are there any other options I have?

Thanks.
[https://www.royhill.com.au/email/Emalisignaturecurrent.jpg]

Re: version conflict in freebsdports?

2018-01-23 Thread Vlad K. 

On 2018-01-24 02:22, @lbutlr wrote:

I have dovecot 2.2.33 installed. When trying to install
dovecot2-pigeonhole (v 0.4.19) I get the following when it tries to
install dovecot 2.2.31_1



dovecot2 was renamed to dovecot back in August, so was 
dovecot2-pigeonhole to dovecot-pigeonhole, as dovecot v1 was dropped, in 
FreeBSD ports. Read /usr/ports/UPDATING for more info (20170807). 
Uninstall *2 and reinstall packages without 2.



--
Vlad K.

version conflict in freebsdports?

2018-01-23 Thread @lbutlr 
I have dovecot 2.2.33 installed. When trying to install dovecot2-pigeonhole (v 
0.4.19) I get the following when it tries to install dovecot 2.2.31_1

I run portsnap fetch update daily, and I ran it again after this error, but 
same result.

===>  Installing for dovecot2-2.2.31_1
===>  Checking if dovecot2 already installed
===>   Registering installation for dovecot2-2.2.31_1 as automatic
Installing dovecot2-2.2.31_1...
pkg-static: dovecot2-2.2.31_1 conflicts with dovecot-2.2.33.2_2 (installs files 
into the same place).  Problematic file: /usr/local/bin/doveadm
*** Error code 70

(FreeBSD 11.1)

-- 
Take my hand and I'll show you what was and will be.

Re: PDFs getting mangled

2018-01-23 Thread Stephan Bosch 
Op 1/22/2018 om 8:58 PM schreef Stephan Bosch:
> Op 1/21/2018 om 4:34 PM schreef Stephan Bosch:
>> Op 1/20/2018 om 11:01 PM schreef Adam Weinberger:
 On 20 Jan, 2018, at 10:05, Adam Weinberger  wrote:


> On 19 Jan, 2018, at 4:39, Aki Tuomi  wrote:
>
>
>
> On 19.01.2018 04:35, Adam Weinberger wrote:
>> Since upgrading to 2.3.0 / 0.5.0.1, incoming PDFs are getting mangled.
>> It seems to be happening when I use vnd.dovecot.filter. When I comment
>> out the block, things come through fine.
>>
>> My filter block looks like this:
>>    require "vnd.dovecot.filter";
>>    filter "bogofilter_filter";
>>
>>     if header :contains "X-Bogosity" [
>>     "Spam, tests=bogofilter, spamicity=1.00",
>>     "Spam, tests=bogofilter, spamicity=0.99"
>>     ] {
>>     fileinto "spam/totally";
>>     stop;
>>     }
>>     elsif header :contains "X-Bogosity" "Spam," {
>>     fileinto "spam/probably";
>>     stop;
>>     }
>>     elsif header :contains "X-Bogosity" "Unsure," {
>>     fileinto "spam/maybe";
>>     stop;
>>     }
>>
>> filter/bogofilter_filter looks like this:
>>     #!/bin/sh
>>     cat /dev/stdin | /usr/local/bin/bogofilter -p -e -c
>> /path/to/bogofilter.cf
>>
>> Images seem to come through fine. I didn't have this problem before
>> the
>> upgrade. It could easily be a problem with bogofilter, but I figured
>> that I'd check here first to see if anybody else has an
>> attachment-mangling issue with vnd.dovecot.filter.
>>
>> # Adam
>>
>>
>> -- 
>> Adam Weinberger
>> ad...@adamw.org
>> http://www.adamw.org
> It might work better with
>
> exec /usr/local/bin/bogofilter -p -e -c /path/to/bogofilter.cf
>
> Aki
 After looking into this some more, what's happening is that messages
 are getting truncated. Regardless of whether it's an attachment or
 just a long message body, the message gets truncated.

 To show this, I made a fileinto :copy rule to save a message copy
 before it gets sent off to bogofilter.

 You can see from the below pastings that the message is definitely
 getting truncated. When I replace my filter script with "cat
 /dev/stdin", it works fine. When I send the message to bogofilter on
 the command-line, it works fine. Something about the combination of
 vnd.dovecot.filter + bogofilter is causing the messages to truncate,
 and I don't know whether it's from truncating on the send or receive
 of the filter.

 Can you give me any advice?

 1)
 $ jot 20 1 > numbers.txt
 $ du -a . | grep numbers
 1260    ./numbers-sent.txt
 1248    ./numbers-received.txt

 2)
 root@imap:~# ll test-*
 125 -rw---  1 root  wheel   123K Jan 20 09:35 test-afterbogo.msg
 149 -rw---  1 root  wheel   136K Jan 20 09:35 test-beforebogo.msg
>>> The more I look into it, the more it looks to me like pigeonhole is
>>> somehow losing the last 4-6K of messages over 100K.
>>>
>>> When my filter script is:
>>> cat /dev/stdin | tee /tmp/input | bogofilter[...] | tee /tmp/output
>>> Then /tmp/output is the full message, but what pigeonhole gets back is
>>> truncated at by about 4K.
>>>
>>> Same with
>>> [...] bogofilter[...] > /tmp/output; cat /tmp/output
>>> The message is truncated there too.
>>>
>>> I've tried everything I can think of to make sure it's not a buffering
>>> problem:
>>> [...] bogofilter[...] | cat
>>> [...] bogofilter[...] | dd bs=1k
>>> [...] bogofilter[...] ; a=$?; sleep 2; exit $a
>>>
>>> But everything I do comes up with the same problem.
>>>
>>> But a simple "cat /dev/stdin" and the message comes through fine.
>>>
>>> Your help is really appreciated. I'm in the process of buying a house,
>>> so the mangled attachments is not coming at a great time :-)
>> We are looking into it.
> Problem found; working on a fix.

Fix pending:

https://github.com/stephanbosch/dovecot-core/commits/fix-program-client-big-io

This is a feature branch of 9 commits containing the fix and also
cleanups and reliability improvements. This is of course based on master.

Regards,

Stephan.

Re: Dovecot 2.3.0 TLS

2018-01-23 Thread Mark Moseley 
On Tue, Jan 23, 2018 at 10:05 AM, Aki Tuomi  wrote:

>
> > On January 23, 2018 at 7:09 PM Arkadiusz Miśkiewicz 
> wrote:
> >
> >
> > On Thursday 11 of January 2018, Aki Tuomi wrote:
> >
> > > Seems we might've made a unexpected change here when we revamped the
> ssl
> > > code.
> >
> > Revamped, interesting, can it support milions certs now on single
> machine? (so
> > are certs loaded by demand and not wasting memory)
> >
> > > Aki
> >
> >
> > --
> > Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org )
>
> Unfortunately not. This time round it was about putting the ssl code
> mostly in one place, so that we use same code for all SSL connections.
>
>

Just to chime in, having some way of supporting SSL certs dynamically would
be tremendously useful. Like splitting out the retrieval of certs/key to a
socket, that would typically just be a built-in regular dovecot service
("go and get the certs that are configured in dovecot configs"), but could
also be a custom unix listener that could return certs/keys. Dovecot would
send in the local IP/port and/or SNI name (if there was one) to the socket
and then use whatever comes back. A perl/python/etc script doing the unix
listener could then grab the appropriate cert/key from wherever (and
dovecot would presumably have a time-based cache for certs/keys).  This is
just wish-listing :)

Currently, I've got a million different domains on my dovecot boxes, so
allowing them all to use per-domain SSL is a bit challenging. I've been
searching for an SSL proxy that supports something like nginx/openresty's
"ssl_certificate_by_lua_file" (and can communicate the remote IP to dovecot
like haproxy does) to put in front of dovecot, to no avail. Having
something like that built directly into dovecot would be a dream -- or that
can at least farm that functionality out to a custom daemon).

Auth cache prevents login when non-password fields change

2018-01-23 Thread Tom Sommer 
The auth cache contains all fields returned by "password_query" (in 
itself a little odd), including the fields "nologin" and "reason".


If a user is cached with "nologin=Y" and the database-source is changed 
so nologin condition is no longer true, then the cache prevents login 
for as long as the TTL remain?


is there any way around this?

Thanks
--
Tom

Re: Panic: data stack: Out of memory when allocating bytes

2018-01-23 Thread Josef 'Jeff' Sipek 
On Tue, Jan 23, 2018 at 14:03:27 -0500, Josef 'Jeff' Sipek wrote:
> On Tue, Jan 23, 2018 at 18:21:38 +0100, Thomas Robers wrote:
> > Hello,
> > 
> > I'm using Dovecot 2.3 and sometimes i get this:
> > 
> > --- snip ---
> > Jan 23 14:23:13 mail dovecot: imap(b...@tutech.de)<4880>:
> > Panic: data stack: Out of memory when allocating 134217768 bytes
> 
> Interesting... imap is trying to allocate 128MB and failing.  A couple of
> questions:
> 
> 0. Does this user have any unusually large emails?
> 1. Do you have any idea what the imap process was doing at the time of the
>allocation failure?
> 2. You snipped all the important parts of the back trace. :)  It *starts* on
>the line:
>   #0  0x7f73f1386495 in raise () from /lib64/libc.so.6

In case you haven't used gdb before...  after starting up gdb, run "bt full"
at the gdb prompt.  That'll print out a very detailed backtrace.  (You might
want to sanity check it to make sure there aren't any user passwords in it
before posting it here...)

Jeff.

>Having the backtrace should help answer question number 1.
> 3. How big is this process when it dies?
> 4. Do you have any sort of ulimit/rlimit set on dovecot in whatever startup
>script you use?
> 5. Do you use cgroups to limit memory usage?
> 6. Did you disable memory overcommit on the system?
> 
> Jeff.
> 
> > Jan 23 14:23:13 mail dovecot: imap(b...@tutech.de)<4880>:
> > Fatal: master: service(imap): child 4880 killed with signal 6 (core dumped)
> > --- snip ---
> > 
> > The gdb backtrace is:
> > 
> > --- snip ---
> > GNU gdb (GDB) Red Hat Enterprise Linux (7.2-92.el6)
> > Copyright (C) 2010 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/libexec/dovecot/imap...(no debugging symbols
> > found)...done.
> > Attaching to program: /usr/libexec/dovecot/imap, process 4880
> > ptrace: Kein passender Prozess gefunden.
> > [New Thread 4880]
> > Reading symbols from /usr/lib64/dovecot/libdovecot-storage.so.0...(no
> > debugging symbols found)...done.
> > Loaded symbols for /usr/lib64/dovecot/libdovecot-storage.so.0
> > Reading symbols from /usr/lib64/dovecot/libdovecot.so.0...(no debugging
> > symbols found)...done.
> > Loaded symbols for /usr/lib64/dovecot/libdovecot.so.0
> > Reading symbols from /lib64/libc.so.6...(no debugging symbols found)...done.
> > Loaded symbols for /lib64/libc.so.6
> > Reading symbols from /lib64/librt.so.1...(no debugging symbols
> > found)...done.
> > Loaded symbols for /lib64/librt.so.1
> > Reading symbols from /lib64/libdl.so.2...(no debugging symbols
> > found)...done.
> > Loaded symbols for /lib64/libdl.so.2
> > Reading symbols from /lib64/ld-linux-x86-64.so.2...(no debugging symbols
> > found)...done.
> > Loaded symbols for /lib64/ld-linux-x86-64.so.2
> > Reading symbols from /lib64/libpthread.so.0...(no debugging symbols
> > found)...done.
> > [Thread debugging using libthread_db enabled]
> > Loaded symbols for /lib64/libpthread.so.0
> > Reading symbols from /usr/lib64/dovecot/lib01_acl_plugin.so...(no debugging
> > symbols found)...done.
> > Loaded symbols for /usr/lib64/dovecot/lib01_acl_plugin.so
> > Reading symbols from /usr/lib64/dovecot/lib02_imap_acl_plugin.so...(no
> > debugging symbols found)...done.
> > Loaded symbols for /usr/lib64/dovecot/lib02_imap_acl_plugin.so
> > Reading symbols from /usr/lib64/dovecot/lib15_notify_plugin.so...(no
> > debugging symbols found)...done.
> > Loaded symbols for /usr/lib64/dovecot/lib15_notify_plugin.so
> > Reading symbols from /usr/lib64/dovecot/lib20_mail_log_plugin.so...(no
> > debugging symbols found)...done.
> > Loaded symbols for /usr/lib64/dovecot/lib20_mail_log_plugin.so
> > Reading symbols from /usr/lib64/dovecot/lib20_zlib_plugin.so...(no debugging
> > symbols found)...done.
> > Loaded symbols for /usr/lib64/dovecot/lib20_zlib_plugin.so
> > Reading symbols from /lib64/libz.so.1...(no debugging symbols found)...done.
> > Loaded symbols for /lib64/libz.so.1
> > Reading symbols from /lib64/libbz2.so.1...(no debugging symbols
> > found)...done.
> > Loaded symbols for /lib64/libbz2.so.1
> > Reading symbols from /usr/lib64/dovecot/lib30_imap_zlib_plugin.so...(no
> > debugging symbols found)...done.
> > Loaded symbols for /usr/lib64/dovecot/lib30_imap_zlib_plugin.so
> > Core was generated by `dovecot/imap'.
> > Program terminated with signal 6, Aborted.
> > #0  0x7f73f1386495 in raise () from /lib64/libc.so.6
> > --- snip ---
> > 
> > I searched for that error message but only found some entries regarding
> > older dovecot versions and setting "mail_process_size" but i couldn't
> > fi

Re: Panic: data stack: Out of memory when allocating bytes

2018-01-23 Thread Josef 'Jeff' Sipek 
On Tue, Jan 23, 2018 at 18:21:38 +0100, Thomas Robers wrote:
> Hello,
> 
> I'm using Dovecot 2.3 and sometimes i get this:
> 
> --- snip ---
> Jan 23 14:23:13 mail dovecot: imap(b...@tutech.de)<4880>:
> Panic: data stack: Out of memory when allocating 134217768 bytes

Interesting... imap is trying to allocate 128MB and failing.  A couple of
questions:

0. Does this user have any unusually large emails?
1. Do you have any idea what the imap process was doing at the time of the
   allocation failure?
2. You snipped all the important parts of the back trace. :)  It *starts* on
   the line:
#0  0x7f73f1386495 in raise () from /lib64/libc.so.6
   Having the backtrace should help answer question number 1.
3. How big is this process when it dies?
4. Do you have any sort of ulimit/rlimit set on dovecot in whatever startup
   script you use?
5. Do you use cgroups to limit memory usage?
6. Did you disable memory overcommit on the system?

Jeff.

> Jan 23 14:23:13 mail dovecot: imap(b...@tutech.de)<4880>:
> Fatal: master: service(imap): child 4880 killed with signal 6 (core dumped)
> --- snip ---
> 
> The gdb backtrace is:
> 
> --- snip ---
> GNU gdb (GDB) Red Hat Enterprise Linux (7.2-92.el6)
> Copyright (C) 2010 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/libexec/dovecot/imap...(no debugging symbols
> found)...done.
> Attaching to program: /usr/libexec/dovecot/imap, process 4880
> ptrace: Kein passender Prozess gefunden.
> [New Thread 4880]
> Reading symbols from /usr/lib64/dovecot/libdovecot-storage.so.0...(no
> debugging symbols found)...done.
> Loaded symbols for /usr/lib64/dovecot/libdovecot-storage.so.0
> Reading symbols from /usr/lib64/dovecot/libdovecot.so.0...(no debugging
> symbols found)...done.
> Loaded symbols for /usr/lib64/dovecot/libdovecot.so.0
> Reading symbols from /lib64/libc.so.6...(no debugging symbols found)...done.
> Loaded symbols for /lib64/libc.so.6
> Reading symbols from /lib64/librt.so.1...(no debugging symbols
> found)...done.
> Loaded symbols for /lib64/librt.so.1
> Reading symbols from /lib64/libdl.so.2...(no debugging symbols
> found)...done.
> Loaded symbols for /lib64/libdl.so.2
> Reading symbols from /lib64/ld-linux-x86-64.so.2...(no debugging symbols
> found)...done.
> Loaded symbols for /lib64/ld-linux-x86-64.so.2
> Reading symbols from /lib64/libpthread.so.0...(no debugging symbols
> found)...done.
> [Thread debugging using libthread_db enabled]
> Loaded symbols for /lib64/libpthread.so.0
> Reading symbols from /usr/lib64/dovecot/lib01_acl_plugin.so...(no debugging
> symbols found)...done.
> Loaded symbols for /usr/lib64/dovecot/lib01_acl_plugin.so
> Reading symbols from /usr/lib64/dovecot/lib02_imap_acl_plugin.so...(no
> debugging symbols found)...done.
> Loaded symbols for /usr/lib64/dovecot/lib02_imap_acl_plugin.so
> Reading symbols from /usr/lib64/dovecot/lib15_notify_plugin.so...(no
> debugging symbols found)...done.
> Loaded symbols for /usr/lib64/dovecot/lib15_notify_plugin.so
> Reading symbols from /usr/lib64/dovecot/lib20_mail_log_plugin.so...(no
> debugging symbols found)...done.
> Loaded symbols for /usr/lib64/dovecot/lib20_mail_log_plugin.so
> Reading symbols from /usr/lib64/dovecot/lib20_zlib_plugin.so...(no debugging
> symbols found)...done.
> Loaded symbols for /usr/lib64/dovecot/lib20_zlib_plugin.so
> Reading symbols from /lib64/libz.so.1...(no debugging symbols found)...done.
> Loaded symbols for /lib64/libz.so.1
> Reading symbols from /lib64/libbz2.so.1...(no debugging symbols
> found)...done.
> Loaded symbols for /lib64/libbz2.so.1
> Reading symbols from /usr/lib64/dovecot/lib30_imap_zlib_plugin.so...(no
> debugging symbols found)...done.
> Loaded symbols for /usr/lib64/dovecot/lib30_imap_zlib_plugin.so
> Core was generated by `dovecot/imap'.
> Program terminated with signal 6, Aborted.
> #0  0x7f73f1386495 in raise () from /lib64/libc.so.6
> --- snip ---
> 
> I searched for that error message but only found some entries regarding
> older dovecot versions and setting "mail_process_size" but i couldn't
> find anything regarding Dovecot Version 2.3. Maybe it's something that is
> fixed already but if so i can't find it. Or is this a configuration issue or
> a bug?
> 
> Here my Dovecot configuration:
> 
> --- snip ---
> # 2.3.0 (c8b89eb): /etc/dovecot/dovecot.conf
> # Pigeonhole version 0.5.0.1 (d33dca20)
> # OS: Linux 2.6.32-696.3.1.el6.x86_64 x86_64 CentOS release 6.9 (Final) ext4
> auth_debug = yes
> auth_debug_passwords = yes
> auth_master_user_separator = *
> auth_mechanisms = plain login
> auth_verbose = yes
> disable_plain

Re: Dovecot 2.3.0 TLS

2018-01-23 Thread Aki Tuomi 

> On January 23, 2018 at 7:09 PM Arkadiusz Miśkiewicz  wrote:
> 
> 
> On Thursday 11 of January 2018, Aki Tuomi wrote:
> 
> > Seems we might've made a unexpected change here when we revamped the ssl
> > code. 
> 
> Revamped, interesting, can it support milions certs now on single machine? 
> (so 
> are certs loaded by demand and not wasting memory)
> 
> > Aki
> 
> 
> -- 
> Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org )

Unfortunately not. This time round it was about putting the ssl code mostly in 
one place, so that we use same code for all SSL connections.

Aki

Panic: data stack: Out of memory when allocating bytes

2018-01-23 Thread Thomas Robers 

Hello,

I'm using Dovecot 2.3 and sometimes i get this:

--- snip ---
Jan 23 14:23:13 mail dovecot: 
imap(b...@tutech.de)<4880>: Panic: data stack: Out of 
memory when allocating 134217768 bytes
Jan 23 14:23:13 mail dovecot: 
imap(b...@tutech.de)<4880>: Fatal: master: 
service(imap): child 4880 killed with signal 6 (core dumped)

--- snip ---

The gdb backtrace is:

--- snip ---
GNU gdb (GDB) Red Hat Enterprise Linux (7.2-92.el6)
Copyright (C) 2010 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/libexec/dovecot/imap...(no debugging symbols 
found)...done.

Attaching to program: /usr/libexec/dovecot/imap, process 4880
ptrace: Kein passender Prozess gefunden.
[New Thread 4880]
Reading symbols from /usr/lib64/dovecot/libdovecot-storage.so.0...(no 
debugging symbols found)...done.

Loaded symbols for /usr/lib64/dovecot/libdovecot-storage.so.0
Reading symbols from /usr/lib64/dovecot/libdovecot.so.0...(no debugging 
symbols found)...done.

Loaded symbols for /usr/lib64/dovecot/libdovecot.so.0
Reading symbols from /lib64/libc.so.6...(no debugging symbols found)...done.
Loaded symbols for /lib64/libc.so.6
Reading symbols from /lib64/librt.so.1...(no debugging symbols 
found)...done.

Loaded symbols for /lib64/librt.so.1
Reading symbols from /lib64/libdl.so.2...(no debugging symbols 
found)...done.

Loaded symbols for /lib64/libdl.so.2
Reading symbols from /lib64/ld-linux-x86-64.so.2...(no debugging symbols 
found)...done.

Loaded symbols for /lib64/ld-linux-x86-64.so.2
Reading symbols from /lib64/libpthread.so.0...(no debugging symbols 
found)...done.

[Thread debugging using libthread_db enabled]
Loaded symbols for /lib64/libpthread.so.0
Reading symbols from /usr/lib64/dovecot/lib01_acl_plugin.so...(no 
debugging symbols found)...done.

Loaded symbols for /usr/lib64/dovecot/lib01_acl_plugin.so
Reading symbols from /usr/lib64/dovecot/lib02_imap_acl_plugin.so...(no 
debugging symbols found)...done.

Loaded symbols for /usr/lib64/dovecot/lib02_imap_acl_plugin.so
Reading symbols from /usr/lib64/dovecot/lib15_notify_plugin.so...(no 
debugging symbols found)...done.

Loaded symbols for /usr/lib64/dovecot/lib15_notify_plugin.so
Reading symbols from /usr/lib64/dovecot/lib20_mail_log_plugin.so...(no 
debugging symbols found)...done.

Loaded symbols for /usr/lib64/dovecot/lib20_mail_log_plugin.so
Reading symbols from /usr/lib64/dovecot/lib20_zlib_plugin.so...(no 
debugging symbols found)...done.

Loaded symbols for /usr/lib64/dovecot/lib20_zlib_plugin.so
Reading symbols from /lib64/libz.so.1...(no debugging symbols found)...done.
Loaded symbols for /lib64/libz.so.1
Reading symbols from /lib64/libbz2.so.1...(no debugging symbols 
found)...done.

Loaded symbols for /lib64/libbz2.so.1
Reading symbols from /usr/lib64/dovecot/lib30_imap_zlib_plugin.so...(no 
debugging symbols found)...done.

Loaded symbols for /usr/lib64/dovecot/lib30_imap_zlib_plugin.so
Core was generated by `dovecot/imap'.
Program terminated with signal 6, Aborted.
#0  0x7f73f1386495 in raise () from /lib64/libc.so.6
--- snip ---

I searched for that error message but only found some entries regarding
older dovecot versions and setting "mail_process_size" but i couldn't
find anything regarding Dovecot Version 2.3. Maybe it's something that 
is fixed already but if so i can't find it. Or is this a configuration 
issue or a bug?


Here my Dovecot configuration:

--- snip ---
# 2.3.0 (c8b89eb): /etc/dovecot/dovecot.conf
# Pigeonhole version 0.5.0.1 (d33dca20)
# OS: Linux 2.6.32-696.3.1.el6.x86_64 x86_64 CentOS release 6.9 (Final) ext4
auth_debug = yes
auth_debug_passwords = yes
auth_master_user_separator = *
auth_mechanisms = plain login
auth_verbose = yes
disable_plaintext_auth = no
doveadm_password =  # hidden, use -P to show it
doveadm_port = 12345
imap_max_line_length = 2 M
mail_debug = yes
mail_location = maildir:/export/home/imap/%Lu/Maildir
mail_plugins = acl zlib mail_log notify
mailbox_idle_check_interval = 10 secs
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

namespace {
  hidden = no
  ignore_on_failure = no
  inbox = no
  list = children
  location = maildir:%%h/Maildir:INDEXPVT=%h/shared/%%u
  prefix = shared/%%u/
  separator = /
  subscriptions = yes
  type = shared
}
namespace inbox {
  hidden = no
  inbox = yes
  list = yes
  location =
  mailbox Drafts {
special_use = \Drafts
  }
  mai

Re: Dovecot 2.3.0 TLS

2018-01-23 Thread Arkadiusz Miśkiewicz 
On Thursday 11 of January 2018, Aki Tuomi wrote:

> Seems we might've made a unexpected change here when we revamped the ssl
> code. 

Revamped, interesting, can it support milions certs now on single machine? (so 
are certs loaded by demand and not wasting memory)

> Aki


-- 
Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org )

Re: rewrite copy to trash->delete->expunge mail with move??

2018-01-23 Thread LuKreme 
On Jan 22, 2018, at 01:35, Chi Min Wang  wrote:
> CONFIDENTIALITY NOTICE:This e-mail and any attachments are confidential and 
> may be legally privileged.
> If you are not the intended recipient, (i) please do not read or disclose to 
> others, and (ii) please
> notify immediately the sender by reply mail, and (iii) please delete all 
> copies of the email from your
> system. Failure to follow this process may be unlawful. We greatly appreciate 
> your cooperation.

Everything in this statement is utter bullshit.

-- 
This is my signature. There are many like it, but this one is mine.

Re: How to set autoexpunge rule for single user mailbox in dovecot conf?

2018-01-23 Thread Steffen Kaiser 

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Tue, 23 Jan 2018, Alexey Murz Korepov wrote:


I need to set autoexpunge rule only for one single user and one mailbox
(mail folder), so apply it only for user al...@example.com mailbox INBOX.
How can I set namespace in dovecot config, that will apply only to single
user?


https://wiki2.dovecot.org/Namespaces#From_userdb

However, I don't know if you can limit the setting to mailbox INBOX.

- -- 
Steffen Kaiser

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQEVAwUBWmcddsQnQQNheMxiAQJo+ggAwMC4m6obuK8GHQE8b8FkGkTVlkJZhixr
EyJmphdbtFwSKFTKPQsC+k64Kg8zmuBzPAgN5I513FWhiSQATy2iMSKzsIxGCdy2
pQ8P6XzaLFx+lwMWoARpEz8SS7S8H+amaF4JBYG+p0Y497vDxFVmDCt1G2ubVX68
UrZGIpvtUf+i+O3pBKJFLSYS+GQnrPV0RV9eUZuZjGcHrvP+AqTjY79Owvket9Eh
9C4QLar3GSj9kihwDarPTnPBC0tpDsl/Rzt8mU4qEni2Rv2r4N1f7cr3qDl3j4mC
E2yaEkGGA+6ywflRMoSAsLhb7hg1xdR36uj6lpUEjS0DpnMVmY6khQ==
=ldIj
-END PGP SIGNATURE-

Re: LAYOUT=fs

2018-01-23 Thread Aki Tuomi 


On 23.01.2018 12:58, Jungersen, Danjel - Jungersen Grafisk ApS wrote:
> 
>
> On 23 Jan 2018 at 11:30, Aki Tuomi wrote:
>
>
>
>
> On 23.01.2018 11:27, Jungersen, Danjel - Jungersen Grafisk ApS wrote:
> 
>
> On 22 Jan 2018 at 10:28, Aki Tuomi wrote:
>
>
>
>
> On 22.01.2018 00:46, Jungersen, Danjel - Jungersen Grafisk ApS wrote:
> Hi there.
>
> I have read what I could find, but not enough apparently.
>
> I am about to migrate my server to a postfix / dovecot setup.
>
> I have stumbled on the mentioned option and are wondering if I should
> use it.
>
> I have read about it, and I understand the difference, but I cannot
> find anything that guides me to what I should do.
>
> A pro / con list ?
>
> I figure that there are a reason for the default value, but also
> wonder when I will benefit from changing it.
>
> My plan is to (if possible) make spamassasin put spam i the spamfolder
> under the seperate users (serverside), I dont know if that make any
> difference here.
>
> If it makes any difference, I'm running 2.2.27.
>
> Best regards Danjel
>
> LAYOUT=fs with maildir makes maildir use filesystem directories for
> folders, so instead of '.mail.folder' it will use 'mail/folder'.
>
> Make sure you put mail_location (or mail from userdb) to something
> like maildir:~/Mail
>
> Yes, I understand that, the thing I'm not sure of is when should I use
> one or the other?
>
> What are the pros and cons for each solution?
>
> :-)
> Danjel
>
> Aki
>
> > Asking for pros and cons is bit difficult but I suppose it boils
> down to having or not having
> > subfolders. It might matter if you have lots and lots of folders.
>
> I thought about, what if I have lot and lots of mails?
> I have about 100.000 mails in my mailbox, stored in 402 folders,
> several of my users have similar amounts.
> I don't know if that is "lots and lots".
>
> > Also if you are using third party tools they might expect one way or 
> > another.
>
> Third party
> Any recommendations regarding spamassasin?
>
> As mentioned, a perfect solution for me was to have the server put
> detected spam in the users spamfolders.
>
> :-)
> Danjel
>
> Aki

This should help you out,

https://wiki.dovecot.org/HowTo/AntispamWithSieve

Aki

Re: LAYOUT=fs

2018-01-23 Thread Jungersen, Danjel - Jungersen Grafisk ApS 







On 23 Jan 2018 at 11:30, Aki Tuomi wrote:








On 23.01.2018 11:27, Jungersen, Danjel - Jungersen Grafisk ApS wrote:





On 22 Jan 2018 at 10:28, Aki Tuomi wrote:













On 22.01.2018 00:46, Jungersen, Danjel - Jungersen Grafisk ApS wrote:

Hi there.




I have read what I could find, but not enough apparently.




I am about to migrate my server to a postfix / dovecot setup.




I have stumbled on the mentioned option and are wondering if I should use it.




I have read about it, and I understand the difference, but I cannot find anything that 
guides me to what I should do.




A pro / con list ?




I figure that there are a reason for the default value, but also wonder when I will benefit 
from changing it.




My plan is to (if possible) make spamassasin put spam i the spamfolder under the 
seperate users (serverside), I dont know if that make any difference here.




If it makes any difference, I'm running 2.2.27.




Best regards Danjel


LAYOUT=fs with maildir makes maildir use filesystem directories for folders, so instead 
of '.mail.folder' it will use 'mail/folder'.

Make sure you put mail_location (or mail from userdb) to something like maildir:~/Mail




Yes, I understand that, the thing I'm not sure of is when should I use one or the other?




What are the pros and cons for each solution?




:-)

Danjel

Aki

> Asking for pros and cons is bit difficult but I suppose it boils down to having or not having
> subfolders. It might matter if you have lots and lots of folders.


I thought about, what if I have lot and lots of mails?
I have about 100.000 mails in my mailbox, stored in 402 folders, several of my users have 
similar amounts.
I don't know if that is "lots and lots".


> Also if you are using third party tools they might expect one way or another.



Third party
Any recommendations regarding spamassasin?


As mentioned, a perfect solution for me was to have the server put detected spam in the 
users spamfolders.


:-)
Danjel

Aki

Re: How to set autoexpunge rule for single user mailbox in dovecot conf?

2018-01-23 Thread Aki Tuomi 
You can do

passdb {
  driver = passwd-file
  args =  /path/to/some/file
  skip = unauthenticated
}

and put in this file

al...@example.com::noauthenticate
userdb_namespace/inbox/mailbox/INBOX/autoexpunge=31d

or nopassword instead of noauthenticate.

Please keep replies in-list.

Aki

On 23.01.2018 12:31, Alexey Murz Korepov wrote:
> So, with using `passwd` driver as userdb - there are no ways to set
> some dovecot single per-user setting? Change passwd to real user
> database is too hard on working system.
> Maybe exists some other ways to do auto expunge function for separate
> mailbox folder on single user?
>
> As workaround, can I use command like `doveadm expunge` in cron job
> for do this task?
> ---
> doveadm expunge -u al...@example.com 
> mailbox INBOX savedbefore 31d
> ---
>
> On 23 January 2018 at 13:20, Aki Tuomi  > wrote:
>
> Well, to have per-user settings, you need a userdb, that can
> provide per-user settings.
>
> Aki
>
>
> On 23.01.2018 12:19, Alexey Murz Korepov wrote:
>> I can't understand what you mean in `return from userdb` - in
>> which place of dovecot config files I can set this rule? I don't
>> use separate userdb for dovecot users.
>> Or maybe this must be set somewhere in user home folder?
>>
>> On 23 January 2018 at 13:17, Aki Tuomi > > wrote:
>>
>> No.
>>
>> The namespace name is irrelevant, it just has to be there.
>> Assuming you have no other namespace config around,
>>
>> namespace inbox {
>>   inbox = yes
>>   mailbox INBOX {
>>   }
>> }
>>
>> Then return from userdb,
>> namespace/inbox/mailbox/INBOX/autoexpunge=31d
>>
>> The namespace config will be global (affects all users), but
>> autoexpunge setting will be for alice only.
>>
>> Aki
>>
>> On 23.01.2018 12:08, Alexey Murz Korepov wrote:
>>> Thanks, Aki, for quick answer! But can you give me please a
>>> real example with user al...@example.com
>>>  and mailbox INBOX? In my setup I
>>> have no user database, I use real linux users, managed via
>>> Webmin/Virtualmin.
>>> So I must set in `/etc/dovecot/conf.d/15-mailboxes.conf`
>>> file something this?
>>> --
>>> namespace al...@example.com  {
>>>    mailbox INBOX {
>>>    }
>>> }
>>>
>>> namespace/al...@example.com/mailbox/INBOX/autoexpunge=31d
>>> 
>>>
>>> --
>>> Or I must fill last string not in `mailboxes.conf` file, but
>>> in some other place?
>>>
>>> On 23 January 2018 at 12:58, Aki Tuomi >> > wrote:
>>>
>>> Configure
>>>
>>> namespace  {
>>>    mailbox  {
>>>    }
>>> }
>>>
>>> and return from userdb
>>>
>>> namespace//mailbox//autoexpunge=value
>>>
>>> Ak
>>>
>>>
>>> On 23.01.2018 11:57, Alexey Murz Korepov wrote:
 I need to set autoexpunge rule only for one single user
 and one mailbox (mail folder), so apply it only for
 user al...@example.com 
 mailbox INBOX. How can I set namespace in dovecot
 config, that will apply only to single user?

 -- 
 Best regards,
 Alexey Murz Korepov.
 Email, Jabber: mur...@gmail.com 
>>>
>>>
>>>
>>>
>>> -- 
>>> Best regards,
>>> Alexey Murz Korepov.
>>> Email, Jabber: mur...@gmail.com 
>>
>>
>>
>>
>> -- 
>> Best regards,
>> Alexey Murz Korepov.
>> Email, Jabber: mur...@gmail.com 
>
>
>
>
> -- 
> Best regards,
> Alexey Murz Korepov.
> Email, Jabber: mur...@gmail.com

Re: How to set autoexpunge rule for single user mailbox in dovecot conf?

2018-01-23 Thread Aki Tuomi 
Configure

namespace  {
   mailbox  {
   }
}

and return from userdb

namespace//mailbox//autoexpunge=value

Ak


On 23.01.2018 11:57, Alexey Murz Korepov wrote:
> I need to set autoexpunge rule only for one single user and one
> mailbox (mail folder), so apply it only for user al...@example.com
>  mailbox INBOX. How can I set namespace in
> dovecot config, that will apply only to single user?
>
> -- 
> Best regards,
> Alexey Murz Korepov.
> Email, Jabber: mur...@gmail.com

How to set autoexpunge rule for single user mailbox in dovecot conf?

2018-01-23 Thread Alexey Murz Korepov 
I need to set autoexpunge rule only for one single user and one mailbox
(mail folder), so apply it only for user al...@example.com mailbox INBOX.
How can I set namespace in dovecot config, that will apply only to single
user?

-- 
Best regards,
Alexey Murz Korepov.
Email, Jabber: mur...@gmail.com

Re: LAYOUT=fs

2018-01-23 Thread Aki Tuomi 


On 23.01.2018 11:27, Jungersen, Danjel - Jungersen Grafisk ApS wrote:
> 
>
> On 22 Jan 2018 at 10:28, Aki Tuomi wrote:
>
>
>
>
> On 22.01.2018 00:46, Jungersen, Danjel - Jungersen Grafisk ApS wrote:
> Hi there.
>
> I have read what I could find, but not enough apparently.
>
> I am about to migrate my server to a postfix / dovecot setup.
>
> I have stumbled on the mentioned option and are wondering if I should
> use it.
>
> I have read about it, and I understand the difference, but I cannot
> find anything that guides me to what I should do.
>
> A pro / con list ?
>
> I figure that there are a reason for the default value, but also
> wonder when I will benefit from changing it.
>
> My plan is to (if possible) make spamassasin put spam i the spamfolder
> under the seperate users (serverside), I dont know if that make any
> difference here.
>
> If it makes any difference, I'm running 2.2.27.
>
> Best regards Danjel
>
> LAYOUT=fs with maildir makes maildir use filesystem directories for
> folders, so instead of '.mail.folder' it will use 'mail/folder'.
>
> Make sure you put mail_location (or mail from userdb) to something
> like maildir:~/Mail
>
> Yes, I understand that, the thing I'm not sure of is when should I use
> one or the other?
>
> What are the pros and cons for each solution?
>
> :-)
> Danjel
>
> Aki

Asking for pros and cons is bit difficult but I suppose it boils down to
having or not having subfolders. It might matter if you have lots and
lots of folders. Also if you are using third party tools they might
expect one way or another.

Aki

Re: LAYOUT=fs

2018-01-23 Thread Jungersen, Danjel - Jungersen Grafisk ApS 







On 22 Jan 2018 at 10:28, Aki Tuomi wrote:








On 22.01.2018 00:46, Jungersen, Danjel - Jungersen Grafisk ApS wrote:

Hi there.




I have read what I could find, but not enough apparently.




I am about to migrate my server to a postfix / dovecot setup.




I have stumbled on the mentioned option and are wondering if I should use it.




I have read about it, and I understand the difference, but I cannot find anything that 
guides me to what I should do.




A pro / con list ?




I figure that there are a reason for the default value, but also wonder when I will benefit 
from changing it.




My plan is to (if possible) make spamassasin put spam i the spamfolder under the 
seperate users (serverside), I dont know if that make any difference here.




If it makes any difference, I'm running 2.2.27.




Best regards Danjel

LAYOUT=fs with maildir makes maildir use filesystem directories for folders, so instead of 
'.mail.folder' it will use 'mail/folder'.

Make sure you put mail_location (or mail from userdb) to something like maildir:~/Mail


Yes, I understand that, the thing I'm not sure of is when should I use one or the other?


What are the pros and cons for each solution?


:-)
Danjel

Aki

Re: LAYOUT=fs

2018-01-23 Thread Aki Tuomi 


On 22.01.2018 00:46, Jungersen, Danjel - Jungersen Grafisk ApS wrote:
> Hi there.
>
> I have read what I could find, but not enough apparently.
>
> I am about to migrate my server to a postfix / dovecot setup.
>
> I have stumbled on the mentioned option and are wondering if I should
> use it.
>
> I have read about it, and I understand the difference, but I cannot
> find anything that guides me to what I should do.
>
> A pro / con list ?
>
> I figure that there are a reason for the default value, but also
> wonder when I will benefit from changing it.
>
> My plan is to (if possible) make spamassasin put spam i the spamfolder
> under the seperate users (serverside), I dont know if that make any
> difference here.
>
> If it makes any difference, I'm running 2.2.27.
>
> Best regards Danjel

LAYOUT=fs with maildir makes maildir use filesystem directories for
folders, so instead of '.mail.folder' it will use 'mail/folder'.

Make sure you put mail_location (or mail from userdb) to something like
maildir:~/Mail

Aki

Re: Dovecot 2.3.0 TLS

2018-01-23 Thread Odhiambo Washington 
On 23 January 2018 at 10:35, Aki Tuomi  wrote:

>
>
> On 22.01.2018 22:14, Odhiambo Washington wrote:
>
>
>
> On 22 January 2018 at 23:10, Matthias Fechner  wrote:
>
>> Dear Odhiambo,
>>
>> Am 22.01.2018 um 19:58 schrieb Odhiambo Washington:
>>
>> ...and I am still unable to successfully compile 2.3RC on FreeBSD 8.4 and
>> 9.3
>> and my reports were ignored, so should I assume support for those has
>> been dropped?
>>
>> Support for FreeBSD 8.4 stopped August 1, 2015.
>> Support for FreeBSD 9.3 stopped December 31, 2016
>>
>> Please see here:
>> https://www.freebsd.org/security/unsupported.html
>>
>> You should really upgrade to current version 10.4 or 11.1.
>>
>> Gruß
>> Matthias
>>
>> Hello Matthias,
>
> I am running the latest version of Dovecot on FreeBSD 8.4, 9.3 and 11.
> I am not really planning to upgrade now, unless I am told that Dovecot
> 2.3.x will not compile on them. In which case I can let them run the
> version they have and forget about 2.3.
> Until I hear such from Aki or Timo, I will wait :-)
>
>
>
>
>
> --
> Best regards,
> Odhiambo WASHINGTON,
> Nairobi,KE
> +254 7 3200 0004/+254 7 2274 3223
> "Oh, the cruft."
>
>
> Have you tried compiling latest 2.3.0 instead of RC?
>
> Aki
>

Hello Aki,

I didn't even know that 2.3 was released. After the disappointment with the
RC, I kinda got withdrawn.
I have just tested the 2.3 release and it compiles successfully on all my
servers.

Thank you.


-- 
Best regards,
Odhiambo WASHINGTON,
Nairobi,KE
+254 7 3200 0004/+254 7 2274 3223
"Oh, the cruft."