- dovecot - dovecot.org

dovecot 2.3.5 - tests fail: http payload echo (ssl)
by Helmut K. C. Tessarek 26 Mar '19

26 Mar '19

Hi, I was womdering, if anyone has experienced the same issues. When I run the tests after compiling 2.3.5, the following 4 tests fail: http payload echo (ssl): sequential .................................. : ok http payload echo (ssl): pipeline .................................... : ok http payload echo (ssl): parallel .................................... : FAILED: Test is hanging http payload echo (ssl) .............................................. : FAILED http payload echo (ssl; unknown size): sequential .................... : ok http payload echo (ssl; unknown size): pipeline ...................... : ok http payload echo (ssl; unknown size): parallel ...................... : FAILED: Test is hanging http payload echo (ssl; unknown size) ................................ : FAILED 4 / 114 tests failed Failed to run: ./test-http-payload The tests ran fine for 2.3.4.1. Is there any way, to debug the issue any further? Do the tests write log files? It just doesn't make amy sense. Nothing has changed on the OS since I compiled and tested 2.3.4.1. Cheers, K. C. -- regards Helmut K. C. Tessarek KeyID 0x172380A011EF4944 Key fingerprint = 8A55 70C1 BD85 D34E ADBC 386C 1723 80A0 11EF 4944 /* Thou shalt not follow the NULL pointer for chaos and madness await thee at its end. */

4 11

Panic
by Odhiambo Washington 25 Mar '19

25 Mar '19

