similar to: Authenticating to AD with usernames containing dots

Hi All, Is it possible to vampire across dots in usernames? I got over 1000 accounts with dots in them eg. <firstname>.<lastname> The smbldap-tools (version 0.8.2) don't seem to like adding users and groups with dots in them. Any help much appreciated. Darren

Now that I have winbind working, life is good. However, I've hit upon a real kick in the pants. As you can see from my email address, we have a convention here of usernames being firstname.lastname. So, when I go to change the owner ship of a file: $ chown chris.palmer myfile Linux thinks I mean user chris, group palmer, and says "invalid group" (there is no palmer group,

Hi In addition to the inconsistency in make.names(), the text in ?Reserved seems incomplete: "Reserved words outside quotes are always parsed to be references to the objects linked to in the ?Description?, and hence they are not allowed as syntactic names (see make.names). They **are** allowed as non-syntactic names, e.g. inside backtick quotes." `..1` and `...` are allowed for

hi everyone, I have a pesky problem with page caching, sorry if it sounds dummy. Whenever I''m caching an url like /controller/argument.with.dots instead of getting a saved page like /public/controller/arguments.with.dots.html I get /public/controller/arguments.with.dots which makes the webserver confused as to how to send it (it gets a Content-Type of text/plain instead of

Hi, When I try to specify a file I want copied in place, like: configfile { "/etc/init.d/puppet": source => "config/apps/puppet/puppet" } and has a require on that later on: exec { "/usr/sbin/update-rc.d puppet defaults": require => "/etc/init.d/puppet" } puppetd throws an error: err: Could not find type

Hello, all. Since syslinux 3.81 the dots representing the progress of loading kernel and initrd disappeared. Is there a way to get this back? --- Jan Schneider http://www.opsi.org

I need a validates_format_of that disallow dots. In the api there is nothing to find about how validates_format_of exatly works. Is there a better documentation or is there something that can tell me howto disallow dots. -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups

Is it possible to disallow creation of maildir subfolders with dots in their name? Thanks --- Alan Mosca

Hi Samba Team & Users, I recently found "THE" problem with files ending with a white space or a dot. After searching and finding very few pointers (ok, I do not know that much about the smb protocol), I found myself a bit disappointed. (I didn't RTFM however, I beg pardon.). It seems that files ending with whitespaces or dots cannot be correctly shared through a windows

Hi, There is a way to allow usernames with dots like firstname.lastname. On Red hat 7.3 it was possible, but after Fedora 1 it was blocked. How this could be changed? Thanks, -- Cleber P. de Souza

"vychytraly ." <vychytraly at gmail.com> wrote: > I forgot to write that the dots start to appear only inside "Desktop > Environment" (in my case Gnome), not for example in grub/bios. Today > I tried to install ubuntu 16.04 and the green dots appeared there too > (in Unity). Video BIOS isn't the same as the usual video graphics:

"vychytraly ." <vychytraly at gmail.com> wrote: > My only worry is that they would not accept it since I am running > Linux (the laptop came with Windows - and I am not sure if the problem > would be also present on Windows). You can download and install Windows legally: https://www.microsoft.com/en-us/software-download/windows10 . Without a valid code, it will stop

Just a minor cosmetic issue: We use the listescape plugin in order to support "." characters in Maildir++ folder names, and in at least the following case, the escaped representation of the dot character ("\2e") won't be translated back to a "." in messages for the IMAP client: | 1 SELECT non.existent | 1 NO Mailbox doesn't exist: non\2eexistent However,

We are looking to move to Dovecot from a customized Courier implementation.? Our current format is maildir-like. It's basically a filesystem layout...hierarchies are identified by real directories/subdirectories.? Our folder names do have a leading dot and for reasons related to other systems, we do not want to change our format at all.The Layout=FS is very close to working for us.? The?

I've noticed lately that Dovecot seems to be inserting an extra dot in some url's contained in html email. The most consistent example I see is in the newsletters from the Washington Post. For example, if I look at the raw email on the mail server I see text that starts <http://link.washingtonpost.com/click But if I look at what Thunderbird shows it starts

On 10.01.2017 17:38, Marek Grondecki wrote: > Hello Dovecot Community, > > I am using Dovecot 2.2.13-12~deb8u1 (Debian Jessie). > > separator = / > listescape plugin is NOT active > LAYOUT=fs is NOT active > > I would like to prohibit a creation of folders with dot "." in the > names - > so creation of a folder "foo.bar" should NOT be possible.

Hello Dovecot Community, I am using Dovecot 2.2.13-12~deb8u1 (Debian Jessie). separator = / listescape plugin is NOT active LAYOUT=fs is NOT active I would like to prohibit/ban the creation of folders with dot "." in the names - so creation of a folder "foo.bar" should NOT be possible. Currently, when I create "foo.bar" in Outlook 2013 it will be created but

On 11.01.2017 11:35, Steffen Kaiser wrote: > On Wed, 11 Jan 2017, Aki Tuomi wrote: > > On 10.01.2017 17:38, Marek Grondecki wrote: > >> Hello Dovecot Community, > >> > >> I am using Dovecot 2.2.13-12~deb8u1 (Debian Jessie). > >> > >> separator = / > >> listescape plugin is NOT active > >> LAYOUT=fs is NOT active > >>

I have "hide dot files" on, but I have noticed that while files with a single dot are hidden, files with multiple dots are not: ".foo" - hidden "...foo" - not hidden Is this by design? *nix certainly hide such files by default... -- Barry -- http://barrkel.blogspot.com/

Hi all, The `--itemize-changes' has the following notes within the manual: The other letters in the string above are the actual letters that will be output if the associated attribute for the item is being updated or a "." for no change. Three exceptions to this are: (1) a newly created item replaces each letter with a "+",