Hi
I understand the crash below is caused by filesystem quota. I just report
it because perhaps it could have a more graceful failure.
Apr 29 09:39:17 danceny dovecot: dsync-local(jdoe): Error: Mailbox Sent: Saving
failed: Not enough disk space
Apr 29 09:39:17 danceny syslogd[165]: last
Sorry,
I checked my dovecot version, and it has not been updated by Debian yet.
I will check if I can find a method to update without breaking dependancies.
André
On 28/04/13 17:42, Andre Rodier wrote:
Hello Everyone,
I have a small base of users (30), but a lot of emails.
I have an
Am 29.04.2013 11:08, schrieb Andre Rodier:
Sorry,
I checked my dovecot version, and it has not been updated by Debian yet.
I will check if I can find a method to update without breaking dependancies.
André
perhaps look at
Hi
I am trying replication over dsync/ssh, as explained there:
http://wiki2.dovecot.org/Replication
I added the options below to dovecot.conf. It works, but it
seems there is a new SSH connexion for each user, which is a bit
overkill performance-wise. Since I sync as root, I guess there
is a
Thanks Robert,
I was not aware of this distribution.
ATB,
André
On 29/04/13 10:21, Robert Schetterer wrote:
Am 29.04.2013 11:08, schrieb Andre Rodier:
Sorry,
I checked my dovecot version, and it has not been updated by Debian yet.
I will check if I can find a method to update without
I just upgraded one of our servers to dovecot v2.1.16 (ee), and am looking
into the stats feature. Am I interpreting the wiki correct in reading that
the doveadm stats dump command only returns statistics about IMAP
commands?
Is it possible to collect info about POP3 and LMTP commands also ?
Hi,
I know that a lot of work has been done regarding doveadm server, but I'm still
experiencing easily reproducible segfault crashes of doveadm-server with 2.1.16
when running the following command in a 4 node director/mailbox cluster:
/usr/bin/doveadm -c
this task into the dovecot-auth source code, maybe in the
passdb-ldap.c file. What do you recomend about this? Thanks.
__ Information from ESET Mail Security, version of virus signature
database 8278 (20130429) __
The message was checked by ESET Mail Security.
http://www.eset.com
Am 29.04.2013 16:50, schrieb Oscar A. Jara:
Hello, I am settiing up a dovecot (imap, pop, sieve, lda) + openldap
infrastructure. I need to store the timestamp of the last login of each
user in an attribute of its corresponding ldap object. I could not find
a way of doing this through
On Tuesday, April 23 at 09:06 PM, quoth Timo Sirainen:
On Tue, 2013-04-23 at 10:52 -0600, Kyle Wheeler wrote:
I got all excited about IMAP NOTIFY support and tried enabling
mailbox_list_index on my server. Unfortunately, I rather quickly ran
into trouble of the segfault variety. This prevented
Oscar A. Jara oaj...@frsf.utn.edu.ar wrote:
Hello, I am settiing up a dovecot (imap, pop, sieve, lda) + openldap
infrastructure. I need to store the timestamp of the last login of
each user in an attribute of its corresponding ldap object. I could
not find a way of doing this through
On Thursday, April 25 at 07:44 PM, quoth Robert Schetterer:
Am 25.04.2013 18:55, schrieb Kyle Wheeler:
As you can probably tell, I'm using the fts_lucene plugin, which used to
work just fine (with Dovecot 2.1.x). Is this expected behavior? Are
these errors truly ignorable? Why are these
Am 29.04.2013 17:03, schrieb Peer Heinlein:
Am 29.04.2013 16:50, schrieb Oscar A. Jara:
Hello, I am settiing up a dovecot (imap, pop, sieve, lda) + openldap
infrastructure. I need to store the timestamp of the last login of each
user in an attribute of its corresponding ldap object. I could
Am 29.04.2013 17:51, schrieb Kyle Wheeler:
On Thursday, April 25 at 07:44 PM, quoth Robert Schetterer:
Am 25.04.2013 18:55, schrieb Kyle Wheeler:
As you can probably tell, I'm using the fts_lucene plugin, which used to
work just fine (with Dovecot 2.1.x). Is this expected behavior? Are
these
Am 29.04.2013 18:01, schrieb Robert Schetterer:
doing touch method may slow down your i.e cluster filesystem, database
etc specially with high frequent logins, related how/what you need such
timestamps
you can get them from logs too, to get an idea
If a system's breaking down by touching
Am 29.04.2013 18:23, schrieb Peer Heinlein:
Am 29.04.2013 18:01, schrieb Robert Schetterer:
doing touch method may slow down your i.e cluster filesystem, database
etc specially with high frequent logins, related how/what you need such
timestamps
you can get them from logs too, to get an
ünchen, Amtsgericht München: HRB 199263 Vorstand:
Patrick Ben Koetter, Axel von der Ohe, Marc Schiffbauer
Aufsichtsratsvorsitzender: Florian Kirstein __ Information from
ESET Mail Security, version of virus signature database 8279 (20130429)
__ The message was checked by ESET Mail Sec
Im trying to convert my dovecot-lda setup to use LMTP for better
security. My setup is postfix + dovecot + mysql with virtual users.
Im setting up dovecot 2.2.1 w/postfix 2.10.0
Im still learning dovecot so Im not totally sure where Im going wrong.
Can someone point out why Im getting
Am 29.04.2013 19:14, schrieb oaj...@frsf.utn.edu.ar:
I guess I don't have such a high load so I will try Peer's
recomendation about using PostLoginScripting first and measure the
impact. I will try the log monitoring technique if the impact is
significant. Thank you very much.
for low/middle
Am 29.04.2013 19:26, schrieb Jeff Lacki:
my postfix/master.cf entry:
dovecot unix - n n - - pipe
flags=DRhu user=vmail:vmail argv=/opt/dovecot/libexec/dovecot/lmtp -f
${sender} -d ${recipient}
with short look
you mixed wrong with lda setup ?
which may
I'm pleased to see that dovecot-2.2 includes support for RFCs 4467 and 4469
(URLAUTH and CATENATE). I have begun testing these features (in dovecot-2.2.1)
and comparing their functionality against Apple's implementation. So far I
have discovered a few inconsistencies. I will report each of
Dovecot-2.2.1 does not appear to support URLs specified via non-synchronizing
literals (RFC 2088 LITERAL+), and also does not read and discard the literal+
input after reporting the error. This results in the literal+ input being
interpreted as IMAP commands, which could alter the user's mail
Dovecot-2.2.1 allows empty messages to be APPENDed when using CATENATE:
b1 append inbox catenate (text {0+}
)
b1 OK [APPENDUID 1366726248 12] Append completed.
Contrast this with regular APPEND:
b2 append inbox {0+}
b2 NO Can't save a zero byte message.
Note that zero-size literals are OK
Something ate an important leading space from my message.
b3 append inbox catenate (text {0+}
text {8+}
foobar
)
b3 OK [APPENDUID 1366726248 13] Append completed.
There was and should be a single space before the text {8+} above.
Robert Schetterer r...@sys4.de wrote:
Am 29.04.2013 19:26, schrieb Jeff Lacki:
my postfix/master.cf entry:
dovecot unix - n n - - pipe
flags=DRhu user=vmail:vmail argv=/opt/dovecot/libexec/dovecot/lmtp -f
${sender} -d ${recipient}
with short
Dovecot-2.2.1 does not appear to support URLs specified via non-synchronizing
literals
Or synchronizing literals either:
b2 append inbox catenate (url {8}
b2 BAD Error in IMAP command APPEND: Invalid arguments.
Although the consequences of this are less severe since clients should send no
On 29.4.2013, at 23.43, Mike Abbott michael.abb...@apple.com wrote:
Dovecot-2.2.1 does not appear to support URLs specified via
non-synchronizing literals
Or synchronizing literals either:
b2 append inbox catenate (url {8}
b2 BAD Error in IMAP command APPEND: Invalid arguments.
On 29.4.2013, at 21.40, Mike Abbott michael.abb...@apple.com wrote:
Dovecot-2.2.1 allows empty messages to be APPENDed when using CATENATE:
b1 append inbox catenate (text {0+}
)
b1 OK [APPENDUID 1366726248 12] Append completed.
Contrast this with regular APPEND:
b2 append inbox {0+}
Em 29/04/2013 14:54, Robert Schetterer escreveu:
Am 29.04.2013 19:14, schrieb oaj...@frsf.utn.edu.ar:
I guess I don't have such a high load so I will try Peer's
recomendation about using PostLoginScripting first and measure the
impact. I will try the log monitoring technique if the impact is
In dovecot-2.2.1 neither the SELECT nor the EXAMINE commands include an
untagged URLMECH reply. (Note, this is not the one mandated by the RESETKEY
command.)
AFAICT RFC 4467 does not require an URLMECH reply to SELECT or EXAMINE but
without it clients have no way of knowing about
j...@rahul.net (Jeff Lacki) wrote:
Thanks Robert, unfortunately I still get the same error after
making those modifications. Any other suggestions?
Thanks!
/mf/home/jeep/shell/.signature
Ok I changed the permissions on the directory:
/opt/imapdata/j/jeff/INBOX to 777:
total 20
Dovecot-2.2.1's imap processes crash reliably when they use an IMAP URL with an
invalid access specifier. A backtrace and some debug output follows. The
crash is likely caused by imap_urlauth_fetch_parsed() returning 0 without
having set *mpurl_r to NULL, and then imap_urlauth_fetch_local()
Hi Guys,
I am wondering about mail deduplication. I am looking into the possibility
of seperating out all of the message bodies with multiple parts inside mail
that is recived from `dovecot` and hashing them all.
The idea is that by hashing all of the parts inside the email, I will be
able to
Am 30.04.2013 00:40, schrieb Julio Cesar Covolato:
My aproach is just find the oldest message in the folder
mailbase/domain/user/Maildir/new/ for every user once a day
yes that works too, used this years ago, but i think its not working
with mdbox etc
Best Regards
MfG Robert Schetterer
--
Am 30.04.2013 02:48, schrieb Jeff Lacki:
j...@rahul.net (Jeff Lacki) wrote:
Thanks Robert, unfortunately I still get the same error after
making those modifications. Any other suggestions?
Thanks!
/mf/home/jeep/shell/.signature
Ok I changed the permissions on the directory:
35 matches
Mail list logo