Dovecot-2.3.5, FreeBSD-12 (amd64), I will wait to see coredumps after setting up things to allow it. Mar 24 20:56:08 imap(john.doe(a)crownkenya.com)<82746><wg80zdqEy+eaTXHr>: Panic: file mempool-system.c: line 137 (pool_system_realloc): assertion failed: (old_size == (size_t)-1 || mem == NULL || old_size <= malloc_usable_size(mem)) Mar 24 20:56:08 imap(john.doe(a)crownkenya.com)<82746><wg80zdqEy+eaTXHr>: Fatal: master: service(imap): child 82746 killed with signal 6 (core not dumped - https://dovecot.org/bugreport.html#coredumps - set service imap { drop_priv_before_ exec=yes }) Mar 24 20:56:08 imap(john.doe(a)crownkenya.com)<81688><pdUzzdqEyueaTXHr>: Panic: file mempool-system.c: line 137 (pool_system_realloc): assertion failed: (old_size == (size_t)-1 || mem == NULL || old_size <= malloc_usable_size(mem)) Mar 24 20:56:08 imap(john.doe(a)crownkenya.com)<81688><pdUzzdqEyueaTXHr>: Fatal: master: service(imap): child 81688 killed with signal 6 (core not dumped - https://dovecot.org/bugreport.html#coredumps - set service imap { drop_priv_before_ exec=yes }) Mar 24 20:56:08 imap(john.doe(a)crownkenya.com)<82020><qO8zzdqEyeeaTXHr>: Panic: file mempool-system.c: line 137 (pool_system_realloc): assertion failed: (old_size == (size_t)-1 || mem == NULL || old_size <= malloc_usable_size(mem)) Mar 24 20:56:08 imap(john.doe(a)crownkenya.com)<82020><qO8zzdqEyeeaTXHr>: Fatal: master: service(imap): child 82020 killed with signal 6 (core not dumped - https://dovecot.org/bugreport.html#coredumps - set service imap { drop_priv_before_ exec=yes }) Mar 24 20:56:08 imap(john.doe(a)crownkenya.com)<83452><Bw80zdqEzOeaTXHr>: Panic: file mempool-system.c: line 137 (pool_system_realloc): assertion failed: (old_size == (size_t)-1 || mem == NULL || old_size <= malloc_usable_size(mem)) Mar 24 20:56:08 imap(john.doe(a)crownkenya.com)<83452><Bw80zdqEzOeaTXHr>: Fatal: master: service(imap): child 83452 killed with signal 6 (core not dumped - https://dovecot.org/bugreport.html#coredumps - set service imap { drop_priv_before_ exec=yes }) Mar 24 20:56:08 imap(john.doe(a)crownkenya.com)<84305><9vV0zdqEzueaTXHr>: Panic: file mempool-system.c: line 137 (pool_system_realloc): assertion failed: (old_size == (size_t)-1 || mem == NULL || old_size <= malloc_usable_size(mem)) Mar 24 20:56:08 imap(john.doe(a)crownkenya.com)<84305><9vV0zdqEzueaTXHr>: Fatal: master: service(imap): child 84305 killed with signal 6 (core not dumped - https://dovecot.org/bugreport.html#coredumps - set service imap { drop_priv_before_ exec=yes }) -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)

1 0

imapsieve: script not triggered
by Andreas Krischer 24 Mar '19

24 Mar '19

Hi, folks! My problem: I set up dovecot with imapsieve to execute a script whenever a user copies a mail to his Spam folder (spam autolearning). Unfortunately this script is never executed regardless what I’m configuring for imapsieve. It looks like dovecot doesn’t really load the plugin… The "dovecot -n" output is attached. I already tried setting imapsieve_mailbox1_name to *, but even this does not execute the script… Also I tried a mailbox without mail_crypt enabled, no success as well. In the attached mail.log (mail_debug=yes) you can see, that imap_sieve_plugin is loaded, but it isn’t really executed. The normal (LMTP) sieve is working - if a mail is incoming the sieve module shows it work in mail.log: May 7 17:54:04 dovecot dovecot: lmtp(postmaster(a)myhost.name): Debug: YEm9ILyS8FqSaAAAujt/SA: sieve: file storage: Storage path `/var/vmail/myhost.name/postmaster/sieve' not found May 7 17:54:04 dovecot dovecot: lmtp(postmaster(a)myhost.name): Debug: YEm9ILyS8FqSaAAAujt/SA: sieve: file storage: Storage path `/var/vmail/myhost.name/postmaster/.dovecot.sieve' not found May 7 17:54:04 dovecot dovecot: lmtp(postmaster(a)myhost.name): Debug: YEm9ILyS8FqSaAAAujt/SA: sieve: storage: No default script location configured May 7 17:54:04 dovecot dovecot: lmtp(postmaster(a)myhost.name): Debug: YEm9ILyS8FqSaAAAujt/SA: sieve: User has no personal script May 7 17:54:04 dovecot dovecot: lmtp(postmaster(a)myhost.name): Debug: YEm9ILyS8FqSaAAAujt/SA: sieve: file storage: Using script storage path: /etc/dovecot/sieve/after/ May 7 17:54:04 dovecot dovecot: lmtp(postmaster(a)myhost.name): Debug: YEm9ILyS8FqSaAAAujt/SA: sieve: file script: Opened script `spam' from `/etc/dovecot/sieve/after/spam.sieve' May 7 17:54:04 dovecot dovecot: lmtp(postmaster(a)myhost.name): Debug: YEm9ILyS8FqSaAAAujt/SA: sieve: executed after user's Sieve script(1): /etc/dovecot/sieve/after/spam.sieve May 7 17:54:04 dovecot dovecot: lmtp(postmaster(a)myhost.name): Debug: Mailbox <lmtp DATA>: Opened mail UID=1 because: header Message-ID (Cache file is unusable) May 7 17:54:04 dovecot dovecot: lmtp(postmaster(a)myhost.name): Debug: YEm9ILyS8FqSaAAAujt/SA: sieve: Opening script 1 of 1 from `/etc/dovecot/sieve/after/spam.sieve' May 7 17:54:04 dovecot dovecot: lmtp(postmaster(a)myhost.name): Debug: YEm9ILyS8FqSaAAAujt/SA: sieve: Loading script /etc/dovecot/sieve/after/spam.sieve May 7 17:54:04 dovecot dovecot: lmtp(postmaster(a)myhost.name): Debug: YEm9ILyS8FqSaAAAujt/SA: sieve: Script binary /etc/dovecot/sieve/after/spam.svbin successfully loaded May 7 17:54:04 dovecot dovecot: lmtp(postmaster(a)myhost.name): Debug: YEm9ILyS8FqSaAAAujt/SA: sieve: binary save: not saving binary /etc/dovecot/sieve/after/spam.svbin, because it is already stored May 7 17:54:04 dovecot dovecot: lmtp(postmaster(a)myhost.name): Debug: YEm9ILyS8FqSaAAAujt/SA: sieve: Executing script from `/etc/dovecot/sieve/after/spam.svbin' I already spent hours on this problem so please let me know if you have any idea what the problem could be… :( Thanks in advance! Andreas

3 4

Sieve matching "size" with user variable?
by Ed W 24 Mar '19

24 Mar '19

Hi, I am trying to create a sieve filter which does something similar to the following: if size :over ${extdata.max_size} { # do something } This doesn't seem supported in recent dovecot and size only appears to accept a literal number? I'm not sure I could extra size into a variable either (to use variable matching). My understanding of sieve filters is that one needs to use something like a match, then use something like SET to put the match into a variable? This syntax doesn't seem to be compatible with the size test here either, so I don't see that I can do this? My goal is that users can set a user configurable setting (in an external front end) and if the email size is greater than this size then we will do some processing on it. This particular filter is actually in a global sieve filter. I guess I could use an external executable program, but is there another way to do this? Thanks for ideas Ed W

2 3

dovecot sasl support
by Wojciech Puchar 24 Mar '19

24 Mar '19

i've tried to replace saslauthd with dovecot sasl service stopped saslauthd daemon and added service auth { unix_listener /var/run/saslauthd/mux { mode = 0660 user = root group = mail } } so it will listen on the same socket. the effect with sendmail is as below Mar 23 21:23:29 <2.3> puchar dovecot: auth: Error: Authentication client not compatible with this server (mixed old and new binaries?) do i need to specify something while compiling sendmail to make it compatible?

3 6

Cannot get sieve script replication to work
by Marcel Menzel 24 Mar '19

24 Mar '19

Hello, I've set up dsync replication on 2 nodes and mail replication is working flawlessly, however it seems that replicating the sieve scripts won't work. Managesieve and sieve filter in gerneral seems to work on both nodes, however in order to have a synchronized state, I have to log onto both nodes with managesieve and save & activate the script. What's funny about this is that only deactivating the active sieve script (which removes the symlink) replicates from one node to the other (it's gone on both nodes then), but saving a new sieve script and activating it does not work. I cannot find anything on the internet about this problem (only old threads where an old commit should've fixed it), so I am asking here. Enabling mail_debug = yes and sieve_trace_debug = yes does not print anything useful here, the only thing I spotted was after creating and deleting the script afterwards, the other node complained about not being able to find the script: dovecot[15942]: doveadm: Debug: sieve: file script: File `/var/vmail/mcl.gg/mail/sieve/unnamed.sieve' not found dovecot[15942]: doveadm: Debug: doveadm-sieve: Value missing for key `vendor/vendor.dovecot/pvt/server/sieve/files/unnamed' (last change: 2019-03-24 15:24:27) All the messages about "Debug: sieve: file storage:" are correct. I am using Dovecot 2.3.5 (513208660) with Pigeonhole version 0.5.4 (60b0f48d) on Arch Linux 4.20.16.a-1-hardened. I've attached both node's doveconf -n. Kind regards, Marcel Menzel

1 0

Is this assumption correct?
by Tobi 24 Mar '19

24 Mar '19

Hello list we encounter a weird SSL issue with one of our dovecot (2.2.24 on Centos6) which we can only explain if our assumtion is correct Symptoms are that imaps connections (on port 993) suddenly get veeeery slow. Up to 180s for one connection with openssl s_client The thing we do not understand is that in the same time imap connections with starttls are just 1s. We can see that entropy on the affected system is not so high cat /proc/sys/kernel/random/entropy_avail 138 So our current theory is: we're running short of entropy but imaps connections are much more affected because they are encrypted from first bit. Whereas a starttls connection has an unencrypted part which generates some entropy it does not use. So I can add entropy to the system that other connections can use. We're open for any other theory but for the moment we believe (tm) that this is the reason that starttls is far more less affected than SSL Cheers tobi

3 2

Re: Dovecot quota and Postfix smtpd_recipient_restrictions?
by Davide Marchi 24 Mar '19

24 Mar '19

>> Well, >> >> so the right syntax (in my case) would be: >> >> -o smtpd_recipient_restrictions = >> reject_non_fqdn_recipient,reject_unknown_recipient_domain,permit_sasl_authenticated,reject,check_policy_service >> inet:mailstore.example.com:12340 >> >> right?? > I configured it before the "permit_sasl_authenticated" and the "reject" > statement. > I've a doubt (again): Is it correct the the space between "[..]service" and "inet[..]"? As suggested here: https://blog.sys4.de/postfix-dovecot-mailbox-quota-en.html I've run: postconf smtpd_recipient_restrictions=check_policy_service inet:mailstore.example.com:12340 but obtain the error: postconf: fatal: missing '=' after attribute name: "inet:mailstore.example.com:12340" Please, which is the correct syntax? :-) Thanks again! Davide

2 1

is it possible - username aliases
by Wojciech Puchar 23 Mar '19

23 Mar '19

i already have quite large dovecot installation with multiple domains but with users handled via unix passwd. Domain name mapping in both directions is done by sendmail, and mail delivery by procmail to Maildir format - one account per user. this accounts are often used for more than mail. So for example john smith have email john(a)foo.pl and unix username foo-john. His imap client and smtp client is configured to use login foo-john and email address john(a)foo.pl Everything works flawlessly. But i will have few new users that insist of being able to login as someone(a)somewhere.pl Can i have something similar to sendmail method in dovecot - an alias table like someone(a)somewhere.pl some-unix-account For this few users and have everything like it is now?

2 3

quota-service with Director - A workaround
by Tom Sommer 23 Mar '19

23 Mar '19

I realize quota-service on Director is not supported, which is a shame. As a workaround I'm thinking of setting up quota-service on one of my backend nodes, and have all my Postfix services ask this one node for the quota status. This sort of defeats the purpose of the Director (having per-user assigned hot nodes), since now this one node running the quota-service will access all mailboxes to check the status of all inbound mail. Is this a problem though? In terms of NFS locking etc. etc.? -- Tom

3 5