and 9 "waiting 'failed' requests" for
the past couple of days. But I have no idea how to resolve the issue.
Suggestions welcome.
Rich Wales
ri...@richw.org
? (If possible, something I can
set up to run periodically in Nagios?)
Thanks for any suggestions.
Rich Wales
ri...@richw.org
would be processed
first (instead of near the end).
It matters what order the configuration files are processed in because
later files can override parameters set by earlier files.
Rich Wales
ri...@richw.org
I am syncing two Dovecot sites using dsync. Are there any tools
available to confirm that dsync is (or is not) running properly between
the two sites? (E.g., something I could run periodically in Nagios?)
Rich Wales
ri...@richw.org
s? Or do I need to configure
replication on both servers (with each one replicating to the other)?
Rich Wales
ri...@richw.org
bout 24 hours ago (and which I assume was
too long for people to be willing to read).
Rich Wales
ri...@richw.org
username
exec /usr/bin/doveadm dsync-server -u $username
With the above setup, replication ALMOST seems to work, EXCEPT that it's
failing with the following error in the local host's mail.log:
richatwork dovecot: doveadm: Error: dsync-remote(richatwork): Error:
dsync(local):
orking
may be that I'm not sure which user ID is being used on each end, so my SSH
keys aren't being used properly and the connection is failing.
Finally, the "Replication" wiki page mentions the "authorized_keys2" file,
which (AFAIK) is deprecated in the current SSH -- all authorized keys should
be in a single "authorized_keys" file on the target host, right?
Rich Wales
ri...@richw.org
(http://wiki2.dovecot.org/Replication), but I'm
still confused. I'd love to see an example that clearly shows how to
set up specific individual mail users to be replicated on a different
set of servers for each user, like what I described above.
Rich Wales
ri...@richw.org
file)? Or will Dovecot be broken unless I recopy everything from
scratch (with a command-line option to imapsync to put everything
in the INBOX destination namespace)?
Rich Wales
ri...@richw.org
ldir format).
I'm not familiar enough with Dovecot or IMAP to know exactly what this
difference means, but hopefully it will reveal something to someone here.
Let me know if you need to see other stuff in these raw logs that I didn't
mention here.
Rich Wales
ri...@richw.org
Replying to e-frog:
> http://wiki2.dovecot.org/Debugging/Rawlog
Thanks. I'll try this and (hopefully) be able to tell what's going on.
Rich Wales
ri...@richw.org
via a free licence. (!?!)
OK, thanks for setting my mind at ease.
Rich Wales
ri...@richw.org
no error messages of
any kind. There were a bunch of "Debug: Namespace" messages saying "
doesn't exist yet, using default permissions", but that's all. I'm including
(see below) an excerpt from my log output, sh
gh to say how to make its low-level IMAP module give a full logging
of all commands and responses?
For what it may or may not be worth, I'm trying my same mail migration test
using Maildir instead of mdbox, and it appears to be working fine.
Rich Wales
ri...@richw.org
sages could not be migrated because of this problem.
Am I doing something wrong? Or is the "folders containing both messages
and sub-folders" feature simply broken for the "mdbox" format -- meaning
presumably that I'll be forced either to use the Maildir format, or else
abandon Dovecot entirely and install Cyrus on my new mail server instead?
Rich Wales
ri...@richw.org
> I never said anything about breaking Thunderbird.
Sorry if I misinterpreted your response to reg9...@yahoo.de (when
he said that your proposed change "would actually just break with a
rather common client and change behaviour to all previous versions").
--
Rich Wales / ri
While I recognize that Timo has some valid points here with regard
to determining capabilities before vs. after login, I definitely
would consider breaking compatibility with Thunderbird to be a
MAJOR, MAJOR showstopper, regardless of the reasons for doing it.
--
Rich Wales / ri...@richw.org
nd also Dovecot's failure to
recognize a "user.XXX." prefix on a mailbox name as designating
user XXX's inbox (something that seems to work fine on Cyrus).
My Cyrus server currently has over 1,600 folders and subfolders,
so I absolutely can't / won't consider switching
19 matches
Mail list logo
