Hi.
In my setup exim delivers mails to dovecot using LMTP. In one LMTP session exim
can deliver up to 200 recipients (batch_max set to that value).
Now the problem is that sometimes 256MB is not enoug for dovecot lmtp to handle
incoming emails.
My questions:
- how big memory limit should be for
Hi,
In the documentation of FTS lucene, I need little more clarification
about this section:
--
--with-lucene --with-stemmer
The second switch is only required if you have compiled libstemmer
yourself or if it's included in the CLucene you are usin
No matter what the answer's gonna be the "solution" till then still might be
the z-push+exchange-approach? Or did I miss anything more sophisticated out
there?
Am 05.09.2014 um 15:22 schrieb Stefan Arentz :
>
>> On Sep 5, 2014, at 5:53 AM, Charles Marcus wrote:
>>
>> On 9/4/2014 9:35 PM, Stef
Hello,
Our Postfix setup uses multi-instance feature. I would like to enable
dovecot SASL mechanisms in postfix. Open two unix sockets is not a
problem for us:
service auth {
unix_listener /var/spool/postfix-instance1/private/auth {
mode = 0660
user = postfix
group = postfix
}
u
"... I will try to contact Apple and find out if they are willing to open
up the certificate generation. "
I'm willing to bet the answer will be no.
Apple != Open
On Sep 5, 2014 9:22 AM, "Stefan Arentz" wrote:
>
> > On Sep 5, 2014, at 5:53 AM, Charles Marcus
> wrote:
> >
> > On 9/4/2014 9:35 P
On 9/5/2014 9:22 AM, Stefan Arentz wrote:
When you enable Push Email on OS X Server, that certificate will be generated
for you and stored in your Keychain.
There is no other way to generate this certificate. This is why you need a
legal copy of OS X Server.
You don’t actually have to run OS
> On Sep 5, 2014, at 5:53 AM, Charles Marcus wrote:
>
> On 9/4/2014 9:35 PM, Stefan Arentz wrote:
>> Although this is at version 0.1, it is working pretty well for me and I am
>> looking for some additional testers that are interested.
>>
>> Please note that it is not possible to use thi
On Fri, 05 Sep 2014 13:43:49 +0300, Teemu Huovila wrote:
> Hello
>
> On 08/28/2014 04:57 PM, Alessandro Bono wrote:
>> I'm using Enterprise repository for centos 6 and works perfectly
>> but upgrading packages there is not changelog or other info
>> I don't have idea what's changed on every updat
<<< image/gif: EXCLUDED >>>
On 2014-09-05 13:44, Michael Grimm wrote:
IIRC dsync can be run independently from a running dovecot server.
I remembered correctly (http://wiki2.dovecot.org/Tools/Dsync):
| dsync can be run completely standalone. It doesn't require any
| Dovecot server processes to be running, except when us
On 2014-09-05 11:54, Jens Dueholm Christensen wrote:
Filesystems are prepared for the expected amount of inodes required,
and for the time beeing a change to mdbox is seen as an added
complexity.
With that amount of mails in mind, a migration to mdbox is a good idea,
IMHO.
One requirement
From: Reindl Harald on Friday, September 05, 2014 11:58 AM
>>> I was hoping of rsync'ing all Maildirs from the old machine to the new one
>>> (including indexes etc etc) and power up
>>> Dovecot 2.2.x and see what happens, but is that possible or is there
>>> another (and better) way short of i
Hello
On 08/28/2014 04:57 PM, Alessandro Bono wrote:
> I'm using Enterprise repository for centos 6 and works perfectly
> but upgrading packages there is not changelog or other info
> I don't have idea what's changed on every update
>
> Can you post somewhere changelog info or include in rpms?
A
Am 05.09.2014 um 11:54 schrieb Jens Dueholm Christensen:
> Since dsync is incompatible between 2.0<->2.1<->2.2 what is the best way to
> perform this migration?
>
> I was hoping of rsync'ing all Maildirs from the old machine to the new one
> (including indexes etc etc) and power up Dovecot 2.2
On 9/4/2014 9:35 PM, Stefan Arentz wrote:
Although this is at version 0.1, it is working pretty well for me and I am
looking for some additional testers that are interested.
Please note that it is not possible to use this project without legally
running a copy
of OS X Server.
Hi
I'm about to migrate a setup with <20 IMAP (but with a few million mails in
all) accounts that belong to the same system-user on an older machine running
Dovecot 2.0.13 to a new machine running Dovecot 2.2.13 (or possibly newer..).
Mails are stored in Maildirs with no special or advanced fea
Hi
I'm running into regular problems with dovecot choking on "corrupted"
index files. The main problem is that it doesn't sort itself out and
recover. This message below is repeated regularly in the log files
(until I delete the index files)
I *think* the trigger to get into this situation
This is interesting; I'm not sure if I got that right from scanning
the READMEs. Do I really need to have a working OSX-server setup
which I then do migrate away from? What makes this certificate that
special such that I only can export it from the existing server
setup?
-M
Am 05.09.2014 um 03:35
18 matches
Mail list logo
