I've updated the wiki under:
http://wiki2.dovecot.org/LMTP/Exim
to document the discussed problem. Maybe someone can review this.
Regards, Adrian.
Am 19.12.13 22:59 schrieb Timo Sirainen:
> auth_username_format = %u
> protocol lmtp {
> auth_username_format = %Lu
> }
On 18.12.2013, at 16.52, Adrian Zaugg wrote:
> Am 18.12.13 11:33 schrieb Timo Sirainen:
>> I think this would work as well:
>>
>> protocol lmtp {
>> auth_username_format = %Lu
>> }
>
> I tried this with dovecot 2.1.7, but it did not work. It may work on a
> newer dovecot?
Well, this is alread
Am 18.12.13 11:33 schrieb Timo Sirainen:
> I think this would work as well:
>
> protocol lmtp {
> auth_username_format = %Lu
> }
I tried this with dovecot 2.1.7, but it did not work. It may work on a
newer dovecot?
Regards, Adrian.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 18 Dec 2013, Timo Sirainen wrote:
A) Either:
-
Configure dovecot auth to lower case user names, which LMTP inherits, by
setting
auth_username_format = "%Lu"
Co-Effect: authenticating logins with wrongly cased user names do a
On 18.12.2013, at 3.01, Adrian Zaugg wrote:
> A) Either:
> -
> Configure dovecot auth to lower case user names, which LMTP inherits, by
> setting
> auth_username_format = "%Lu"
>
> Co-Effect: authenticating logins with wrongly cased user names do also
> succeed.
I think this would
Hi again
Thanks for helping me on this, especially to Steffen. If you do not need
case sensitivity on user names the use of a redirect router in exim to
lowercase the local part of the address to deliver works well.
If one wants for whatever reasons to have support for user names, that
just diff
On 12/17/2013 8:02 AM, Reindl Harald wrote:
there are enough writing their address uppercase while the server was never
configured
that way, there are enough writing firstnamelastn...@domain.tld and you can
hardly
find a normal person who accepts that writing a message to "y...@domain.tld"
goe
On 2013-12-17 11:02 AM, Reindl Harald wrote:
there are enough writingfirstnamelastn...@domain.tld and you can hardly
find a normal person who accepts that writing a message to"y...@domain.tld"
goes
to a different person than"y...@domain.tld" or bounce in one of the cases
I agree, but as I
Am 17.12.2013 16:55, schrieb Charles Marcus:
> On 2013-12-17 2:39 AM, Andreas Schulze wrote:
>> Am 16.12.2013 15:25 schrieb Charles Marcus:
>>> >auth_username_format = %Lu"
>>> >This really should be the default...
>> I disagree. That solve a symptom, not the problem.
>>
>> As of rfc3522 a local
On 2013-12-17 2:39 AM, Andreas Schulze wrote:
Am 16.12.2013 15:25 schrieb Charles Marcus:
>auth_username_format = %Lu"
>This really should be the default...
I disagree. That solve a symptom, not the problem.
As of rfc3522 a localpart*may* be used case sensitive or not.
I suggest a switch "my
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 17 Dec 2013, Steffen Kaiser wrote:
However, it's maybe best to lowercase the local part in the exim
lmtp-transport and leave dovecot's LMTP in peace.
that's what I wanted to suggest :)
More or less, it is the duty of the MTA, IMHO.
Um,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 17 Dec 2013, Adrian Zaugg wrote:
RFC 2821, Page 13, 1st paragraph:
"The local-part of a mailbox
MUST BE treated as case sensitive. Therefore, SMTP implementations
However, it's maybe best to lowercase the local part in the exim
lmtp-
Am 16.12.2013 15:25 schrieb Charles Marcus:
> auth_username_format = %Lu"
> This really should be the default...
I disagree. That solve a symptom, not the problem.
As of rfc3522 a localpart *may* be used case sensitive or not.
I suggest a switch "my_local_parts_are_casesensitive = yes/no"
or "my_
Hi David
> I believe RFC822 email addresses are case-insensitive, and (in some
RFC 2821, Page 13, 1st paragraph:
"The local-part of a mailbox
MUST BE treated as case sensitive. Therefore, SMTP implementations
MUST take care to preserve the case of mailbox local-parts. Mailbox
domai
Am 16.12.13 22:55 schrieb Charles Marcus:
> On 2013-12-16 4:32 PM, Adrian Zaugg wrote:
>> But the main effect and disadvantage is, that authenticating logins with
>> wrongly cased usernames do also succeed, which I actually do not like to
>> happen.
>
> Trying very hard to understand why this w
On 2013-12-16 4:32 PM, Adrian Zaugg wrote:
The change of adding an L to
auth_username_format = %Ln"
indeed has the side effect, that LMTP delivers wrongly cased addresses.
But the main effect and disadvantage is, that authenticating logins with
wrongly cased usernames do also succeed,
Hi Marcus
The change of adding an L to
auth_username_format = %Ln"
indeed has the side effect, that LMTP delivers wrongly cased addresses.
But the main effect and disadvantage is, that authenticating logins with
wrongly cased usernames do also succeed, which I actually do not like to
hap
On 2013-12-16 2:36 PM, Adrian Zaugg wrote:
How can I tell dovecot to deliver "USER" to the mailbox "user" aswell?
"Username
LDAP lookups are case-insensitive. Unless you somehow normalize the
username, it's possible that a user logging in as "user", "User" and
"uSer" are treated differently
Dear List
Using dovecot 2.1.7 with LMTP and exim4 I want to accept local parts
regardless of their case.
Exim does all virtual alias handling and delivers the messages to
dovecot LMTP addressed to the right mailbox name. This works well except
for addresses which do not need to be resolved
19 matches
Mail list logo
