similar to: Disabled accounts

I''m trying to install SBS 2008 (essentially Windows Server 2008 x64) in an HVM domain. The install starts OK, but when I get to the disk part of the installation it doesn''t detect the disk I have configured. What is the trick for getting the installer to recognise my disk? Here''s my config file: name = "06-sbs2008" memory = 4096 vcpus = 1 builder =

Timo et al; The last bit of functionality that the Dovecot director is missing compared to our existing load balancers is mailserver health monitoring. As I understand it, if a mailserver goes down, Dovecot does not take any action to route connections around the offline node, and will keep trying to proxy clients to it. Since we're hoping to cut over to Directors soon, but don't want to

Hello, I am having an issue with email on all IP-based site/accounts that I set up on CENTOS 6.3 x86_64 standard ? WHM 11.34.1 (build 5). On the server's main IP address domain account/site, both sending and receiving email works just fine, however, on all IP-based accounts/sites I create the email users can send email but not receive it, and dnsstuff.com shows: All connections to

Hi all How can I prevent my Samba PDC from setting the D flag (Disabled) in SambaAcctFlags of all machine accounts created on the fly? smbldap-useradd -w from Idealx which is called by the add machine script directive doesn't do that, so i must be Samba... I use Samba 3.0.7, Debian Sarge, ldapsam Backend (OpenLDAP 2.1.30). Here is my conf: [global] workgroup = UB

Hello, 1. Just having a problem when moving from version 3.0.0 RedHat8 to FDC4 v 3.0.14. I realize there are some attributes new to the schema in 3.0.14 but when a user attempts to login, a "D" is placed in the account flags. How can I get around this without having to run smbpasswd -e? I have many users in my LDAP directory and don't want to enable accounts one at a time. What

I'm in an AD environment, with a samba server a member of the domain, and I'm trying to create a guest-level/read-only share accesssible by *anyone*. The purpose of this share is a network distribution point for .msi package deployment via AD Group Policy. My relevant smb.conf bits are: [global] guest account = nobody map to guest = Bad User [deploy] [msi] comment =

Hello, We have been running Samba 2.2.x/Sun ONE LDAP on a particular machine for about 3 years now and I recently upgraded it to 3.0.14a with ldapsam compatibility (I can mess with the directory later if necessary). Now when users try to connect to the server their accounts get disabled unless I have specifically enabled them using smbpasswd -e username (which is kind of tough because I have to

xen_play_dead calls cpu_bringup() which looks weird, because xen_play_dead() is invoked in the cpu down path, whereas cpu_bringup() (as the name suggests) is useful in the cpu bringup path. Getting rid of xen_play_dead()'s dependency on cpu_bringup() helps in hooking on to the generic SMP booting framework. Also remove the extra call to preempt_enable() added by commit 41bd956 (xen/smp: Fix

xen_play_dead calls cpu_bringup() which looks weird, because xen_play_dead() is invoked in the cpu down path, whereas cpu_bringup() (as the name suggests) is useful in the cpu bringup path. Getting rid of xen_play_dead()'s dependency on cpu_bringup() helps in hooking on to the generic SMP booting framework. Also remove the extra call to preempt_enable() added by commit 41bd956 (xen/smp: Fix

> On 21 Feb 2019, at 12.23, Hajo Locke via dovecot <dovecot at dovecot.org> wrote: > I think mbox+procmail is a classic setup and wide used and good solution for many usecases. Same setup we use many years. > We run ~2 mio mailboxes. our automated systems depends on this setup. creating mailboxes, managing mailboxes, creating automated filterrules, backupsystem to tell something of

Hello! We have userdb=passwd. userdb { driver = passwd #server was entered domain Active Directory override_fields = home=/var/vmail/glu_vrem/%u } If I disable in AD user's account, he can not sign in. But he can and will receive letters, which of course is not correct. How can I exclude disabled accounts from 'userdb'? dovecot -n: # 2.2.27 (c0f36b0): /etc/dovecot/dovecot.conf

On 2019-02-21 22:18, Sami Ketola via dovecot wrote: >> On 21 Feb 2019, at 12.23, Hajo Locke via dovecot <dovecot at dovecot.org> >> wrote: >> I think mbox+procmail is a classic setup and wide used and good >> solution for many usecases. Same setup we use many years. >> We run ~2 mio mailboxes. our automated systems depends on this setup. >> creating

Just a heads up to anyone upgrading to 3.0.2. In our case we used the new Fedora Core updates (the ones from the Fedora team, not the ones on the samba website) to update a samba PDC from 3.0.0. As stated in the release notes for 3.02a (which I read on the samba website): Beginning with Samba 3.0.2, passwords for accounts with a last change time (LCT-XXX in smbpasswd, sambaPwdLastSet attribute

Hi to all I have some *production* pop3/inappropriate server that i would like to move under a proxy Some questions: 1. Keeping the same original hostname on the proxy (in example mail.mydomain.tld) and changing the hostname on the imap server, makes some troubles like MUA redownloading all the messages? Is dovecot (running on the imap server) happy seeing the hostname change? What about

> > On Sat, 3 Jul 2004, Tilo Lutz wrote: > > > None of my acounts in ldap have set sambaPwdLastSet, even those > > > acounts which became disabled. If I have understand you right, > > > samba should not disable account if the attribute sambaPwdLastSet > > > is not defined in ldap? > On Mon, 2004-07-05 at 06:56, Gerald (Jerry) Carter wrote: > > If

> On Feb 24, 2015, at 8:45 AM, Tobias Grosser <tobias at grosser.es> wrote: > > On 09.02.2015 20:12, Chris Bieneman wrote: >> It came up on another thread that our current minimum required CMake version 2.8.8, has some bugs that cause issues when building with MSVC + Ninja, and one potential solution was to raise the minimum required version of CMake. >> >> CMake

Did anyone set up the enviroment in dovecot with post login scripting in which imapsync does sync between two mailservers on users login (on login sync mail from old to new mailserver) is there a alternative or different approach? something like #!/bin/bash /usr/bin/imapsync --syncinternaldates --nosyncacls --authmech1 PLAIN --host1 old.server.com --user1 $USER*master --password1 master

> Andrew, you should understand that you are talking to experts in Linux > here. > No, i was talking to the OP who is seemingly not an expert. Advising those who not competent that they can set up and run their own mailserver is probably negligent. Whipping up Exim and Dovecot for your own private email server is one thing. Setting up for an organisation is a completely different story.

thx, Bob . . . The e-mail problems appears to be a permissions and summary file issue. I gave the users Administrative permissions, and everything worked perfectly. Then I compacted the folders and rebuilt the summary files, took away Administrator permissions, and everything STILL works perfectly. When I posted the question, I wondered if there was some step in joining the mailserver

>I probably shouldn''t have been operating machinery yesterday. >The crash is probably because I committed the e820 memory rearranging >stuff into the wrong branch, but something may have broken us from >tip/master as well. >   J Kernel was already broken at 2/28/09 --- On Sat, 2/28/09, Marc - A. Dahlhaus <mad@wol.de> wrote: From: Marc - A. Dahlhaus