Re: PATCH for Stephan: Re: pigeonhole/lda accessing -m folder
I just noticed you implemented the Dovecot Environment Extension.
Thanks!
maybe it helps somebody to get this referenced in this thread
https://raw.githubusercontent.com/dovecot/pigeonhole/master/doc/rfc/spec-bosch-sieve-dovecot-environment.txt
example:
default folder is accessible with:
${env.vnd.dovecot.default_mailbox}
Greetz Matze
Am Mon, 10 Aug 2015 17:05:58 +0200
schrieb Stephan Bosch :
> Op 8/10/2015 om 4:29 PM schreef Steffen Kaiser:
> > On Mon, 10 Aug 2015, matthias lay wrote:
> >
> > Dear Stephan,
> >
> > If you find this code OK, please merge it into Pigeonhole.
>
> Non-standard entries like this require a vnd.dovecot prefix.
>
> > I find this information useful, too. The +detail and the default
> > mailbox are not necessarily the same. Maybe, there is a namespace to
> > expose this information easily?
>
> The Pigeonhole internals support custom variable namespaces. The
> extdata plugin uses this too, so adding something like that is
> architecturally not problematic.
>
> I would make this dependent on an extension like
> "vnd.dovecot.environment", so that non-standard features are only
> added when this is in the require line. Currently, the "auth"
> envelope field (CMUSieve) is the only exception and I like to keep it
> that way.
>
> I'll give this a look. Also, are there any other environment items
> that may be useful?
>
> Regards,
>
> Stephan.
Re: Dovecot and Oauth
Am Tue, 20 Aug 2019 11:07:13 +1200 schrieb Michael Hallager via dovecot : > Hi all, > > I am considering expanding a mail server to support Oauth with > Google. I have read through the following: > https://wiki.dovecot.org/PasswordDatabase/oauth2 > however, it doesn't work and appears to me to be missing important > information, the least of which is API authorisation. Searching with > Google, I can't find any more information beyond what amounts to > C&P'ing of the above link. > > Has anyone successfully deployed Oauth with Google and could they > please send me their config files? > > Thanks, > > Michael Hi, you should try the ## HTTP request raw log directory # rawlog_dir = /tmp/oauth2 option. this dumps the http requests in this dir and you can see the requests and the response from the server. maybe its the missing scope= option as mentioned in this thread [[ Dovecot - Microsoft Azure AD ]] if its the case try building dovecot from master branch. Greetz Matze
Re: lmtp with non ASCII Parameters changed in dovecot 2.3
> mail from: > 500 5.5.2 Invalid command syntax this was a bad example. the problem is more common on rcpt to: if you deliver to usernames or special folders rcpt to:<üser> or rcpt to:
lmtp with non ASCII Parameters changed in dovecot 2.3
Hi, I updated from 2.2 to 2.3 and noticed lmtp rejects parameters containing non ASCII now. this worked with dovecot-2.2 lmtp. the string is already denied after reading in "smtp_command_parse_parameters()" mail from: 500 5.5.2 Invalid command syntax is there a plan to change this behaviour, or to implement the SMTPUTF8 extension in lib-smtp? I guess thie would fix Michals "Dovecot LMTP rejecting mail from address with apostrophe" Problem too. Greetz Matze
Re: Variable expansion with variables containing '%' (ldap with 2.3.6)
Am Tue, 2 Jul 2019 08:51:24 +0300
schrieb Aki Tuomi :
> On 2.7.2019 8.24, Aki Tuomi via dovecot wrote:
> > On 1.7.2019 13.37, Matthias Lay via dovecot wrote:
> >> Am Mon, 1 Jul 2019 13:08:46 +0300 (EEST)
> >> schrieb Aki Tuomi :
> >>
> >>> Hi,
> >>>
> >>> there seems to be a problem when expanding variables containing a
> >>> single '%' in value in dovecot V2.3.6
> >>>
> >>> having a user defined Variable in user_attrs like
> >>>
> >>> user_attrs = name=home=/maildir/%Ln,
> >>> =myvar=path/%L{ldap:sAMAccountName}
> >>>
> >>>
> >>> and sAMAccountName conains a '%', in my example "sonder%zeichen"
> >>> leads to:
> >>>
> >>> lda(sonder%zeichen)<5723>: Fatal: Failed
> >>> to expand plugin setting myvar = 'path/sonder%zeichen': Unknown
> >>> variable '%z'
> >>>
> >>> same setup works with dovecot 2.2.29
> >>>
> >>> Any Feedback appreciated.
> >>> Thanks.
> >>> Matze
> >>>
> >>> You can use %% to escape a %
> >>> ---
> >>> Aki Tuomi
> >>>
> >> Hi Aki,
> >>
> >> nope this doesnt work. if I use 'sonder%%zeichen', the ldap lookup
> >> searches for the User/Value "sonder%%zeichen" in ldap/AD. what
> >> fails, as this user doesnt exist.
> >>
> >> and I cant escape the value in all cases anyway, as its an remote
> >> value, coming from the ldap server.
> >>
> >> seems to me the sequence of intepreting variables and modifiers
> >> changed between 2.2 ans 2.3
> >> now it gets the variable value from remote in the first place, and
> >> interprets the value itself for more variables or modifiers, which
> >> might not be what you want.
> >>
> >> like in a subquery using
> >>
> >> @mail=%{ldap:mailDN}
> >>
> >> but I dont use subqueries. just a simple expansion
> >>
> >> =myvar=%{ldap:mailDN}
> >>
> >> any more ideas?
> >>
> >>
> >>
> >>
> >>
> > I have to investigate this a bit.
> >
> >
> > Aki
> >
>
> Seems to be a bug of a kind. I'll open it in our issue tracker.
>
> Aki
>
thx for your effort Aki.
If I can help out testing a patch, just let me
know
Matze
Re: Variable expansion with variables containing '%' (ldap with 2.3.6)
Am Mon, 1 Jul 2019 13:08:46 +0300 (EEST)
schrieb Aki Tuomi :
> Hi,
>
> there seems to be a problem when expanding variables containing a
> single '%' in value in dovecot V2.3.6
>
> having a user defined Variable in user_attrs like
>
> user_attrs = name=home=/maildir/%Ln,
> =myvar=path/%L{ldap:sAMAccountName}
>
>
> and sAMAccountName conains a '%', in my example "sonder%zeichen"
> leads to:
>
> lda(sonder%zeichen)<5723>: Fatal: Failed to
> expand plugin setting myvar = 'path/sonder%zeichen': Unknown
> variable '%z'
>
> same setup works with dovecot 2.2.29
>
> Any Feedback appreciated.
> Thanks.
> Matze
>
> You can use %% to escape a %
> ---
> Aki Tuomi
>
Hi Aki,
nope this doesnt work. if I use 'sonder%%zeichen', the ldap lookup
searches for the User/Value "sonder%%zeichen" in ldap/AD. what fails, as
this user doesnt exist.
and I cant escape the value in all cases anyway, as its an remote
value, coming from the ldap server.
seems to me the sequence of intepreting variables and modifiers changed
between 2.2 ans 2.3
now it gets the variable value from remote in the first place, and
interprets the value itself for more variables or modifiers, which
might not be what you want.
like in a subquery using
@mail=%{ldap:mailDN}
but I dont use subqueries. just a simple expansion
=myvar=%{ldap:mailDN}
any more ideas?
Variable expansion with variables containing '%' (ldap with 2.3.6)
Hi,
there seems to be a problem when expanding variables containing a
single '%' in value in dovecot V2.3.6
having a user defined Variable in user_attrs like
user_attrs = name=home=/maildir/%Ln,
=myvar=path/%L{ldap:sAMAccountName}
and sAMAccountName conains a '%', in my example "sonder%zeichen"
leads to:
lda(sonder%zeichen)<5723>: Fatal: Failed to
expand plugin setting myvar = 'path/sonder%zeichen': Unknown
variable '%z'
same setup works with dovecot 2.2.29
Any Feedback appreciated.
Thanks.
Matze
Variable expansion with variables containing '%' (ldap with 2.3.6)
Hi,
there seems to be a problem when expanding variables containing a
single '%' in value in dovecot V2.3.6
having a user defined Variable in user_attrs like
user_attrs = name=home=/maildir/%Ln,
=myvar=path/%L{ldap:sAMAccountName}
and sAMAccountName conains a '%', in my example "sonder%zeichen"
leads to:
lda(sonder%zeichen)<5723>: Fatal: Failed to
expand plugin setting myvar = 'path/sonder%zeichen': Unknown
variable '%z'
same setup works with dovecot 2.2.29
Any Feedback appreciated.
Thanks.
Matze
