- Original Message -
> From: Reindl Harald
> To: dovecot@dovecot.org
> Cc:
> Sent: Tuesday, 5 March 2013, 23:50
> Subject: Re: [Dovecot] Upgrading 1.2 to 2.x
>
>
>
> Am 05.03.2013 22:24, schrieb Benny Pedersen:
>> Simon Brereton skrev den 2013-03-05 15:30:
>>
honestly, especi
Simon,
* Simon Brereton :
> I'm about to upgrade to 2.1.7 in my test environment, but "doveconf
> -n -c dovecot.1.conf > dovecot.2.conf" is producing a blank file, so I
> am unsure how to proceed. I know a lot has changed between them, so I
> don't really want to have to start from scratch unles
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 5 Mar 2013, pvsuja wrote:
I have installed Dovecot 2.2 Unstable in my Ubuntu 12.04 with ssl enabled
But when I am starting dovecot, I am getting the following error
*doveconf: Fatal: Error in configuration file
/usr/local/etc/dovecot/conf.d
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 6 Mar 2013, Daniel Parthey wrote:
Noel Butler wrote:
On Tue, 2013-03-05 at 08:28 -0800, Professa Dementia wrote:
On 3/5/2013 7:34 AM, Simon Brereton wrote:
What's the recommended approach then? Pack it all into dovecot.conf
as it was be
Reindl Harald skrev den 2013-03-05 22:50:
Am 05.03.2013 22:24, schrieb Benny Pedersen:
Simon Brereton skrev den 2013-03-05 15:30:
honestly, especially because "a lot has changed between them"
I would start from scratch.
as same as saying if new iso file is out anyone need to delete there
ol
Dear sir,
I have to set up a mail gateway which will be explored to Internet and a
secure mail server in the Intranet.
I need a smart imap proxy in the mail gateway which will fetch the mail from
server and present to user through either a stand alone mail client or a web
mail client.
All authent
On Wed, 2013-03-06 at 00:06 +0100, Daniel Parthey wrote:
> > WTF? Everything in one file is much nicer and easier, and you don't
> > have to guess what option is in what file
>
> We're using a single file too, since this can be easily managed by
> a configuration management system and avoids un
On Tue, 2013-03-05 at 15:33 -0800, Professa Dementia wrote:
>
> I am basing most of this on my experience of RedHat vs. the SuSE
> configuration for Apache. The split files of SuSE were always easier to
httpd, which utilises identical directives is nothing like Dovecot with
split config fil
On 3/5/2013 3:06 PM, Daniel Parthey wrote:
We're using a single file too, since this can be easily managed by
a configuration management system and avoids unexpected changes.
Split files might get accidentally updated or added on package
updates and change the behaviour of your whole mail syste
Am 2013-03-05 23:27, schrieb Noel Butler:
On Tue, 2013-03-05 at 08:28 -0800, Professa Dementia wrote:
On 3/5/2013 7:34 AM, Simon Brereton wrote:
What's the recommended approach then? Pack it all into dovecot.conf
as it was before, or use the split config files under conf.d/ - is
this even a c
Noel Butler wrote:
> On Tue, 2013-03-05 at 08:28 -0800, Professa Dementia wrote:
> > On 3/5/2013 7:34 AM, Simon Brereton wrote:
> >
> > > What's the recommended approach then? Pack it all into dovecot.conf
> > > as it was before, or use the split config files under conf.d/ - is
> > > this even a
Hi,
I frequently get errors similar to this logged:
Mar 5 17:49:20 alphonse dovecot: imap(roger): Error: Corrupted squat
uidlist file /home/roger/Maildir/.Debian/dovecot.index.search.uids: wrong
indexid
I am running the Debian package version 1:2.1.7-7 on an up to date Debian
Testing system with
On Tue, 2013-03-05 at 08:28 -0800, Professa Dementia wrote:
> On 3/5/2013 7:34 AM, Simon Brereton wrote:
>
> > What's the recommended approach then? Pack it all into dovecot.conf
> > as it was before, or use the split config files under conf.d/ - is
> > this even a choice?
>
> Split configs are
On Tue, 2013-03-05 at 11:33 +0100, Simon Brereton wrote:
> Hi
>
> I'm about to upgrade to 2.1.7 in my test environment, but "doveconf
> -n -c dovecot.1.conf > dovecot.2.conf" is producing a blank file, so I
> am unsure how to proceed. I know a lot has changed between them, so I
> don't really w
Am 05.03.2013 22:24, schrieb Benny Pedersen:
> Simon Brereton skrev den 2013-03-05 15:30:
>
>>> honestly, especially because "a lot has changed between them"
>>> I would start from scratch.
>
> as same as saying if new iso file is out anyone need to delete there old
> servers ?
and you think
Simon Brereton skrev den 2013-03-05 15:30:
honestly, especially because "a lot has changed between them"
I would start from scratch.
as same as saying if new iso file is out anyone need to delete there
old servers ?
I'd prefer to have a semi-decent config to work from without having
to
res
On 3/5/2013 7:34 AM, Simon Brereton wrote:
What's the recommended approach then? Pack it all into dovecot.conf
as it was before, or use the split config files under conf.d/ - is
this even a choice?
Split configs are nicer and easier to work with and I am all for nicer
and easier.
Dem
On 5 March 2013 16:28, Professa Dementia wrote:
> On 3/5/2013 6:30 AM, Simon Brereton wrote:
>
>>
>> I'd prefer to have a semi-decent config to work from without having to
>> research 100 new variable names and values. The migration tool exists for
>> a reason.
>>
>
> I just went through the same
On 3/5/2013 6:30 AM, Simon Brereton wrote:
I'd prefer to have a semi-decent config to work from without having to
research 100 new variable names and values. The migration tool exists for
a reason.
I just went through the same thing - converting from 1.2.10 to 2.1.15.
Trust me, you are bet
On 5 Mar 2013 15:19, "Steffen Kaiser" wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
>
> On Tue, 5 Mar 2013, Simon Brereton wrote:
>
>> I'm about to upgrade to 2.1.7 in my test environment, but "doveconf
>> -n -c dovecot.1.conf > dovecot.2.conf" is producing a blank file, so I
>> am
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 5 Mar 2013, Simon Brereton wrote:
I'm about to upgrade to 2.1.7 in my test environment, but "doveconf
-n -c dovecot.1.conf > dovecot.2.conf" is producing a blank file, so I
am unsure how to proceed. I know a lot has changed between them, s
El 26/02/13 14:45, Dimos Alevizos escribió:
I've noticed that our directors point to different backends if the user
logins as "user" vs "user@domain" and as a result there are users ending
up in more than one server (several of them use just their username in
one client and the full user@domain
On Thu, Feb 28, 2013 at 02:59:52PM +0100, Pavel Dimow wrote:
>
> we have /var/spool/vmail/mydomain.com/u...@mydomain.com and I want a
> new server with version 2 to have
> hashed directory structure like /var/spool/vmail/mydomain.com/u/s/user
> I was wondering it f there is some better solution t
Hi
I'm about to upgrade to 2.1.7 in my test environment, but "doveconf
-n -c dovecot.1.conf > dovecot.2.conf" is producing a blank file, so I
am unsure how to proceed. I know a lot has changed between them, so I
don't really want to have to start from scratch unless I have to.
I have tried both
Hello.
I tested dovecot's work with expunge messages on Mdbox over strace (see
at tail of message). As I can see dovecot process opens old storage m.*
file, reads it content, opens new temporary file, writes in this one
content and rename this new one to m.(*+1).
How fast this algorithm works on
I'm trying to setup a samba4 with openchange which uses
postfix+dovecot+openldap on a ubuntu 12.04.2 system. I can send outgoing
emails but incoming emails fail. I looked up the logs and I get:
Mar 5 11:03:48 testerA dovecot: lda(sammy): Error: user sammy:
Initialization failed: mail_location not
26 matches
Mail list logo
