Last night dovecot died because of time changed backward.
I noticed that the line from dovecot read
Oct 9 01:00:44 mailstore16 dovecot: Time just moved backwards by 132
seconds. This might cause a lot of problems, so I'll just kill myself now.
Shouldn't such lines have the word "Error" or "Fa
Timo Sirainen writes:
But are you saying that Dovecot should log errors also with "info" level
by default?
No.
Looks like Dovecot currently uses "info" for info/debug messages, "err"
for errors and "crit" for fatals/panics.
That is good.
So I guess, just make syslog the default and write
Timo Sirainen writes:
Is there a need to have both? I was thinking about just splitting the
current dovecot-example.conf to example/*.conf or something
I think this may be somewhat a matter of preference, but I would find it
easier to have a "simple" file.. and a complete file.
I would find i
Timo Sirainen writes:
Why not go with a pure log replication scheme?
this way you basically have 3 processes.
1- The normal, currently existing programs. Add logs to the process
2- A Master replication process which listens for clients requesting for
info.
3- The slave processes that request i
Timo Sirainen writes:
# dovecot
Error: POP3 enabled but pop3_uidl_format not set
And don't let Dovecot come up?
Charles Marcus writes:
Maybe the answer is to have two .conf files - one, the example, that
contains the comments as it is now, and the other, the basic config
file, with bare minimum comments.
I think one single file with basic defaults uncommented is best.
As someone else mentioned, anyone
Timo Sirainen writes:
"Set pop3_uidl_format setting in config file"
"pop3_uidl_format setting is missing from config file"
"Set pop3_uidl_format in config file"
How about:
You have choosen to run POP3. The setting pop3_uidl_format needs to be set
in the dovecot.conf file for the POP3 server t
Joseba Torre writes:
there's no easy way to get rid of newbie problems: right now dovecot is quite
a complex software
I tried Cyrus once, and have been working with Courier for nearly 2 years
before I tried Dovecot.
In my opinion Dovecot is much simpler than Cyrus, but perhaps more complex
t
Timo Sirainen writes:
Master keeps all the changes in memory until slave has replied that it
has committed the changes. If the memory buffer gets too large (1MB?)
Does this mean that in case of a crash all that would be lost?
I think the cache should be smaller.
because the slave is handli
Timo Sirainen writes:
actually giving useful error messages. Often the admin is only looking
at the log file where "info" messages go (eg mail.log) because Dovecot
logs its startup message and login messages there, but not where the
errors go (eg mail.err). This has happened even with people wh
Timo Sirainen writes:
Then there are also people who would want to run Dovecot on their laptop
and have it synchronize with the main server whenever network connection
is available.
YES!
I had not thought of that, but that would be killer.. although that would be
multi-master which I think w
Timo Sirainen writes:
1) Split the config files, so the less used settings are separate files
I think that would be good.
Specially if you could have a tool chain that would produce both files from
one source.
2) Remove some of the settings completely from dovecot-example.conf,
although th
Troy Benjegerdes writes:
But that's currently not *really* replicated. The real question I guess
is why not use a cluster/distributed/san filesystem like AFS, GFS,
Because those distribute filesystems may be more difficult to setup, more
difficult to maintain and may be less portable than a d
Troy Benjegerdes writes:
I think you should at least try Coda, but don't spend too much time on
it. It is mostly a research project. I don't know of anyone really using
it in production use.
Hmmm. Didn't know that.
I knew it was a research project, but did not know it was not much in
producti
Troy Benjegerdes writes:
http://www.openafs.org/pipermail/port-freebsd/2007-February/000199.html
The freebsd port looks like it might be a bit hairy yet though.
AFS and CODA are on my list to check.
Another user in this list mentioned Gluster.
I must say gluster looks very interesting.
John Rowe writes:
gluster is looking extremely interesting although it's rather new.
Thanks. Saw it on a list of distributed FS but didn't click on it.
I was planning to take a look at AFS and Coda to start. Will also take a
look at gluster, although so far it seems a Linux only FS.
Scott Silva writes:
If you want to experiment with a inexpensive NAS with replication, look at
Freenas. It can do nfs sharing and automatic replication with rsync.
And it is free and based on Freebsd. Still immature, but it has a lot of
promise.
Our experience with FreeBSD+NFS has been less t
Zbigniew Szalbot writes:
I am using dovecot 1.0.0 and have only 5 pop3 users. However, I have
counted over 200 pop3-loging processes. I just wonder if it is normal for
dovecot (has been running maybe for 2-3 weeks after installing the stable
verion).
What is your login_processes_count in dovec
Justin McAleer writes:
On top of the performance gains, gathering disk usage for billing
changes from parsing hundreds of thousands of maildirsize files (and du
-s or equivalent for those really large maildirs, ugh) to a single sql
query,
Not sure how difficult it would be, but that would be
Steffen Kaiser writes:
My statement is simply my point of view, that the API should be independed
of the backend.
LDAP, Postgresql, Mysql.. I think any of them is fine.
I think anything BUT the initial setup that Timo mentioned. Files in
the mailstore I think is the least scalable option.
John H. Bennett III writes:
I am having difficulties trying to get the current stable version of
horde's imp webmail to work correctly using dovecot 1.0rc15. I am
using a pre-release version of SME Server 8 which runs on top of
CentOS 5. I have also tried using the 1.0 release of dovecot
Redudancy and recovering from a mailstore failure is one of the concerns I
am trying to address where I work.
Any plans to have Dovecot store emails in a database?
NAS/SAN devices which do automatic replication to a second device are
extremely expensive.
I also don't see any distributed file
Steffen Kaiser writes:
Having ACLs in SQL allows companies to have a centralized place for all ACLs.
Well, this statement is true for any backend, incl. LDAP.
Correct.
But many companies do not have a LDAP infrastructure.
It is much easier to setup a Mysql DB and put a table for ACL than it
Dean Manners writes:
options right though. Personally I prefer to exempt the dovecot* files from
the rsync, and let them be recreated fresh on the new installation.
I recently asked if it was necessary to delete/not sync the dovecot files
and Timo replied that they should work.
If copying
Timo Sirainen writes:
Keeping ACLs in SQL is different from keeping the whole mailbox data
in SQL. Currently the ACL plugin supports only vfile backend, but it
wouldn't be too difficult to add support for SQL backend.
Having ACLs in SQL allows companies to have a centralized place for all
Is it ever necessary to delete any of the dovecot files when moving between
machines from different RC versions?
I read all the RC notes from RC15 to 31 and didn't see any notes about
this, but wanted to be completely sure.
Have some domains that I need to move from a RC15 machine to a RC29 m
Francisco Reyes writes:
I took off the Mac support and myself and two co-workers that were helping
me test were about to call it a day. The co-worker testing the Mac support
tried it.. and it worked.
Reporting back.
It has been two days since we upgraded to rc29
No reports of problems on Mac
David Jonas writes:
Or perhaps similar to postfix, like dovecot/deliver[pid]:
I think that one would be the best scenario.
Timo Sirainen writes:
On Mon, 2007-04-02 at 22:31 -0400, Francisco Reyes wrote:
Based on some TCP dumps we did we noticed that Outlook was doing LIST, but
no select (except at account) creation.
Could you show me the tcpdumps?
Will report back today.
After we upgraded to r29 and had both
Francisco Reyes writes:
Several attempts to support both Mac and PCs keep failing.
In my latest attempt I used the following settings:
#courier-imap compatibility/Thunderbird
namespace private {
separator = .
prefix = INBOX.
inbox = yes
}
For MAC OS Mail.app
namespace private
After sending a messasge about a problem (The folder 'Inbox' cannot contain
items. Namespace problems) I found what seems to be a fix in the release for
rc29.
Besides any potential configuration files, do I need to delete the old index
files? Any of the dovecot files?
Based on the release no
Kenneth Porter writes:
In rc27:
A few new small features and lots of index/mbox fixes. I've been heavily
stress testing this release, so I think it should be about perfect. :)
*Features*?! In an rc?! No wonder there's no convergence.
If I were installing this for just me, I'd have no proble
Several attempts to support both Mac and PCs keep failing.
In my latest attempt I used the following settings:
#courier-imap compatibility/Thunderbird
namespace private {
separator = .
prefix = INBOX.
inbox = yes
}
For MAC OS Mail.app
namespace private {
separator = /
prefix = INBOX/
33 matches
Mail list logo
