Hi to all,
I'm a sys admin in a college, and we're using Dovecot as IMAP/POP3
server and delivery; we're also patch dovecot to add managesieve
capability. I've a question:
I've read on dovecot's wiki, that is possible improve the performance on
maildir files by adding ,S=size,W=vsize fields on
On Tue, 2008-05-13 at 08:36 +0200, Marco Giunta wrote:
Hi to all,
I'm a sys admin in a college, and we're using Dovecot as IMAP/POP3
server and delivery; we're also patch dovecot to add managesieve
capability. I've a question:
I've read on dovecot's wiki, that is possible improve the
Greetings,
I am using dovecot as our POP3 and IMAP server and Squirrelmail for the
Webmail. Some of our users get the error message below when trying to access
the mailbox using Webmail:
ERROR: Could not complete request.
Query: SELECT INBOX
Reason Given: Internal error occurred.
Hello,
I would like to suggest a change in handling of 'Time moved backwards'
problem.
Right now dovecot just dies. So, the scenario:
1) Colocation server is shut down for some reason. The internal time drifts.
2) Server is started again.
3) Dovecot starts successfully.
4) In about a minute,
On Tue, 2008-05-13 at 11:13 +0400, Eugene wrote:
I suggest that Dovecot simply terminate the current connections (causing the
client to reconnect) or -- if the time change is really that much of a
problem -- to restart itself automatically.
I guess terminating all current connections and
On Tue, 2008-05-13 at 09:56 +0300, Sadiq Walji wrote:
To resolve this issue, I need to open the /var/spool/mail/username
(mailbox of the user) and delete an empty line that is inserted at the top
of the mailbox file. I am running dovecot-0.99.11-8.EL4 on CentOS release
4.6 (Final).
Kindly
On 09:23:57 2008-05-13 Timo Sirainen [EMAIL PROTECTED] wrote:
On Tue, 2008-05-13 at 11:13 +0400, Eugene wrote:
I suggest that Dovecot simply terminate the current connections
(causing the client to reconnect) or -- if the time change is really
that much of a problem -- to restart itself
Hi Timo,
From: Timo Sirainen [EMAIL PROTECTED]
I suggest that Dovecot simply terminate the current connections (causing
the
client to reconnect) or -- if the time change is really that much of a
problem -- to restart itself automatically.
I guess terminating all current connections and
On Tue, May 13, 2008 at 11:13:39AM +0400, Eugene wrote:
Hello,
I would like to suggest a change in handling of 'Time moved backwards'
problem.
Right now dovecot just dies. So, the scenario:
1) Colocation server is shut down for some reason. The internal time drifts.
2) Server is started
Hello,
From: Quentin Garnier [EMAIL PROTECTED]
4) In about a minute, NTP daemon feels confident about adjusting the
system
time.
The admin should run ntpdate before launching ntpd and dovecot. ntpd
will _never_ move time backwards under normal drifting conditions (it
has other ways of coping
I have an issue with shares mailboxes
Example : I have 2 users A and B.
A must have an access to all mail of B
So i create a public namespace
namespace public {
separator = /
prefix = Public/
location = maildir:/home/users/B/Maildir
}
It's OK for the subfolders, but not for the
Thank you Timo, I'll use quota plugin on delivery.
Timo Sirainen wrote:
On Tue, 2008-05-13 at 08:36 +0200, Marco Giunta wrote:
Hi to all,
I'm a sys admin in a college, and we're using Dovecot as IMAP/POP3
server and delivery; we're also patch dovecot to add managesieve
capability. I've a
On Tue, May 13, 2008 at 11:39:54AM +0400, Eugene wrote:
Hello,
From: Quentin Garnier [EMAIL PROTECTED]
4) In about a minute, NTP daemon feels confident about adjusting the
system
time.
The admin should run ntpdate before launching ntpd and dovecot. ntpd
will _never_ move time backwards
On Tue, 2008-05-13 at 12:51 +0400, Anton Yuzhaninov wrote:
Timo Sirainen пишет:
On Tue, 2008-05-13 at 11:13 +0400, Eugene wrote:
I suggest that Dovecot simply terminate the current connections (causing
the
client to reconnect) or -- if the time change is really that much of a
On 10:48:28 2008-05-13 Eugene [EMAIL PROTECTED] wrote:
Hello,
From: Quentin Garnier [EMAIL PROTECTED]
I'm not the one having trouble reading, here. The proper way to
start a system is to run ntp*date* (as early as possible) and then
ntpd.
That's what you say, and it is far from being
Timo Sirainen пишет:
On Tue, 2008-05-13 at 11:13 +0400, Eugene wrote:
I suggest that Dovecot simply terminate the current connections (causing the
client to reconnect) or -- if the time change is really that much of a
problem -- to restart itself automatically.
I guess terminating all
Hello,
From: Quentin Garnier [EMAIL PROTECTED]
I'm not the one having trouble reading, here. The proper way to start a
system is to run ntp*date* (as early as possible) and then ntpd.
That's what you say, and it is far from being officially accepted.
NTP project clearly deprecates ntpdate
Thanks buddy, will get back if the problem persists.
-Original Message-
From: Timo Sirainen [mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 13, 2008 10:25 AM
To: Sadiq Walji
Cc: dovecot@dovecot.org
Subject: Re: [Dovecot] Mailbox problem
On Tue, 2008-05-13 at 09:56 +0300, Sadiq Walji
Hi,
I'm trying to get dovecot's LDA 'deliver' to deliver mails that come in through
a postfix daemon on the same box. I'm talking
about dovecot version 1.0.rc15 (on CentOS 5 as Linux-VServer guest on a CentOS
5 host).
Configuration
-
# /etc/dovecot.conf
ssl_cert_file:
On 5/13/2008, Patrick Nagel ([EMAIL PROTECTED]) wrote:
I'm trying to get dovecot's LDA 'deliver' to deliver mails that come
in through a postfix daemon on the same box. I'm talking about
dovecot version 1.0.rc15 (on CentOS 5 as Linux-VServer guest on a
CentOS 5 host)
Upgrade...
It may or may
Hi Charles,
On Tuesday 13 May 2008, Charles Marcus wrote:
On 5/13/2008, Patrick Nagel ([EMAIL PROTECTED]) wrote:
I'm trying to get dovecot's LDA 'deliver' to deliver mails that come
in through a postfix daemon on the same box. I'm talking about
dovecot version 1.0.rc15 (on CentOS 5 as
On 5/13/2008, Patrick Nagel ([EMAIL PROTECTED]) wrote:
Thanks for that hint. I just upgraded to 1.0.13. I'll watch it carefully and
report back here in a few days.
Lots of nifty stuff (much improved performance for one thing) in the
impending 1.1 (currently at rc5)...
If this is a new
At 11:31 AM +0400 5/13/08, Eugene wrote:
Hi Timo,
From: Timo Sirainen [EMAIL PROTECTED]
I suggest that Dovecot simply terminate the current connections (causing the
client to reconnect) or -- if the time change is really that much of a
problem -- to restart itself automatically.
I guess
On 15:48:42 2008-05-13 Bill Cole [EMAIL PROTECTED]
wrote:
At 11:31 AM +0400 5/13/08, Eugene wrote:
Hi Timo,
From: Timo Sirainen [EMAIL PROTECTED]
I suggest that Dovecot simply terminate the current connections
(causing the client to reconnect) or -- if the time change is really
that much
At 11:13 AM +0400 5/13/08, Eugene wrote:
Hello,
I would like to suggest a change in handling of 'Time moved
backwards' problem.
Right now dovecot just dies. So, the scenario:
1) Colocation server is shut down for some reason. The internal time drifts.
2) Server is started again.
3) Dovecot
Nevertheless, it would be very nice if you could fix it. It's a
fairly big availability problem (for us, at least).
Then you have a badly broken system. There is no explanation for time
going backwards on a server on a frequent unplanned basis that is not
reducible to administrative
At 3:58 PM +0200 5/13/08, AndraÏ 'ruskie' Levstik wrote:
On 15:48:42 2008-05-13 Bill Cole [EMAIL PROTECTED]
wrote:
At 11:31 AM +0400 5/13/08, Eugene wrote:
Hi Timo,
From: Timo Sirainen [EMAIL PROTECTED]
I suggest that Dovecot simply terminate the current connections
(causing the client
Martin Preen wrote:
Hello,
I just found this message in our dovecot logfiles:
Disconnected: BUG: Unknown internal error
Should I worry about this ?
There are no complaints yet (although it is not limited to one user).
It seems to occur with different clients (Apple/MacOS mail,
I tried to migrate from a server courier to dovecot with imapsync but i get
this errore:
Couldn't append msg #15 (Subject:[Registrazione]) to folder INBOX: Error
sending command '16 APPEND INBOX (\Answered \Seen) {3478}
': 16 BAD Invalid internal date.
thk you in advance
Workino
At 12:48 PM +0400 5/13/08, Eugene wrote:
Hello,
From: Quentin Garnier [EMAIL PROTECTED]
I'm not the one having trouble reading, here. The proper way to start a
system is to run ntp*date* (as early as possible) and then ntpd.
That's what you say, and it is far from being officially accepted.
Dovecot version: 1.0.13
Linux: Debian Testing (kernel 2.6.22)
Fs: local
# 1.0.13: /etc/dovecot/dovecot.conf
log_timestamp: %Y-%m-%d %H:%M:%S
protocols: imap pop3
disable_plaintext_auth: no
login_dir: /var/run/dovecot/login
login_executable(default): /usr/lib/dovecot/imap-login
On May 13, 2008, at 6:17 PM, Gabriele Fergola wrote:
I tried to migrate from a server courier to dovecot with imapsync
but i get
this errore:
Couldn't append msg #15 (Subject:[Registrazione]) to folder INBOX:
Error
sending command '16 APPEND INBOX (\Answered \Seen) {3478}
': 16 BAD
Charles Marcus wrote:
On 5/13/2008, Eugene ([EMAIL PROTECTED]) wrote:
I guess terminating all current connections and restarting all processes
would be pretty safe, but it's not really a high priority change for
me..
Nevertheless, it would be very nice if you could fix it. It's
on 5-13-2008 12:13 PM Adam McDougall spake the following:
Charles Marcus wrote:
On 5/13/2008, Eugene ([EMAIL PROTECTED]) wrote:
I guess terminating all current connections and restarting all
processes
would be pretty safe, but it's not really a high priority change for
me..
On 5/13/08 3:33 PM, Scott Silva wrote:
This would be a good case for running ntpdate on startup at least on
the ntp server. Just point it to a reliable outside server. AFAIR
RedHat and clones do this in the init script for ntpd.
...and how much more TIME shall we spend rechewing this
Unfortunately, I received no replies on this problem so I guess that
there are very few people using Dovecot and Exim with virtual users on
Solaris 10 :=( ...
... I do now have a working mail system of sorts but with real unix
users so the virtual mail domains issues still remains for me
At 9:12 AM +1000 5/14/08, Neil Muller wrote:
Unfortunately, I received no replies on this problem so I guess that
there are very few people using Dovecot and Exim with virtual users
on Solaris 10 :=(
Or the list just doesn't always respond in a swift manner...
You problem is fully expressed
Hi,
On Tuesday 13 May 2008, Charles Marcus wrote:
On 5/13/2008, Patrick Nagel ([EMAIL PROTECTED]) wrote:
Thanks for that hint. I just upgraded to 1.0.13. I'll watch it carefully
and report back here in a few days.
Lots of nifty stuff (much improved performance for one thing) in the
38 matches
Mail list logo
