Bug report

[Peter Nabbefeld via dovecot]

Hello,

I've got a problem fetching my emails using getmail. First question is, of 
course, what's causing the problems. I'm going to think that getmail get's an 
error code from dovecot when trying to connect and just signals the most common 
error, so it seems to be a problem with dovecot.

Sorry but I cannot upload any files with the silly web interface of my 
provider, so I cannot attach a core dump here.  :-(

Kind regards

Peter



~/.getmail/log
=
2019-11-01 21:44:20 Delivery error (command deliver 42245 error (127, exec of 
command deliver failed (change UID/GID to vmail/vmail failed ([Errno 1] 
Operation not permitted


dovecot-info.log
==
Oct 31 20:27:00 lda(mein.n...@gmx.de)<42409><2+iBJIQ1u12ppQAA7IIYzw>: 
Panic: file istream-crlf.c: line 24 (i_stream_crlf_read_common): assertion 
failed: (ret != -2)
Oct 31 20:27:00 lda(mein.n...@gmx.de)<42409><2+iBJIQ1u12ppQAA7IIYzw>: 
Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0xff784) 
[0x7f4ec8e62784] -> /usr/lib/dovecot/libdovecot.so.0(+0xff7c1) [0x7f4ec8e627c1] 
-> /usr/lib/dovecot/libdovecot.so.0(+0x493aa) [0x7f4ec8dac3aa] -> 
/usr/lib/dovecot/libdovecot.so.0(+0x4bf62) [0x7f4ec8daef62] -> 
/usr/lib/dovecot/libdovecot.so.0(+0x111076) [0x7f4ec8e74076] -> 
/usr/lib/dovecot/libdovecot.so.0(i_stream_read_memarea+0x81) [0x7f4ec8e70291] 
-> /usr/lib/dovecot/libdovecot.so.0(i_stream_read+0x37) [0x7f4ec8e70477] -> 
/usr/lib/dovecot/libdovecot.so.0(+0x1164a8) [0x7f4ec8e794a8] -> 
/usr/lib/dovecot/libdovecot.so.0(i_stream_read_memarea+0x81) [0x7f4ec8e70291] 
-> /usr/lib/dovecot/libdovecot.so.0(i_stream_read+0x37) [0x7f4ec8e70477] -> 
/usr/lib/dovecot/libdovecot.so.0(i_stream_read_data+0x4c) [0x7f4ec8e70f3c] -> 
/usr/lib/dovecot/libdovecot.so.0(io_stream_copy+0x8a) [0x7f4ec8e8bbea] -> 
/usr/lib/dovecot/libdovecot.so.0(+0x12aa86) [0x7f4ec8e8da86] -> 
/usr/lib/dovecot/libdovecot.so.0(o_stream_send_istream+0x4f) [0x7f4ec8e8b86f] 
-> /usr/lib/dovecot/libdovecot-storage.so.0(index_storage_save_continue+0x2e) 
[0x7f4ec901114e] -> 
/usr/lib/dovecot/libdovecot-storage.so.0(maildir_save_continue+0x27) 
[0x7f4ec8fafbe7] -> 
/usr/lib/dovecot/libdovecot-storage.so.0(mailbox_save_continue+0x47) 
[0x7f4ec8f815b7] -> 
/usr/lib/dovecot/libdovecot-storage.so.0(mail_storage_copy+0xe8) 
[0x7f4ec8f72388] -> /usr/lib/dovecot/libdovecot-storage.so.0(maildir_copy+0x6d) 
[0x7f4ec8fab99d] -> /usr/lib/dovecot/libdovecot-lda.so.0(+0x3c46) 
[0x7f4ec90a2c46] -> /usr/lib/dovecot/modules/lib20_fts_plugin.so(+0x11004) 
[0x7f4ec8af0004] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0x59b0c) 
[0x7f4ec8f81b0c] -> /usr/lib/dovecot/libdovecot-sieve.so.0(+0x4edb8) 
[0x7f4ec67e0db8] -> 
/usr/lib/dovecot/libdovecot-sieve.so.0(sieve_result_execute+0x54d) 
[0x7f4ec67d65cd] -> /usr/lib/dovecot/libdovecot-sieve.so.0(+0x57a79) 
[0x7f4ec67e9a79] -> 
/usr/lib/dovecot/libdovecot-sieve.so.0(sieve_multiscript_run+0xa9) 
[0x7f4ec67eac49] -> /usr/lib/dovecot/modules/lib90_sieve_plugin.so(+0x376b) 
[0x7f4ec685c76b] -> /usr/lib/dovecot/libdovecot-lda.so.0(mail_deliver+0x199) 
[0x7f4ec90a46d9]

dovecot -n
===
# 2.3.8 (9df20d2db): /etc/dovecot/dovecot.conf
# Pigeonhole version 0.5.8 (b7b03ba2)
# OS: Linux 5.3.7-arch1-2-ARCH x86_64 Arch Linux 
# Hostname: mein.host.name
auth_verbose = yes
disable_plaintext_auth = no
info_log_path = /var/log/dovecot-info.log
log_path = /var/log/dovecot.log
mail_location = maildir:~/Maildir:LAYOUT=fs
mail_plugins = " fts fts_solr"
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 editheader
namespace inbox {
  inbox = yes
  location = 
  mailbox Entwürfe {
special_use = \Drafts
  }
  mailbox Gesendet {
special_use = \Sent
  }
  mailbox Spamverdacht {
special_use = \Junk
  }
  mailbox Trash {
special_use = \Trash
  }
  prefix = 
}
passdb {
  args = username_format=%u /etc/dovecot/passwd
  driver = passwd-file
}
plugin {
  fts = solr
  fts_solr = url=http://localhost:8983/solr/
  sieve = file:/home/vmail/sieve;active=/home/vmail/.dovecot.sieve
  sieve_extensions = +editheader
}
service stats {
  unix_listener stats-reader {
group = vmail
mode = 0666
user = vmail
  }
  unix_listener stats-writer {
group = vmail
mode = 0666
user = vmail
  }
}
ssl = no
ssl_dh = # hidden, use -P to show it
userdb {
  args = uid=vmail gid=vmail home=/home/vmail/%d/%n
  driver = static
}
protocol lda {
  mail_plugins = " fts fts_solr sieve"
  postmaster_address = mein.n...@gmx.de
}

SIGABRT on fetching mail

[Peter Nabbefeld via dovecot]

Good Morning,

I tried using gdb, but that doesn't work for me:

$ ulimit -c unlimited
$ sudo systemctl restart dovecot
$ sudo -E getmail
getmail version 5.13
Copyright (C) 1998-2019 Charles Cazabon.  Licensed under the GNU GPL
version 2.
SimpleIMAPSSLRetriever:peter.nabbef...@gmx.de@imap.gmx.net:993:
getmailrc: operation error (child pid 19702 killed by signal 6)
  1 messages (12551 bytes) retrieved, 0 skipped
$ gdb bt 19702
GNU gdb (GDB) 8.3
Copyright (C) 2019 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-pc-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
    .

For help, type "help".
Type "apropos word" to search for commands related to "word"...
bt: Datei oder Verzeichnis nicht gefunden.
Attaching to process 19702
ptrace: Kein passender Prozess gefunden.
/home/peter/NetBeansProjects/19702: Datei oder Verzeichnis nicht gefunden.
(gdb)

Finally, I could find a file in /var/lib/systemd/coredump:
-rw-r-+ 1 root root 710416 30. Mai 08:54
core.deliver.1003.d14b28050b8343f5a60c5998ef3947df.19702.155919928600.lz4

This is obviously the required dump. However, I'd not attach such a file
to a post to the mailing list, so where can I put that? Send it directly
to You?

Kind regards

Peter

PS: I'm using Arch Linux - probably the hint above could be added to
https://www.dovecot.org/bugreport-mail as a hint for other Arch users,
as it's much easier than using gdb for those not using it?

SIGABRT on fetching mail

[Peter Nabbefeld via dovecot]

Hello,

I've never used gdb, so I don't know why I'm running into problems using
"gdb bt".

Usually, I'm fetching my mail using "sudo -E getmail", but this doesn't
seem to work with backtrace. :-/

Output from "dovecot -n" attached.

Kind regards,
Peter




# 2.3.6 (7eab80676): /etc/dovecot/dovecot.conf
# Pigeonhole version 0.5.6 (92dc263a)
# OS: Linux 5.1.4-arch1-1-ARCH x86_64 Arch Linux 
# Hostname: tuchola.fritz.box
auth_verbose = yes
disable_plaintext_auth = no
info_log_path = /var/log/dovecot-info.log
log_path = /var/log/dovecot.log
mail_location = maildir:~/Maildir:LAYOUT=fs
mail_plugins = " fts fts_solr"
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 editheader
namespace inbox {
  inbox = yes
  location = 
  mailbox Entwürfe {
special_use = \Drafts
  }
  mailbox Gesendet {
special_use = \Sent
  }
  mailbox Spamverdacht {
special_use = \Junk
  }
  mailbox Trash {
special_use = \Trash
  }
  prefix = 
}
passdb {
  args = username_format=%u /etc/dovecot/passwd
  driver = passwd-file
}
plugin {
  fts = solr
  fts_solr = url=http://localhost:8983/solr/
  sieve = file:/home/vmail/sieve;active=/home/vmail/.dovecot.sieve
  sieve_extensions = +editheader
}
service stats {
  unix_listener stats-reader {
group = vmail
mode = 0666
user = vmail
  }
  unix_listener stats-writer {
group = vmail
mode = 0666
user = vmail
  }
}
ssl = no
ssl_dh = # hidden, use -P to show it
userdb {
  args = uid=vmail gid=vmail home=/home/vmail/%d/%n
  driver = static
}
protocol lda {
  mail_plugins = " fts fts_solr sieve"
  postmaster_address = peter.nabbef...@gmx.de
}

Re: SIGABRT on fetching mail

[Peter Nabbefeld via dovecot]

Hello,

thank You for Your reply!

If I knew, which message caused the problem, I'd probably just removed it.

I'll send the dovecot version output later, when I've found out how to get the 
gdb output - don't want to fragment this thread more than necessary.

Kind regards,
Peter



Am 27. Mai 2019 19:24:44 MESZ schrieb Aki Tuomi via dovecot 
:
>
>> On 27 May 2019 20:20 Peter Nabbefeld via dovecot
> wrote:
>> 
>>  
>> Hello,
>> 
>> I still cannot fetch my mails, relying on my smartphone (which makes
>it
>> a burden to read my mails ...) - could probably somebody help me?
>> 
>> Kind regards,
>> Peter
>
>Hi!
>
>I read your previous email, can you provide gdb bt full from the core
>file? Also, doveconf -n and message corpus (if possible) would be nice
>to have. If you need to, you can try 
>
>https://dovecot.org/tools/maildir-obfuscate.pl
>
>to obfuscate the mail beforehand.
>
>Aki

-- 
Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.

SIGABRT on fetching mail

[Peter Nabbefeld via dovecot]

Hello,

I still cannot fetch my mails, relying on my smartphone (which makes it
a burden to read my mails ...) - could probably somebody help me?

Kind regards,
Peter

SIGABRT on fetching mail

[Peter Nabbefeld via dovecot]

Hello,

I'm running dovecot with getmail for several months already, but today
it's always crashing: "getmailrc: operation error (child pid 2995 killed
by signal 6)".

The deliver process aborts due to an unknown reason.

> tail /var/log/dovecot-info.log
May 24 12:10:28 imap-login: Info: Login: user=,
method=PLAIN, rip=::1, lip=::1, mpid=2970, secured,
session=
May 24 12:10:49
lda(peter.nabbef...@gmx.de)<2994>: Info: sieve:
msgid=<318d121b-37fc-4e8c-b4b8-93c87e069...@gmx.de>: stored mail into
mailbox 'Gesendet'
May 24 15:14:30 imap-login: Info: Login: user=,
method=PLAIN, rip=::1, lip=::1, mpid=6304, secured,
session=<+Rae+qGJ4IUB>
May 24 15:14:31
imap(peter.nabbef...@gmx.de)<6304><+Rae+qGJ4IUB>:
Info: Connection closed (append finished 0.562 secs ago) in=157758
out=520 deleted=0 expunged=0 trashed=0 hdr_count=0 hdr_bytes=0
body_count=0 body_bytes=0
May 24 15:14:37 imap-login: Info: Login: user=,
method=PLAIN, rip=::1, lip=::1, mpid=6307, secured,
session=
May 24 15:55:28 imap-login: Info: Login: user=,
method=PLAIN, rip=::1, lip=::1, mpid=7205, secured,
session=
May 24 15:57:00 imap-login: Info: Login: user=,
method=PLAIN, rip=::1, lip=::1, mpid=7254, secured,
session=
May 24 16:08:22 imap-login: Info: Login: user=,
method=PLAIN, rip=::1, lip=::1, mpid=7507, secured,
session=
May 24 16:16:40
imap(peter.nabbef...@gmx.de)<6307>:
Info: Connection closed (IDLE running for 0.001 + waiting input for
0.001 secs, 2 B in + 10 B out, state=wait-input) in=4251 out=137885
deleted=0 expunged=0 trashed=0 hdr_count=1 hdr_bytes=661 body_count=0
body_bytes=0
May 24 16:16:54 imap-login: Info: Login: user=,
method=PLAIN, rip=::1, lip=::1, mpid=7662, secured,
session=


> tail /var/log/dovecot.log
May 24 11:25:33 master: Warning: Killed with signal 15 (by pid=12275
uid=0 code=kill)
May 24 11:25:35 log(660): Warning: Killed with signal 15 (by pid=1 uid=0
code=kill)
May 24 12:10:47
lda(peter.nabbef...@gmx.de)<2994>: Warning:
Failed to parse return-path header
May 24 12:10:50
lda(peter.nabbef...@gmx.de)<2995>: Panic: file
istream-crlf.c: line 24 (i_stream_crlf_read_common): assertion failed:
(ret != -2)
May 24 12:10:50
lda(peter.nabbef...@gmx.de)<2995>: Error: Raw
backtrace: /usr/lib/dovecot/libdovecot.so.0(+0xeee14) [0x7fd668defe14]
-> /usr/lib/dovecot/libdovecot.so.0(+0xeee51) [0x7fd668defe51] ->
/usr/lib/dovecot/libdovecot.so.0(+0x46268) [0x7fd668d47268] ->
/usr/lib/dovecot/libdovecot.so.0(+0x4892e) [0x7fd668d4992e] ->
/usr/lib/dovecot/libdovecot.so.0(+0x1004e6) [0x7fd668e014e6] ->
/usr/lib/dovecot/libdovecot.so.0(i_stream_read_memarea+0x81)
[0x7fd668dfd681] -> /usr/lib/dovecot/libdovecot.so.0(i_stream_read+0x36)
[0x7fd668dfd8a6] -> /usr/lib/dovecot/libdovecot.so.0(+0x1058f8)
[0x7fd668e068f8] ->
/usr/lib/dovecot/libdovecot.so.0(i_stream_read_memarea+0x81)
[0x7fd668dfd681] -> /usr/lib/dovecot/libdovecot.so.0(i_stream_read+0x36)
[0x7fd668dfd8a6] ->
/usr/lib/dovecot/libdovecot.so.0(i_stream_read_data+0x4c)
[0x7fd668dfe33c] ->
/usr/lib/dovecot/libdovecot.so.0(io_stream_copy+0x8a) [0x7fd668e18aba]
-> /usr/lib/dovecot/libdovecot.so.0(+0x119ac2) [0x7fd668e1aac2] ->
/usr/lib/dovecot/libdovecot.so.0(o_stream_send_istream+0x4f)
[0x7fd668e1874f] ->
/usr/lib/dovecot/libdovecot-storage.so.0(index_storage_save_continue+0x2e)
[0x7fd668f981ee] ->
/usr/lib/dovecot/libdovecot-storage.so.0(maildir_save_continue+0x27)
[0x7fd668f36887] ->
/usr/lib/dovecot/libdovecot-storage.so.0(mailbox_save_continue+0x44)
[0x7fd668f083f4] ->
/usr/lib/dovecot/libdovecot-storage.so.0(mail_storage_copy+0xf8)
[0x7fd668ef9828] ->
/usr/lib/dovecot/libdovecot-storage.so.0(maildir_copy+0x59)
[0x7fd668f32639] -> /usr/lib/dovecot/libdovecot-lda.so.0(+0x3d5c)
[0x7fd66902ad5c] ->
/usr/lib/dovecot/modules/lib20_fts_plugin.so(+0x10eec) [0x7fd668a90eec]
-> /usr/lib/dovecot/libdovecot-storage.so.0(+0x58981) [0x7fd668f08981]
-> /usr/lib/dovecot/libdovecot-sieve.so.0(+0x4e6df) [0x7fd66676e6df] ->
/usr/lib/dovecot/libdovecot-sieve.so.0(sieve_result_execute+0x4e5)
[0x7fd666764065] -> /usr/lib/dovecot/libdovecot-sieve.so.0(+0x57259)
[0x7fd666777259] ->
/usr/lib/dovecot/libdovecot-sieve.so.0(sieve_multiscript_run+0xa2)
[0x7fd6667783f2] ->
/usr/lib/dovecot/modules/lib90_sieve_plugin.so(+0x3d45) [0x7fd668cecd45]
-> /usr/lib/dovecot/libdovecot-lda.so.0(mail_deliver+0xf9) [0x7fd66902c229]


How can I find out which message is causing the crash?

It would be very helpful, if the message's subject and receipt time
could be logged in case of an abort or anything else that could help
identify the corrupt message. This would also enable me to send You the
message for further investigation (if appropriate).

Kind regards
Peter

Re: Error configuring unix_listener stats-writer

[Peter Nabbefeld via dovecot]

Am 18.02.19 um 11:34 schrieb Sami Ketola:



On 18 Feb 2019, at 12.15, Peter Nabbefeld  wrote:



Am 17.02.19 um 18:27 schrieb Sami Ketola:

Easy way is to use just one config file. That is what I have done for years.

Sami



I'd preferred that, too, but it seems the 'modern' way - and I don't want to 
get any possible configuration issues on updates, so I won't change this.


If your distribution modifies config files on updates then it's time to switch 
to another distribution.

Sami
Not the config files itself. But IIRC, the "main" config files have been 
changed in distros when the new style was introduced. Usually the main 
file wasn't overwritten, but a new file with an extension like "new" had 
been added.


However, my laptop installation isn't as old, and every application I 
install already has the new style, and of course it has it pros when You 
get used to the structure of the config file, but if You're new to some 
application, You also have to learn about this structure for every new 
one ...


Peter

Re: Error configuring unix_listener stats-writer

[Peter Nabbefeld via dovecot]

Am 17.02.19 um 14:45 schrieb Aki Tuomi:

On 17 February 2019 at 11:47 Peter Nabbefeld via dovecot  
wrote:



Hello,

I've got a very strange problem:
When I try to configure the stats-writer socket, I'm told the
configuration is a duplicate, though none exists in the configuration
files. So I'd guess the configuration is set either built-in or implicitly.

I've put the following into conf.d/10-master.conf:
service auth {
    unix_listener auth-userdb {
    }

    unix_listener stats-writer {
      user = vmail
      group = vmail
      mode = 0666
    }
}

BTW, using imap for mail traffic.

Is there any tool displaying an "effective" config tree (i.e., a tool
displaying the resulting configuration from every file, displaying the
original file and line number)? "dovecot -a" only displays all
configurations, but without source reference, so it's impossible to find
out about the details.  :-(

Kind regards

Peter

Hi

The stats-writer config belongs for service stats, not auth.


Ooops - Thank You!

You can see effective config with 'doveconf -n'.

Nope - it even displays less information than "dovecot -a".

Peter

Aki

Re: Error configuring unix_listener stats-writer

[Peter Nabbefeld via dovecot]

Am 17.02.19 um 18:27 schrieb Sami Ketola:



On 17 Feb 2019, at 11.47, Peter Nabbefeld via dovecot 
 wrote:



Is there any tool displaying an "effective" config tree (i.e., a tool 
displaying the resulting configuration from every file, displaying 
the original file and line number)? "dovecot -a" only displays all 
configurations, but without source reference, so it's impossible to 
find out about the details.  :-(




Easy way is to use just one config file. That is what I have done for 
years.


Sami


I'd preferred that, too, but it seems the 'modern' way - and I don't 
want to get any possible configuration issues on updates, so I won't 
change this.


Peter

Error configuring unix_listener stats-writer

[Peter Nabbefeld via dovecot]

Hello,

I've got a very strange problem:
When I try to configure the stats-writer socket, I'm told the 
configuration is a duplicate, though none exists in the configuration 
files. So I'd guess the configuration is set either built-in or implicitly.


I've put the following into conf.d/10-master.conf:
service auth {
  unix_listener auth-userdb {
  }

  unix_listener stats-writer {
    user = vmail
    group = vmail
    mode = 0666
  }
}

BTW, using imap for mail traffic.

Is there any tool displaying an "effective" config tree (i.e., a tool 
displaying the resulting configuration from every file, displaying the 
original file and line number)? "dovecot -a" only displays all 
configurations, but without source reference, so it's impossible to find 
out about the details.  :-(


Kind regards

Peter