On Tue, 21 May 2019 18:24:46 +
MRob via dovecot wrote:
> Many people prefer to use LMTP for delivery from postfix for better
> efficiency but X-Original-to header support still missing after many
> years. One affect of this is need to set
> sieve_vacation_dont_check_recipient = yes which v
Let me know if you find a nice solution to migrate mailboxes per user,
without downtime. I tried the use of the adviced userdb and using the
override of the maillocation. But that doesn’t work with my mbox inbox.
I wanted to migrate then per user to an new server environment but still
did n
Is it possible to do some sort of integrity check on mdbox's
On 22 May 2019 12:11 Marc Roos via dovecot <
dovecot@dovecot.org> wrote:
Is it possible to do some sort of integrity check on mdbox's
doveadm force-resync
---
Aki Tuomi
Unfortunately we have not been able to work on this much, but also the
JMAP spec was until very recently still being worked. We have open
dialogue with the Thunderbird people, they haven't so far indicated any
pressing need for JMAP in Dovecot.
This said, JMAP is still very much in our roadmap. Pe
From dovecot, you can add any additional attributes you like using the
auth_policy_request_attributes configuration setting, e.g.
By default in 2.3.1 this looks like:
login=%{requested_username} pwhash=%{hashed_password} remote=%{rip}
device_id=%{client_id} protocol=%s
But you can add addition
Hello,
when receiving mails for multiple recipients via LMTP, I often see the
following messages on our servers:
May 22 11:06:10 sinon dovecot[44304]: lmtp(119718): Connect from $IP$
May 22 11:06:11 sinon dovecot[44304]: lmtp($USER1$)<119718><2HnmOgIR5Vym0wEA22L5Rg>:
msgid=<$MSGID$>: saved m
Hi Neil
thanks for the hint with the dovecot config, adding this and I can see that
> ... attrs={local_ip="XX.XX.XX.XX"} ...
is now logged by wforce daemon. Then I tried to access that value from
wforce with the following testcode
> if (#lt.attrs > 0)
> then
> return 7, "ip_local", "ip_local"
Hi Tobi,
you need to process lt.attrs in a loop. It's not a real Lua table, it's a user data pretending to be a table, so # doesn't work.
For example:
for k, v in pairs(lt.attrs) do
if ((k == "acc
On Wed May 22 2019 05:44:59 GMT-0400 (Eastern Standard Time), Aki Tuomi
via dovecot wrote:
> Unfortunately we have not been able to work on this much, but also the
> JMAP spec was until very recently still being worked. We have open
> dialogue with the Thunderbird people, they haven't so far indic
On 2019-05-22 08:18, Tuomo Soini via dovecot wrote:
On Tue, 21 May 2019 18:24:46 +
MRob via dovecot wrote:
Many people prefer to use LMTP for delivery from postfix for better
efficiency but X-Original-to header support still missing after many
years. One affect of this is need to set
sieve
On Wed May 22 2019 13:34:42 GMT-0400 (Eastern Standard Time), MRob via
dovecot wrote:
> On 2019-05-22 08:18, Tuomo Soini via dovecot wrote:
>> On Tue, 21 May 2019 18:24:46 +
>> MRob via dovecot wrote:
>>
>>> Many people prefer to use LMTP for delivery from postfix for better
>>> efficiency bu
On 22 May 2019, at 07:42, Tanstaafl via dovecot wrote:
> Thanks Aki - no pressing need because of the old chicken/egg problem I
> guess...
I have to say, looking at JAMP it looks very interesting. I'd love to throw a
JAMP webmail implementation up and play with it.
--
"I can't marry her; she's
On 21/05/2019 15:45, mabi via dovecot wrote:
> ‐‐‐ Original Message ‐‐‐
> On Monday, May 20, 2019 12:37 AM, John Fawcett via dovecot
> wrote:
>
>> So looking into this with a postgresql databse to work with: the
>> above query does not work. You have to specify either the column name
>> or
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 22 May 2019, John Fawcett via dovecot wrote:
an update when insert fails seems to be a MySQL specific extension to
standard Sql. So I think that it's clear that support for PostgreSql and
Sqlite needs to be implemented. The same issue likel
> Maybe, one should drop the automatic at all and let the user specify
> the commands manually like with the userdb/passwd. Hence, the generic
> SQL preparation code is already present. There could/should/would be
> documented lots of "best practice" settings for various backends.
>
> In fact, thi
16 matches
Mail list logo
