On 20/01/16 12:15, Brendan Kearney wrote:
when i telnet to the sieve instance running with dovecot, i see that
SASL is supported, but i cannot get thunderbird to connect to the
sieve instance. it seems that i am not providing the right auth
methods for sieve to work.
"IMPLEMENTATION" "Doveco
when i telnet to the sieve instance running with dovecot, i see that
SASL is supported, but i cannot get thunderbird to connect to the sieve
instance. it seems that i am not providing the right auth methods for
sieve to work.
"IMPLEMENTATION" "Dovecot Pigeonhole"
"SIEVE" "fileinto reject enve
On 19/1/2016 8:54 μμ, Timo Sirainen wrote:
No, this is used only when TLS SNI extension is used. It expands to the TLS SNI
hostname. Typically this is only used to configure per-host TLS certificates.
So, when TLS SNI extension is not used, we can skip the entire block? Like:
local 127.0.
Nikolaos Milas wrote:
...
Pragmatically, I set it high enough so that it meets the need of most
clients, then deal with problems on a case by case basis
...
Thank you very much Joseph for your quite useful advice and experience.
Are you monitoring using "doveadm who"?
No, I occasionally loo
> On 19 Jan 2016, at 20:23, Nikolaos Milas wrote:
>
> On 19/1/2016 6:34 μμ, Timo Sirainen wrote:
>
>> The nesting must be in this order or it'll give an error:
>>
>> local 127.0.0.1 {
>> local_name foo {
>> remote 127.0.0.1 {
>> protocol imap {
>> }
>> }
>> }
>> }
>
>
On 19/1/2016 6:34 μμ, Timo Sirainen wrote:
The nesting must be in this order or it'll give an error:
local 127.0.0.1 {
local_name foo {
remote 127.0.0.1 {
protocol imap {
}
}
}
}
Please allow me to ask for clarifications:
local --> Local Dovecot Server
> On 19 Jan 2016, at 16:04, Nikolaos Milas wrote:
>
> On 19/1/2016 3:31 μμ, Timo Sirainen wrote:
>
>> Change it the other way around:
>>
>> remote 127.0.0.1 {
>> protocol imap {
>> ...
>> }
>> }
>
> Thank you for your advice Timo (on "remote" blocks).
>
> So, the "remote" block shoul
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 19 Jan 2016, Lucky . wrote:
Can you please provide the step for configure sendmail with dovecot.
We could not understand the parameter which mention in sendmail.cf file. Please
provide the parameter description as well as where need to cha
Webmail probably just quickly opens and closes the connections, so
there aren't any connections that are visible for more than a fraction
of a second.
On the real issue: I am trying to identify why (just recently) webmail
users recently are increasingly facing the error: "ERROR : Connection
dro
On 19/1/2016 3:31 μμ, Timo Sirainen wrote:
Change it the other way around:
remote 127.0.0.1 {
protocol imap {
...
}
}
Thank you for your advice Timo (on "remote" blocks).
So, the "remote" block should not have any parent (i.e. should not be
included in any other block)?
Webmai
Hi Dovecot team/All,
First of all, I always appreciated your contribution & effort.
Can you please provide the step for configure sendmail with dovecot.
We could not understand the parameter which mention in sendmail.cf file. Please
provide the parameter description as well as where need to
On 19 Jan 2016, at 13:34, Nikolaos Milas wrote:
>
> On 15/1/2016 8:02 μμ, Nikolaos Milas wrote:
>
> Having received no reply, I tried using the above info by configuring:
>
> protocol imap {
> imap_client_workarounds = "delay-newmail"
> mail_plugins = quota imap_quota notify replica
On 15/1/2016 10:05 μμ, Joseph Tam wrote:
...
Pragmatically, I set it high enough so that it meets the need of most
clients, then deal with problems on a case by case basis
...
Thank you very much Joseph for your quite useful advice and experience.
Are you monitoring using "doveadm who"?
4.
On 15/1/2016 8:02 μμ, Nikolaos Milas wrote:
Where can I find detailed documentation on how "remote" & "local"
blocks are used in protocol configuration to provide specific settings
for particular IPs/Names?
I've been searching around (wiki2, Google) but I found very few
things. I also checke
On 2016-01-04 19:21, Timo Sirainen wrote:
On 04 Jan 2016, at 12:54, Timo Sirainen wrote:
On 04 Jan 2016, at 09:58, Florian Pritz wrote:
On 04.01.2016 15:49, Timo Sirainen wrote:
What about:
#5 0x0041dde6 in client_check_command_hangs
(client=0x2363450) at imap-client.c:841
15 matches
Mail list logo
