similar to: 2.2.18 initial setup permissions problem

Displaying 20 results from an estimated 70 matches similar to: "2.2.18 initial setup permissions problem"

2015 Oct 26
0
2.2.18 initial setup permissions problem
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Fri, 23 Oct 2015, Forrest wrote: > I'm using Dovecot 2.2.18, compiled from source, on CentOS 6. > > I'm running into a permissions problem with my first rollout of Dovecot which > has to do with directory permissions: > > Oct 23 14:34:51 mail dovecot: imap(username): Error: > stat(/home/username/Maildir/tmp) failed:
2006 Dec 07
0
sip qualify unreachable/reachable - ci$co 7940
I have logs full with this messages... I must have qualify turned on, because phone is behind firewall, main problem si, that phone is each hour about one hour unavailable! :'( I tried to modify minexpiry/maxexpiry sip.conf timeouts, but nothing help me. I'm using latest firmware 8.4 in phone, will be better to downgrade? to what version? (latest asterisk 1.4branch) [Dec 7 00:36:56]
2015 May 20
0
"doveadm backup" doesn't work anymore after upgrading to 2.2.18
On 5/19/15 6:19 AM, Jesus Cea wrote: > dsync-local(jcea): Error: Remote command returned error 65: ssh csi > doveadm dsync-server dsync-server > """ > > Now in 2.2.18 I get the second error and the backup is aborted. It > doesn't work anymore. > > I don't find any reference to error 65 anywhere. Error 65 is likely the SSH process exit code. Pages
2015 May 22
0
dovecot 2.2.18 and ssl_parameters_regenerate
HI Timo, On http://wiki2.dovecot.org/SSL/DovecotConfiguration I read in chapter SSL security settings: When Dovecot starts up for the first time, it generates new 512bit and 1024bit Diffie Hellman parameters and saves them into <prefix>/var/lib/dovecot/ssl-parameters.dat. After the initial creation they're by default regenerated every week. With newer computers the generation
2015 Jun 19
0
crash dovecot 2.2.18
Hello, after upgrading from 2.1.17 to 2.2.18 i have a specific Inbox which causes a crash on dovecot: Jun 19 09:28:03 hostname dovecot: imap(username): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x7075f) [0x7f9298c4375f] -> /usr/lib/dovecot/libdovecot.so.0(+0x707be) [0x7f9298c437be] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7f9298bf11aa] ->
2015 Aug 06
0
2.2.18: Mailbox INBOX sync: mailbox_delete failed: INBOX can't be deleted.
Hello Could my previously reported error above have something to do with the IMAP path prefix? It's not configured on either of the previously mentioned servers. I see a similar error, which may be related, when trying to sync using offlineimap.py: Folder INBOX [acc: test_account]: ERROR: ERROR in syncfolder for test_account folder INBOX Thanks Dale On 5 August 2015 at 16:59, Dale
2015 Sep 07
0
Dovecot 2.2.18 Panic: file index-mail-binary.c
On 28 Jul 2015, at 10:12, Michael Borgelt <mborgelt at borgelt.org> wrote: > > Hi, > I got the following in my dovecot log's on an particular email message with dovecot-imap. > > ---snip--- > Jul 28 08:42:11 hermes dovecot: imap(mborgelt): Panic: file index-mail-binary.c: line 354 (blocks_count_lines): assertion failed: (ret == -1) Not sure why this wasn't more
2015 Sep 23
0
[dovecot-2.2.18] dsync error: Error: Can't delete mailbox INBOX: INBOX can't be deleted.
With dovecot-2.2.19.rc1 still have this error.
2015 Sep 24
0
[dovecot-2.2.18] dsync error: Error: Can't delete mailbox INBOX: INBOX can't be deleted.
W dniu 23.09.2015 o 22:12, Timo Sirainen pisze: > On 23 Sep 2015, at 18:10, Marcin Miros?aw <marcin at mejor.pl> wrote: >> >> With dovecot-2.2.19.rc1 still have this error. > > "doveadm backup" wants to delete and recreate a folder if there are some changes that can't be incrementally just added to it (mainly if IMAP UIDs would need to be inserted in the
2015 Sep 30
1
userdb prefetch doesn't work with imapc (2.2.18)
Hi, I have the following config in dovecot 2.2.18: # doveconf -n userdb passdb userdb { driver = prefetch } passdb { args = host=127.0.0.1 port=1430 default_fields = userdb_imapc_user=%u userdb_imapc_password=%w driver = imap } I guess it should cause a single login to the backend IMAP server when issuing a LOGIN to dovecot. Yet, dovecot opens two TCP sessions. In the first, it
2017 Jan 31
0
dovecot 2.2.18 replication I/O Timeout
Dear list, I am having an issue like this http://www.dovecot.org/list/dovecot-cvs/2014-September/024898.html with my current dovecot 2.2.18 Concret: doveadm -Dv replicator replicate -p high -f info throws an I/O Timeout error and the only thing I can see are some lock issues: Error: Couldn't lock /var/vmail/info/.dovecot-sync.lock: Timed out after 30 seconds Can I debug the
2015 Sep 23
2
[dovecot-2.2.18] dsync error: Error: Can't delete mailbox INBOX: INBOX can't be deleted.
On 23 Sep 2015, at 18:10, Marcin Miros?aw <marcin at mejor.pl> wrote: > > With dovecot-2.2.19.rc1 still have this error. "doveadm backup" wants to delete and recreate a folder if there are some changes that can't be incrementally just added to it (mainly if IMAP UIDs would need to be inserted in the middle of the folder). Maildir doesn't allow INBOX to be deleted
2015 Oct 26
1
2.2.18 initial setup permissions problem
On 10/26/15 5:30 AM, Steffen Kaiser wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Fri, 23 Oct 2015, Forrest wrote: > >> I'm using Dovecot 2.2.18, compiled from source, on CentOS 6. >> >> I'm running into a permissions problem with my first rollout of >> Dovecot which has to do with directory permissions: >> >> Oct 23
2015 Sep 15
1
2.2.18 Regression: Incorrect STATUS response for virtual mailboxes
As shown below, adding a message to TRASH doesn't increase virtual/test's MESSAGES count. However SELECTing virtual/test triggers the increase; so does running `doveadm mailbox status vsize virtual/test` in another shell. $ mkdir -m0700 ~/mail/virtual/test $ echo -e "TRASH\n\tall" > ~/mail/virtual/test/dovecot-virtual $ /usr/lib/dovecot/imap S: * PREAUTH [CAPABILITY
2015 Jul 15
2
Null deference pointer in dovecot-2.2.18
Dear, use our static analysis tools, I find some bugs (Null deference pointer) for dovecot-2.2.18. Null deference pointer bugs often make program crashes, Please confim them, Thanks! 1. dovecot-2.2.18/src/config/config-request.c 332 'setting_export_section_name(ctx->prefix, def, children[i], i);', pointer 'children' in line 202 assigned NULL and if
2016 Aug 23
2
Possible IMAP IDLE bug in Dovecot 2.2.18 and 2.2.25
On 23.08.2016 15:08, cleber-listas at inetweb.com.br wrote: > Hello Guys, > I guess that I found a bug in Dovecot 2.2.18 and 2.2.25 versions. The > problem it's when I try to connect in a Dovecot used a proxy to another > e-mail server (in our case it's a Smartermail Server) the DoveCot send a > lot of IDLE commands to the destination server. With that, the LOG files >
2015 May 19
2
"doveadm backup" doesn't work anymore after upgrading to 2.2.18
Until today I could do this to backup my primary IMAP4 server: """ doveadm backup ssh csi doveadm dsync-server """ It doesn't work anymore after upgrading to Dovecot 2.2.18: """ jcea at ubuntu:~$ doveadm backup ssh csi doveadm dsync-server Enter passphrase for key '/home/jcea/.ssh/id_rsa': dsync-remote(root): Error: Mailbox INBOX: Failed
2015 Aug 05
2
2.2.18: Mailbox INBOX sync: mailbox_delete failed: INBOX can't be deleted.
Hello I have 2.2.18 built with: ./configure \ --prefix="$prefix" \ --bindir="$prefix/bin" \ --sbindir="$prefix/bin" \ --sysconfdir="/etc" \ --with-storages="maildir,imapc,pop3c" \ --without-vpopmail \ --without-ldap I'm attempting to sync (backup) from another Dovecot server running version 2.0.21: Both servers
2016 Mar 16
2
Index corruption in 2.2.18
We are using dbox with lz4 compression and dovecot-lda + sieve for delivery. Mail recieved: Mar 16 06:27:55 mail2 dovecot: lda(svs at example.com): sieve: msgid=<20160316032754.4C89D2C4 at rdbms.oldstable.office.example.com>: stored mail into mailbox 'INBOX' Around 08:14:00 user start his thunderbird with local filters. He found one mail without headers. Around that time user do
2015 Jul 28
0
Dovecot 2.2.18 Panic: file index-mail-binary.c
Hi. I have tried this email also with thunderbird imap which works. So this is as special Problem with the imap-module of the Horde framework. I will do some more debugging this evening. My Horde framework has the following Versions: Horde Groupware Webmail Edition 5.2.7 Horde (horde) 5.2.6 Horde_Imap_Client 2.29.1 Regards, Michael. Am 28.07.2015 um 09:12 schrieb Michael Borgelt: > Hi, >