[Dovecot] Client got empty email from dovecot
Hi,
I built a mail server with qmail + vpopmail + dovecot , the qmail and
vpopmail worked well, until the dovecot was installed.
Client always get empty email, I have try some solutions from
google, neither of then can solve the problem.
Here is the detailed information of logs, version, and output of
'dovecot -n', please help, thanks.
Lori
*Log:*
May 9 14:16:23 mail dovecot: pop3-login: Login: user=us...@site1.com,
method=PLAIN, rip=111.14.98.135, lip=10.247.108.189, mpid=23467,
session=VCJGcZS/FQBvDmKH
May 9 14:16:25 mail dovecot: pop3(us...@site1.com): Error: Cached message
size larger than expected (575 61)
May 9 14:16:25 mail dovecot: pop3(us...@site1.com): Error: Maildir
filename has wrong S value, renamed the file from /home/vpopmail/domain_dir/
site1.com/sunl/Maildir/cur/1336544158.23459.mail.site1.com,S=575:2, to
/home/vpopmail/domain_dir/
site1.com/sunl/Maildir/cur/1336544158.23459.mail.site1.com,S=61:2,
May 9 14:16:25 mail dovecot: pop3(us...@site1.com): Error: Corrupted
index cache file /home/vpopmail/domain_dir/
site1.com/sunl/Maildir/dovecot.index.cache: Broken physical size for mail
UID 1
May 9 14:16:25 mail dovecot: pop3(us...@site1.com): Error: Cached message
size larger than expected (575 61)
May 9 14:16:25 mail dovecot: pop3(us...@site1.com): Error: Corrupted index
cache file /home/vpopmail/domain_dir/
site1.com/sunl/Maildir/dovecot.index.cache: Broken physical size for mail
UID 1
May 9 14:16:25 mail dovecot: pop3(us...@site1.com): Error:
read(/home/vpopmail/domain_dir/
site1.com/sunl/Maildir/cur/1336544158.23459.mail.site1.com,S=575:2,)
failed: Input/output error (uid=1)
May 9 14:16:25 mail dovecot: pop3(us...@site1.com): Disconnected: Logged
out top=0/0, retr=1/78, del=0/1, size=63
*Version:*
[root]vpopmail# dovecot --version
*2.1.6*
dovecot -n:
[root]vpopmail# dovecot -n
# 2.1.6: /usr/local/etc/dovecot/dovecot.conf
# OS: Linux 2.6.18-164.el5 x86_64 Red Hat Enterprise Linux Server release
5.4 (Tikanga) ext3
auth_cache_size = 10 M
auth_default_realm = site1.com
auth_mechanisms = plain login cram-md5
auth_socket_path = /usr/local/var/run/dovecot/auth-userdb
default_internal_user = vpopmail
default_login_user = vpopmail
disable_plaintext_auth = no
first_valid_uid = 516
hostname = mail.site1.com
last_valid_uid = 516
listen = *
mail_access_groups = 516
mail_gid = 513
mail_location = maildir:/home/vpopmail/domain_dir/%d/%n/Maildir/
mail_privileged_group = 513
mail_uid = 516
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 = cache_key=%u webmail=127.0.0.1
driver = vpopmail
}
postmaster_address = postmas...@site1.com
protocols = imap pop3
sendmail_path = /var/qmail/bin/sendmail
service auth-worker {
user = $default_internal_user
}
service auth {
unix_listener auth-userdb {
group = vchkpw
mode = 0666
user = vpopmail
}
user = $default_internal_user
}
service imap-login {
inet_listener imaps {
ssl = yes
}
}
service pop3-login {
inet_listener pop3s {
ssl = yes
}
}
ssl_cert = /etc/ssl/certs/dovecot.pem
ssl_key = /etc/ssl/private/dovecot.pem
userdb {
args = quota_template=quota_rule=*:backend=%q
driver = vpopmail
}
protocol lda {
mail_plugins =
}
protocol imap {
mail_plugins =
}
protocol pop3 {
mail_plugins =
}
Re: [Dovecot] Dovecot for POP3S proxying
It works. Thanks a lot. Regards -Message d'origine- From: Timo Sirainen Sent: Sunday, May 06, 2012 5:46 AM To: Gilles ALBUSAC Cc: Dovecot Mailing List Subject: Re: [Dovecot] Dovecot for POP3S proxying So, what you need is to first make authentication with LDAP work, and then add the proxying fields: pass_attrs = \ =proxy=y, =host=exchange-ip, ..any other fields required for auth.. On 5.5.2012, at 11.51, Gilles ALBUSAC wrote: LDAP passdb lookup Message du 04/05/12 17:42 De : Timo Sirainen A : Gilles Albusac Copie à : Dovecot Mailing List Objet : Re: [Dovecot] Dovecot for POP3S proxying On 4.5.2012, at 9.33, Gilles Albusac wrote: Dovecot is installed but actually I just use auth module (for postfix authentication). In your dovecot.conf example, I don't see the proxy command ? The proxying is enabled by having the passdb lookup return a proxy extra field. What passdb are you planning on using?
Re: [Dovecot] mixed MBOX and Maildir format ?
On 05/09/2012 02:20 AM, Timo Sirainen wrote: On Tue, 2012-05-08 at 09:16 +0200, Frank Bonnet wrote: Hello would it be possible to have mixed formats in Dovecot 2.1.x userland ? I mean MBOX format for INBOXes Maildir format for IMAP folders ( to let users create subfolders ) You could, although I think it's a bad idea (more complex, mbox breaks easlier, etc.) http://wiki2.dovecot.org/Namespaces#Examples Hello Yes I know it is far from the best solution , but this will be temporary my final goal is to convert all users's email space to maildir but I cannot do it all at once because of time it will take. I cannot stop my production server 24 hours to convert all mailboxes from MBOX to Maildir or I would have to face at a users's riot !!!
Re: [Dovecot] mixed MBOX and Maildir format ?
On 05/09/2012 09:24 AM, Frank Bonnet wrote: On 05/09/2012 02:20 AM, Timo Sirainen wrote: On Tue, 2012-05-08 at 09:16 +0200, Frank Bonnet wrote: Hello would it be possible to have mixed formats in Dovecot 2.1.x userland ? I mean MBOX format for INBOXes Maildir format for IMAP folders ( to let users create subfolders ) You could, although I think it's a bad idea (more complex, mbox breaks easlier, etc.) http://wiki2.dovecot.org/Namespaces#Examples Hello Yes I know it is far from the best solution , but this will be temporary my final goal is to convert all users's email space to maildir but I cannot do it all at once because of time it will take. I cannot stop my production server 24 hours to convert all mailboxes from MBOX to Maildir or I would have to face at a users's riot !!! BTW would it be possible to run 2 Dovecot instances on the same server ? one running on std ports numbers and one running on customs ports numbers thank you
Re: [Dovecot] default mail quota when using per user quota (news1204: message 6 of 20)
On 23/4/2012 1:34 μμ, Timo Sirainen wrote: What do you get in logs with auth_debug=yes? Sorry for being late in responding. When I run: # doveadm quota get -u tester1 Quota name TypeValue Limit % User quota STORAGE 0 - 0 User quota MESSAGE 1 - 0 # doveadm quota get -u tester2 Quota name TypeValue Limit % User quota STORAGE 0 20480 0 User quota MESSAGE 1 - 0 Then in the logs: --- May 9 10:01:16 vdev dovecot: auth: Debug: master in: USER 1 tester1 service=doveadm May 9 10:01:16 vdev dovecot: auth: Debug: ldap(tester1): user search: base=ou=people, dc=noa, dc=gr scope=onelevel filter=(uid=tester1) fields=roomNumber,uid May 9 10:01:16 vdev dovecot: auth: Debug: ldap(tester1): result: uid=tester1; roomNumber missing May 9 10:01:16 vdev dovecot: auth: Debug: master out: USER 1 tester1 quota_rule=*:bytes= home=/home/vmail/tester1 May 9 10:01:29 vdev dovecot: auth: Debug: master in: USER 1 tester2 service=doveadm May 9 10:01:29 vdev dovecot: auth: Debug: ldap(tester2): user search: base=ou=people, dc=noa, dc=gr scope=onelevel filter=(uid=tester2) fields=roomNumber,uid May 9 10:01:29 vdev dovecot: auth: Debug: ldap(tester2): result: uid=tester2 roomNumber=20M May 9 10:01:29 vdev dovecot: auth: Debug: master out: USER 1 tester quota_rule=*:bytes=20M home=/home/vmail/tester2 --- So, in essence, when there is an explicitly defined quota for an account (as with tester2 above), doveadm returns the limit correctly; if not (as with tester1), it should get the default quota value, but it doesn't. Nick
Re: [Dovecot] mixed MBOX and Maildir format ?
On 05/09/2012 02:20 AM, Timo Sirainen wrote: On Tue, 2012-05-08 at 09:16 +0200, Frank Bonnet wrote: Hello would it be possible to have mixed formats in Dovecot 2.1.x userland ? I mean MBOX format for INBOXes Maildir format for IMAP folders ( to let users create subfolders ) You could, although I think it's a bad idea (more complex, mbox breaks easlier, etc.) http://wiki2.dovecot.org/Namespaces#Examples And ... ( at last I promise ) would it be possible to convert some IMAP folders during the transfert WITHOUT stopping the production ? I mean , actually all mailboxes are in MBOX format ( INBOX and IMAP folders ) what I would like to do is : When a user is not connected I transfert his/her IMAP folders from the server's local disk to a NFS mounted bigger and expendable partition ( NetAPP filer's volume ) During this transfert I also would like to convert the IMAP folders format from MBOX to Maildir Is it possible ? thank you
Re: [Dovecot] Client got empty email from dovecot
It's not dovecot's problem, it's about the vpopmail spam options.
I finilly resolved this problem by rebuilding vpopmail with spam options
removed.
Sorry for botherred everybody.
On Wed, May 9, 2012 at 2:49 PM, Lori Seda lori.s...@gmail.com wrote:
Hi,
I built a mail server with qmail + vpopmail + dovecot , the qmail and
vpopmail worked well, until the dovecot was installed.
Client always get empty email, I have try some solutions from
google, neither of then can solve the problem.
Here is the detailed information of logs, version, and output of
'dovecot -n', please help, thanks.
Lori
*Log:*
May 9 14:16:23 mail dovecot: pop3-login: Login: user=us...@site1.com,
method=PLAIN, rip=111.14.98.135, lip=10.247.108.189, mpid=23467,
session=VCJGcZS/FQBvDmKH
May 9 14:16:25 mail dovecot: pop3(us...@site1.com): Error: Cached
message
size larger than expected (575 61)
May 9 14:16:25 mail dovecot: pop3(us...@site1.com): Error: Maildir
filename has wrong S value, renamed the file from
/home/vpopmail/domain_dir/
site1.com/sunl/Maildir/cur/1336544158.23459.mail.site1.com,S=575:2, to
/home/vpopmail/domain_dir/
site1.com/sunl/Maildir/cur/1336544158.23459.mail.site1.com,S=61:2,
May 9 14:16:25 mail dovecot: pop3(us...@site1.com): Error: Corrupted
index cache file /home/vpopmail/domain_dir/
site1.com/sunl/Maildir/dovecot.index.cache: Broken physical size for mail
UID 1
May 9 14:16:25 mail dovecot: pop3(us...@site1.com): Error: Cached
message
size larger than expected (575 61)
May 9 14:16:25 mail dovecot: pop3(us...@site1.com): Error: Corrupted
index
cache file /home/vpopmail/domain_dir/
site1.com/sunl/Maildir/dovecot.index.cache: Broken physical size for mail
UID 1
May 9 14:16:25 mail dovecot: pop3(us...@site1.com): Error:
read(/home/vpopmail/domain_dir/
site1.com/sunl/Maildir/cur/1336544158.23459.mail.site1.com,S=575:2,)
failed: Input/output error (uid=1)
May 9 14:16:25 mail dovecot: pop3(us...@site1.com): Disconnected: Logged
out top=0/0, retr=1/78, del=0/1, size=63
*Version:*
[root]vpopmail# dovecot --version
*2.1.6*
dovecot -n:
[root]vpopmail# dovecot -n
# 2.1.6: /usr/local/etc/dovecot/dovecot.conf
# OS: Linux 2.6.18-164.el5 x86_64 Red Hat Enterprise Linux Server release
5.4 (Tikanga) ext3
auth_cache_size = 10 M
auth_default_realm = site1.com
auth_mechanisms = plain login cram-md5
auth_socket_path = /usr/local/var/run/dovecot/auth-userdb
default_internal_user = vpopmail
default_login_user = vpopmail
disable_plaintext_auth = no
first_valid_uid = 516
hostname = mail.site1.com
last_valid_uid = 516
listen = *
mail_access_groups = 516
mail_gid = 513
mail_location = maildir:/home/vpopmail/domain_dir/%d/%n/Maildir/
mail_privileged_group = 513
mail_uid = 516
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 = cache_key=%u webmail=127.0.0.1
driver = vpopmail
}
postmaster_address = postmas...@site1.com
protocols = imap pop3
sendmail_path = /var/qmail/bin/sendmail
service auth-worker {
user = $default_internal_user
}
service auth {
unix_listener auth-userdb {
group = vchkpw
mode = 0666
user = vpopmail
}
user = $default_internal_user
}
service imap-login {
inet_listener imaps {
ssl = yes
}
}
service pop3-login {
inet_listener pop3s {
ssl = yes
}
}
ssl_cert = /etc/ssl/certs/dovecot.pem
ssl_key = /etc/ssl/private/dovecot.pem
userdb {
args = quota_template=quota_rule=*:backend=%q
driver = vpopmail
}
protocol lda {
mail_plugins =
}
protocol imap {
mail_plugins =
}
protocol pop3 {
mail_plugins =
}
Re: [Dovecot] Thunderbird STARTTLS error
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 08.05.2012 20:58, schrieb Ken Stevenson: I'm just learning about this, but I was able to get it working recently. Also I haven't read your earlier posts. Did you receive intermediate certificates from StartCom? When I got my certificate, I had to concatenate together the contents of the domain_name.crt file and the gd_bundle.crt file. That concatenated file is the one I specify for ssl_cert_file. It has 4 certificates in it. I ask because when I run the openssl command, my certificate chain has 4 sections where yours only has one. Does your ssl.cert have the intermediate certificates in it? On 2012-05-08 14:17, Markus Fritz wrote: Hello, the error is still present: May 8 19:47:18 opsys dovecot: imap-login: Disconnected (no auth attempts): rip=82.113.119.140, lip=78.46.216.126 Whenever I start a session with openssl to STARTTTL (Server: mail.opsys.de) the handshake is successfull. Also I am able to login to my account via 1 login. In Thunderbird port 993 for SSL/TLS works correct, only STARTTLS on port 143 isn't working properly. The cert is Class 1 and signed by StartCom Ltd.. Dovecot.conf (for viewable reasons of this mail pasted): http://pastie.org/private/bmrymyuo16ohzxdahf0nq And here openssl output: http://pastie.org/private/3rpgll2s7hblev9ozpcq8w Note the 'Verify return code: 21 (unable to verify the first certificate)' in the output... Thanks for helping, I am working on this problem since 3 days. Kind regards Markus Fritz I got only this keys. Can you explain me what exactly you mean with adding chains? And I wonder why this error only occurs in Thunderbird, not in openssl. - -- Markus Fritz Administration -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.17 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJPqjmiAAoJEINBXoxEgR1s+moIAJMfHRtIRC1JrBno8bbRxVuR Yc1xx196N80DFzzMD9+G77SXO0gJqmbzD5KjFwllt3JxtTr3XFIjKhutW8mEcLh2 EU65CH9TCWByXkzQSoFGTGKwdX7OKG4doSm7MZuQtpV6jVmZrIOs6GEFD+cApWy/ I1aWfKqK7b6S8bYRqw57hlNsuYxv6kB4w1t+IC9wMHbx5ULNWmZwxL2O/TWBnv2c qEbu8bkHIhebNq9NdEGGWZnAd36Kv3Ji231HjgD/WhQjcnF2LNzHIQ4B11xRiOBC LzYN8RLi4iOuloSHLlylNmob/bgAwxL8AdESo5n+1SwYDBcRy1CllEbD+QYSUoc= =Cjg6 -END PGP SIGNATURE-
Re: [Dovecot] acls not copied when creating subfolder of private INBOX
Am 25.04.2012 23:27, schrieb Timo Sirainen: On 24.4.2012, at 17.09, Andreas Helmcke wrote: Using brand new dovecot 2.1.5 I still have a problem with the inheritance of acls. Maybe http://hg.dovecot.org/dovecot-2.1/rev/e8b80e0767ac fixes this as well? I am not sure if this change is part of the 2.1.6 release but I just checked again with release 2.1.6. Still the same problem.
Re: [Dovecot] acls not copied when creating subfolder of private INBOX
Am 09.05.2012 12:31, schrieb Andreas Helmcke: Am 25.04.2012 23:27, schrieb Timo Sirainen: On 24.4.2012, at 17.09, Andreas Helmcke wrote: Using brand new dovecot 2.1.5 I still have a problem with the inheritance of acls. Maybe http://hg.dovecot.org/dovecot-2.1/rev/e8b80e0767ac fixes this as well? I am not sure if this change is part of the 2.1.6 release but I just checked again with release 2.1.6. Still the same problem. if i create a folder , set acls to it ( by manual i.e edit dovecot-acl) same acl are copied to its subfolders if the folder gets its acls from global-acl the acls arent copied to its subfolders As far i remember Timo is thinking about redesign acl config , check the list archives -- Best Regards MfG Robert Schetterer Germany/Munich/Bavaria
Re: [Dovecot] dovecot and systemd
On 05/04/2012 08:54 PM, Timo Sirainen wrote: On 16.4.2012, at 12.55, Michal Hlavinka wrote: I wrote simple patch that close the extra sockets. It's tested and works fine. You'll maybe want to move that function to different place and/or change wording of error messages. I committed it to v2.1 now with a couple of changes. One is that it doesn't actually close the fd, but instead puts /dev/null into it. I think otherwise Dovecot might use that fd to something else and the check would later fail again and close the wrong fd. http://hg.dovecot.org/dovecot-2.1/rev/4a3bf567da54 Thanks. I tested it, but it does not work because of the ret == 0 check before services_verify_systemd. ret is usually 1 Michal
Re: [Dovecot] dovecot and systemd
On 9.5.2012, at 14.49, Michal Hlavinka wrote: On 05/04/2012 08:54 PM, Timo Sirainen wrote: On 16.4.2012, at 12.55, Michal Hlavinka wrote: I wrote simple patch that close the extra sockets. It's tested and works fine. You'll maybe want to move that function to different place and/or change wording of error messages. I committed it to v2.1 now with a couple of changes. One is that it doesn't actually close the fd, but instead puts /dev/null into it. I think otherwise Dovecot might use that fd to something else and the check would later fail again and close the wrong fd. http://hg.dovecot.org/dovecot-2.1/rev/4a3bf567da54 Thanks. I tested it, but it does not work because of the ret == 0 check before services_verify_systemd. ret is usually 1 Oh, right. Fixed: http://hg.dovecot.org/dovecot-2.1/rev/17b20880453c
Re: [Dovecot] Thunderbird STARTTLS error
I got only this keys. Can you explain me what exactly you mean with adding chains? And I wonder why this error only occurs in Thunderbird, not in openssl. Never mind, I don't think my first guess was correct. I wonder if it has to do with the error 27 reported in the verify by openssl. According to the manual, an error 27 means: the root CA is not marked as trusted for the specified purpose. It looks like the certificate is valid cryptographically, but that it wasn't certified for how you're using it. If I run: openssl x509 -in ssl.crt -noout -text The output includes the following: X509v3 Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication X509v3 Key Usage: critical Digital Signature, Key Encipherment Does yours look different?
Re: [Dovecot] Thunderbird STARTTLS error
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 09.05.2012 14:32, schrieb Ken Stevenson: I got only this keys. Can you explain me what exactly you mean with adding chains? And I wonder why this error only occurs in Thunderbird, not in openssl. Never mind, I don't think my first guess was correct. I wonder if it has to do with the error 27 reported in the verify by openssl. According to the manual, an error 27 means: the root CA is not marked as trusted for the specified purpose. It looks like the certificate is valid cryptographically, but that it wasn't certified for how you're using it. If I run: openssl x509 -in ssl.crt -noout -text The output includes the following: X509v3 Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication X509v3 Key Usage: critical Digital Signature, Key Encipherment Does yours look different? Mine looks like this: X509v3 Basic Constraints: CA:FALSE X509v3 Key Usage: Digital Signature, Key Encipherment, Key Agreement X509v3 Extended Key Usage: TLS Web Server Authentication - -- Markus Fritz Administration -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.17 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJPqmuQAAoJEINBXoxEgR1sshwIALPRc0ozkTms2z9q+wLo8nP4 ELA7OsIUYiRUbhO1WOvfUQ+Ltssw5WcmvDQdpiAEZBL92s3hLvGqiJxc4TjoF3Fd lfar4OIQ/G2GMgzA9QeJu/EVMks29031RifSo2zkXnmTJMoTVAtsnRMc3UwIOTPV 0yDAXMZN7Ph4t5TbjJRk6Dox2PZj9qsixsOXb82ErE9TyaKT/p+Qdk2U/gvKWMUM Himz4q6bWIpc5D+h1KKes27+HIHPWjFLE2OPKfF58vw1ws1dmYvwM14v3RRW9e1X UYBZXcv5dIJHNXhkANgY/reWQjl3QU5JIalyU4S8MaF1OTr4Gr4SzsBBzY5eCd0= =j6Vx -END PGP SIGNATURE-
[Dovecot] mailbox_check_mismatching_separators
I using dovecot with mdbox and in one account i get this error: doveadm(xxx): Panic: file mail-storage.c: line 787 (mailbox_check_mismatching_separators): assertion failed: (strncmp(vname, ns-prefix, ns-prefix_len-1) == 0) doveadm(xxx): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x4472a) [0x7fd429a4172a] - /usr/lib/dovecot/libdovecot.so.0(default_fatal_handler+0x32) [0x7fd429a41812] - /usr/lib/dovecot/libdovecot.so.0(i_error+0) [0x7fd429a185bf] - /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_open_stream+0) [0x7fd429d05bb0] - /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_open+0xf) [0x7fd429d05bcf] - /usr/lib/dovecot/libdovecot-storage.so.0(mdbox_storage_rebuild_in_context+0xb2b) [0x7fd429cc7e1b] - /usr/lib/dovecot/libdovecot-storage.so.0(mdbox_sync_begin+0x7ec) [0x7fd429cc5dec] - /usr/lib/dovecot/libdovecot-storage.so.0(mdbox_sync+0x46) [0x7fd429cc5e56] - /usr/lib/dovecot/libdovecot-storage.so.0(mdbox_storage_sync_init+0x87) [0x7fd429cc5f37] - /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_sync_init+0x31) [0x7fd429d04781] - /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_sync+0x27) [0x7fd429d05297] - doveadm() [0x4104c7] - doveadm() [0x40f988] - doveadm() [0x40fce4] - doveadm(doveadm_mail_try_run+0x141) [0x410161] - doveadm(main+0x3a1) [0x416f01] - /lib/libc.so.6(__libc_start_main+0xfd) [0x7fd4296b9c8d] - doveadm() [0x40f2b9] The error also occurs with force-resync . The dovecot director version is 2.1.5 . Danilo Acquaviva
Re: [Dovecot] Thunderbird STARTTLS error
On 9 May 2012, at 9:05, Markus Fritz wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 09.05.2012 14:32, schrieb Ken Stevenson: I got only this keys. Can you explain me what exactly you mean with adding chains? And I wonder why this error only occurs in Thunderbird, not in openssl. Never mind, I don't think my first guess was correct. I wonder if it has to do with the error 27 reported in the verify by openssl. According to the manual, an error 27 means: the root CA is not marked as trusted for the specified purpose. It looks like the certificate is valid cryptographically, but that it wasn't certified for how you're using it. If I run: openssl x509 -in ssl.crt -noout -text The output includes the following: X509v3 Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication X509v3 Key Usage: critical Digital Signature, Key Encipherment Does yours look different? Mine looks like this: X509v3 Basic Constraints: CA:FALSE There's your problem. If you use a root CA in any X.509 trust chain (even one consisting of a single self-signed certificate) that declares itself to not be legitimate for use as a CA, you will have any signed certificates treated as bogus by any proper X.509v3 implementation. Most tools that create certificates do so with assumptions suited to the external CA model, and set options like the Basic Constraints extension flags that are not fit for a self-signed certificate.
Re: [Dovecot] Thunderbird STARTTLS error
Am 09.05.2012 15:42, schrieb Bill Cole: On 9 May 2012, at 9:05, Markus Fritz wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 09.05.2012 14:32, schrieb Ken Stevenson: I got only this keys. Can you explain me what exactly you mean with adding chains? And I wonder why this error only occurs in Thunderbird, not in openssl. Never mind, I don't think my first guess was correct. I wonder if it has to do with the error 27 reported in the verify by openssl. According to the manual, an error 27 means: the root CA is not marked as trusted for the specified purpose. It looks like the certificate is valid cryptographically, but that it wasn't certified for how you're using it. If I run: openssl x509 -in ssl.crt -noout -text The output includes the following: X509v3 Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication X509v3 Key Usage: critical Digital Signature, Key Encipherment Does yours look different? Mine looks like this: X509v3 Basic Constraints: CA:FALSE There's your problem. If you use a root CA in any X.509 trust chain (even one consisting of a single self-signed certificate) that declares itself to not be legitimate for use as a CA, you will have any signed certificates treated as bogus by any proper X.509v3 implementation. Most tools that create certificates do so with assumptions suited to the external CA model, and set options like the Basic Constraints extension flags that are not fit for a self-signed certificate. Sorry for my stupid question, but how I can resolve this with a SartSSL signed cert? There I am able to generate a WEB or MIME cert. Thanks for help! -- Markus Fritz Administration
Re: [Dovecot] Thunderbird STARTTLS error
On 9 May 2012, at 9:51, Markus Fritz wrote:
Am 09.05.2012 15:42, schrieb Bill Cole:
On 9 May 2012, at 9:05, Markus Fritz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am 09.05.2012 14:32, schrieb Ken Stevenson:
I got only this keys. Can you explain me what exactly you mean
with
adding chains?
And I wonder why this error only occurs in Thunderbird, not in
openssl.
Never mind, I don't think my first guess was correct. I wonder if
it
has to do with the error 27 reported in the verify by openssl.
According
to the manual, an error 27 means:
the root CA is not marked as trusted for the specified purpose.
It looks like the certificate is valid cryptographically, but that
it
wasn't certified for how you're using it.
If I run:
openssl x509 -in ssl.crt -noout -text
The output includes the following:
X509v3 Extended Key Usage:
TLS Web Server Authentication, TLS Web Client Authentication
X509v3 Key Usage: critical
Digital Signature, Key Encipherment
Does yours look different?
Mine looks like this:
X509v3 Basic Constraints:
CA:FALSE
There's your problem.
If you use a root CA in any X.509 trust chain (even one consisting of
a single self-signed certificate) that declares itself to not be
legitimate for use as a CA, you will have any signed certificates
treated as bogus by any proper X.509v3 implementation. Most tools
that
create certificates do so with assumptions suited to the external CA
model, and set options like the Basic Constraints extension flags
that
are not fit for a self-signed certificate.
Sorry for my stupid question, but how I can resolve this with a
SartSSL
signed cert? There I am able to generate a WEB or MIME cert. Thanks
for
help!
I apologize: I misunderstood which certificate you were looking at with
openssl.
Having re-read the whole thread and after reading at the pastebin items
you posted, I believe the problem you are having is a result of the fact
that your certificate is not directly signed by the StartSSL root CA,
but is chained with an intermediate certificate. This is a common
situation, and it means that a client needs some way to get a copy of
the intermediate certificate that was used to sign the server
certificate. The normal way to do that is to put all of the certificates
in the chain into the certificate file so that the server using that
file sends them all to clients. This is documented at
http://wiki.dovecot.org/SSL/DovecotConfiguration#Chained_SSL_certificates
The intermediate certificate that you need can be retrieved from
http://aia.startssl.com/certs/sub.class1.server.ca.crt in DER format.
You need to convert that to PEM format ('openssl x509 -inform DER
sub.class1.server.ca.crt' will put out the certificate in PEM form) and
add it to your certificate file (based on your pastebin:
/etc/ssl/opsys/startssl/ssl.crt). You may also want to add the actual
StartSSL root certificate as well, but that is unlikely to be necessary.
A failure of a certificate to verify in some clients and not others or
for some users and not others is usually do to a server not including
intermediate CA certificates. Some clients and users may have a store of
certificates that includes a widely-used intermediate CA cert provide by
some other server in the past, so they will be able to verify the chain,
while others won't have the cert and may have no persistent cert store.
Re: [Dovecot] lmtp_save_to_detail_mailbox not working?
On 05/ 8/12 08:30 PM, Timo Sirainen wrote: On Tue, 2012-05-08 at 13:36 -0400, Oscar del Rio wrote: Dovecot 2.1.6, with lmtp_save_to_detail_mailbox=yes recipient_delimiter=+ messages addressed to user+detail@domain are always delivered to INBOX regardless if detail mailbox already exists or lda_mailbox_autocreate=yes. Anything else needed to enable lmtp_save_to_detail_mailbox feature? Works fine with me. Do you have Sieve enabled? Set mail_debug=yes, what does it log when delivering a mail? After some more debugging, my problem seems to be sendmail not passing +detail and not a dovecot problem. I will check what's needed to work with sendmail. Thanks for the prompt reply and sorry for the noise.
Re: [Dovecot] Thunderbird STARTTLS error
Am 09.05.2012 17:07, schrieb Bill Cole:
On 9 May 2012, at 9:51, Markus Fritz wrote:
Am 09.05.2012 15:42, schrieb Bill Cole:
On 9 May 2012, at 9:05, Markus Fritz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am 09.05.2012 14:32, schrieb Ken Stevenson:
I got only this keys. Can you explain me what exactly you mean with
adding chains?
And I wonder why this error only occurs in Thunderbird, not in
openssl.
Never mind, I don't think my first guess was correct. I wonder if it
has to do with the error 27 reported in the verify by openssl.
According
to the manual, an error 27 means:
the root CA is not marked as trusted for the specified purpose.
It looks like the certificate is valid cryptographically, but that it
wasn't certified for how you're using it.
If I run:
openssl x509 -in ssl.crt -noout -text
The output includes the following:
X509v3 Extended Key Usage:
TLS Web Server Authentication, TLS Web Client Authentication
X509v3 Key Usage: critical
Digital Signature, Key Encipherment
Does yours look different?
Mine looks like this:
X509v3 Basic Constraints:
CA:FALSE
There's your problem.
If you use a root CA in any X.509 trust chain (even one consisting of
a single self-signed certificate) that declares itself to not be
legitimate for use as a CA, you will have any signed certificates
treated as bogus by any proper X.509v3 implementation. Most tools that
create certificates do so with assumptions suited to the external CA
model, and set options like the Basic Constraints extension flags that
are not fit for a self-signed certificate.
Sorry for my stupid question, but how I can resolve this with a SartSSL
signed cert? There I am able to generate a WEB or MIME cert. Thanks for
help!
I apologize: I misunderstood which certificate you were looking at
with openssl.
Having re-read the whole thread and after reading at the pastebin
items you posted, I believe the problem you are having is a result of
the fact that your certificate is not directly signed by the StartSSL
root CA, but is chained with an intermediate certificate. This is a
common situation, and it means that a client needs some way to get a
copy of the intermediate certificate that was used to sign the server
certificate. The normal way to do that is to put all of the
certificates in the chain into the certificate file so that the server
using that file sends them all to clients. This is documented at
http://wiki.dovecot.org/SSL/DovecotConfiguration#Chained_SSL_certificates
The intermediate certificate that you need can be retrieved from
http://aia.startssl.com/certs/sub.class1.server.ca.crt in DER format.
You need to convert that to PEM format ('openssl x509 -inform DER
sub.class1.server.ca.crt' will put out the certificate in PEM form)
and add it to your certificate file (based on your pastebin:
/etc/ssl/opsys/startssl/ssl.crt). You may also want to add the actual
StartSSL root certificate as well, but that is unlikely to be necessary.
A failure of a certificate to verify in some clients and not others or
for some users and not others is usually do to a server not including
intermediate CA certificates. Some clients and users may have a store
of certificates that includes a widely-used intermediate CA cert
provide by some other server in the past, so they will be able to
verify the chain, while others won't have the cert and may have no
persistent cert store.
Thanks! That might help, yes I got the sub.class1.server.ca.pem file.
How I include this to my ssl.crt file now? This cert terms are so
confusing and I recognize that I am still standing at the beginning. But
it's really interesting.
Thanks for help!
--
Markus Fritz
Administration
Re: [Dovecot] Thunderbird STARTTLS error
On 2012-05-09 22:48, Markus Fritz wrote: Thanks! That might help, yes I got the sub.class1.server.ca.pem file. How I include this to my ssl.crt file now? Just append the intermediate CA certificate in the same file AFTER your own certificate. As in: # cat sub.class1.server.ca.pem ssl.crt As a result you should have a file ssl.crt which consists of the following: -BEGIN CERTIFICATE- [several lines of your own certificate] -END CERTIFICATE- -BEGIN CERTIFICATE- [several lines of the intermediary certificate] -END CERTIFICATE- ...and nothing else. -- Janne Snabb / EPIPE Communications sn...@epipe.com - http://epipe.com/
Re: [Dovecot] mixed MBOX and Maildir format ?
Hi Frank, Frank Bonnet wrote: would it be possible to run 2 Dovecot instances on the same server? one running on std ports numbers and one running on customs ports numbers thank you http://wiki2.dovecot.org/RunningDovecot Section Running Multiple Invocations of Dovecot describes exactly what is needed to run two instances. Kind regards Daniel
Re: [Dovecot] Thunderbird STARTTLS error
Am 09.05.2012 18:50, schrieb Janne Snabb: On 2012-05-09 22:48, Markus Fritz wrote: Thanks! That might help, yes I got the sub.class1.server.ca.pem file. How I include this to my ssl.crt file now? Just append the intermediate CA certificate in the same file AFTER your own certificate. As in: # cat sub.class1.server.ca.pem ssl.crt As a result you should have a file ssl.crt which consists of the following: -BEGIN CERTIFICATE- [several lines of your own certificate] -END CERTIFICATE- -BEGIN CERTIFICATE- [several lines of the intermediary certificate] -END CERTIFICATE- ...and nothing else. Thanks, I've done that. But it didn't help. Thunderbird still has the error 'TLS not aviable due tempoary reason'. The key still has (when I do openssl x509 -in ssl.crt -noout -text) X509v3 Basic Constraints: CA:FALSE Remember: IMAP with SSL/TLS on port 993 is running well. STARTTLS on port 143 not. -- Markus Fritz Administration
Re: [Dovecot] Thunderbird STARTTLS error
On 2012-05-10 03:29, Markus Fritz wrote: The key still has (when I do openssl x509 -in ssl.crt -noout -text) X509v3 Basic Constraints: CA:FALSE I believe this only means that you can not use the certificate as a CA certificate and issue sub-certificates of that certificate. IMHO this is not an issue, it is how it should be. The problem is somewhere else. -- Janne Snabb / EPIPE Communications sn...@epipe.com - http://epipe.com/
Re: [Dovecot] Thunderbird STARTTLS error
On 2012-05-08 14:17, Markus Fritz wrote: Hello, the error is still present: May 8 19:47:18 opsys dovecot: imap-login: Disconnected (no auth attempts): rip=82.113.119.140, lip=78.46.216.126 Whenever I start a session with openssl to STARTTTL (Server: mail.opsys.de) the handshake is successfull. Also I am able to login to my account via 1 login. In Thunderbird port 993 for SSL/TLS works correct, only STARTTLS on port 143 isn't working properly. The cert is Class 1 and signed by StartCom Ltd.. Dovecot.conf (for viewable reasons of this mail pasted): http://pastie.org/private/bmrymyuo16ohzxdahf0nq And here openssl output: http://pastie.org/private/3rpgll2s7hblev9ozpcq8w Note the 'Verify return code: 21 (unable to verify the first certificate)' in the output... Thanks for helping, I am working on this problem since 3 days. Kind regards Markus Fritz How about this: Note: If you receive an error that looks like: 454 TLS not available due to temporary reason', Port: 25, Secure(SSL): Yes, Server Error: 455, Error Number: 0x800CCC7F or anything similar, it is because your Norton AntiVirus Email Scanning or other Anti-Virus software is scanning your outgoing email. Shut off the 'Scan outgoing Email' option and it should work. It came from here: https://cs.stanford.edu/computing-guide/email/client-settings
Re: [Dovecot] Thunderbird STARTTLS error
Am 09.05.2012 22:40, schrieb Ken Stevenson: On 2012-05-08 14:17, Markus Fritz wrote: Hello, the error is still present: May 8 19:47:18 opsys dovecot: imap-login: Disconnected (no auth attempts): rip=82.113.119.140, lip=78.46.216.126 Whenever I start a session with openssl to STARTTTL (Server: mail.opsys.de) the handshake is successfull. Also I am able to login to my account via 1 login. In Thunderbird port 993 for SSL/TLS works correct, only STARTTLS on port 143 isn't working properly. The cert is Class 1 and signed by StartCom Ltd.. Dovecot.conf (for viewable reasons of this mail pasted): http://pastie.org/private/bmrymyuo16ohzxdahf0nq And here openssl output: http://pastie.org/private/3rpgll2s7hblev9ozpcq8w Note the 'Verify return code: 21 (unable to verify the first certificate)' in the output... Thanks for helping, I am working on this problem since 3 days. Kind regards Markus Fritz How about this: Note: If you receive an error that looks like: 454 TLS not available due to temporary reason', Port: 25, Secure(SSL): Yes, Server Error: 455, Error Number: 0x800CCC7F or anything similar, it is because your Norton AntiVirus Email Scanning or other Anti-Virus software is scanning your outgoing email. Shut off the 'Scan outgoing Email' option and it should work. It came from here: https://cs.stanford.edu/computing-guide/email/client-settings Sorry but: oh my god Thanks, really. Days of working and this simple resolution. I am running Avira and EMail scanning was turned on. Now it's working perfectly. That made my day. -- Markus Fritz Administration
Re: [Dovecot] Enforcing Dovecot Quotas
On Wed, May 09, 2012 at 10:39:17PM +0100, Tim wrote:
Thanks Leon
I changed my SQL to the following after trying a few combinations:
user_query = SELECT maildir, 5000 as uid, 5000 as
gid,concat('maildir:bytes=',quota) as quota FROM virtual_mailbox WHERE
username = '%u'
Try the above but with quota changed to quota_rule:
user_query = SELECT maildir, 5000 as uid, 5000 as
gid,maildir:bytes=1 as quota_rule FROM virtual_mailbox WHERE
username = '%u'
And also have at least something like
plugin {
quota = maildir:User quota
}
You could also do
plugin {
quota = maildir:User quota
quota_rule = *:storage=1
}
to have the quota_rule fixed in dovecot.conf and then only
user_query = SELECT maildir, 5000 as uid, 5000 as
gid FROM virtual_mailbox WHERE username = '%u'
as query.
I don't have my users in mysql though so other will probably have more
insights.
HTH,
Leon
It seems that Dovecot didn't understand the * backend for some reason
(even though it's mentioned in the documentation)
and my logs now seem to picking up on this
May 09 22:29:09 IMAP(t...@example.com): Info: Effective uid=mailuser,
gid=mailgroup, home=(none)
May 09 22:29:09 IMAP(t...@example.com): Info: Quota root: name=bytes=1
backend=maildir args=
But the address in question is still receiving mail - should I be doing
something additional to cease mail delivery?
Thanks in advance!
Tim
On Tue, 2012-05-08 at 22:12 +0200, Leon Meßner wrote:
On Tue, May 08, 2012 at 01:59:38AM -0700, tcsmith1978 wrote:
Hello,
I have been looking at enforcing quotas for users of my mail system
(postfix
and Dovecot v1.2). Have tried to follow a few tuts on the web but its not
having the desired effect. Essentially I can still send and receive mail
on
an account that I believe has had its quota exceeded.
In my main.cf, I have:
userdb sql {
args = /etc/dovecot/mysql/dovecot-mysql.conf
}
passdb sql {
args = /etc/dovecot/mysql/dovecot-mysql.conf
}
and...
protocol lda {
mail_plugins = quota
}
protocol imap {
mail_plugins = quota imap_quota
}
plugin {
quota_exceeded_message = You have exceeded the maximum quota for
your mailbox
}
the dovecot sql (mysql) file has the following query for pulling out user
ids and quotas etc:
user_query = SELECT maildir, mymailuser as uid, mymailgroup as
gid,concat('maildir:storage=',quota) as quota FROM virtual_mailbox WHERE
username = '%u'
I have set one of my users to have a quota of 1 (so one byte I believe) so
it should be over the limit pretty much immedisoemately.
Looking at the logs I can see that the system is picking up on the quota
limit but doesn't seem to enforce it.
Apr 27 10:29:02 deliver(t...@testdomain.com): Info: auth input:
quota=maildir:storage=1
Apr 27 10:29:02 deliver(t...@testdomain.com): Info: Quota root:
name=storage=1 backend=maildir args=
Any ideas? Am i missing something?
i would try something like in the wiki:
plugin {
quota = maildir:User quota
quota_exceeded_message = You have exceeded
}
Never used mysql for userdb or passdb though. Perhaps this would work:
user_query = SELECT maildir, mymailuser as uid, mymailgroup as
gid,concat('*:storage=',quota) as quota_rule FROM virtual_mailbox
WHERE
username = '%u
--
View this message in context:
http://old.nabble.com/Enforcing-Dovecot-Quotas-tp33763561p33763561.html
Sent from the Dovecot mailing list archive at Nabble.com.
--
Tim tcsmith1...@googlemail.com
[Dovecot] dovecot/auth killed with signal 6
I've had this working for over a month now with no problems. Then I
suffered a power outage today, and now dovecot/auth dies as soon as I start
dovecot. I've spent the past three hours searching google, but can't find
even a hint at what's wrong with my server. As far as I can tell, this is
the only thing that has failed after bringing the server back up when power
was restored. Can anyone help me figure out what is wrong?
The maillog records:
May 9 20:27:37 box dovecot: auth: Debug: Loading modules from directory:
/usr/lib64/dovecot/auth
May 9 20:27:37 box dovecot: auth: Debug: Module loaded:
/usr/lib64/dovecot/auth/libauthdb_ldap.so
May 9 20:27:37 box dovecot: auth: Debug: Module loaded:
/usr/lib64/dovecot/auth/libdriver_mysql.so
May 9 20:27:37 box dovecot: auth: Debug: Module loaded:
/usr/lib64/dovecot/auth/libdriver_pgsql.so
May 9 20:27:37 box dovecot: auth: Debug: Module loaded:
/usr/lib64/dovecot/auth/libdriver_sqlite.so
May 9 20:27:37 box dovecot: auth: Debug: Module loaded:
/usr/lib64/dovecot/auth/libmech_gssapi.so
May 9 20:27:37 box dovecot: auth: Panic: io_add(0x1) called twice fd=13,
callback=0x3016833290 - 0x3016836cd0
May 9 20:27:37 box dovecot: auth: Error: Raw backtrace:
/usr/lib64/dovecot/libdovecot.so.0() [0x301683ca6a] -
/usr/lib64/dovecot/libdovecot.so.0() [0x301683ca
b6] - /usr/lib64/dovecot/libdovecot.so.0() [0x3016816dba] -
/usr/lib64/dovecot/libdovecot.so.0(ioloop_iolist_add+0x7f) [0x301684872f]
- /usr/lib64/dovecot/li
bdovecot.so.0(io_loop_handle_add+0x39) [0x3016849149] -
/usr/lib64/dovecot/libdovecot.so.0(io_add+0xa3) [0x3016848593] -
/usr/lib64/dovecot/libdovecot.so.0(ma
ster_service_io_listeners_add+0x68) [0x3016835b88] -
/usr/lib64/dovecot/libdovecot.so.0(master_service_init_finish+0x192)
[0x30168363c2] - dovecot/auth(main+0
x207) [0x415567] - /lib64/libc.so.6(__libc_start_main+0xfd) [0x3016c1ecdd]
- dovecot/auth() [0x409aa9]
May 9 20:27:37 box dovecot: master: Error: service(auth): child 25615
killed with signal 6 (core dumped)
May 9 20:27:37 box dovecot: master: Error: service(auth): command startup
failed, throttling
A core dump was produced. The backtrace shows:
# gdb /usr/libexec/dovecot/auth coredump
Core was generated by `dovecot/auth'.
Program terminated with signal 6, Aborted.
#0 0x003016c32885 in raise () from /lib64/libc.so.6
Missing separate debuginfos, use: debuginfo-install
dovecot-2.0.9-2.el6_1.1.x86_64
(gdb) bt full
#0 0x003016c32885 in raise () from /lib64/libc.so.6
#1 0x003016c34065 in abort () from /lib64/libc.so.6
#2 0x00301683ca78 in ?? () from /usr/lib64/dovecot/libdovecot.so.0
#3 0x00301683cab6 in ?? () from /usr/lib64/dovecot/libdovecot.so.0
#4 0x003016816dba in i_panic () from /usr/lib64/dovecot/libdovecot.so.0
#5 0x00301684872f in ioloop_iolist_add () from
/usr/lib64/dovecot/libdovecot.so.0
#6 0x003016849149 in io_loop_handle_add () from
/usr/lib64/dovecot/libdovecot.so.0
#7 0x003016848593 in io_add () from /usr/lib64/dovecot/libdovecot.so.0
#8 0x003016835b88 in master_service_io_listeners_add () from
/usr/lib64/dovecot/libdovecot.so.0
#9 0x0030168363c2 in master_service_init_finish () from
/usr/lib64/dovecot/libdovecot.so.0
#10 0x00415567 in main ()
This is running on CentOS 6.2
# rpm -q dovecot
dovecot-2.0.9-2.el6_1.1.x86_64
# dovecot --version
2.0.9
# dovecot -n
# 2.0.9: /etc/dovecot/dovecot.conf
# OS: Linux 2.6.32-220.13.1.el6.x86_64 x86_64 CentOS release 6.2 (Final)
auth_debug = yes
auth_mechanisms = plain login
auth_verbose = yes
listen = *
mail_debug = yes
mail_location = mbox:~/mail:INBOX=/var/mail/%u
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
mbox_write_locks = fcntl
passdb {
driver = pam
}
plugin {
sieve = ~/.dovecot.sieve
sieve_dir = ~/sieve
}
service auth {
inet_listener {
port = 12345
}
unix_listener /var/spool/postfix/private/auth {
mode = 0666
}
user = $default_internal_user
}
ssl_cert = /etc/pki/dovecot/certs/dovecot.pem
ssl_key = /etc/pki/dovecot/private/dovecot.pem
userdb {
driver = passwd
}
Re: [Dovecot] dovecot/auth killed with signal 6
Okay, I figured out about installing debuginfo for a better backtrace, so
here it is:
#0 0x003016c32885 in raise (sig=6) at
../nptl/sysdeps/unix/sysv/linux/raise.c:64
resultvar = 0
pid = 2598
selftid = 2598
#1 0x003016c34065 in abort () at abort.c:92
save_stage = 2
act = {__sigaction_handler = {sa_handler = 0x1, sa_sigaction =
0x1}, sa_mask = {__val = {206536311181, 35954576, 35955280, 0,
206536165913, 4281703, 206536010617,
206158430224, 140734171103856, 140734171103648, 7, 7,
35807776, 0, 16992, 6717507389398987896}}, sa_flags = 1768709983,
sa_restorer = 0}
sigs = {__val = {32, 0 repeats 15 times}}
#2 0x00301683ca78 in default_fatal_finish (type=value optimized out,
status=0) at failures.c:187
backtrace = 0x2226220 /usr/lib64/dovecot/libdovecot.so.0()
[0x301683ca6a] - /usr/lib64/dovecot/libdovecot.so.0() [0x301683cab6] -
/usr/lib64/dovecot/libdovecot.so.0() [0x3016816dba] -
/usr/lib64/dovecot/libdovecot.so.0(...
#3 0x00301683cab6 in i_internal_fatal_handler (ctx=0x7fff3a46c2e0,
format=value optimized out, args=value optimized out) at failures.c:645
status = 0
#4 0x003016816dba in i_panic (format=0xa26 Address 0xa26 out of
bounds) at failures.c:259
ctx = {type = LOG_TYPE_PANIC, exit_status = 0, timestamp = 0x0}
args = {{gp_offset = 40, fp_offset = 48, overflow_arg_area =
0x7fff3a46c3b0, reg_save_area = 0x7fff3a46c2f0}}
#5 0x00301684872f in ioloop_iolist_add (list=value optimized out,
io=value optimized out) at ioloop-iolist.c:26
i = value optimized out
idx = value optimized out
#6 0x003016849149 in io_loop_handle_add (io=0x224a250) at
ioloop-epoll.c:104
ctx = 0x2243b20
list = 0x2249558
event = {events = 1, data = {ptr = 0x16836cd0, fd = 0, u32
= 0, u64 = 1622259931392507904}}
op = value optimized out
first = value optimized out
#7 0x003016848593 in io_add (fd=13, condition=IO_READ,
callback=0x3016836cd0 master_service_listen, context=0x2249f90) at
ioloop.c:54
io = 0x224a250
__FUNCTION__ = io_add
#8 0x003016835b88 in master_service_io_listeners_add
(service=0x222e4d0) at master-service.c:777
l = 0x2249f90
i = value optimized out
#9 0x0030168363c2 in master_service_init_finish (service=0x222e4d0) at
master-service.c:385
st = {st_dev = 8, st_ino = 15492, st_nlink = 1, st_mode = 4480,
st_uid = 0, st_gid = 0, __pad0 = 0, st_rdev = 0, st_size = 0, st_blksize =
4096, st_blocks = 0, st_atim = {
tv_sec = 1336599449, tv_nsec = 793902156}, st_mtim = {tv_sec =
1336599449, tv_nsec = 793902156}, st_ctim = {tv_sec = 1336599449, tv_nsec =
793902156}, __unused = {0, 0,
0}}
value = value optimized out
count = 4096
__FUNCTION__ = master_service_init_finish
#10 0x00415567 in main (argc=1, argv=0x222e370) at main.c:293
c = value optimized out
Re: [Dovecot] dovecot/auth killed with signal 6
Some more info...
I finally got it working by commenting out the configuration under service
auth {
# inet_listener {
#port = 12345
# }
which I had in there for SASL with postfix, and which WAS working before
the power outage.
I guess now I need to figure out why it doesn't like that now, but at least
dovecot is working again.
