Op 22-11-2010 1:47, Glen Lee Edwards schreef:
I'm trying to configure Dovecot 2.0.7. In the Dovecot Wiki for Maildirs
it says that Maildirs are almost always located in ~/Maildir. I'm a
Linux end user, not a programmer, so I may be wrong in this; but isn't
the notation ~/ used for system users
Hi all.
I have a troube with GSSAPI (Dovecot 2.0.7) auth:
auth: Debug: client in: AUTH1 GSSAPI service=imap
lip=192.168.1.56rip=192.168.1.2 lport=143 $
auth: Debug: gssapi(?,192.168.1.2): Obtaining credentials for imap@
auth: Info: gssapi(?,192.168.1.2): While
Hey dovecot-users,
we are running dovecot 1.2.15 and are seeing some odd errors in our
logfiles:
--- dovecot.log ---
2010-11-22 12:34:56 imapserver local2.warning dovecot dovecot:
IMAP(usern...@domain.tld): Timeout leak: 0x4bd230
--- /dovecot.log ---
Those errors only appear if connections are
Hi Timo
Im have a situation here with the syntax for doveadm in a unix socket.
My string have it:
std::string ask = d\texpunge\tu\ta...@exemplo.com.br
\tmailbox\t\\*\tsavedbefore\t1s\n;
My Order todo is.
Create socket
Connect
Write this strinng
Read the return
Close socket.
finish my
On 11/22/2010 12:48 AM, Egbert Jan van den Bussche wrote:
Op 22-11-2010 1:47, Glen Lee Edwards schreef:
I'm trying to configure Dovecot 2.0.7. In the Dovecot Wiki for Maildirs
it says that Maildirs are almost always located in ~/Maildir. I'm a
Linux end user, not a programmer, so I may be wrong
On Sun, 2010-11-21 at 12:11 +0100, Patrick Westenberg wrote:
Miha Vrhovnik schrieb:
Patrick Westenbergp...@wk-serv.de wrote on 20.11.2010 23:46:14:
You can give additional space to e.g. Trash mailbox:
quota_rule2 = Trash:storage=100M
Patrick you sure, that doesn't mean that the trash
On 2010-11-22 12:16 AM, Joy wrote:
I know that i can change the default namespace configuation of dovecot
to work with courier-imap namespace but not willing to do that so
suggest me something which can help me doing the same.
Just setup both - the ones already configured to use INBOX. will
On Mon, 2010-11-22 at 13:38 -0200, Alex Baule wrote:
Im have a situation here with the syntax for doveadm in a unix socket.
My string have it:
std::string ask = d\texpunge\tu\ta...@exemplo.com.br
\tmailbox\t\\*\tsavedbefore\t1s\n;
Looks like there was also a bug, fixed:
It wasn't really a bug, more like a feature I thought would have been a
good idea, but wasn't really. Instead of using 100M, you could use e.g.
10% (10% of 0 is 0 = unlimited). Or apply this patch:
http://hg.dovecot.org/dovecot-2.0/rev/3a93121f652a
On Sun, 2010-11-21 at 23:51 -0800, Tim Traver
On Sun, 2010-11-21 at 20:23 +0100, Ralf Hildebrandt wrote:
# ps auxwww|egrep -i imap-login
dovenull 11879 1.4 0.9 83484 77656 ?SNov20 19:12
dovecot/imap-login [822 connections (822 TLS)]
What exactly is TLS in this context?
All connections from imap - imap-login?
All
On Mon, 2010-11-22 at 13:45 +0100, Christian Rohmann wrote:
we are running dovecot 1.2.15 and are seeing some odd errors in our
logfiles:
--- dovecot.log ---
2010-11-22 12:34:56 imapserver local2.warning dovecot dovecot:
IMAP(usern...@domain.tld): Timeout leak: 0x4bd230
It's not really
On Mon, 2010-11-22 at 15:33 +0300, asd dsa wrote:
auth: Debug: gssapi(?,192.168.1.2): Obtaining credentials for imap@
auth: Info: gssapi(?,192.168.1.2): While acquiring service
credentials: An invalid name was supplied
Maybe you need to set auth_gssapi_hostname?
On Sat, 2010-11-20 at 17:02 +1100, Lox wrote:
dovecot: deliver(virtuser_537): file_dotlock_create(/var/mail/virtuser_537)
failed: Permission denied (euid=537(virtuser_537) egid=518(neaevents)
missing +w perm: /var/mail) (set mail_privileged_group=mail)
See
On Fri, 2010-11-19 at 11:45 +0200, Axel Thimm wrote:
evolution has a bug when it comes to closing and IDLE' connection:
https://bugzilla.gnome.org/show_bug.cgi?id=628515
evolution does not send a DONE command, and dovecot properly answers
with an error. evolution ignores this and seems to
Thanks Timo! That patch did the trick!
Its great that you are so quick with changes that affect your users.
Tim
On 11/22/2010 10:36 AM, Timo Sirainen wrote:
It wasn't really a bug, more like a feature I thought would have been a
good idea, but wasn't really. Instead of using 100M, you could
Hello, I am new to this list, so feel free to correct me if I do
something wrong. I don't have a problem, just a question.
The RFC which covers IMAP ACLs [1] states that one of the standard
rights is:
l - lookup (mailbox is visible to LIST/LSUB commands, SUBSCRIBE
mailbox)
If I have
On Mon, 2010-11-22 at 12:22 -0700, Willie Gillespie wrote:
Hello, I am new to this list, so feel free to correct me if I do
something wrong. I don't have a problem, just a question.
The RFC which covers IMAP ACLs [1] states that one of the standard
rights is:
l - lookup (mailbox is
Timo Sirainen wrote:
On Mon, 2010-11-22 at 12:22 -0700, Willie Gillespie wrote:
Two things I noticed though:
SUBSCRIBE-ing to the mailbox is still successful
Hmm. I kind of disagree with the RFC there.. If you have 'r' rights to
the mailbox, you can select it. You know that it exists then.
Hello -
is it syntacticly possible to define different imap_capability settings per
each inet-listener?
I might have to provide a service through a caching proxy sitting in front of
dovecot, which might involve restrictions re: the announced imap capabilities.
Any hint is highly appreciated!
On 22.11.2010, at 20.33, Clemens Schrimpe wrote:
is it syntacticly possible to define different imap_capability settings per
each inet-listener?
local 10.0.0.1 {
imap_capability = a
}
local 10.0.0.2 {
imap_capability = b
}
On 22.11.2010, at 21.10, Christian Schmidt wrote:
are there any (dis)advantages in connecting dovecot and an MTA (in our
case: exim) using LMTP over using other methods (e.g. the exim
transports definitions that can be found in the wiki)?
LMTP should have better performance, since less
is it syntacticly possible to define different imap_capability settings
per each inet-listener?
local 10.0.0.1 {
imap_capability = a
}
local 10.0.0.2 {
imap_capability = b
}
Understood. How would that work for different /ports/ (i.e., 143 vs. 10143)?
Thanks again for the quick
You can't force clients to do anything, but you can force users of course. If
you just configure Dovecot to only have prefix= namespace, users who had
their clients previously configured with namespace=INBOX. will have to clear
the namespace so that they'll see their folders.
I didn't
Running doveadm purge with both -D and -v parms, and both -A and -u
options, I don't see much in the way of output.
doveadm -v purge -u username just returns with no output
doveadm -v purge -A returns no output for most users - for my own
mailbox it yields 20 / 21
-D returns the same, along
24 matches
Mail list logo
