I don't know how this happened. I'm not sure if there is a coredump
somewhere because
I don't know what user, and I have nothing for 'root' or 'dovecot'. Any
advice, or should
I make all my coredumps go to a central writable directory so I have
better chance of
catching it if it happens again?
On Mar 8, 2008, at 8:04 PM, Timo Sirainen wrote:
On Mar 9, 2008, at 3:02 AM, Timo Sirainen wrote:
On Mar 9, 2008, at 2:58 AM, Bruce Bodger wrote:
Mar 8 14:02:14 G518X2 launchd: org.dovecot: exited with exit
code: 89
89 is a generic exit code meaning that Dovecot should have logged
som
On Sun, Mar 9, 2008 at 1:12 AM, Timo Sirainen <[EMAIL PROTECTED]> wrote:
>
> It's copying over itself, so it shouldn't break anything. But I fixed
> the error anyway: http://hg.dovecot.org/dovecot-1.1/rev/8e014fd46e84
Thanks Timo. With this patch valgrind gives 0 errors most of the time.
Forgiv
On Mar 9, 2008, at 3:02 AM, Timo Sirainen wrote:
On Mar 9, 2008, at 2:58 AM, Bruce Bodger wrote:
Mar 8 14:02:14 G518X2 launchd: org.dovecot: exited with exit code:
89
89 is a generic exit code meaning that Dovecot should have logged
something before exiting.
If you can't find anything
On Mar 9, 2008, at 2:58 AM, Bruce Bodger wrote:
Mar 8 14:02:14 G518X2 launchd: org.dovecot: exited with exit code: 89
89 is a generic exit code meaning that Dovecot should have logged
something before exiting.
If you can't find anything from existing logs, try setting log_path = /
tmp/do
On Mar 8, 2008, at 7:22 PM, Timo Sirainen wrote:
On Sat, 2008-03-08 at 14:09 -0500, Bruce Bodger wrote:
When I set...
mail_privileged_group = mail
...dovecot refuses to start. We are NOT using mbox here, only
Maildir.
With what error message (should be something in logs)? You mean
run
On Sat, 2008-03-08 at 14:09 -0500, Bruce Bodger wrote:
> When I set...
>
> mail_privileged_group = mail
>
> ...dovecot refuses to start. We are NOT using mbox here, only Maildir.
With what error message (should be something in logs)? You mean running
"dovecot" doesn't start Dovecot processes, o
On Sat, 2008-03-08 at 17:26 +0100, Diego Liziero wrote:
> Valgrind is stating that "Source and destination overlap in memcpy".
> I'm wondering if this code is just coping the same memory over itself,
> or if it is doing something useful.
It's copying over itself, so it shouldn't break anything. B
Hi
At line 1118 of src//lib-index/mail-index-map.c, inside the function
mail_index_map_move_to_memory, there is:
mail_index_map_copy_header(map, map);
Valgrind is stating that "Source and destination overlap in memcpy".
I'm wondering if this code is just coping the same memory over itself,
or if
Andrew Roberts wrote:
After upgrading to 1.1_rc2, however, deliver creates a maildir named "%Lu"
and delivers all mail for all users to it. Everything else works just
fine as before: users can log in, postfix can auth smtp via dovecot sasl,
etc.
I think you need this patch,
http://hg.do
Can dovecot-1.1 deliver work with static userdb? I'm currently running
dovecot-1.0.12 and postfix-2.4.6, with virtual users' maildirs all owned
by vmail and mail_location = maildir:/var/mail/%Lu. The following
definition of the dovecot transport in postfix/master.conf works fine with
dovecot-
On Mar 7, 2008, at 11:10 PM, Timo Sirainen wrote:
http://dovecot.org/releases/1.1/rc/dovecot-1.1.rc2.tar.gz
http://dovecot.org/releases/1.1/rc/dovecot-1.1.rc2.tar.gz.sig
Changes since rc1:
* mail_extra_groups setting was commonly used insecurely. This
setting
is now deprecated.
Hello,
I would like to know if it could be appears problem using POP and IMAP
in a mailbox?
Is it adviced to use one of the two protocols?
My users use IMAP to see their emails (in the webmail) and POP3 to
download their emails (in outlook/thunderbird).
Is it best to use the same protocol?
On 3/8/2008, Michel Vega Fuenzalida ([EMAIL PROTECTED]) wrote:
I use dovecot-1.0-1.2.rc15.el5.x86_64rpm for Centos 5.1
Upgrade... very old...
atrpms has current stable rpms for Centos 5...
--
Best regards,
Charles
Good list
I am not very good with English.
I use dovecot-1.0-1.2.rc15.el5.x86_64rpm for Centos 5.1, Maildir like
mailbox and I have
it configured as it continues:
base_dir = /var/run/dovecot/
protocols = imaps pop3s imap
mail_location = maildir:~/Maildir
protocol imap {
mail_plugins = quo
On Mar 7, 2008, at 11:33 PM, Jeff Grossman wrote:
Here is my dovecot -n (without the squat entries):
# 1.1.rc2: /usr/local/etc/dovecot.conf
base_dir: /var/run/dovecot/
Jeff,
I've noticed that you've been having a few issues that might appear
to be OS X related. We've been running Dovecot
Hi,
We're running a Debian server with system users where the mail is by
default delivered by postfix and procmail, before being served by
Dovecot (mail_location = mbox:~/Mail:INBOX=/var/mail/%u) or read by
local MUAs, depending on users' preferences.
For people using mostly remote MUAs, i
Hi
Im trying something new with my test dovecot.
I set my mail_location to to a new location
mail_location = maildir:/var/maildir/%u/Maildir
But with this new setup i too am authenticating against Mysql. This worked
fine till i decided to move the mail.
So now i have moved the mail, deleted th
Timo Sirainen wrote:
Mar 8 13:02:57 vs02 deliver((null)): User request from dovecot-auth
timed out
Oh, that's a new bug. This should fix it:
http://hg.dovecot.org/dovecot-1.1/rev/631fd6f25e41
Works, thanks a lot.
Regards,
Bernhard
On Sat, 2008-03-08 at 13:05 +0100, Bernhard Schmidt wrote:
> Mar 8 13:02:57 vs02 deliver((null)): User request from dovecot-auth
> timed out
Oh, that's a new bug. This should fix it:
http://hg.dovecot.org/dovecot-1.1/rev/631fd6f25e41
signature.asc
Description: This is a digitally signed message
Timo Sirainen <[EMAIL PROTECTED]> wrote:
>> I'm having a really really strange problem. After upgrading from
>> 1.1.beta13 to 1.1.rc2 (happened with rc1 as well IIRC) I can't connect
>> to the services using IPv4 anymore. dovecot happily binds to the IPv6
>> wildcard socket which should accept IPv
On Mar 8, 2008, at 1:51 PM, Bernhard Schmidt wrote:
I'm having a really really strange problem. After upgrading from
1.1.beta13 to 1.1.rc2 (happened with rc1 as well IIRC) I can't connect
to the services using IPv4 anymore. dovecot happily binds to the IPv6
wildcard socket which should accept IP
Hi,
I'm having a really really strange problem. After upgrading from
1.1.beta13 to 1.1.rc2 (happened with rc1 as well IIRC) I can't connect
to the services using IPv4 anymore. dovecot happily binds to the IPv6
wildcard socket which should accept IPv4 connections as well.
[EMAIL PROTECTED]:~# nets
Hello Dovecot users,
For those of you who like to live on the edge, there is now a
Debian-testing repository available with hourly updates from recent
Dovecot-1.1 changes in the Mercurial repositories. It automatically
releases a new set of packages if it notices any changes in any of the
rep
Timo Sirainen wrote:
http://dovecot.org/releases/1.1/rc/dovecot-1.1.rc2.tar.gz
http://dovecot.org/releases/1.1/rc/dovecot-1.1.rc2.tar.gz.sig
I refreshed the managesieve patch for the new dovecot-1.1.rc2 release:
http://www.rename-it.nl/dovecot/1.1/dovecot-1.1.rc2-managesieve-0.10.1.diff.gz
ht
Thanks again Timo.
Does work.
Typo my side.
Regards
Brent
On Sat, Mar 8, 2008 at 12:07 PM, Brent Clark <[EMAIL PROTECTED]>
wrote:
> Thanks Timo
>
> Ill try again.
>
> Regards
> Brent Clark
>
>
> On Sat, Mar 8, 2008 at 11:52 AM, Timo Sirainen <[EMAIL PROTECTED]> wrote:
>
> > On Sat, 2008-03-08
Thanks Timo
Ill try again.
Regards
Brent Clark
On Sat, Mar 8, 2008 at 11:52 AM, Timo Sirainen <[EMAIL PROTECTED]> wrote:
> On Sat, 2008-03-08 at 11:27 +0200, Brent Clark wrote:
>
> > use Digest::SHA1;
> > use MIME::Base64;
> > $ctx = Digest::SHA1->new;
> > $ctx->add($passwd_string);
> > $ctx->a
On Sat, 2008-03-08 at 11:27 +0200, Brent Clark wrote:
> use Digest::SHA1;
> use MIME::Base64;
> $ctx = Digest::SHA1->new;
> $ctx->add($passwd_string);
> $ctx->add('salt');
> my $salted = '{SSHA}' . encode_base64($ctx->digest . 'salt' ,'');
This looks correct, and it also worked when I tried it.
Hi
I would like to simulate dovecot's dovecotpw with a perl script
I tried / used
use Crypt::SaltedHash;
my $csh = Crypt::SaltedHash->new(algorithm => 'SHA-1');
$csh->add($passwd_string);
my $salted = $csh->generate;
also
use Digest::SHA1;
use MIME::Base64;
$ctx = Digest::SHA1->new;
$ctx->add(
29 matches
Mail list logo
