On Wed, 2007-05-16 at 10:09 -0400, Bruce Bodger wrote:
> "If you're using mbox, giving a path to the INBOX file (eg. /var/mail/
> %u) isn't enough. You'll also need to tell Dovecot where the other
> mailboxes are and where Dovecot can place its index files. This is
> called the "root mail dire
Francisco Reyes spake the following on 5/20/2007 5:21 PM:
> 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_u
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:
# dovecot
Error: POP3 enabled but pop3_uidl_format not set
And don't let Dovecot come up?
On Tue, 2007-05-22 at 02:10 +0300, Timo Sirainen wrote:
> On Sun, 2007-05-20 at 20:21 -0400, Francisco Reyes wrote:
> > 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 f
On Sun, 2007-05-20 at 20:21 -0400, Francisco Reyes wrote:
> 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 pop
On Sun, 2007-05-20 at 20:15 -0400, Francisco Reyes wrote:
> I think "mail.info" may be a better choice, although this may be somewhat OS
> dependant. Many people may not even know where their syslog configuration
> file is or even how to configure it. Because of this whatever is the most
> commo
On Sun, 2007-05-20 at 20:35 -0400, Francisco Reyes wrote:
> 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.
Is there a
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:
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:
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
> No amount of effort can help someone who is unwilling to learn the bare
> minimum about a new program they want to use - and if they aren't even
> aware that dovecot has a config file (as does every other server app
> I've ever used), or what it is named or where it is - well, I don't
> think I
On May 16, 2007, at 9:29 AM, Charles Marcus wrote:
I see what you're getting at, but personally i really like having
plenty of documentation in the config files. That way when you're
editing the config file, you can know exactly what you're doing
and have good descriptions right in front o
On Wed, 2007-05-16 at 09:29 -0400, Charles Marcus wrote:
> > I see what you're getting at, but personally i really like having plenty
> > of documentation in the config files. That way when you're editing the
> > config file, you can know exactly what you're doing and have good
> > descriptions
I see what you're getting at, but personally i really like having plenty
of documentation in the config files. That way when you're editing the
config file, you can know exactly what you're doing and have good
descriptions right in front of you
Of course this is no substitute for other doc
On 5/16/2007 Timo Sirainen ([EMAIL PROTECTED]) wrote:
Anyway, with all of these 3 messages people have still copy&pasted
logs and asked "How do I fix this?" I just don't know how to make it
any more clearer.
I don't think you can... I really respect your desire to make things as
easy/simple f
I'm trying to get up to speed enough so that I am confident enough to
answer more questions... I think that would help more than anything
(people helping him out here on the list)...
That, and, of course, adding more well written, targeted articles to the
wiki...
--
Best regards,
Charles
You could have a number of sanity checks at startup where dovecot
checks out the environment verifying that directories exist and
perhaps do some write testing to make sure areas that need to be
writable actually are.
And even if it has write access to areas it shouldn't...
I like the idea of
Udo Rader wrote:
I've upgraded our and come clients' dovecot installations multiple times, and
to be honest I did not like the extensive documentation provided in the default
configuration files. Saying 'I did not like it' does not mean that the information
was useless, on the contrary, the amo
On Wed, 2007-05-16 at 02:15 +0200, Udo Rader wrote:
> Getting people to actually read _and_ understand what a log message
> means is very difficult on a very psychological level :-)
A good example would be this error that I've changed 2 times already:
"Set pop3_uidl_format setting in config file"
Am Dienstag, den 15.05.2007, 19:40 +0300 schrieb Timo Sirainen:
> I think the most common Dovecot newbie problems are:
>
> - Not looking at the (correct) logs for errors
> - Authentication problems
> - Mail location problems
> - Mail permission problems
>
> Below are some of my ideas how I co
On 5/16/2007 Joseba Torre ([EMAIL PROTECTED]) wrote:
For me, the easier solution would be an entry in the wiki with well
documented common configs:
- system users (using pam/passwd)
- ldap (with a common conf)
- mysql
- postgresql
I agree completely... also, explanations for what is required
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 15 May 2007, Timo Sirainen wrote:
* Logging
Logging to eg. /var/log/dovecot.log by default would be helpful here,
Personally, I found logging to a separate file helpful during setting up
Dovecot, because you can focus on Dovecot that way
Hi,
there's no easy way to get rid of newbie problems: right now dovecot is quite
a complex software, so configuration is complex. Even more, all the
userdb/passdb thing is really powerfull, but also a bit diferent of anything
I was used to, so it's normal that people is a bit confused in the b
Timo,
In general, the better the docs are and the better the error messages
are the less support they will need. If the log message said "Failure
XXX, check YYY to see if it is set" giving the user as much help as
possible. You could have a number of sanity checks at startup where
dovecot che
I think the most common Dovecot newbie problems are:
- Not looking at the (correct) logs for errors
- Authentication problems
- Mail location problems
- Mail permission problems
Below are some of my ideas how I could stop people from asking these
questions with future Dovecot (v1.1+) releases
29 matches
Mail list logo
