Hi Timo,
Am 08.11.2013 14:07, schrieb Timo Sirainen:
> I've never really wanted to create my own MTA, because I like Postfix
> quite a lot. And I always thought it would require a horribly lot of
...and there virtually nothing which could not be built with Postfix.
Maybe a Postfix addon/proxy for
Timo,
* Timo Sirainen :
> I've never really wanted to create my own MTA, because I like Postfix quite
> a lot. And I always thought it would require a horribly lot of time to be
> able to create something that was anywhere even close to having Postfix's
> features. (I would shudder to even think a
Daniel Parthey schrieb:
Hi Patrick
the director does not check backends for availability. If one backend goes up
or down, you need to instruct the director to add/remove this backend from its
pool.
http://blog.dovecot.org/2012/02/dovecot-clustering-with-dsync-based.html
says:
One possibilit
Am 2013-11-08 22:31, schrieb Achim Gottinger:
Am 08.11.2013 22:19, schrieb Alter Depp:
I am running dovecot 2.1.7 for a while, with roundcube webmail
frontend 0.9.5 .
An wild guess but it may help if you define mail_home as well.
Does this setting exist in dovecot 2? Where should I set it and
Hi Patrick,
do you want to use the proxy *without* the director? Then you would need to
remove all director_... entries from your proxy config.
The proxy backend is controlled by passdb extra fields. Here is how to setup a
proxy without the director:
http://wiki2.dovecot.org/PasswordDatabase/E
Am 2013-11-08 22:58, schrieb Manuel Delgado:
On Fri, Nov 8, 2013 at 3:19 PM, Alter Depp wrote:
I am running dovecot 2.1.7 for a while, with roundcube webmail
frontend
0.9.5 .
I've a similar design with Dovecot 2.1.7 and Roundcube 0.9.x. I'm using
the
SieveRules plugin from JohnDoh and Pigeon
Daniel Parthey schrieb:
You need to keep the password database up-to-date and ensure to not return an unhealthy
backend IP in the "host" extra field, since the knowledge of the proxy (as
mentioned in the blog) is simply read from the passdb database. Database content needs to
be maintained by
On 10.11.2013, at 19.24, Patrick Westenberg wrote:
> Daniel Parthey schrieb:
>
>> You need to keep the password database up-to-date and ensure to not return
>> an unhealthy backend IP in the "host" extra field, since the knowledge of
>> the proxy (as mentioned in the blog) is simply read from
On 5.11.2013, at 11.01, IT geek 31 wrote:
> Thanks for the info. I've upgraded to v2.2.7 and made the change. Now I
> get:
>
> Nov 5 11:00:00 server1 dovecot: dsync-server(mark): Error: Couldn't lock
> /home/mark/.dovecot-sync.lock: Timed out after 30 seconds
> Nov 5 11:00:02 server1 dovecot
Timo Sirainen schrieb:
The blog was telling the idea how things would work, not exactly whose
responsibility it is to do every part of them. The Dovecot proxies will know
which backend servers are down (but not without extra scripting).
So another ineffectual feature from Dovecot.
You shoul
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am 10.11.2013 19:43, schrieb Patrick Westenberg:
> Timo Sirainen schrieb:
>
>> The blog was telling the idea how things would work, not exactly
>> whose responsibility it is to do every part of them. The Dovecot
>> proxies will know which backend se
On 10.11.2013, at 19.43, Patrick Westenberg wrote:
> Timo Sirainen schrieb:
>
>> The blog was telling the idea how things would work, not exactly whose
>> responsibility it is to do every part of them. The Dovecot proxies will know
>> which backend servers are down (but not without extra scrip
On 08/11/2013 14:07, Timo Sirainen wrote:
> I've never really wanted to create my own MTA, because I like Postfix
> quite a lot. And I always thought it would require a horribly lot of
> time to be able to create something that was anywhere even close to
> having Postfix's features.
Hello Timo,
I
On 10.11.2013, at 20.00, Daniele Nicolodi wrote:
> At the same time I see here on the mailing list frequent reports of bugs
> in Dovecot that would have been quite easy to catch with more test
> coverage. Spending time and energies into extending unit and integration
> tests for the current Dovec
Timo Sirainen skrev den 2013-11-08 14:07:
So perhaps something like this could be done in time for Dovecot v2.4.
Any thoughts/ideas/suggestions?
why is users not just change from postfix/dovecot to currier-* ?
its imho much better :)
http://www.courier-mta.org/
On Nov 10, 2013, at 1:00 PM, Daniele Nicolodi wrote:
> On 08/11/2013 14:07, Timo Sirainen wrote:
>> I've never really wanted to create my own MTA, because I like Postfix
>> quite a lot. And I always thought it would require a horribly lot of
>> time to be able to create something that was anywher
On 11/10/2013 14:15, Benny Pedersen wrote:
> Timo Sirainen skrev den 2013-11-08 14:07:
>
>> So perhaps something like this could be done in time for Dovecot v2.4.
>> Any thoughts/ideas/suggestions?
>
> why is users not just change from postfix/dovecot to currier-* ?
>
> its imho much better :)
>
Am 09.11.2013 14:01, schrieb Stefan Liebl:
Am 2013-11-08 22:31, schrieb Achim Gottinger:
Am 08.11.2013 22:19, schrieb Alter Depp:
I am running dovecot 2.1.7 for a while, with roundcube webmail
frontend 0.9.5 .
An wild guess but it may help if you define mail_home as well.
Does this setting e
On 10 November 2013 19:34, Timo Sirainen wrote:
> On 5.11.2013, at 11.01, IT geek 31 wrote:
>
> > Thanks for the info. I've upgraded to v2.2.7 and made the change. Now I
> > get:
> >
> > Nov 5 11:00:00 server1 dovecot: dsync-server(mark): Error: Couldn't lock
> > /home/mark/.dovecot-sync.lock
On 11/10/2013 02:20 PM, Larry Stone wrote:
Timo said in his reply that he doesn't know how to improve the current
documentation. I'll take him at his word. I submit that it really needs a total
rewrite, not continued editing. And before someone suggests if I believe it
needs to be rewritten, I
Timo Sirainen skrev den 2013-11-08 15:44:
Actually its main target audience is large ISPs and such :) The Sieve
scripting for configurations is especially useful for many who want
complex configurations.
extend dovecot -n to output current config as xml ?
maybe even configure it all via xml ?
On 10.11.2013, at 21.24, Benny Pedersen wrote:
> extend dovecot -n to output current config as xml ?
>
> maybe even configure it all via xml ?
All the configuration goes through src/config/* code, which can be easily
replaced with anything else. The original idea was to make it possible to sto
Am 10.11.2013 21:24, schrieb Benny Pedersen:
> Timo Sirainen skrev den 2013-11-08 15:44:
>
>> Actually its main target audience is large ISPs and such :) The Sieve
>> scripting for configurations is especially useful for many who want
>> complex configurations.
>
> extend dovecot -n to output cu
Timo Sirainen skrev den 2013-11-10 21:38:
On 10.11.2013, at 21.24, Benny Pedersen wrote:
extend dovecot -n to output current config as xml ?
maybe even configure it all via xml ?
All the configuration goes through src/config/* code, which can be
easily replaced with anything else. The origi
Am 10.11.2013 22:39, schrieb Benny Pedersen:
> here i still using dovecot 1.2.17 in gentoo, i feal no need yet to discard
> that old software
> yet here, asked gentoo devs to put it back to portage, but was denied for
> some reason i
> just dont understand
what exactly dou you not understand
Robert Schetterer skrev den 2013-11-10 19:49:
So another ineffectual feature from Dovecot.
Hey Patrick, its open software why dont hack yourself , everyone would
like to see things getting better
+1
Hello,
we can reproduce a bug where lmtp crashes:
LMTP telnet session:
Trying 127.0.0.1...
Connected to localhost.localdomain (127.0.0.1).
Escape character is '^]'.
220 lisa.m-otion.at Dovecot ready.
lhlo xyz
250-xyz.m-otion.at
250-8BITMIME
250-ENHANCEDSTATUSCODES
250 PIPELINING
mail from:
250 2.
On 11/11/2013 12:54 AM, Christian Ferbar wrote:
> Hello,
>
> we can reproduce a bug where lmtp crashes:
> If you use a sieve script containing the following line
> notify :method "mailto" :options "xyz" :message "$from$*#+$subject$";
>
> and send a mail without a Subject: header line lmtp crash
My company have 36 dovecots, one biggest ISP in country 3 million user,
agree with Nick poster, we had stop use dovecot load balance because too
bad effect on primary database, now use single localhost, we have script
run every 30 second to test login, if fail sleep 30 second, try again, fail
and
Appears some change between 2.2.6 and 2.2.7 altered the response codes for LMTP
user verification probes.
Dovecot 2.2.6:
Nov 2 15:50:48 spectre postfix/qmgr[627]: 3dBjr80wMgz1s:
from=, size=271, nrcpt=1 (queue active)
Nov 2 15:50:48 spectre postfix/cleanup[6226]: 3dBjr80xbYz1w:
message-id=<2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, 8 Nov 2013, Dean Carpenter wrote:
Running /usr/bin/sa-learn directly always returns with an error code of
1, and the bayes DB isn't actually updated. Running the
/usr/local/bin/sa-learn-pipe.sh script from the example will run
sa-learn succ
31 matches
Mail list logo
