Op 3/7/2018 om 6:28 PM schreef Philipp Berger:
> Interesting, the documentation and the build-in help of dovecot-lda do
> not mention -r exists :)
>
> case 'r':
>
> /* final recipient address */
>
> if (smtp_address_parse_path(ctx.pool, optarg,
>
> SMTP_ADDRESS_PARSE_FLAG_ALLOW_LO
Interesting, the documentation and the build-in help of dovecot-lda do
not mention -r exists :)
case 'r':
/* final recipient address */
if (smtp_address_parse_path(ctx.pool, optarg,
SMTP_ADDRESS_PARSE_FLAG_ALLOW_LOCALPART |
SMTP_ADDRESS_PARSE_FLAG_BRACKETS_OPTIO
Op 7-3-2018 om 15:40 schreef Stephan Bosch:
Op 7-3-2018 om 13:46 schreef Philipp Berger:
I wrapped the LDA command in a script. I can see that Postfix passes
"@@mydomain.tld" as the -d argument, without quotes.
I then adapted the script to specifically replace this address with
"@"@mydomain.
Op 7-3-2018 om 13:46 schreef Philipp Berger:
I wrapped the LDA command in a script. I can see that Postfix passes
"@@mydomain.tld" as the -d argument, without quotes.
I then adapted the script to specifically replace this address with
"@"@mydomain.tld, but this results in the following error me
Hello!
Maybe experiment with auth_username_chars:
# List of allowed characters in username. If the user-given username contains
# a character not listed in here, the login automatically fails. This is just
# an extra check to make sure user can't exploit any potential quote escaping
# vulnerabil
I wrapped the LDA command in a script. I can see that Postfix passes
"@@mydomain.tld" as the -d argument, without quotes.
I then adapted the script to specifically replace this address with
"@"@mydomain.tld, but this results in the following error message by
Dovecot:
auth: Info: userdb(?): Use
Op 6-3-2018 om 14:34 schreef Philipp Berger:
I upgraded to Dovecot 2.3.0.1 as advised, but it still seems broken. In
the Postfix log I now see:
Mar 6 13:49:03 myhost amavis[7165]: (07165-10) K00VtLRHdrYw FWD from
-> <"@"@mydomain.tld>, BODY=7BIT 250 2.0.0 from
MTA(smtp:[127.0.0.1]:10025): 25
I upgraded to Dovecot 2.3.0.1 as advised, but it still seems broken. In
the Postfix log I now see:
Mar 6 13:49:03 myhost amavis[7165]: (07165-10) K00VtLRHdrYw FWD from
-> <"@"@mydomain.tld>, BODY=7BIT 250 2.0.0 from
MTA(smtp:[127.0.0.1]:10025): 250 2.0.0 Ok: queued as B8CA22DA1B37
Mar 6 13:49:0
Op 3/1/2018 om 2:07 PM schreef Philipp Berger:
> Dear all,
>
> I have a working setup with Postfix + Dovecot, storing users in a MySQL
> table.
>
> I ran into problems setting up and using a mail address like
> a"@"b...@mydomain.tld, which by RFC should be valid, but leads to problems
> in Dovecot.
On Mar 1, 2018, at 08:13, Philipp Berger wrote:
> Sadly, it does not change the outcome. Even with a pure
> "@"@mydomain.tld, Dovecot splits it into the empty string user (%n) and
> @mydomain.tld as the domain part (%d).
That's a shame. Doe sit handle other quoted user names? I know it breaks on
Of course you are right!
It should either be "a@b"@mydomain.tld or a."@".b...@mydomain.tld, both
would be valid.
Sadly, it does not change the outcome. Even with a pure
"@"@mydomain.tld, Dovecot splits it into the empty string user (%n) and
@mydomain.tld as the domain part (%d).
Am 01-Mar-18 um 1
On Mar 1, 2018, at 05:07, Philipp Berger wrote:
> mail address like a"@"b...@mydomain.tld, which by RFC should be valid
Shouldn't it be "a@b"@mydoamin.tld ?
--
My main job is trying to come up with new and innovative and effective ways to
reject even more mail. I'm up to about 97% now.
Dear all,
I have a working setup with Postfix + Dovecot, storing users in a MySQL
table.
I ran into problems setting up and using a mail address like
a"@"b...@mydomain.tld, which by RFC should be valid, but leads to problems
in Dovecot. From my debugging, I can see that on the lookup, Dovecot
rep
13 matches
Mail list logo
