similar to: case (non-)sensitivity for folder names

hello, some users' login fails since they type upper case for their user ids ,etc ... how can case sensitivity be disabled so they can login with mix of upper and lower case? this is what i tried: in /etc/sssd/sssd.conf i tested this below [domain/default] case_sensitive = false i stopped sssd, deleted all inside /var/sss/db and started sssd but that did not help .... thank you,

On 09/07/2017 08:11 AM, Stephen John Smoogen wrote: > This was always > problematic because DNS hostnames and email addresses in the RFC > standards were case insensitive Not quite.? SMTP is required to treat the "local-part" of the RCPT argument as case-sensitive, and to preserve case when relaying mail.? The destination is allowed to treat addresses according to local

I have also posted this on IRC. I have a linux host running stock RHEL 5.4 Samba 3.0.33-3.15. The host acts both as a Samba server and does a CIFS mount of that same share. The reason for doing this is so that programs running on the Linux host have the same case insensitive view as the Windows clients. I have nocase set in the relevant line in /etc/fstab I have case sensitive = No set in the

Am 07.09.2017 um 20:07 schrieb hw: > Gordon Messmer wrote: >> On 09/07/2017 08:11 AM, Stephen John Smoogen wrote: >>> This was always >>> problematic because DNS hostnames and email addresses in the RFC >>> standards were case insensitive >> >> >> Not quite.? SMTP is required to treat the "local-part" of the RCPT >> argument as

I suspect this is a user agent issue, given that Evolution is flaky in so many areas. When I deliver mail to a subfolder/subbox (e.g. the -m option in the deliver command), and Evolution doesn't know of it, yet, creating it fails, and Evolution still can't get to it. Doing things the other way around (create it in Evolution first, then deliver to it) works fine. Seems to be silliness to

Hi, Yesterday I found big problems concerning my roaming profiles. They seem to work on some computers where they are always used, on some other the did not load properly (i.e. a default profile was loaded instead). After some debugging with userenv.log I found the very strange problem: case sensitivity for ntuser.dat!: [...] IsCentralProfileReachable: Testing <F:\testuser\ntuser.dat>

Is there anything about this analyzer that says "case-sensitive" to you? module Ferret::Analysis class StemmingAnalyzer def token_stream(field, text) StemFilter.new(StandardTokenizer.new(text)) end end end Just wondering how I can force my index to be case-insensitive. Thanks, -Adam -- Posted via http://www.ruby-forum.com/.

On 09/05/2017 06:01 PM, Yves Bellefeuille wrote: > FHDATA wrote: > >> some users' login fails since they type upper >> case for their user ids ,etc ... > Wouldn't it be better to explain to the users that the userid is case > sensitive? You probably don't want a system where Fhdata, FHData and > FHDATA are all possible and are different users. >

https://bugzilla.mindrot.org/show_bug.cgi?id=2685 Bug ID: 2685 Summary: Case sensitive hostname matching Product: Portable OpenSSH Version: 7.4p1 Hardware: Other OS: All Status: NEW Severity: normal Priority: P5 Component: ssh Assignee: unassigned-bugs at mindrot.org

Hello, The uniqueness validator was always case sensitive but that seems wrong because we want uniqueness validations to be insensitive in most of the time. Do not make more sense be insensitive by default and set sensitive only where it should be? We are migrating a lot of big applications from mysql to postgresql here and we are setting case sensitive to false on **all** uniqueness

> I want to have it case-insensitive again, like in Pigeonhole version 0.4.24 i would also plea for making it case-insensitive again! We were hit by this too, and I never saw any mail system in which the local Part ist Case sensitive! Sincerly, Klaus Steinberger -- Rechnerbetriebsgruppe / IT, Fakult?t f?r Physik Klaus Steinberger FAX: +49 89 28914280 Tel: +49 89 28914287 --------------

Hi, I have recently updated from Dovecot 2.2 to 2.3. Since I have noticed that vacation responses from sieve are not working the same anymore. For example, my sieve script looks like this: vacation :days 1 :addresses ["Kippels at hhu.de","julian.kippels at hhu.de"] it used to be that I got a vacation response if I sent a mail to kippels at hhu.de and Kippels at hhu.de. Now

The recipients in the vacation :addresses String list are matched case-sensitive. If the recipient gets a mail with wrong case, the message is discarded with: "discarding vacation response for implicitly delivered message; no known (envelope) recipient address found in message headers" I think the matching should be case-insensitive. Is this a bug or do I miss some option? I'm

> > It is not recommended to rely on local-part case, but it is indeed > case-sensitive. > > And this is to avoid such issues that postfix supports address > cleanup/canonicalisation before forwarding mails to dovecot. > > ---------- > RFC 5321: > > "Local-part = Dot-string / Quoted-string ; MAY be case-sensitive > [?] > While the above definition

Hi All, I am trying to match two character arrays (email lists) using either pmatch(), match() or charmatch() functions. However the function is "missing" some matches due to differences in the cases of some letters between the two arrays. Is there any way to disable case sensitivity or is there an entirely better way to match two character arrays that have identical entries but written

> On 9 Sep 2019, at 16.17, Philipp Faeustlin via dovecot <dovecot at dovecot.org> wrote: > >> It is not recommended to rely on local-part case, but it is indeed >> case-sensitive. >> And this is to avoid such issues that postfix supports address >> cleanup/canonicalisation before forwarding mails to dovecot. >> ---------- >> RFC

Hi, as recently noticed by one of our customers, ssh tends to perform hostname matching in a case sensitive manner since the lowercasing has been delayed till after configuration parsing (by commits d56b44d2dfa093883a5c4e91be3f72d99946b170 and eb6d870a0ea8661299bb2ea8f013d3ace04e2024). Given that hostnames are ususally interpreted in a case insensitive way (and the code actually expects the

Forgive me if this topic has already been discussed on the list. I googled but couldn''t find much. I''d like to search through text for US state abbreviations that are written in capitals. What is the best way to do this? I read somewhere that tokenized fields are stored in the index in lowercase, so I am concerned that I will lose precision. What is the best way to store a

Hi- I've got a weird case sensitivity problem. I've looked through past messages but haven't been able to find a solution. This is an environment using samba to mount shares from a Solaris machine onto a Red Hat machine (originally done because of 16-bit UID limitations in Red Hat 6.x). Now I've upgraded to Red Hat 7.2 (samba 2.2.1a) and the share from the Solaris machine

On Wed, Sep 4, 2019 at 8:25 AM Philipp Faeustlin via dovecot < dovecot at dovecot.org> > Further investigation showed me that it has to be a bug. > > I tested with Dovecot 2.2.36.3 (a7d78f5a2), Pigeonhole version 0.4.24 > (5a7e9e62): > > In this version the additional addresses in vacation :addresses > ["test at example.com"] are handled case-insensitive. >