Unable to get mail?

Hey everyone, I'm not sure I'm on the right list for this one... I have a postfix/dovecot install that was running fine on amazon web services that all of a sudden stopped receiving mail... In my mail log all I get is this: Apr 30 03:16:26 ip-172-31-28-46 dovecot: imap(b...@primelashdiva.info):

Re: Changing Password Schemes

That's not SHA512-CRYPT. That's just a simple sha512 of the password, without salt. A SHA512-CRYPT password will be generated with: printf "1234\n1234" | doveadm pw -s SHA512-CRYPT or: doveadm pw -s SHA512-CRYPT -p 1234 or: mkpasswd -m sha-512 1234 (without the "{SHA512-CRYPT}" prefix)

Re: Changing Password Schemes

Hi Bill, using PHPMYAdmin: UPDATE 'mailbox' SET 'password' = SHA2 ('clearpwd',512); {UPDATE 'the users table' SET 'cryptic password column' = SHA2 ('clear text password column',512);} gives this error: #1064 - You have an error in your SQL syntax; check the manual that corresponds to your

Panic: file message-part-serialize.c: line 90 (part_serialize): assertion failed: (part->children == NULL)

Hi, I just found this in my logs: Apr 29 11:05:20 lmtp(joerg.eggenst...@ruhr-uni-bochum.de): Panic: file message-part-serialize.c: line 90 (part_serialize): assertion failed: (part->children == NULL) Apr 29 11:05:20 lmtp(joerg.eggenst...@ruhr-uni-bochum.de): Error: Raw backtrace:

Re: Changing Password Schemes

Thanks for insight Bill, will look at that and report back. You have a good day now, en mag jou môre ook so wees, Carl A Jeptha On 2016-04-29 21:20, Bill Shirley wrote: Looks like an SQL update would do this: UPDATE `users` SET `passwd_SHA512` = SHA2(`passwd_clear`, 512); Bill

Re: Changing Password Schemes

Looks like an SQL update would do this: UPDATE `users` SET `passwd_SHA512` = SHA2(`passwd_clear`, 512); Bill On 4/29/2016 9:07 AM, Carl A Jeptha wrote: converting the passwords in the database from clear/plain text to SHA512-CRYPT You have a good day now, en mag jou môre ook so

segfault in imap "Warning: Timeout leak: 0x7fd584e8e050 (line 399)"

Corresponding log entry: Apr 29 17:14:07 mproxy dovecot: imap(v**d): copy from INBOX: box=Trash, uid=512, msgid=, size=error Apr 29 17:14:07 mproxy dovecot: imap(v**d): expunge: box=INBOX, uid=3322, msgid=, size=22485 Apr 29 17:14:19 mproxy dovecot: imap(v**d): copy from INBOX:

Re: Password database extra fields and SQL

On 2016-04-29 6:49 AM, Dave wrote: > > Hi everyone, > > first post to the list, be gentle with me! > > Perhaps I'm missing something here, but it appears to me that many > password database extra fields currently aren't much use inside SQL > queries? > > All boolean fields like

Re: Password database extra fields and SQL

On 29/04/2016 14:57, Matthias Fechner wrote: > Am 29.04.2016 um 15:49 schrieb Dave: >> >> For example, say you have a query like: >> >> password_query = SELECT hash AS password, NULLIF(active = 1, 'y') AS >> nologin FROM users WHERE name = '%u' > > why not using a logic like this to block users

more info about deleting users

Hi, i've search a lot in order to find a way to delete account by dovecot but i found only this way http://dovecot.org/list/dovecot/2011-November/079273.html It's possible today delete a maildir remotely with doveadm or with dovecot api? Thanks Matteo

Re: Password database extra fields and SQL

Am 29.04.2016 um 15:49 schrieb Dave: For example, say you have a query like: password_query = SELECT hash AS password, NULLIF(active = 1, 'y') AS nologin FROM users WHERE name = '%u' why not using a logic like this to block users that are not active: password_query = SELECT username as user,

Password database extra fields and SQL

Hi everyone, first post to the list, be gentle with me! Perhaps I'm missing something here, but it appears to me that many password database extra fields currently aren't much use inside SQL queries? All boolean fields like nologin/nodelay/nopassword are set if the column is

Re: Backtrace:dovecot/imap

* Timo Sirainen : > Oh, imapc expunges were broken when imapc_features didn't have > "modseq". > https://github.com/dovecot/core/commit/de8fc9d21460bf0369d671e9ba9361592379a7c5 Fixed, thanks! -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité -

