Here are some logs, maybe related to my problem.
Aug 23 20:43:57 Panic:
doveadm(m...@example.com)<1355655>: file
dsync-brain-mailbox.c: line 883 (dsync_brain_slave_recv_mailbox):
assertion failed: (memcmp(dsync_box->mailbox_guid,
local_dsync_box.mailbox_guid, sizeof(dsync_box->mailbox_guid))
Very interesting new insights:
When I use imapsync and let it synchronize mails from INBOX to
INBOX/testfolder, the automatic replication works fine.
All mails are synchronized between my two backends.
When I move the mails to the INBOX (doveadm move -u m...@example.com
INBOX mailbox
416.642.7266
Main 1.866.411.7266
Fax 1.888.892.7266
Email p...@scom.ca
On 7/31/2022 8:16 AM, Patrick Westenberg wrote:
Hi everyone,
I have a weird problem with replication that I'm unable to solve.
A new account is sychronized from an external provider via imapsync.
The mails end up on
Hi everyone,
I have a weird problem with replication that I'm unable to solve.
A new account is sychronized from an external provider via imapsync.
The mails end up on my backend1. I see that the folder structure is
immediately replicated to backend2.
However, a lot of mails are missing and
gt; In this scenario MUA just connects to mail.yourdomain.com
> <http://mail.yourdomain.com> and randomly uses one of the two ips. You
> can't control which one, but this gives you active/active loadbalancing.
> In case one server is down the MUA just uses the other ip.
Are you sure that thi
Hajo
>
> Am 23.08.2017 um 14:21 schrieb Patrick Westenberg:
>> I haven't done this on the old, working machine.
>>
>> So there must be a difference between Debian 7 and 9 how open files are
>> handled?
>>
>> Regards
>> Patrick
>>
>&
I haven't done this on the old, working machine.
So there must be a difference between Debian 7 and 9 how open files are
handled?
Regards
Patrick
Aki Tuomi schrieb:
> You probably need to increase ulimit -n
>
> Aki
>
>
> On 23.08.2017 14:10, Patrick Westenberg
Hi @all,
after re-installing one of my two frontends/proxy-servers I get the
following error messages after some time (sometimes after 1h, sometimes
after 24h):
11:23:55 imap-login: Error: socketpair() failed: Too many open files
11:23:55 imap-login: Error: socketpair() failed: Too many open
Hi @all,
I have a 3 server setup (MX ==LMTP== Proxy ==LMTP== Backend).
After upgrading to 2.2.18 I was able to use LMTPs from MX to the proxy
but not from the proxy to the backend:
Received: from mf01.example.net ([172.17.1.5])
by mb01.example.net (Dovecot) with LMTP id
Hi everyone,
can anybody explain the difference between Dovecots fast sync and full
sync in replication mode?
Regards
Patrick
Nathan Schultheiss schrieb:
My config:
Dell Equallogic
|- VMWare ESXI (iscsi mount in VMware with VMWare VMFS 5 format 4To)
|-- Mounted as slave disk on a VM Ubuntu and exported with this options
(rw,no_subtree_check,all_squash,anonuid=1000,anongid=1000,async) and formated as
ReiserFS (I've
Hi all,
I'm running two directors with lmtp proxy as relay transport for my
mail exchangers.
relay_transport = lmtp:inet:dovecot-directors.example.net
dovecot-directors.example.net resolves to 172.17.1.3 and 172.17.1.4
Now, .3 is down and Postfix tries to deliver it to .4 but this
connection
Hi,
this seems to be a problem with Outlook 2013 and not NFS.
Regards
Patrick
Hi everyone,
some days ago I had trouble with my NFS-Server (high delays) which
caused dovecot lmtp to deliver the same message several times
(up to 10x).
I recognized some old/unused .nfs files in the maildirs which
seemed to be index files. I deleted them and everything was fine again.
Hi all,
I just recognized a lot of log entries like this on my proxy:
Dec 03 13:50:54 imap-login: Info: proxy(m...@example.com): disconnecting
1.2.3.4 (Disconnected by server): user=m...@example.com, method=PLAIN,
rip=1.2.3.4, lip=2.4.6.8, TLS, session=qk02v6DsJwBTlUQX
There are no similar
Timo Sirainen schrieb:
See the session ID “qk02v6DsJwBTlUQX”. Find the disconnection message from the
backend server’s logs by grepping it.
There is only the login entry:
Dec 03 13:50:53 imap-login: Info: Login: user=m...@example.com,
method=PLAIN, rip=1.2.3.4, lip=2.3.4.5, mpid=3707, TLS,
Timo Sirainen schrieb:
On 3.12.2013, at 22.15, Patrick Westenberg p...@wk-serv.de wrote:
Timo Sirainen schrieb:
See the session ID “qk02v6DsJwBTlUQX”. Find the disconnection message from the
backend server’s logs by grepping it.
There is only the login entry:
Dec 03 13:50:53 imap-login
Daniel Parthey schrieb:
Hi Patrick
the director does not check backends for availability. If one backend goes up
or down, you need to instruct the director to add/remove this backend from its
pool.
http://blog.dovecot.org/2012/02/dovecot-clustering-with-dsync-based.html
says:
One
Daniel Parthey schrieb:
You need to keep the password database up-to-date and ensure to not return an unhealthy
backend IP in the host extra field, since the knowledge of the proxy (as
mentioned in the blog) is simply read from the passdb database. Database content needs to
be maintained by
Timo Sirainen schrieb:
The blog was telling the idea how things would work, not exactly whose
responsibility it is to do every part of them. The Dovecot proxies will know
which backend servers are down (but not without extra scripting).
So another ineffectual feature from Dovecot.
You
Hi everyone,
I'm running a test environment with a proxy in front of working
replication between two backends but redirecting in case of a
backend failure is not working.
Nov 09 21:03:59 imap-login: Error: proxy(m...@example.net):
connect(10.5.29.211, 143) failed: Connection refused (after 0
Hi everyone,
this article
(http://blog.dovecot.org/2012/02/dovecot-clustering-with-dsync-based.html)
describes the situation for director/NFS-based clusters and SSH-based
clusters.
Right now I'm running the first setup with one proxy/director and two
backends (all 2.2.x) mounting an
Romer Ventura schrieb:
Scenario1: This should allow any to lose any of the servers and clients
still have access to their emails (although I am not sure how the indexes
would react to this and sudden disconnection)
- 2 Dovecot Proxy servers, using a virtual IP to where the clients
Hi everyone,
I would like to move my mails from ocfs2 to an NFS share.
As the mountpoint and all folders and files belong to nobody/nogroup,
dovecot is only able to access the mails if I give full access to
others. I don't like that.
How do you NFS-using guys solve this problem?
Regards
Benny Pedersen schrieb:
there is 2 kinds of people, one that understand unix auth, and the
others that dont :)
There are friendly people ... and you :)
Matthias Hofer schrieb:
postfix/lmtp[10994]: C2DF4C000DF: to=us...@mydomain.org,
relay=mail.mydomain.org[private/dovecot-lmtp],
delay=0.1, delays=0.05/0/0/0.04, dsn=5.1.1, status=bounced (host
mail.mydomain.org[private/dovecot-lmtp]
said: 550 5.1.1 us...@mydomain.org User doesn't exist:
Matthias Hofer schrieb:
So, is there a way for dovecot-{lda/lmtpd} to accept us...@mydomain.org but checks for
user1 in the user
DB?
Try username_format=%n so dovecot uses the username only:
http://wiki2.dovecot.org/Variables
passdb {
driver = passwd-file
args = scheme=PLAIN
Peer Heinlein schrieb:
Even on midrange-systems it's necessary to set ulimit -n to a higher
value then the system default of 1024.
Could this lead to this problem?
Error:
file_dotlock_create(/var/mail/example.com/john.doe/Maildir/.Sent/dovecot-uidlist)
failed: No space left on device
Bjørn T Johansen schrieb:
I have configured a new server and copied the dovecot-sql.conf file that works
a different server to the new server... But when Dovecot tries to connect to
the database, the
following error appears..:
Mar 16 22:28:25 smtp dovecot: auth: Error: pgsql: Connect failed to
Timo Sirainen schrieb:
Just to let you know: I'm planning on releasing v2.1.11 today/tomorrow. If you
wish to get something fixed for it, ask quickly. :)
Backend-Failover would be nice ;-)
Hi,
no one here who is able to reply to my questions?
Regards
Patrick
Patrick Westenberg schrieb:
Hi everyone,
short version:
Is there no built in failover mechanism for the director service to
handle a backend failure?
Long version:
I have a frontend server running the director service
Hi everyone,
short version:
Is there no built in failover mechanism for the director service to
handle a backend failure?
Long version:
I have a frontend server running the director service and two backends.
Due to maintenance I had to shut down one of the backends which caused
connection
Can you provide the output of doveconf -n?
Regards
Patrick
Hi Luigi,
with regard to SSL my configuration is much more simple and it works
fine with IPv4 and IPv6. But you have of course to use a hostname
matching the certificates common name.
# 2.1.6: /usr/local/etc/dovecot/dovecot.conf
# OS: Linux 2.6.32-5-amd64 x86_64 Debian 6.0.5
auth_mechanisms
Hi all,
isn't it possible to use the director functionality for smtp-auth too?
I have a frontend system for imap and outgoing mails using sasl and I
recognized that all sasl username/password combinations are accepted as
these credentials aren't checked by the backend servers.
Regards
isn't it possible to use the director functionality for smtp-auth too?
I have a frontend system for imap and outgoing mails using sasl and I
recognized that all sasl username/password combinations are accepted as
these credentials aren't checked by the backend servers.
I found a workaround
Hello,
yesterday I set up a second director and even it works fine, some errors
occur in the logfile on the new director:
director: Error: Director 172.17.1.3:9090/left disconnected
director: Error: Director 172.17.1.3:9090/right disconnected
172.17.1.3 belongs to the first director which
Hi everyone,
I recognized a very strange behavior when doing backups of my mdbox
mailboxes. After the backup the quota for each mailbox is twice as much
as before the backup and I have to recalculate the quota to get the
former/correct information.
root@mb01:~# doveadm quota get -u
Timo Sirainen schrieb:
You must not lose indexes with mdbox or you'll lose message flags and
mails may also end up going to wrong mailboxes.
Yes, have been there but this behaviour is confusing me as I find
conflicting information in the wiki:
http://wiki2.dovecot.org/IndexFiles
If index
Timo Sirainen schrieb:
But you really don't want any of this with mdbox, not deleting index
files or having per-backend index files.
What is the director/backend-stuff useful for if per-backend index files
is not recommended? As far as I understood, that's what it's all about.
Patrick
Timo Sirainen schrieb:
No. Director is simply about making sure that more than one server won't access
the same user's mailbox simultaneously. I'm not recommending per-backend index
files to any kind of setups. Perhaps the NFS wiki page should be changed also.
So using a director it should
Hi,
right now my index directory is part of the users home directory:
mail_home = /var/mail/%d/%n
mail_location = mdbox:~/mdbox
I want the indexes to be stored in a different location:
mail_home = /var/mail/%d/%n
mail_location = mdbox:~/mdbox:INDEX=/var/indexes/%d/%n
If I just switch this
Hi Stephan,
after re-installing the whole system the files have been installed
properly.
Patrick
Hello,
I installed Dovecot 2.1.4 and Pigeonhole 0.3.0 and wondered that there
is no 20-managesieve.conf file anymore.
It is no problem to use one of my old files. I just want to know whether
this is a bug or not.
Regards
Patrick
Stephan Bosch schrieb:
I wouldn't know why it is missing in your installation. It is still
contained in the tarball. How did you install it exactly?
I installed it the same way as usual:
./configure
make
make install
No errors reported.
I checked the configure options and also tried
Hi,
I switched from dovecot-lda to lmtp for my quota warnings but there is
something wrong with the parameters:
/usr/local/libexec/dovecot/lmtp -d $USER -o plugin/quota=dict:User
quota::file:%h/mdbox/dovecot-quota:noenforcing
/usr/local/libexec/dovecot/lmtp: invalid option -- 'd'
Timo Sirainen schrieb:
On 10.4.2012, at 13.44, Patrick Westenberg wrote:
I switched from dovecot-lda to lmtp for my quota warnings but there is
something wrong with the parameters:
/usr/local/libexec/dovecot/lmtp -d $USER -o plugin/quota=dict:User
quota::file:%h/mdbox/dovecot
Timo Sirainen schrieb:
The :noenforcing isn't in the right location.
dict:User quota::noenforcing:file:%h/...
Aww.. thank you!
Hi again,
I tried to setup a test invironemnt like this:
MTA --(lmtp)--\ /--(lmtp)-- backend1 --\
-- director -- -- NFS
MTA --(lmtp)--/ \--(lmtp)-- backend2 --/
IMAP-User -- frontend1 --\ /--(imap)-- backend1 --\
Timo Sirainen schrieb:
On Fri, 2012-03-30 at 21:37 +0200, Patrick Westenberg wrote:
MTA --(lmtp)--\ /--(lmtp)-- backend1 --\
-- director -- -- NFS
MTA --(lmtp)--/ \--(lmtp)-- backend2 --/
IMAP-User -- frontend1
Timo Sirainen schrieb:
Another director. They're meant to connect to each others and do LB/HA.
But what about my MTAs? How can I tell my two postfix servers that there
are two directors and it should/can use the other one if the
first is down?
Now I use relay_transport =
Timo Sirainen schrieb:
where lmtp.example.com expands to your two IP addresses. DNS server handles
load balancing by returning IPs in round robin and Postfix handles fallbacking
to the second IP if the first one doesn't work. Dovecot has similar behavior in
several places.
As far as I
Timo Sirainen schrieb:
A small Dovecot stone can be bought for 10 euros, a medium sized stone for 100
euros and a large stone for 500 euros. Each large stone can usually handle
around 1000-2000 users before you need to buy more. If you have millions of
users we'll need to find you a larger
Patrick Westenberg schrieb:
Nick Warr schrieb:
I think some of the new Dovecot (director?) software is user aware, but
I don't know if it's quite ready for production.
Yes, with director it should be something like that:
MTA --(lmtp)--\ /--(lmtp)-- backend1 --\
-- director -- -- NFS
MTA
Hi everyone,
as I have often trouble with OCFS2 I want to switch to NFS but
I'm not sure how to rebuild my cluster with regard to locking
and indexing problems.
By now my I have a four server configuration (there are another 2
servers for outgoing mail but they can be ignored):
MTA(MX10)
Nick Warr schrieb:
I think some of the new Dovecot (director?) software is user aware, but
I don't know if it's quite ready for production.
Yes, with director it should be something like that:
MTA --(lmtp)--\ /--(lmtp)-- backend1 --\
-- director --
Hi guys,
recently I had some trouble with my ocfs2 cluster and it unmounted
itself from /var/mail.
Unfortunately I received mails while my mailstore was unmounted and some
mails are stored in /var/mail on the hosts local harddisk.
Now I need to merge/move these locally stored mails to my
On Thu, 16 Feb 2012 02:04:52 +0100, Finn B f...@kirstineslund.dk
wrote:
Now I come to think of it I realize that my production system is
intel
based and the 2 new ones are AMD based and wonder if this may be the
case ?
Dovecot 2.0.3 to 2.0.16 works fine on my DualCore Opterons (VMs).
Nikolaos Milas schrieb:
No, this did not solve the problem. I changed to vmail
service quota-warning {
executable = script /opt/mail1.sh
user = vmail
unix_listener quota-warning {
}
}
This is what works for me:
service quota-warning {
executable = script
Hi there,
is anyone using munin to monitor connections to dovecot?
If someone does, which plugin is used?
Regards
Patrick
Hi again,
I have a working test environment not but I don't feel very comfortable
with a non encrypted connection between the proxy/director and the
backend servers.
If I set ssl = required on my backend server I get this error:
imap-login: Disconnected (tried to use disabled plaintext auth)
Jan-Frode Myklebust schrieb:
Yes, and in ascii-art this becomes :-)
MTA -(lmtp)-- dovecot-director ---(lmtp)--- backend-server1
\---(lmtp)--- backend-server2
IMAP-user -(imap)-- dovecot-director --(imap) -- backend-server1
Jan-Frode Myklebust schrieb:
MTA -(lmtp)-- dovecot-director ---(lmtp)--- backend-server1
\---(lmtp)--- backend-server2
IMAP-user -(imap)-- dovecot-director --(imap) -- backend-server1
\--(imap) -- backend-server2
Timo Sirainen schrieb:
On Wed, 2011-11-16 at 19:40 +0100, Patrick Westenberg wrote:
I already use lmtp:unix:private/dovecot-lmtp as transport but where is
the link to the indexes?
You can switch to lmtp:tcp:1.2.3.4:24 where 1.2.3.4 would be Dovecot
LMTP proxy, which would forward
Peer Heinlein schrieb:
I have 11 TB hard used Mailstorage, saved als maildir in ext3 on HP EVA.
You have 11 TB of mails on a non cluster filesystem?
Is it only accessed from one server or how does it work?
Ed W schrieb:
See the sticky in my reply. You use one of several techniques to
ensure that users always end up on the server with the indexes on. That
way much of the IO is served from that local machine and you only access
the SAN for the (in theory much less frequent) access to the mail
Ed W schrieb:
I'm using NexentaStor (Solaris, ZFS) to export iSCSI-LUNs and I was
thinking about a SSD based LUN for the indexes. As I'm using multiple
servers this LUN will use OCFS2.
Given that the SAN always has the network latency behind it, might you
be better to look at putting the SSDs
Dovecot-GDH schrieb:
If I/O performance is a concern, you may be interested in ZFS and Flashcache.
Specifically, ZFS' ZIL (ZFS Intent Log) and its L2ARC (Layer 2 Adaptive Read
Cache)
ZFS does run on Linux http://zfs-fuse.net
I'm using NexentaStor (Solaris, ZFS) to export iSCSI-LUNs and I was
Hi all,
is anyone on this list who dares/dared to store his index files on a
MLC-SSD?
Regards,
Patrick
Hi guys,
is there any way to configure Dovecot to process the default sieve
script and, after that, a user specific script?
I have a default script to sort spam into a spam folder but if a
user specific script is present, the default script is ignored.
sieve = ~/.dovecot.sieve
sieve_dir =
On Fri, 19 Aug 2011 11:13:21 +0200, Angel L. Mateo ama...@um.es
wrote:
Is there any way to manually update indexes?
As far as I understood, you just have to delete the index files and
Dovecot will regenerate them when a user logs in the next time.
Regards
Patrick
On Thu, 11 Aug 2011 17:23:38 -0400, Patrick Domack
patric...@patrickdk.com wrote:
Ya, would have to be one of the namespace }'s is missing, as they are
right before mail_uid/gid
I really missed to uncomment the namespace ending curly bracket even
though I triple checked this file.
Thank you
Hi guys,
I setup a new box with Debian Squeeze 64bit and installed dovecot from
the sources. However, I can't start dovecot or even use doveconf:
root@imap01:~# doveconf -n
# 2.0.13: /usr/local/etc/dovecot/dovecot.conf
doveconf: Fatal: Error in configuration file
Vincent Richomme schrieb:
I have tested and there is still an issue with mysql because I get the
following error :
Aug 07 12:51:20 auth: Fatal: Unknown passdb driver 'mysql'
Aug 07 12:51:20 master: Error: service(auth): command startup failed,
throttling
It looks like you haven't compiled
The config files are well commented.
Take a look...
Patrick
Patrick Westenberg schrieb:
Feb 26 00:39:25 endeavour dovecot: lmtp(6967, m...@jasbafliesen.de):
Error: 1WYlBCE1aE03GwAA0CSSVw: sieve: msgid=4d683da5.7030...@gmx.de:
failed to store into mailbox m...@jasbafliesen.de': Unknown namespace
Feb 26 00:39:25 endeavour dovecot: lmtp(6967, m
I didn't change anything for months.
I'll upgrade to the latest versions and see what happens
Timo Sirainen t...@iki.fi schrieb:
On Sat, 2011-02-26 at 01:15 +0100, Patrick Westenberg wrote: Feb 26 00:39:25
endeavour dovecot: lmtp(6967, m...@jasbafliesen.de): Error:
1WYlBCE1aE03GwAA0CSSVw
Hi guys,
my default sieve script fails due to an unknown mailspace even I told
him to use one.
What's wrong?
Patrick
Feb 26 00:39:25 endeavour dovecot: lmtp(6967, m...@jasbafliesen.de):
Error: 1WYlBCE1aE03GwAA0CSSVw: sieve: msgid=4d683da5.7030...@gmx.de:
failed to store into mailbox
Timo Sirainen schrieb:
Someone did? .. It anyway depends on IMAP client and possibly also user. There
are no easy ways to calculate it exactly. I think it's usually around 10-20% of
mailbox size, but it really depends more on the number of messages than the
size of messages.
Okay, so what
Hi guys,
2 or 3 weeks ago, one of you explained how to calculate the size of the
index files for an user.
Can somebody explain this again please?
Thx
Patrick
Hello,
just to get it right:
DRBD for shared storage replication is OK?
Patrick
Eric Rostetter schrieb:
Quoting Patrick Westenberg p...@wk-serv.de:
just to get it right:
DRBD for shared storage replication is OK?
Yes, but only if done correctly. ;) There is some concern on Stan's part
(and mime) that you might do it wrong (e.g., in a vm guest rather than
at the vm host
Peter Reinhold schrieb:
I have a virtual user called @reinhold.dk setup to redirect to my main
account, pe...@reinhold.dk.
If I send a spam mail (GTUBE) to pe...@reinhold.dk, the mail is marked
with Amavis x-headers as it should be.
You have to create an AmavisUsers for this Alias/Forwarding
Won't be 15k U320 SCSI disks also faster than average SATA disks for the
indexes?
Miha Vrhovnik schrieb:
Patrick Westenbergp...@wk-serv.de wrote on 20.11.2010 23:46:14:
You can give additional space to e.g. Trash mailbox:
quota_rule2 = Trash:storage=100M
Patrick you sure, that doesn't mean that the trash quota is 100M?
Haven't tested your version, but for sure I know,
Glen Lee Edwards schrieb:
I'm trying to configure Dovecot 2.0.7. In the Dovecot Wiki for Maildirs
it says that Maildirs are almost always located in ~/Maildir. I'm a
Linux end user, not a programmer, so I may be wrong in this; but isn't
the notation ~/ used for system users only to reference
Tim Traver schrieb:
Is there a quota setting that will let them move things to the trash
without error? this of course would be so they could decrease their disk
usage and become under quota again...
You can give additional space to e.g. Trash mailbox:
quota_rule2 = Trash:storage=100M
Hi @all,
is there any way to inform a mailbox user via mail that his mailbox reached
a specified limit?
Regards
Patrick
On Thu, 28 Oct 2010 12:16:11 +0200, Patrick Westenberg p...@wk-serv.de
wrote:
is there any way to inform a mailbox user via mail that his mailbox
reached
a specified limit?
Forget it. Found it in the wiki.
Hi again,
I just recognized that my dovecot forgets the quota for a mailbox.
This is what the maildirsize looks like:
1 read mail present, 1 new/unread mail
2097152S
0 0
909936 1
and later, with 2 read mails:
2097152S
0 0
There are no errors logged.
Moreover, my quota warning script doesn´t
Patrick Westenberg schrieb:
Timo Sirainen schrieb:
mdbox doesn't work with Maildir++ quota, you need to use dict quota
with e.g. file backend.
Oh, very sad :(
In this case we have to switch back to maildir.
Hm, I should read everything.
File backend should be ok.
Timo Sirainen schrieb:
Error: quota: connect(/usr/local/var/run/dovecot/quota-warning) failed:
Permission denied
You need to give enough permissions for that.
mail_uid = vmail
..
service quota-warning {
executable = script /usr/local/etc/dovecot/quota-warning.sh
user = vmail
This
Hello,
if new mails arrive, the quota information is updated and reported via
imap immediately. However, after deleting a message, nothing happens.
Even if I delete all messages and the mailbox e.g. was over quota, new
mails won´t be accepted because the mailbox is over quota.
Is this the way
Hi @all,
I tried to change the log_timestamp to
log_timestamp = %Y-%m-%d %H:%M:%S
However it is not recognized and log entries are still written with the
default settings:
Oct 4 22:04:42 discovery dovecot: imap-login: Login:
Oct 4 22:04:42 discovery dovecot: imap: Debug: Module loaded:
Oct
Charles Marcus schrieb:
This is Debian - chroot problem?
I don´t think so. There aren´t any error messages.
The settings seems just not being used.
Hello,
I´m using Dovecot 2.0.1 with quota support (quota and imap_quota) which
works perfect. However, I´d like to give some mailboxes unlimited quota.
What quota setting (in the backend (SLQ)) is needed to tell Dovecot as
LDA that the mailbox has unlimited quota?
0 or NULL or -1 or something
Daniel L. Miller schrieb:
Reviewing some mailing list archives and the wiki, I still don't have a
real clear picture of why I'd want to use mdbox. What I've taken from
the info I've reviewed says mdbox is more complicated (than sdbox), has
greater potential for breakage (simply because it's more
Daniel L. Miller schrieb:
Reviewing some mailing list archives and the wiki, I still don't have a
real clear picture of why I'd want to use mdbox. What I've taken from
the info I've reviewed says mdbox is more complicated (than sdbox), has
greater potential for breakage (simply because it's more
On Wed, 22 Sep 2010 23:03:58 -0400, Edward Carraro ednit...@gmail.com
wrote:
This could lead to a possible bottleneck eventually and we were wondering
if
it's possible to have dovecot
direct x number of users to one message store location while others get
their mail on a different mount?
Dieter Knopf schrieb:
I alway get a failed to find namespace for mailbox 'foo'
but/home/vmail/domain.tld/name/.foo/ exist.
I tried it with:
fileinto foo; and fileinto .foo;
This works for me:
fileinto :create INBOX.foo;
:create will create this folder if it does not exist.
Patrick
1 - 100 of 117 matches
Mail list logo
