Hello everyone,
I have successfully set up Dovecot with an LDAP backend, and everything
works like a charm, except one small use case.
I know it is possible, so if anyone knows a solution, thank you!
Basically, I just want to send an email to one of my email address,
which contains an accent, i.
Hello,
It looks like the "mail_always_cache_fields" and "mail_never_cache_fields"
can be used to control dovecot's caching decisions. I cannot seem to find
any documentation regarding how these fields should be used.
What are acceptable values for these fields? I am quite new to this so any
help
Are the dovecot environment variables mutable? I'd like to override
like:
set "${env.vnd.dovecot.username}" "someu...@example.org"
Or better, I prefer to override %u Dovecot variable during the userdb
lookup.
Is either possible?
PS, when Sieve does extdata lookups for username key, where do
Am 18.03.2018 um 23:25 schrieb André Rodier:
Every other alias works, but not those with accents. They are correctly
stored in the LDAP database, using base64.
Why do you even think a character like 'é' would be legal in the local
part of an email address?
Alexander
On 19.03.2018 07:58, Alexander Dalloz wrote:
> Am 18.03.2018 um 23:25 schrieb André Rodier:
>> Every other alias works, but not those with accents. They are correctly
>> stored in the LDAP database, using base64.
>
> Why do you even think a character like 'é' would be legal in the local
> part of
On 19.03.2018 06:40, MRob wrote:
> Are the dovecot environment variables mutable? I'd like to override like:
>
> set "${env.vnd.dovecot.username}" "someu...@example.org"
>
> Or better, I prefer to override %u Dovecot variable during the userdb
> lookup.
>
> Is either possible?
>
> PS, when Sieve
On 19.03.2018 05:14, Sivathmican Sivakumaran wrote:
> Hello,
>
> It looks like the "mail_always_cache_fields" and
> "mail_never_cache_fields" can be used to control dovecot's caching
> decisions. I cannot seem to find any documentation regarding how these
> fields should be used.
>
> What are acc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sun, 18 Mar 2018, André Rodier wrote:
Every other alias works, but not those with accents. They are correctly
stored in the LDAP database, using base64.
Despite Aki's answer, whether it works at all, I would expect the
enconding in LDAP is UTF
On 19/03/18 06:30, Aki Tuomi wrote:
>
>
> On 19.03.2018 07:58, Alexander Dalloz wrote:
>> Am 18.03.2018 um 23:25 schrieb André Rodier:
>>> Every other alias works, but not those with accents. They are correctly
>>> stored in the LDAP database, using base64.
>>
>> Why do you even think a character
