Hi,
I also experienced that thunderbird behavior, I guess
> [...]
>
> When I move a message to Archive in Thunderbird. On the server the
> files
What exactly means move? Like drag and drop or via context menu
"archive/archivieren"?
> .Archives and .Archives.2018 are created (Thunderbird creat
Op 15/12/2018 om 19:10 schreef Marc Roos:
dovecot-2.2.36-3.el7.x86_64
The below configuration seems to work for Thunderbird and emclient, when
moving a message to Junk. Emclient uses "Junk E-mail" and Thunderbird
uses "Junk". On the server is only the file .Junk created as expected.
When I mo
Op 20/12/2018 om 18:09 schreef Ludovic Pouzenc:
Hi,
I hit a bizare problem with dovecot 2.2.7 on debian 9 with LMTP enabled and
auth/penalty disabled as documented here :
https://wiki.dovecot.org/Authentication/Penalty
Use case : I run a swaks command to send an email to an exim4 that trie
Op 06/01/2019 om 17:02 schreef Steven Craig:
Thanks, its a weird one.
On 1/6/2019 8:00 AM, Stephan Bosch wrote:
Op 06/01/2019 om 11:50 schreef Stephan Bosch:
Op 31/12/2018 om 23:59 schreef Steven Craig:
Hello there,
Everything was working fine on Dovecot 2.2.10 (on CentOS 7), but
after
and stupid me missed a character, the full fix is in SVN r489516.
On Sun, Jan 6, 2019 at 11:47 AM Larry Rosenman wrote:
> I'm the FreeBSD port maintainer for dovecot and I just added this patch to
> the port in SVN. 489515.
>
> On Sun, Jan 6, 2019 at 11:39 AM Stephan Bosch
> wrote:
>
>>
>> Op
Op 06/01/2019 om 18:58 schreef Christian Wolf:
Dear mailinglist,
I have the problem that I had to migrate a setup and since then my
user's sieve script does no longer log anything.
I have sieve_user_log unset and sieve points to a folder (ready for
ManageSievev service). In the old config I
Dear mailinglist,
I have the problem that I had to migrate a setup and since then my user's sieve
script does
no longer log anything.
I have sieve_user_log unset and sieve points to a folder (ready for
ManageSievev service).
In the old config I had sieve point to the symlink and sieve_dir poi
I'm the FreeBSD port maintainer for dovecot and I just added this patch to
the port in SVN. 489515.
On Sun, Jan 6, 2019 at 11:39 AM Stephan Bosch wrote:
>
> Op 06/01/2019 om 18:12 schreef John Fawcett:
> > On 06/01/2019 11:37, Stephan Bosch wrote:
> >> Op 06/01/2019 om 03:35 schreef John Fawcett
Op 06/01/2019 om 18:12 schreef John Fawcett:
On 06/01/2019 11:37, Stephan Bosch wrote:
Op 06/01/2019 om 03:35 schreef John Fawcett:
On 06/01/2019 02:26, John Fawcett wrote:
Can't see anything in the Dovecot 2.3.4 code that would give this
problem, setting
stats_writer_socket_path =
will o
On 06/01/2019 11:37, Stephan Bosch wrote:
>
> Op 06/01/2019 om 03:35 schreef John Fawcett:
>> On 06/01/2019 02:26, John Fawcett wrote:
>>
>>> Can't see anything in the Dovecot 2.3.4 code that would give this
>>> problem, setting
>>>
>>> stats_writer_socket_path =
>>>
>>> will overwrite the default
Op 31/12/2018 om 06:32 schreef Laz C. Peterson:
Hello Sami, yes, see below.
We run Dovecot at a different versions, mainly 2.2.10 (CentOS), 2.2.22
(Ubuntu) and now 2.2.36 (CentOS). The issue is weird, because it only
happened after the update from 2.2.10->36. Just to understand it
would b
Thanks, its a weird one.
On 1/6/2019 8:00 AM, Stephan Bosch wrote:
Op 06/01/2019 om 11:50 schreef Stephan Bosch:
Op 31/12/2018 om 23:59 schreef Steven Craig:
Hello there,
Everything was working fine on Dovecot 2.2.10 (on CentOS 7), but
after updating to version 2.2.36, our director servers
Op 06/01/2019 om 11:50 schreef Stephan Bosch:
Op 31/12/2018 om 23:59 schreef Steven Craig:
Hello there,
Everything was working fine on Dovecot 2.2.10 (on CentOS 7), but
after updating to version 2.2.36, our director servers are not able
to proxy LMTP.
We are sending mail from exim to the
Hello Stephan,
I'm interested to see this get fixed (and ideally one day for it to be
really easy for people to set up Alpine so that it competes fairly with
heavier GUIs!), but I do not know that I am qualified to help (beyond
light testing). Is there someone from Alpine on this thread? The s
Op 31/12/2018 om 16:53 schreef Chris Barrington-Leigh:
I then followed the instructions in the Warning lines above and now I
get:
dovecot -n -c /home/meuser/dotfiles/auto-stanford-dovecot.conf
# 2.3.2.1 (0719df592): /home/meuser/dotfiles/auto-stanford-dovecot.conf
# Pigeonhole version 0.5.2
Op 31/12/2018 om 23:59 schreef Steven Craig:
Hello there,
Everything was working fine on Dovecot 2.2.10 (on CentOS 7), but after
updating to version 2.2.36, our director servers are not able to proxy
LMTP.
We are sending mail from exim to the local Dovecot LMTP socket, which
then used to
Op 06/01/2019 om 03:35 schreef John Fawcett:
On 06/01/2019 02:26, John Fawcett wrote:
Can't see anything in the Dovecot 2.3.4 code that would give this
problem, setting
stats_writer_socket_path =
will overwrite the default value and dovecot does not attempt to open a socket
in that case.
and finally , for fts_backend__lookup_multi, why is that backend
dependent ?
Would- nt the below function below be the same for any backend ?
Waiting fro your feedback on all those questions
Thank you
JM
-
static int fts_backend_xapian_lookup_multi(struct fts_backe
for fts_backend_xxx_lookup, where is specidifed in which field (to, cc,
subject, body, from, all) to lookup ?
On 2019-01-06 16:03, Joan Moreau wrote:
For "rescan " and "optimize", wouldn't it be the dovecot core who indicate which are to be dismissed (expunged), or re-ask for indexing a particul
Hey guys,
I had some corruptions whereby dovecot would bomb out on mail files in
my maildir. I found that if piped the files to dovecot-lda the all
email was clean &lost. I even retrieved email I thought might have
been lost for good. I have some better ideas now, but I still processed
a
For "rescan " and "optimize", wouldn't it be the dovecot core who
indicate which are to be dismissed (expunged), or re-ask for indexing a
particular (or all) uid ? WHy would the backend be aware of the
transactions on the mailbox ???
There is alredy "fts_backend_xxx_update_expunge", so I beleiv
21 matches
Mail list logo
