Displaying 20 results from an estimated 2000 matches similar to: "Couldn't init INBOX: BUG: Unknown internal error"
2010 Dec 01
2
Virtual folder root cannot be opened, virtual folders ok
I am running dovecot 1.2.16 and not able to figure out an error
that happens whenever I select the root of a virtual mailbox tree.
At the moment I have a simple maildir store, accessed via IMAP, and
have successfully added a virtual fs namespace with two subdirectories.
I have created dovecot-virtual entries in the subdirs and they are
working fine; they show the expected messages, etc.
My
2014 Feb 24
1
A question regarding doveadm replicator status
Hello,
I am using Dovecot version 2.2.10. I am quite familiar with ssh replication
and I managed to set it up correctly. The only problem I see is that when i
run the command:
doveadm replicator status I get a wrong "Total number of known users" which
is
a) is different between the two (2) replicated dovecot servers, i.e. in
mail1 I get a total of 21 users and in mail2 I get a total of
2016 Mar 22
3
Replication issues master <-> master nfs backend
I keep having some replication issues and not sure what can be done to resolve or correct. It
does not seem to happen all the time, though for the last ~30 or so minutes and many
messages seems to be happening consistent for me.
I have 2 mail servers, basically clones, and thus master master replication. Most of the time
things work fine. But many times an email or several will arrive on one,
2009 Aug 25
3
Two server certificates for two common names
Hi there!
I have two DNS records
mail1.domain.tld
mail2.domain.tld
I have issued SSL server Certificates for both my domain names.
Is it possible to tell dovecot to use both , depending on
client access;
clients using the mail1.domain.tld be served by the mail1.domain.tld
.key and .cert
and those using mail2.domain.tld be served by the mail2.domain.tld .key
and .cert
Thanks in advance
2019 Apr 11
0
High availability of Dovecot
> Am 11.04.2019 um 11:48 schrieb luckydog xf <luckydogxf at gmail.com>:
>
> As your statement, nothing speical is needed to do except setting up DNS MX records, right?
MX records are for incoming MAIL:
yourdomain.com <http://yourdomain.com/> IN MX 100 mail1.yourdomain.com <http://server1.yourdomain.com/>
yourdomain.com <http://yourdomain.com/> IN MX 100
2019 Apr 11
2
High availability of Dovecot
Gerald Galster via dovecot schrieb:
> mail1.yourdomain.com <http://mail1.yourdomain.com> IN A 192.168.10.1
> mail2.yourdomain.com <http://mail2.yourdomain.com>?IN A 192.168.20.1
>
> mail.yourdomain.com <http://mail.yourdomain.com> ?IN A 192.168.10.1
> mail.yourdomain.com <http://mail.yourdomain.com> ?IN A 192.168.20.1
>
>
> mail1/mail2 is for
2009 Aug 04
2
1.2.3 - fchown failed messages
Hello,
I installed 1.2.3 and we are seeing a few messages in the log files such
as:
---
Aug 4 16:40:24 xyz dovecot: IMAP(john): fchown() failed with file
/home/john/.imap/INBOX/dovecot.index.log.newlock: Operation not permitted
Aug 4 16:40:24 xyz dovecot: IMAP(john): fchown() failed with file
/home/john/.imap/INBOX/dovecot.index.tmp: Operation not permitted
---
dovecot -n:
# 1.2.3:
2014 Sep 24
1
LDA randomly failing to write email to disk
We're using 2.2.13 with pigeonhole 0.4.3, in a clustered environment
(maildir on netapp, dual dovecot instances where each server is both a
proxy and a backend).
Every now and then (once a month per user, maybe?), users will see a blank
email in their inbox. Investigating further, and we will see that the only
information recorded in the maildir file for the message is the
Return-Path,
2019 Apr 11
0
High availability of Dovecot
> Am 11.04.2019 um 13:45 schrieb Patrick Westenberg via dovecot <dovecot at dovecot.org>:
>
> Gerald Galster via dovecot schrieb:
>
>> mail1.yourdomain.com <http://mail1.yourdomain.com> IN A 192.168.10.1
>> mail2.yourdomain.com <http://mail2.yourdomain.com> IN A 192.168.20.1
>>
>> mail.yourdomain.com <http://mail.yourdomain.com> IN A
2010 Aug 21
1
dsync and active-active fault tolerance mail servers
I would like to set up an active-active fault tolerance couple of mail servers.
Is the following procedure correct?
Let's suppose I want to set up two servers for acme.com, mail1.acme.com and
mail2.acme.com
I declare both servers as MX in DNS configuration.
Mailbox are stored in maildir with a single UID/GID owner for all the maildir files
Userbase is MySQL, user tables are replicated
2017 Jan 02
0
multiple shared/mail format namespaces
Yeah, that's valid configuration. As long as they have unique prefix.
Aki
> On January 2, 2017 at 5:58 PM Michal Soltys <soltys at ziu.info> wrote:
>
>
> Hi,
>
> Are configurations (with separate formats per namespace) - such as ...
>
> namespace {
> type = shared
> list = children
> inbox = no
> separator = /
> subscriptions =
2015 Feb 12
0
Dovecot dsync not replicating ".dovecot.sieve -> .sieve/managesieve.sieve" / setactive
Am 12.02.2015 um 15:47 schrieb Martin ?tefany:
> Hello,
>
> I've ran into problem with Dovecot and dsync replication. Everything
> works perfectly, including replication of sieve scripts, except fact
> that if user activates the 'managesieve' ruleset (I'm using currently
> Roundcubemail) on "mail1" host, it wouldn't be activated on
2017 Jan 02
2
multiple shared/mail format namespaces
Hi,
Are configurations (with separate formats per namespace) - such as ...
namespace {
type = shared
list = children
inbox = no
separator = /
subscriptions = no
prefix = shared1/%%n/
location = maildir:/var/mail1/%%n/
}
namespace {
type = shared
list = children
inbox = no
separator = /
subscriptions = no
prefix = shared2/%%n/
location =
2013 Sep 26
0
Dsync: Mailbox changes caused a desync.
Hi!
Here such synchronization error:
dovecot: dsync-local(alex at aaa.com): Warning: Mailbox changes caused a desync. You may want to run dsync again.
dovecot: dsync-remote(alex at aaa.com): Warning: /var/mail/virtual/aaa.com/alex/.INBOX.System/dovecot-uidlist: Duplicate file entry at line 2298: 1380157263.M585262P25253.mail1.aaa.com,S=2476,W=2553 (uid 3645 -> 3662)
dovecot: dsync-remote(alex
2017 Jan 09
2
multiple shared/mail format namespaces
On January 2, 2017 at 5:58 PM Michal Soltys <soltys at ziu.info> wrote:
>>
>>
>> Hi,
>>
>> Are configurations (with separate formats per namespace) - such as ...
>>
>> namespace {
>> type = shared
>> list = children
>> inbox = no
>> separator = /
>> subscriptions = no
>> prefix = shared1/%%n/
2019 Mar 11
0
dovecot Connection closed IDLE running
Hello,
sometimes I get lines like this on mail log.
Mar 11 07:57:14 mail2 dovecot: imap(john.one at domain.ro): Connection
closed (IDLE running for 0.006 + waiting input for 1765.640 secs, 0.001
in locks, 2 B in + 10+0 B out, state=wait-input) in=323201 out=3177999
Mar 11 07:58:56 mail3 dovecot: imap(john.two at domain.ro): Connection
closed (IDLE running for 0.005 + waiting input for
2006 Jun 20
4
Mailers and records MX
I've installed bind on centos 4.3.. This is a part of my config file:
example.com. IN MX 10 mail.example.com.
example.com. IN MX 15 mail1.example.com.
example.com. IN MX 20 mail2.example.com.
mail.example.com. IN A IP
mail.example.com. IN A IP
2013 Sep 28
2
New install not working.
Hello.
I need some help. I was running uw-imap on my IMAP server (so I am using mbox email files), but I was having trouble with Outlook 2013, so I decided to move to dovecot. At first things were looking much better, except that most of my folders, other than the Inbox, were not showing up. I started changing both the dovecot configuration and the folder structure of my mail files,
2015 Feb 12
2
Dovecot dsync not replicating ".dovecot.sieve -> .sieve/managesieve.sieve" / setactive
Hello,
I've ran into problem with Dovecot and dsync replication. Everything
works perfectly, including replication of sieve scripts, except fact
that if user activates the 'managesieve' ruleset (I'm using currently
Roundcubemail) on "mail1" host, it wouldn't be activated on "mail2"
host, by creating symlink ".dovecot.sieve ->
2013 Jun 05
1
partionning users among backends
Hi
I face growing load on a mailserver, and I would like to spread the load
on multiple machines. I made a first attempt with dsync but got burnt with
issues with mbox, therefore now I am looking for another safer approach.
Partitionning users on multiple backends would address my load problem.
I would have 50% of users on mail1.example.net and 50% on mail2.example.net,
but I need to correctly