Re: Changing Password Schemes

converting the passwords in the database from clear/plain text to SHA512-CRYPT You have a good day now, en mag jou môre ook so wees, Carl A Jeptha On 2016-04-29 15:02, Steffen Kaiser wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Fri, 29 Apr 2016, Carl A Jeptha wrote:

Re: Changing Password Schemes

Yes, but the machine is very old, can't more memory (maxed out) hard drive size maxed out. But we cannot keep on going plain text password saved in the database, that is asking for trouble to happen, which (touch wood) has not happened yet. You have a good day now, en mag jou

Re: Changing Password Schemes

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Fri, 29 Apr 2016, Carl A Jeptha wrote: Good Day, I have been following this tutorial without much luck - http://wiki2.dovecot.org/HowTo/ConvertPasswordSchemes#CA-26af2b83a43b8100522c57565773f605c21f2f27_1 It is obvious to me that I am not

Re: Changing Password Schemes

On 4/29/2016 5:58 AM, Carl A Jeptha wrote: > I have an old postfix + dovecot + Roundcube mailserver > (mail.domain.Tld). Server clock is loosing time and adjusting it causes > dovecot to kill itself, we cannot install more memory, bigger > hard-drives, etc. > > I have built

Re: Backtrace:dovecot/imap

On 29 Apr 2016, at 14:31, Ralf Hildebrandt wrote: > > #0 buffer_delete (_buf=0x0, pos=0, size=0) at buffer.c:213 > #0 buffer_delete (_buf=0x0, pos=0, size=0) at buffer.c:213 >buf = 0x0 >end_size = > #1 0x7f5729a7507e in array_delete_i

Backtrace:dovecot/imap

Config: # 2.2.devel (2dc8e2d): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.devel (850d80b) # OS: Linux 3.13.0-77-generic x86_64 Ubuntu 16.04 LTS auth_mechanisms = plain login default_vsz_limit = 1 G imapc_host = email.charite.de imapc_port = 993 imapc_ssl = imaps imapc_ssl_verify = no

Changing Password Schemes

Good Day, I have been following this tutorial without much luck - http://wiki2.dovecot.org/HowTo/ConvertPasswordSchemes#CA-26af2b83a43b8100522c57565773f605c21f2f27_1 It is obvious to me that I am not following the instructions correctly and need to be shown what I am misunderstanding. I

Re: Recent update causes segfault in proxy mode

* Ralf Hildebrandt schrieb am 29.04.16 um 11:42 Uhr: > * Ralf Hildebrandt : > > > Apr 29 11:05:30 mproxy dovecot: imap(hildeb): Fatal: master: service(imap): > > child 12393 killed with signal 11 (core dumped) > > > > Unfortunately, I'm not getting a backtrace :( >

Re: Recent update causes segfault in proxy mode

* Ralf Hildebrandt : > Unfortunately, I'm not getting a backtrace :( got it: # gdb /usr/lib/dovecot/imap 16784 GNU gdb (Ubuntu 7.11-0ubuntu1) 7.11 Copyright (C) 2016 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later

Re: Recent update causes segfault in proxy mode

* Ralf Hildebrandt : > Apr 29 11:05:30 mproxy dovecot: imap(hildeb): Fatal: master: service(imap): > child 12393 killed with signal 11 (core dumped) > > Unfortunately, I'm not getting a backtrace :( Got a core dump, but I need to find out where to get the debug

Recent update causes segfault in proxy mode

I'm using the auto builds (2:2.2.24-1~auto+3) for Ubuntu/Debian. The recent upgrade to 2.2.24 cause the follwoing error to appear: I can log in to a mailbox via dovecot I can delete emails Upon expunge, dovecot crashes: Apr 29 11:05:30 mproxy dovecot: imap(hildeb): expunge: box=INBOX,

Re: WP8/Windows 10 mail app can't login, tries double auth

On 04/28/16 21:27, Joseph Tam wrote: Attila Nagy writes: Are there anybody who could make WP8 (and W10 desktop clients it seems) devices working with Dovecot's POP3 server? The conversation looks like this: S +OK ready C CAPA S +OK S CAPA S TOP S UIDL S RESP-CODES S PIPELINING S

Re: Long delays when deleting a message in inbox

On 28.04.2016 20:54, Yves Goergen wrote: > Hi, > > Since recently, there's a long delay when deleting any message from my > inbox folder. This affects deleting and moving messages, but only the > inbox of a single mailbox. The delay is a few seconds. Other > operations work instantly. > > The